On Tue, Oct 05, 2004 at 11:51:49AM +0100, Owain wrote: > 2. Up until now I have been doing form validation mainly in client > Javascript to pick mandatory fields etc. However Validate > RM/Data::Form::Validator looks like a way forward since "you can't trust the > client".
> I can't seem to find any documentation on the Plugin::architecture > and how it works. Specifically I want to clarify the role of Exporter since > I never really understood it from my non-OO perl modules other than it let > you break the scope rules (I came from Pascal). And I usually exported too > much. Have you checked the POD in the latest release? There are several paragraphs of docs in there. As for using Exporter, Mark's suggestion to require explicitly importing functions helps to create better tracability so perhaps you won't feel quite so uncomfortable with using it in this format; check the Exporter pod for details. > 3. Has anyone developed a generic class based on Class::DBI that supports > "codes tables". Not me but your example looks interesting. I often do this sort of thing in a config file. > My aim would be to be able to access the "decode" directly from the > HTML::Template by declaring a relationship solely in the Class::DBI. E.g. > error decode message in from ValidateRM and labels for fields in the > original forms themselves. I've only used HTML::Template a little but do not think that it supports objects. I often pass in a CDBI object(s) to my templates[1] which can then be used as I please. HTH, William [1] http://search.cpan.org/~jhiver/Petal/ -- Knowmad Services Inc. http://www.knowmad.com --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
