Hi Jjanandith, On Mon, May 12, 2008 at 8:41 PM, janandith jayawardena <[EMAIL PROTECTED]> wrote: > ...So does this mean if i come across any reference to microsling i can > consider it as part of the launchpad and isolate it from other parts of > sling ?....
Not really - microsling was a standalone experiment in simplfying Sling, and the microsling ideas have been integrated in various Sling components (resource and script resolution, etc.). If you come across references to microsling, chances are the basic ideas are implemented somewhere in Sling now, but better ask or lookup details in the code and tests. > ... is > > Sling framework = (all code in Sling directory) minus ( site + parent > + maven + launchpad directories)... I never looked at it this way but it makes sense - though the launchpad is an integral part of the Sling project, it is mostly an assembly of Sling components, for demo and testing purposes. There is some specific code in launchpad/base that is usually needed to bootstrap Sling applications - that could be considered an integral part of the framework. -Bertrand
