
Kalcoolus
Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net
This is a KDE frontend for GNU bc calculator. It need testing.
This is version 0.2 alfa 1
Bug fixed.
Added accelerator buttons
If you get strange compiler errors, try this:
make -f Makefile.cvs; ./configure; make
this should fix problems
See ChangeLog and manuals
gohanz
15 years ago
http://www.slacky.it/
http://www.slacky.it/index.php?option=com_remository&Itemid=1&func=fileinfo&filecatid=750&parent=category
Report
anmaster
15 years ago
Report
3milian0
15 years ago
well I don't know if there are ebuilds for Gentoo, actually, for what I know, there are rpm packages released by some distro vendors. I released only the tar.bz2 format for space saving and because I use slackware ;-)
Report
fungs
15 years ago
Report
Quique
15 years ago
http://www.pycs.net/lateral/weblog/2005/03/08.html
Kalcoolus está todavÃa en una fase muy temprana de desarrollo, asà que si Emiliano lo desea, podrÃa cambiar su enfoque.
Report
3milian0
15 years ago
Report
Brandybuck
15 years ago
I while ago he wrote a blog about usability, and used kcalc as a demonstration. You can find it here: http://www.pycs.net/lateral/stories/33.html. With kalcoolus you seem to be duplicating the mistakes of kcalc, and he mentioned it in yesterday's blog here: http://www.pycs.net/lateral/weblog/2005/03/08.html#P283.
In a nutshell, his main concern is that the command line interface (CLI) to bc was sufficient, and that the GUI frontend of kalcoolus has considerably reduced usability. You need to read his first blog to understand why. He is not arguing that kalcoolus should never have been done, but rather that the approach it is taking is the wrong one.
Report
sodamnmad
15 years ago
Such a feature would also be useful for people who are copying some expression from some other source. Most (probably all) other calculators force you to retype it-- scratch that, re-click it. Your application _is_ a little better than most because it lets you see the full expression whereas other applications mimic the single 10 digit display for both answer and input.
Anyway, a text input field would be cool because then if the user messed up, there could be an "up/down" history like on the terminal that would allow him/her to edit the mistake.
I don't see how it will be hard to implement since with the current mouse input its still possible to have invalid input: try using the custom function with multiple parameters, its pretty hard to use. With a text input, I could have typed "a + test(1, 3, 4)" and gotten my answer in about 3 seconds. Mouse input took me 45 seconds, and never figured out how to set the second/third parameters.
But other than that, this application seems very good. I voted "good" for it.
Report
3milian0
15 years ago
you pointed out problems, that I'm trying to solve. I know that moving through the line of the editors is a bit tricky, so I'm thinking to replace input/output editors with a sort of mini electronic sheet of two colums and N rows. This way should simplify both implementation and usability. User will see each line clearly separated and keyboard editing should be more simple. For now I added two DCOP methods to permit user to send data to kalcoolus/ and receive data from it, it could be usefull for example, if you want to copy data to/from a text file opened with kate.
However stay tuned and thank for the hints :-) if you find bugs please let me know.
Report
3milian0
15 years ago
Report
Brandybuck
15 years ago
Report
3milian0
15 years ago
Report