Differences between revisions 2 and 3
Revision 2 as of 2006-04-24 01:11:37
Size: 718
Editor: bluepill
Comment:
Revision 3 as of 2006-04-24 01:23:20
Size: 1057
Editor: bluepill
Comment: comments
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
----
Line 18: Line 18:
----
== Some reasons why this proposal isn't needed: ==
Line 19: Line 21:
 * PGU is good enough for most people who want a Pygame GUI.
 * Most games / multimedia applications use custom GUI code.
 * IMO, the only part of a GUI toolkit which can be successfully genericised for these sorts of applications is the event loop and dispatch mechanism.

A Pygame GUI Toolkit.

On second thoughts, this sort of project probably isn't needed, for many different reasons. - SimonWittber


Build a minimal object oriented GUI toolkit, aimed at use with touchscreens, which uses pygame for display. It should use something like a command dispatch pattern, and make sure to take advantage of the late binding abilities of python.

The minimum widgets needed are:

  • Labels
  • Tool Tips
  • Text Entry (with possible optional virtual keyboard)
  • Buttons
  • Heirarchial Pie Menu System
  • Spacer
  • Dialogs with Customisable buttons

It should also provide customisable layout managers for widget layout. Grid, Horizontal and Vertical Row etc.


Some reasons why this proposal isn't needed:

  • PGU is good enough for most people who want a Pygame GUI.
  • Most games / multimedia applications use custom GUI code.
  • IMO, the only part of a GUI toolkit which can be successfully genericised for these sorts of applications is the event loop and dispatch mechanism.

SummerOfCode/PygameGui (last edited 2008-11-15 14:00:04 by localhost)

Unable to edit the page? See the FrontPage for instructions.