[Dancer-users] Simple Dancer OO approach.

damien krotkine dkrotkine at gmail.com
Thu Jan 26 12:31:50 CET 2012


I think the proposed code is a good idea. It's a simple and fresh
alternative to MVC but keeping some OO concept.

I see it more as a proof of concept though, until it gets more fleshed out.

For me it's not an issue to continue developing new ideas on dancer 1.
Once dancer 2 is out, they can be migrated.

What's is proposed here is different from the OO of dancer 2. Granted,
it'll be easier and shorter to write on top of dancer 2, but it won't
be obsoleted by dancer 2

Only my 2 cents :)

Le 26 janv. 2012 à 10:13, "Роман Галеев" <ip at ncom-ufa.ru> a écrit :

> На Thu, 26 Jan 2012 10:54:37 +0200
> sawyer x <xsawyerx at gmail.com> записано:
>> This seems like a well thought-out idea, but unfortunately I think it
>> shouldn't be done.
>> Dancer 2 is already completely OO and so is the DSL. The idea now is to
>> simply keep Dancer 1 maintained as far as to let Dancer 2 be developed
>> continually. Once Dancer 2 is ready, we'll start moving to it. It will
>> already contain all the things people suggest to put into Dancer 1, being
>> done more cleanly and correctly.
> Moving to dancer 2 could be a big issue. And afaik dancer 2 simply is not ready.
> Meanwhile people may want to write modules.
> This approach is simple and can be used with an existing code base.
> --
> С уважением,
>    Роман Галеев,
>    +7 347 2-900-145
>    www.ncom-ufa.ru
> _______________________________________________
> Dancer-users mailing list
> Dancer-users at perldancer.org
> http://www.backup-manager.org/cgi-bin/listinfo/dancer-users

More information about the Dancer-users mailing list