On Thu, 2015-06-25 at 11:41 +0000, Yann Thorimbert wrote: > However, I think the following important elements are missing (tell me > if I'm wrong): > > - file browser > - draggable elements That's correct, they are on the to-do list. Though there is documentation for creating custom widgets, so anybody could create a new widget. > - to propose a few default themes (by theme I do not only consider > color and size, but all the graphical aspect) to the users. When > someone wants to use a GUI for its game, this person expect at least > to be able to set a 'modern' theme in no more than one line (for > example, 'human'-like themes (Gnome-like buttons)). For example : > http://www.thorpy.org/examples/submenus.png There is limited theming support (you can replace the code-drawn images, with your own). There will be more comprehensive support in the next major release (when I finally get round to it). In terms of having a default theme, you could subclass the widgets to create your themed widgets. I've not worried about providing themes, as I expect most developers will end up creating a custom theme for their game. http://sambull.org/program/sgc/tutorial.theming.html > Finally, for people who want it, it seems good to provides features > that allow them to stay completely 'outside the event loop'. I mean > something like what is shown here: > http://www.thorpy.org/tutorials/reactions/step1const.html. Is this not just callbacks? http://program.sambull.org/sgc/tutorial.events.html#callbacks > does it fully support semi-transparent widgets ? It uses transparency for the adding/removing transition, I think you can use it normally too, but I don't recall trying it. > Can you 'unblit' widgets - on forums, I realized that many users who just came > to pygame are looking for an 'unblit' function. It is difficult for > them to code it, and I attached particular attention to the fact that > user could want to draw anything of its own on GUI's elements, and so > writing an efficient 'unblit' handler that take into account the fact > that any widget can be transparent is not trivial. I'm not really sure what you mean here, what is an example use case? Thanks for the feedback, it's interesting to see what users want, and how I might be able to improve the library in future.
Attachment:
signature.asc
Description: This is a digitally signed message part