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

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

I spent the whole day reading and experimenting with
wxPerl. I think I have a grasp of the most elementary
parts, but got stuck when adding the menu bar and its
items. I went back to wxGlade, only to find that the
code it generates is both old and bugged. Further, a
tutorial makes it clear that wxGlade overwrites the
code, so we cannot change it by hand. Thus, if we must
use a GUI builder (because writing by hand from
scratch is just insane), and cannot change the code by
hand (because the builder overwrites it), why
bothering at all about having perl code for the main
GUI inside our scripts? Why bothering with
wxPerl/wxPython etc in the first pace, if we could do
otherwise? The idea is this: wxGlade generates the XML
description of the GUI, then we "use" an interface to
this description, that is, we use a module that reads
the XML file and generates a list of all the variables
we can use to fill the GUI with data and events. The
script, as a result, would be smaller than using tk.
Do I make sense?




 
____________________________________________________________________________________
Need Mail bonding?
Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.
http://answers.yahoo.com/dir/?link=list&sid=396546091