[Dancer-users] Dancer::Forms

[sawyer x]

Linden, this seems like awesome work, way to go!

However, along with Damien, I should note that we appreciate not putting
modules under Dancer that aren't part of Dancer itself. We recommend the
Dancer::Plugin::* namespace.

Also, we prefer people wouldn't use generic names. By calling it "Forms" it
gives an official sound and people might expect this to be the official and
only Dancer forms library. There are definitely more ways (though perhaps
not necessarily as good) to have forms - FormFu, for instance. For example,
if you call yours Dancer::Plugin::Djangoish or
Dancer::Plugin::Forms::Django (just an example), someone else could provide
a FormFu forms plugin under Dancer::Plugin::FormFu or
Dancer::Plugin::Forms::FormFu.

At least consider renaming to the ::Plugin namespace.

And thanks for this great contribution. I'll be sure to check the code and
perhaps even use it myself.
Good work! :)

S.

On Wed, Jan 11, 2012 at 4:40 PM, damien krotkine <dkrotkine at gmail.com>wrote:

> Hi,
>
> Thanks for the work !
>
> I'm a bit worried about the fact that it lies under the Dancer
> namespace, but doesn't depend on Dancer really.
> Could this be rename to a different module name, and then a new Dancer
> Plugin be written, that would use it ?
>
> dams
>
>
> On 11 January 2012 15:03, T. Linden <tom at linden.at> wrote:
> > Hello Everyone,
> >
> > first of all I'd like to thank the developers of Dancer so much. It's a
> > great thing and I love it more from day to day!
> >
> > While I'm new to Dancer, I'm not new to perl, but were using Django as
> > app server for a long time now. Some day I thaught: this has to be done
> > in perl, dammit - and I discovered Dancer.
> >
> > However, I missed one thing, that is the forms module of Django. With
> > forms you can validate user input, and generate forms. Since I didn't
> > find anything near such a thing, I implemented it myself: Dancer::Forms.
> >
> > It does the very same as the Django forms system does: you define some
> > fields, how they shall be validated, feed your template with it, and
> > that's it.
> >
> > Beside user input validation I also added a CSRF protection feature to
> > the module. This one could be better put into a Dancer plugin perhaps,
> > I'm unsure...
> >
> > The name maybe misleading, since Dancer::Forms does in fact not depend
> > on Dancer. So it could be used in other environments as well. I hope it
> > is ok, to put it into the Dancer:: namespace anyway.
> >
> > There's still lots of things to do, like more unit tests, better
> > debugging possibilities and - maybe - some kind of "model forms" sub
> > module, which generates the forms from a dbic definition...
> >
> >
> > Take a look: https://metacpan.org/module/Dancer::Forms
> >
> >
> >
> > best regards,
> > Tom
> >
> > --
> > Please note that according to the German law on data retention,
> > information on every electronic information exchange with me is
> > retained for a period of six months.
> > _______________________________________________
> > Dancer-users mailing list
> > Dancer-users at perldancer.org
> > http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
> _______________________________________________
> Dancer-users mailing list
> Dancer-users at perldancer.org
> http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.backup-manager.org/pipermail/dancer-users/attachments/20120111/a8cd311b/attachment.htm>