-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Casio Graph90/FXCG50 and TI Nspire ports #327
Comments
Did u know Github Desktop ? It make easier to make things with Github without having to append multiples commands to make a simple commit |
Pourriez vous fournir le dossier cloné complet avec le dossier .git |
https://www-fourier.univ-grenoble-alpes.fr/~parisse/casio/upsilon.tar.bz2 |
Yeah but that not practical because when upsilon gonna get updated, it can break ur code |
That's precisely the reason why I have a much smaller archive with only the files I have modified. I guess it's fairly easy for someone who has write access to the main repository to untar my changes in his copy of Upsilon and make the update available to all (it should be much easier than writing the additional code I wrote...). |
That why Github exists ! It isn't for having everyone download archives of others and track where things have changed (and no just pushing ur archive isn't a solution in the state of things imo).
doesn't change. |
It does not take 5 minutes to be comfortable with git (just imagine if I said the same about many math tools like linear algebra). You think it's easy because you are used to it (perhaps you started coding with git) and you have probably a dev environment that makes git easy. My dev environment did not change since 30 years: emacs, tar and Unix commandline and I'm productive that way. I tried git for a project, and I resigned because it's already more complicated than using svn and it's much more complicated than doing a combination of a shell command to archive the files I work on and then a scp to my website (type twice (3 times uparrow, 1 time enter)). |
This is a response to your message and theirs arguments
So your saying that typing
is hard ?
Maybe, nope and maybe. I'm still learning it (thanks documentation), if u see my account, you will notice that i use github since 5 month (i don't count when i didn't use the account)
I don't see the link, they aren't the same level of dificulties and it's your job if i'm not mistaken
Maybe that how you code that need to change, not everyone that not like you. Did u know that is called the evolution of the technology ?
"much more complicated" = typing 3 command or making a sh file with the same 3 commands ?
Making another place for another fork ? Again ? Thanks for reading. |
What's important in the end is the features that are implemented, not the process. Processes are subject to changes, git may be replaced by a more popular tool in the future, like cvs, svn, mercurial in the past... If I'm more comfortable using the same tools as 30 years ago and I'm productive, why change? If other people here find my contributions interesting, I'm confident they will integrate my changes with their preferred tool. Otherwise, it's not really a problem, I'll merge changes I made in Upsilon with Khi. I got today an encouraging first test with a call from Upsilon to a light version of giac in an overlay on the Casio: one factorization and an antiderivative called from the Upsilon addin. If there is no memory problem for more complex tasks, then it should be possible to run giac CAS commands from the calculation app. I'll post when I'll know. |
I am changing some part of the code to match the code style before merging. |
What do you mean by changing the code style? |
Also, you should probably wait a few days before synchronizing, maybe I can provide a working prototype of Calculation linked with giac. |
I made a new version of updates available. The main additions are: An improvement that might really be interesting would be to have fake support for the limit command in Poincare in order to have a nice layout in the calc app. I don't plan to do it myself, Numworks code is really too different from my own coding habits. BTW, I don't know how you are doing devel on Upsilon (or other projects). I use gdb inside emacs on linux myself, and I noticed that it crashes with the DEBUG=1 version of the epsilon binary. I found a workaround that might be helpful for others (since debuggers UI are often based on gdb): build in release mode and copy the nlr* object files of Python from the release subdirectory to the debug subdirectory. Build all other object files in debug mode, then gdb works nicely. |
@parisseb Commencez par faire un fork de ce dépôt via l'interface de GitHub. Ensuite voici les commandes à utiliser : git config user.email "[email protected]"
git config user.name "Bernard Parisse"
git clone --orign=upstream https://github.com/UpsilonNumworks/Upsilon.git
cd Upsilon
git remote add parisseb https://github.com/parisseb/Upsilon.git
git checkout -b upsilon-parrisseb
git push -u parisseb upsilon-parisseb
curl -o upsilon_changes.tgz 'https://www-fourier.univ-grenoble-alpes.fr/~parisse/numworks/upsilon_changes.tgz'
tar xvzf upsilon_changes.tgz
rm upsilon_changes.tgz Un peu de nettoyage : # Clean dirty backup files
find . -name '*~' | xargs rm -f
# Clean trailing spaces
sed -i= 's/ *$//' $(git diff --name-only) apps/home/controller.cpp A partir de là vous pouvez faire des commits de changements cohérents : git add $file
git add $file
git add -p $file # Choose interactively which parts of the file you want to take
git commit
git push Et vous pourrez plus facilement maintenir votre branche. Lorsque des nouveautés apparaîtront sur le dépôt Upsilon, il vous suffira de faire : git remote update upstream
git rebase upstream/master
git push -f |
Et si sa vous embête de tapper ces commandes, faites des scripts et modernisez vous ! |
Je me suis déjà expliqué, je ne vais pas revenir là-dessus parce que la meute aboie. |
Je ne fais que mentionner ce qui a été dit sur le discord d'Omega |
Même si je trouve dommage que vous n'utilisiez pas git pour partager votre code, ce qui faciliterait la relecture, l'historique et la communication (encore que j'hésite à partir de GitHub et vers une autre platforme, peut-être self-hostée, car GitHub devient de plus en plus du "bullshit" autour de l'IA), je n'approuve pas le fait de rejeter le travail des autres simplement car il n'est pas sur la même plateforme. |
Alors en fait j'utilisais lcd_blit au début (c'est en effet plus efficace), mais ça empêche os_draw_string et os_sync_screen de fonctionner correctement. Le problème des appels à gui_gc_* est connu dans le monde nspire, et à priori la solution c'est de compiler avec un flag différent pour les nspire cx hw-w (--uses-lcd-blit true pour les CX2), en tout cas c'est ce que je fais pour les versions de khicas pour Nspire (qui existent en fait en 3 versions si on compte la version pour Nspire monochrome). Il faudrait donc que je compile deux versions d'Upsilon une pour chaque modèle, en remplaçant l'upsilon.tns actuel dans la version nspire cx HW-W de khicas. |
I have working ports of Upsilon with persistence (apps and calc history) and support for file exchanges with the host calculator for the Casio Graph 90/FXCG50 and for all TI Nspire (b&w, cx, cx2). They are based on the ports of Kerry Shen for the TI and Heath on the Casio. I believe it's now good enough for my own students usage, I don't plan to make changes in the short term except for bug fixes.
Binaries:
Casio https://www-fourier.univ-grenoble-alpes.fr/~parisse/casio/upsilon.g3a
TI Nspire https://www-fourier.univ-grenoble-alpes.fr/~parisse/ti/upsilonbw.tns
(for Nspire CX and CX2, next link is optimized for flash storage https://www-fourier.univ-grenoble-alpes.fr/~parisse/ti/upsilon.tns)
Source modifications: get this file
https://www-fourier.univ-grenoble-alpes.fr/~parisse/ti/upsilon_changes.tgz
and run from Upsilon source root directory
tar xvfz upsilon_changes.tgz
(I apologize but I never could familiarize enough with git, it's so much easier for me to make tar archive. Maybe someone more familiar with git will include my changes here).
In the long term, I may add a link to Giac for improved CAS support inside Upsilon for the Casio, as an addin overlay.
The text was updated successfully, but these errors were encountered: