Well, the mailing list just opened, and it's about time to get
re-started with the coding and the web page improvements and all the
good stuff!
Palace and I have been talking about what should be done next. Hence we
ask here in the forum: What should be next?
Of course we know the gController lacks many things, but we are eager to
make it usable for as many applications as possible. We are thinking of
visiting the school's labs this summer and ask what should be required
for them to use it. We know, nevertheless, that the GUI is crap and that
it needs lots of work.
I think we can make this the top-priority stuff to do:
1.- Web page, misc. improvements. Redo the web page, now for real, and
use a good CSS so that it's easy to maintain.
2.- Code, GUI. It's pretty evident that monitors lack information about
what line mean what. We have to think about how to get it alright.
3.- Code, GUI. Well, also on the monitors it looks pretty dumb not
having a time and output scale. I.e. we need numbers on the
monitors!
4.- Code, GUI. On the dialogs, the precision is about 2 decimal places,
which is pretty short for some applications. We might as well make
it free or a 5-digits number.
5.- App, content. A help screen would be reaaally great. In that help
screen we could have the basics of gController, the meaning of the
parameters, some formulas, and stuff like that.
Well, that's sort of what I was thinking about.
So, let's make it rock!
Daniel D=EDaz
yo...@da...
|
