From: Bob H. <cat...@ya...> - 2007-03-19 09:47:15
|
Eriam, I think that my former quote to Larry Wall answers your question deeply. The core problem is how to get the job done quickly, that is, how to have intellectually manageable code that we can write by hand and maintain by hand when answering to the clients needs, and avoid the language/modules to get in the way. Writing the wx-gui directly in PERL clutters the source to such a degree that I am no longer sure it does what I want (will it crash becaue of the gui?, etc.); it also gets in the way, as I have to bother about the gui rather than the actual job. If using XRC turns out to be slow, I will live with it, but I have gained a clear cut between the gui and the application, apart from the interface. If using XRC files is set as default policy (solving a load of problems at once), then speed becomes part of the procedures, and wxPerl would need to speed up its internal routines so that XRC (or compiled versions of it) have performance up to par. The additional benefit is, that a program like wxGlade could do all the hard work for us, and the work itself would be language independent, as wxGlade can generate the XRC files by default and use your specified language for the interface. It would be the ideal solution to a hard problem. I am interested in hearing what people think about this, and also about the actual XRC performance... Bob ____________________________________________________________________________________ Bored stiff? Loosen up... Download and play hundreds of games for free on Yahoo! Games. http://games.yahoo.com/games/front |