On Wed, May 26, 2004 at 03:00:23PM -0700, Jan W wrote: > 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.
Yeah, once we get something out the door, we can discuss what kind of format makes sense to draw the config interface 'on-the-fly.' Then "t4k-config" (or whatever it gets called) can just do a query to Tux Paint, like: tuxpaint --guiconfig which'll dump out the data to stdout. Heck, we can add config option strings to Tux Paint so they get translated right there, so "t4k-config" could even do: tuxpaint --guiconfig --lang spanish and get the Spanish strings of what the checkboxes/etc. should say. (For example) > I'll put what I have working up in CVS, and see what y'all think of it, and > where to go next. Great, thanks! :^) Unless my Knoppix 4 Kids discs have FLTK and SDL devel libraries (doubtful), I probably won't be able to do any Tux Paint Config or Tux Paint work until the weekend, again... > 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... Great, thanks. (diffs of what you commit also get posted to the 'tuxpaint-commits' mailing list, which a bunch of us subscribe to...) <snip> > 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) Definitely thinking XML might be the way to go. Getting interactions to work well may be difficult, but for Tux Paint, the interactions are simple, if there even are any. (Like, it kinda makes sense to grey out the other printing options if "noprint" is enabled. Though, on the other hand, "noprint" can be undone via a command-line option, so it'd be nice to set the other printing options "just in case"... Make sense?) <snip> > 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. I wonder if anyone's working on a standard for this... KDE? Gnome? Freedesktop.org? If not, FD.o would be a good place to talk about this and put it together, once we begin! (Kinda odd that I haven't seen anything similar before...? It's kinda like "flkt-config" and "sdl-config" are for compiling...) -bill! _______________________________________________ Tuxpaint-dev mailing list [EMAIL PROTECTED] http://tux4kids.net/mailman/listinfo/tuxpaint-dev
