> > > If you mean plugins written in Java, that would be Sling OSGi I > guess...it might seem like a big beast now, but once refactored to the > new sling-api, Sling OSGi shouldn't be much harder to use than > microsling for simple things. So we could assume that people with that > kind of needs would "graduate" to Sling OSGi, > > OTOH if by plugins you mean scripts that can be reused as software > components in other scripts, that's a different topic, that might be > interesting to explore...a bit later maybe ;-) > > Well, I deliberately stayed away from the question how an application-level plugin mechanism should be implemented. But, yes, I meant scripts that can be reused (but not necessarily just visual components).
I agree, this discussion is probably a bit too early.
