Hi Felix, On Mon, Feb 25, 2008 at 10:52 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > ...I imagine, there will be the following modules in the > launchpad folder: > > app - Standalone launchpad application > webapp - Launchpad Web Application > (renamed from launchpad-webapp) > content - Initial Launchpad content
ok > ... The app and webapp modules will have three build profiles: > > bare - (default) Launcher only (OSGi framework; Log, > HttpService and Sling Console bundles) > full - Same as "bare" plus all bundles required for > a productive Sling system > launchpad - Same as "full" plus launchpad/content, > samples and documentation Agree about this, but could we make "launchpad" the default instead? In the sense of offering an easy path to get started - "bare" is obviously for people who know more about Sling than "launchpad" users. > ... The difference between "full" and "launchpad" is, that full may be used > as the basis for any productive system without the payload of > demonstration, educational and documentation bundles. The "launchpad" > build is targeted at the "getting-to-know" audience and will include > these > demonstration, educational and documentation bundles.... ok > ... Talking about "demonstration, educational and documentation" bundles, > what will these be ? These are the (current) sling/sample and > launchpad/content bundles. In addition we could also define a bundle, > which contains the sling site as well as JavaDoc and Code XRef > accessible through sling - sort of like a default Apache Httpd > installation also containing documentation... Agreed - I'm going to work on more "developing with Sling" docs examples in the next few weeks, mostly targeted at working with server-side and client-side javascript to develop for Sling. My idea currently is to put that content in the launchpad-content module, but we can always make that more modular later on if needed, that is if we find out that launchpad-content contains too many things. -Bertrand
