> Hi Mattia,
> I've started coding a generic and a text validator for wxPerl, as I want to
> use them in my project.
>
> Would you (or others) be interested in these being contributed to the wxPerl
> community? If so, how do we want to manage it - as part of wxPerl, or just
> a contribution to CPAN?
Well, the rule I will try to follow is that wxPerl should
only contain things that are in wxWindows; since wxValidators are in
wxWindows I think your creatins belong to wxPerl
> With regard to package naming, I'm intending to name them as follows:
> Wx::Perl::GenericValidator
> Wx::Perl::TextValidator
> etc...
Yes, that's what we afreed last time that was discussed
> I'm intending the TextValidator validation to be controlled mainly by a
> regexp to validate against, to make it flexible, but also to match the
> features of the native wxValidator, if possible (though a lot of these can
> be achieved by a regexp, I think).
> Other suggestions/opinions regarding naming conventions are welcome -
> nothing's cast in stone yet!
Yes, one ( *suggestion* ): do not implement Wx::Perl::GenericValidator,
as we discussed last time, there is ( almost ) no hope to implement
it in Perl; and besides, the interface is quite broken IMHO;
I *think* it is better to have something different from Wx::GV,
either
Wx::Perl::IntegerV, Wx::Perl::StringV, Wx::Perl::RealV, etc
or
Wx::Perl::ListBoxV, Wx::Perl::ComboBoxV, Wx::Perl::RadioBoxV, etc
Of course these are suggestions, not necessarily right nor necessarily
useful, just yjrowing some ideas...
Regards
Mattia
|
