From: Eric W. <scr...@gm...> - 2007-03-19 01:39:01
|
Hi all, Now that it is roughly done, I think all I need is a name before putting it on CPAN. Any objections to wxPerl::Constructors? Documentation: http://scratchcomputing.com/tmp/WxPerl-Constructors.html http://scratchcomputing.com/tmp/WxPerl-Constructors-doc.html http://scratchcomputing.com/tmp/WxPerl-Constructors-argmap.html The main change in WP::C::doc.pod being to change 'pos' to 'position' (which avoids the aesthetic issue of using a perl builtin which often highlights as a function despite the fact that perl allows it to be unquoted via => hash-quoting rules.) I thought about 'posi', which is good in that it has the same number of characters as 'size'. Also, 'poz' might work since it is pronounced the same. Alternatively 'place' keeps us in the same neighborhood as 'style' in terms of key length. In the end, I went with the longhand under the assumption that you almost never need to specify a value for position. Is that about right? I'm thinking it *might* get used in dialogs and frames if the window manager can't do its job for some reason. For me, it has always been a piece of padding that I have to mention before I can specify a style. If someone has a frequent use case, I can shorten it. Anyway... running code: svn co http://scratchcomputing.com/svn/WxPerl-Constructors/trunk Thanks, Eric -- Consumers want choice, consumers want openness. --Rob Glaser --------------------------------------------------- http://scratchcomputing.com --------------------------------------------------- |