Re: [wxperl-users] porting a perl/tk application to perl/wx

[Bob H. <cat...@ya...>]

I am forwarding a message that I sent to the wxGlade
community this morning.

Bob



-----

Date:	 Mon, 19 Mar 2007 02:15:54 -0700 (PDT)
From:	"Bob Hunter" <cat...@ya...>  Add to
Address BookAdd to Address Book  Add Mobile Alert
Subject:	wxGlade->XRC+PERL
To:	wxg...@li...

Hello,

When compiling for PERL (but also for PYTHON, or any
other language) wxGlade could adopt a different
approach than it currently does. At this time, wxGlade
generates the wx code in the language; if you specify
c++, it generates the wx code in c++; if you specify
perl, it generates  the wx code in perl; and so forth.
This requires a lot of work to the developers of
wxGlade, and support for specific languages might fall
behind, as it is the case for perl. 

I propose a different approach, to solve the above
problems, and free developers time, who could devote
efforts to improve wxGlade in other ways. The proposal
is this: when compiling, wxGlade generates XRC code by
default. Compiling for a specific language then
reduces to printing a standard template in the
specific language (phthon, perl, etc), call the XRC
files with specific modules (wxPython, wxPerl, etc.),
and finish by loading the widgets from the XRC files
(an automatically generated list of all the handles).

This would allow wxGlade developers to simplify
wxGlade's own code (cut out most of it), improve the
overall stability of wxGlade, and generate code that
is  intellectually manageable (the programmer will not
have to go mad with gui code, but just "use" the
widgets).

What do you think? I think it is a great idea!

Bob Hunter



 
____________________________________________________________________________________
Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.
http://videogames.yahoo.com/platform?platform=120121