Fellas, I opened the following ticket: https://github.com/PerlDancer/Dancer2/issues/1111
To track all such ideas, and it already has both of your ideas there: https://github.com/PerlDancer/Dancer2/issues/1112 https://github.com/PerlDancer/Dancer2/issues/1113 :) On Wed, Jan 13, 2016 at 10:29 PM, John Stoffel <[email protected]> wrote: >>>>>> "Sawyer" == Sawyer X <[email protected]> writes: > > Sawyer> On Wed, Jan 13, 2016 at 3:30 PM, John Stoffel <[email protected]> > wrote: >>> >>> > Sawyer> What do you think should be our next major focus? Would you like to > Sawyer> help? Let us know! >>> >>> I'd love to see expanded skeletons, or a way for Plugins to add >>> themselves into a skeleton so that you can more easily start >>> using/playing with an extension in the manner the Author of the plugin >>> expects it to be used. >>> >>> Think of it as documentation by example, with test cases too ideally. >>> >>> Now how to make this work when you have *lots* of plugins all stomping >>> all over each other, I don't know. It's just a thought. > > > Sawyer> +1 on these ideas from me! > > Sawyer> Would you like to create an issue to try and create a discussion > Sawyer> around it, what it would achieve and how it would look like? > > I'll try to do so, but I'm not sure I have any great ideas. Mostly, > I think having a way to generate skeletons and show off features of > modules would be a great way to get Dancer used more and to lower the > (steep) learning curve at times. > > John > _______________________________________________ > dancer-users mailing list > [email protected] > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users _______________________________________________ dancer-users mailing list [email protected] http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
