--- "Mark K. Kim" <[EMAIL PROTECTED]> wrote:
> On Tue, 25 May 2004, Ben Armstrong wrote:
>
> > On Tue, 2004-05-25 at 21:50, Mark K. Kim wrote:
> > > It would be nice, though, if the config program can simply query the Tux
> > > Paint binary to get the list of available languages and charsets, similar
> > > to `tuxpaint --lang help` but with more information, so the hard coding
> > > doesn't need to be done in two different places, in the main program and
> > > the config program. Furthermore, it'd be even cooler if the Tux Paint
> > > could be queried to get the *complete* list of options and its logical
> > > grouping so the config program doesn't need to have *any* hard coded
> > > information about Tux Paint's options, so it doesn't need to be updated
> > > whenever Tux Paint program gets updated with new options.
> > >
> > > What does everyone on the tuxpaint-dev list think? Comments please!
> >
> > Yes.
> >
> > And cooler still would be to establish this as a standard for all
> > Tux4Kids stuff.
>
> Oo~ there's a thought. Better yet, if ALL open-source programs did
> that...
>
> One can dream...
>
> Seriously, I like Ben's idea. Maybe that's something we can think about
> as a next stage (or *next* *next* stage?) after getting the
> tuxpaint-config program working! =)
>
> -Mark
> <snip>
I _REALLY_ like Mark's idea. I wish that I could query tuxpaint to get the
list of options, and draw all the widgets upon loading this structure... but
that can probably wait until a next revision.
I'll put what I have working up in CVS, and see what y'all think of it, and
where to go next. As mentioned before, there is alot that doesn't work, namely
the languages, but the basic machinery is in place. I'll send a note to this
list once I have my changes in CVS...
Thanks for the suggestion, Mark. Actually, I was whimsically dreaming of the
same thing, so tuxpaint-config could become, anybinary-config. If command line
options could be defined by marked-up text (or some other mechanism, I thought
passing a pointer to a struct built by tuxpaint might be cool) so that I could
know:
1. the option name (e.g. fullscreen, alternatesavedir)
2. type of variable (e.g. boolean, string)
3. range of values (e.g. 0 or 1, directory on disk)
4. grouping (e.g. fullscreen goes in the same tab as sound and 800x600, alt
save dir goes with saving/overwrite)
There could be some other nice info that would round it out, but that would be
the basics. If I knew all this at startup, I could build all the widgets at
runtime, and no additional coding would be needed to add more options, because
there would be no hard coding of any option (if I knew the type of variable, I
could build some logic to draw an appropriate widget for the type).
Hard coding will be fine for now, and that is the way that I thought the
prototype would be. I thought we could powwow and stew for awhile on it.
Again, I'll send an email to this list once my changes are in CVS.
--thanks
jan
=====
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
EDUCATION, n. That which discloses to the wise and disguises from the
foolish their lack of understanding.
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
_______________________________________________
Tuxpaint-dev mailing list
[EMAIL PROTECTED]
http://tux4kids.net/mailman/listinfo/tuxpaint-dev
