From: Daniell F. <win...@gm...> - 2007-03-06 16:55:10
|
While I am not a detractor of new projects, I think a project such as this should be an different beast than wxPerl. It should be a compatibility layer of sorts for wxPerl and Perk/tk. I for one like the way wxPerl currently works (i.e. just like the C++ version and python version). I loath the thought of having to change all of my code to some new API because we wanted to dumb it down a bit (and I mean no disrespect by that). I'm all for having a way to create quick and dirty GUI's using wxPerl, but that isn't always the appropriate way to do things. wxPerl as it stands (and as others have already said) is a very complete GUI API that has a lot of power. Yes there is some complexity to using it, but once you learn to code using it, it isn't any worse than any other API. Just my 2 cents worth. Thanks, Dan Freed On Mar 6, 2007, at 10:43 AM, Bob Hunter wrote: > Mattia, your message is already an important step > forward. At least you acknowledge that wxPerl can be > improved from that point of view, and are open to > change/improvement. Given that time is limited for > everyone, the best approach to proceed is to post a > general "call for contributions", and leverage from > the open source community. Design ideas are valuable > as much as, if not more than, specific code, because > they can save a lot of coding. > > To make the first two contributions, these are two > ideas. > > The first is to talk to the developers of tkPerl and > ask them whether they want to merge with wxPerl. It > might sound odd at first, to both the tkPerl and > wxPerl communities, but read on. The first aim would > be to *design* the same API for both projects. This > API has to be consistent with PERL's philosophy, > profit from the existent API of tkPerl and allow for > wxPerl's enhanced features. When people have debated > at length on design, and everybody is happy about the > final resolution, then it is coding time for both > communities. The tkPerl community would have (a) an > improved API, (b) a means to port applications from tk > to wx with minimal effort, and (b) stay with a tk > interface if they like (wx can interface to gtk, > cocoa, etc., and thus also with tk). The wxPerl > community would finally have an API that is consistent > with PERL's philosophy. > > The second idea is a tiny little one, and arises from > a simple problem that I encountered today on > tk/Perl.---I moved the mouse around the application, > and noted that different parts of the GUI highlight > differently and with different colors. I also noted > that different text areas have different background > colors. I spent two hours to fix a number of them, in > detail, coding in. An idea that saved time was the > following: > > 1. define a general color for the background and the > highlight, at the beginning of the code, say: > > my $bg_text = "#efefef"; > my $bg_texth = "#adbcd6"; > > 2. state the following in the option area of relevant > widgets: > > -background => $bg_text, > -highlightcolor => $bg_texth, > -highlightbackground => $bg_text, > > The result is that those widgets now have consistent > look and feel. The problem is, that I still have to > specify this detail for each relevant widget, coding > by hand. And I am lucky I do not have to do that with > an Interface Builder, clicking around hundreds of > time on various panels. Now, the idea is to specify > this consistent behaviour only one time. The question > is where? I propose to gather all such customizations > in a separate "policy" file, so that, if you have k > entries you just write the policy once. > > Regards, > Bob > > > > > ______________________________________________________________________ > ______________ > TV dinner still cooling? > Check out "Tonight's Picks" on Yahoo! TV. > http://tv.yahoo.com/ > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > wxperl-users mailing list > wxp...@li... > https://lists.sourceforge.net/lists/listinfo/wxperl-users Daniell Freed win...@gm... Bereshit bara Elohim et hashamayim ve'et ha'arets... |