Separate plugins and make them bower packages?

[davej]

These look great, thanks!

Would you consider separating these plugins and making them installable via bower? I'm hoping to roll out a beta of Angular Classy 1.0 before the end of the month and I want to list all of the plugins (with the keyword 'classy-plugin') on the homepage.

I have semi-documented the process here: https://github.com/davej/classy-plugins

[wuxiaoying]

Yea, I might have time next weekend to do it :) (or this week xD)

[wuxiaoying]

well they are all on bower now :P but no read me / examples for most of them.. Hopefully I'll get to that soon xD

[davej]

Excellent!

I'd love to hear your opinions on this issue: davej/angular-classy#32

[wuxiaoying]

Well I'm kind of biased on that, because my whole work project is in angular-classy now so I'm against it :P. I'm not sure I like the extra nested layer. However I read your reasoning, and it might make sense for the future. For me, I'd have to branch it at this point, but I doubt most other users of classy would have to make as many changes (I use classy controllers for directives too so it's a lottt of classy controllers ^^)

[davej]

There would also be a 'classy-compatibility' plugin which would allow you to use pre-1.0 Classy controllers with 1.0. It would be very simple, it would just move the reference to each of the controller methods from the root of the object to the nested methods object.

This would mean that you can mix pre-1.0 and post 1.0 controllers in the same codebase.

By the way, if the Classy-based project your doing at work is public then I'd love to take a look sometime. :-)

[wuxiaoying]

Oh yea, that would be nice :). Unfortunately the project is private :( sorry!