Hi, Just a few notes/comments I took while checking with the current store code * ModuleStoreServerModuleVersionHandler: all the bootstrap tasks are probably redundant. Aren't those files in the standard module bootstrap folder? If the idea is to the make the install more explicit: I like the idea, but then you probably want to extend AbstractMVH instead of DefaultMVH * Content: we should probably consider website.module-list.xml as being sample content, and therefore move it to /mgnl-bootstrap-samples/ ? (i.e use SamplesBootstrapTask) * I moved the project in /community/projects, see previous e-mail * Also did a whole lot of rename - trying to consistently use "store" or "MagnoliaStore" and avoid stuff like module-modulestore-module-server-module ;) (JK) * Resources and templates - shouldn't they be in module rather than the webapp ? * Use a templating model rather than the jsp function? * Use FreeMarker, use includes, etc ? (probably nothing to worry about for now) On the client side: * Did we think about caching the content instead of doing this request every time ? (granted, that's not going to happen with an iframe) * Can we avoid using POST in the iframe (breaks navigation, see STORE-13)
I also created a STORE project on Jira, for all things server-side, and a store-client component in MAGNOLIA for the admininterface module. Cheers, -g ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
