(?:W|w)xPerl::Constructors

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-Constructo
rs-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/tru
nk

Thanks,
Eric
-- 
Consumers want choice, consumers want openness.
--Rob Glaser
---------------------------------------------------
    http://scratchcomputing.c
om
---------------------------------------------------

------------------------------------------------------------
-------------
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
wxperl-userslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxperl-use
rs

On Sun, 18 Mar 2007 18:38:55 -0700
Eric Wilhelm <scratchcomputinggmail.com> wrote:

  Hi,

> Now that it is roughly done, I think all I need is a
name before putting 
> it on CPAN.  Any objections to wxPerl::Constructors?

  Not from me  you might
want to ask for advice on module-authors
before starting a new top-level namespace, though.

> 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.

  This is the only use I can think of, and I find 'position'
better
than the other alternatives you mentioned.

Regards
Mattia


------------------------------------------------------------
-------------
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
wxperl-userslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxperl-use
rs

# from Mattia Barbon
# on Sunday 18 March 2007 10:50 pm:

>Any objections to wxPerl::Constructors?
>
>  Not from me  you might
want to ask for advice on module-authors
>before starting a new top-level namespace, though.

That's sort of a misconception about "top-level"
namespaces.  In the 
past, it's always been "just don't claim it all for
yourself", so 
"wxPerl::Foo" is fine, but "wxPerl.pm"
might be a little audacious (as 
in: "Behold! I have forged the one true wxPerl
thingy!")

Thus, I think I'll go ahead and run with
wxPerl::Constructors rather 
than any more waiting around.

Of course, *you* would be the authority on whether
"wxPerl.pm" was okay 
to use.  If you later decide to bundle-up (or con somebody
else into 
doing it) all of the conveniences into one spot, that might
be it.  At 
that point, you could just require wxPerl::Constructors and
have it all 
available.

Thanks,
Eric
-- 
The opinions expressed in this e-mail were randomly
generated by
the computer and do not necessarily reflect the views of its
owner.
--Management
---------------------------------------------------
    http://scratchcomputing.c
om
---------------------------------------------------

------------------------------------------------------------
-------------
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
wxperl-userslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxperl-use
rs