[dancer-users] Dancer1 plugins and Dancer2 plugins
sukria at gmail.com
Mon Oct 7 14:32:50 BST 2013
I think I could have ideas/background to share as well, let's do that by
email shall we?
The base of Dancer2::Plugin comes from a first brainstorming we had Matt
and I in the early stage of D2, when I was working on porting D1 into a
Moo-ish structure. The main idea is that a plugin is actually an extension
to the DSL of the app.
The idea itself is quite good, I think (credits to mst) but it's true the
reality of the implementation is quite complex and not optimal. It's true
we could/should find a way to implement that in a better way.
I'd be happy to join the thinking process.
2013/10/7 sawyer x <xsawyerx at gmail.com>
> Plugins are a sore point. They've been handled multiple times by gifted
> individuals but it still seems like a problematic issue.
> I think the shared knowledge of David Precious, Alberto Simoes and Damien
> Could you guys chime in for a bit?
> Maybe we could brainstorm on the current problems with the plugins system
> and how to fix them?
> On Mon, Sep 16, 2013 at 10:05 AM, Slavik Goltser <slavikg at gmail.com>wrote:
>> I could not find any information on this, but what is the recommended way
>> of migrating Dancer1 plugins to Dancer2? Is it to add version checking
>> while keeping the Dacer1 naming or is it recommended to rename the plugins
>> to Dancer2::Plugin... ?
>> I apologize if I am uncovering some heated debates relating to the
>> dancer-users mailing list
>> dancer-users at dancer.pm
> dancer-users mailing list
> dancer-users at dancer.pm
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dancer-users