On Dec 18, 2007 2:32 AM, <pi...@wasabicowboy.com> wrote:
I guess I was thinking that microsling could be viewed as a simplified sling programming environment. ...
I agree with that, or maybe more precisely: microsling (once merged)
exposes the parts of Sling that are easiest to use and understand. But
those parts remain available in Sling, if they're activated.
...If so it could be viewed as just a sling bundle which provides script and other services to get people up and running quickly...
I don't think (the merged) microsling has to be a single OSGi bundle,
it will more probably be a collection of bundles, that is activated by
a default configuration that's invisible to beginners.
I'll branch this thread into a "microsling 2.0 requirements"
discussion now, so that we can clarify all this.