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

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

Hi,

I am cross-posting from wxGlade. Perhaps you might
re-consider your position.

------------

I propose/d to adopt XRC as standard description for
the wx gui, write a fast XRC interpreter in c++, purge
the original wxGlade, wxPython, wxPerl, etc, of all
their code for running the gui, and bridge the
resulting gap at the interface by calling the fast XRC
interpreter. It is a hell of a project, it requires
careful consideration, but would solve many problems,
including the above one with wxPython.

>From the standpoint of wxGlade, if XRC is used as the
only wx gui description, then there is no need to
generate language specific code to build and run the
interface. The task of wxGlade would reduce to
generate the XML/XRC code and the language-specfic
interface between a programmer's own code and the
gui's XRC interpreter. wxGlade would still generate
two files: the XRC file and the main file, where the
main file is a template for the programmer, which now
includes a call to the XRC interpreter, via an
enhanced version of wxPython, etc, and the pointer to
a data structure storing all the event handles and
widget variables. The programmer's template will have
very little code in it.

This is an idea. I think it is a good idea, and I
would like to invite you to think about it over and
over again, as you might not see its worth at first
glance. Or, may be, you see that the idea is rubbish
and just want to leave things as they are, that is,
struggle and complaint with the programmers, and be
happy for sharing problems, rather than solutions.

-----



Bob


 
____________________________________________________________________________________
We won't tell. Get more on shows you hate to love 
(and love to hate): Yahoo! TV's Guilty Pleasures list.
http://tv.yahoo.com/collections/265