NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
The GUI Loft
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
I pour the blue liquid on the red liquid. If it doesn't blow up on my
face, I proceed to turn up the flame under the blue liquid, and so on.
I have very little idea of what I am really doing, I just like the
pretty colors :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
That's the way to do it (Score:2)
I've never wanted to use a GUI generator because I didn't want to use pregenerated code. It's like hand-optimizing the assembler that comes out of your compiler. The author of Loft apparently thinks like I do.
Now, my ideal would be your GUI builder creates some kind of text file that specifies the GUI, and you have a preprocessor (read compiler) that turns that text file into code. So then you add a suffix rule to your makefile, and voila! And it's a text file, so it'll stand up (sort of) in version c
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Re:That's the way to do it (Score:1)
Some large data structures didn't go well with Data::Dumper, so I switched to Storable with some hesitation (Data::Denter was an option too, but it's too slow and needs an Inline implementation). I've found that the problem isn't there when using the Perl-only implementation of Data::Dumper, so the Data::Dumper support will return at some point.
Lately there has been requests to be able to dump to XML, and I plan on doing that if I can only find a decent XML dumper module. Data::DumpXML might be the way to go judging from this node: http://www.perlmonks.org/index.pl?node_id=135347
/J
Reply to This
Parent