Im still putting some thought into gui and would share a couple things. I could actually probably sit down and write an exhaustive list of stuff, and someone probably ought to.
* I think a criterion for success is that people use it. Goals should be oriented with this in mind, vs achieving a file dialog. * Layout can be complicated, and it can also be done easy/lame. Right now theres a lot of code in pyglet and in trunk that deal with all sorts of layout issues. Building on these is probably a good idea. Having options for different types of layouts, each building on each other, would probably be ideal. * code implementation for a dialog or modal can be modelled after pyglet modules. A little abstract thought should make the way clear (err maybe fuzzy). * This needs a competent dictator open to collaboration, passionate about writing the system, and none-the-less a little stubborn. I dont know about all of this, but Tristam's work certainly seems competent ;) and he's incorporating alot of the discussion's here into his work. I imagine his work is to early in development for him to really incorporate other's code verbatim as there's alot of design challenges still be tackled. * Ive already said this before, but theme support shouldn't be an integral part of using the gui system. I should be able to create a select box and specify a particular image for it, or i should be able to specify a specific image for all select boxes >>> Select.image = 'select.png' >>> select = Select() # or i should be able to load a bitmap that contains the gui elements for optimized rendering. These aren't even my main thoughts on a gui, but im sure theres probably somewhere better to look then my thoughts about gui development. This is the internet after all. On Jun 6, 12:51 pm, Nicolas Rougier <[email protected]> wrote: > Hi all, > > In an effort to write some kind of specifications for a future pyglet > GUI, I would like to gather user ideas/wishes/comments on what could > be a pyglet GUI. > > The main idea would be to follow the pyglet spirit and to have a GUI > that is both simple to use and reasonably fast. One criterion of > success would be the ability to write a file dialog using the > specifications. Another example could be the ease of having a single > button linked to some user-defined handler. > > Apart from the list of mandatory widgets (like buttons & labels), > there is also a need to know how widgets are to be layout together > (see recent threads to get some ideas), how do we render a widget, > what is the code to write to have minimum running dialog, is there a > native theme support, can the description of an interface be loaded > from a file or string, etc. > > Nicolas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
