[Dancer-users] Dancer 2 for the masses

[sawyer x]

GIVE ME A DAY TO CHECK IT OUT! :)

On Tue, Oct 9, 2012 at 11:42 PM, Damien Krotkine <dkrotkine at gmail.com>wrote:

> Sorry, I wasn't very clear in my last email.
>
> I fully agree with sawyer : I'd like to see the updated dancer script
> included in the master branch. Also, there are a list of improvements that
> should be implemented if possible. I know celogeek has a lot of good ideas
> about it : be able to create a new view using something like dancer
> --new-view, and so on…
>
> However, I think we need a dancer script asap. We need to move forward
> using small steps, and if the current dancer script works, we could add it
> know, so that people can run web apps with Dancer 2 as soon as possible.
>
> Then we can improve it. What do you think about that ?
>
> Le mardi 9 octobre 2012 à 23:18, sawyer x a écrit :
>
> Stefan, props on helping push Dancer 2!
>
> On Tue, Oct 9, 2012 at 6:39 PM, damien krotkine <dkrotkine at gmail.com>wrote:
>
> On 6 October 2012 09:44, Stefan Hornburg (Racke) <racke at linuxia.de> wrote:
> > On 10/05/2012 12:15 PM, Stefan Hornburg (Racke) wrote:
> >>
> >> The core team wants to promote and finalize Dancer 2. IMHO there are a
> >> couple
> >> of things missing to make it easier for people to try out Dancer 2 and
> get
> >> involved into coding and/or improvements:
> >>
> >> 1. dancer script and/or sample application for Dancer 2
> >
> >
> > Actually a Dancer app produced with dancer -a from Dancer 1 works fine
> with
> > Dancer 2. So what's the reason that the script is missing in Dancer 2?
>
> I don't think there is any good reason. Feel free to add it if you
> have some time
>
>
> Actually, there's a lot I want changed. Both gnusosa and perlpilot put
> some effort into improving the script and making it more dynamic. I'd like
> to see those changes in Dancer 2.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.backup-manager.org/pipermail/dancer-users/attachments/20121009/0d8e3e72/attachment-0001.htm>