[wxPython-users] Google Summer Of Code 2008

[Jorgen Bodde]

I do not agree. What I meant was that everything that makes wxPython
really wxPython should be in one spot in a well documented, and
functioning framework. When people encounter e.g. wx.FileConfig they
can see in that application how it should be used in a real live
example. Also other aspects of an application, how to set up a menu,
about box, wx.AUI, XRC to do layout, etc. The benefit of having a
skeleton app is that beginners do not have to find scraps and read
much documentation to compose an application and fall in the same
pitfalls again as everyone else did. If many aspects are covered which
you find in a normal app, the time to have a working application gets
smaller, acceptance grows and less errors are made with things that
are trivial to a developer that uses wxPython for a longer time. And
for the seasoned developers, a good skeleton app written Pythonically
and the way wxPython was meant to be used, is a good jump-start
because nobody would like to do redundant things when it comes to
writing a new app. In the begin phase, a lot of stuff has to be
redone.

If it will become a GSOC2008 project or not, it is a nice idea, right ? ;-)

With regards,
- Jorgen

On Wed, Feb 27, 2008 at 7:53 PM, Mike Driscoll
<mdriscoll at co.marshall.ia.us> wrote:
> Hi,
>
>
>  > -----Original Message-----
>  > From: Jorgen Bodde [mailto:jorgen.maillist at gmail.com]
>  > Sent: Wednesday, February 27, 2008 5:25 AM
>  > To: wxPython-users at lists.wxwidgets.org
>  > Subject: Re: [wxPython-users] Google Summer Of Code 2008
>  >
>  > Maybe a nice idea for wxPython Google Summer Of Code would be
>  > to develop a show case application that contains the following items:
>  >
>  > - Configuration management the way it should be done
>  > - A splash screen at the beginning of the demo app
>  > - A web update / notify mechanism for new updates
>  > - Standardized layout with wx.AUI and menu, toolbar, statusbar
>  > - Standardized file Open, Close, Save, Save As, Save All,
>  > Close (like on an editor)
>  > - Signals for implementing MVC, e.g. not put your main
>  > functionality inside various wxPython files but drive the
>  > wxPython GUI from your functional design with signals (wx.lib.pubsub)
>  > - Standard about box
>  > - Database functionality, wizard to create a new one, select
>  > old one etc
>  > - Etc.
>  >
>
>  Between the wxPython demo and Editra, most of these are covered. You can
>  get the database know how from Dabo and learn about config management by
>  reading the docs for ConfigObj or ConfigParser. That just leaves the
>  signals and the web update with the latter having several solutions that
>  have been posted to the list over the last few months when other
>  developers have asked about it.
>
>
>  Mike
>
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: wxPython-users-unsubscribe at lists.wxwidgets.org
>  For additional commands, e-mail: wxPython-users-help at lists.wxwidgets.org
>
>