Hi Todd,
Todd W wrote:
> To achieve device independence (multiple views) the client must
> specify what format it would like. For example:
There's a bit about this in the Request Cookbook at
http://search.cpan.org/~simonflk/Maypole-2.06/lib/Maypole/Manual/Request.pod#Maypole_for_mobile_devices
It's also worth looking at iBuySpy
http://search.cpan.org/~simonflk/Maypole-2.06/lib/Maypole/Manual/BuySpy.pod
for more information about ways to rewrite URLs in Maypole. I haven't
used any of these techniques so I can't speak for them.
> So, to the corner I'm now coded in: A standard way to authorize,
see below
> accept, validate, and store data from the user.
Yes in Maypole via CDBI and plugins.
> How well could my methodology above integrate with maypole? Could I
> implement it via subclasses, or would I have to modify maypole
> source?
You can subclass most things but it may help to agree some changes to
Maypole to make it easier. I expect other people share at least some of
these needs.
> Can I use existing Class::DBI classes? I already have many Class::DBI
> classes set up. How would I go about, for example, making them work
> with the default templates?
Look at Maypole::Model::CDBI::Plain.
> Looking at http://maypole.perl.org/?About,
Best to look at the docs on CPAN as in the links I gave above, because
they match the current release.
> My next goal after the input mechanism: role based authorization.
This has been mentioned a couple of times. I've just written a module
for it. I'll post an initial version for discussion tomorrow.
Cheers, Dave
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.10 - Release Date: 10/01/05_______________________________________________ maypole mailing list maypole at lists.netthink.co.uk http://lists.netthink.co.uk/listinfo/maypole
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:57 GMT