Hi Erik, Am Mittwoch, 26. Juli 2006 11:43 schrieb Erik Alphenaar: > I completely agree to the fact that you don't want to define anything > in the jsp, but universal 'placeholders'.
What would such a universal placeholder look like? > > What I'm thinking of is a catagorised tree of content, and a placement > system on pages for the content in your content tree. Avantages for this > approach are that you can indeed easily reuse content, and the alternate > views are possible in this way (listing modules, detail views etc etc). > > It'll be content entry in a tree-like catagorised environment in a backend > system (eg: news > sports > football) and then creating a placement system > for the catagorised content. I think this is a pretty typical situation. It also happens to match my need. I have a tree of categorised content, and I'd like one UI for general administration of this tree, and separately the public instance version. > > Instead of editing the content inline, you create a custom dialog type. Are you referring here to the dialog you get when editing page or paragraph properties? > Users can select the preferred view for laying over the data (the > paragraph), and next select the needed content colection from all the > content nodes in the tree (preferrably with matching types :) ). Have you implemented this already? How does the user access the dialog for a given node? > For this view selection, this is just a ususal collection of possible > paragraphs for that position, and for the content, that's for example just > a recursive piece of java through the API, or a xpath query through the > repository. In this way the association is stored where it should be, in > the repository (imho). I think one could say this information about possible paragraphs for a given position is defined in the .jsp file. Through the use of the cms edit tags. Are you moving this sort of information into the repository and using that meta info through your dialog? > > I am not a big fan of overriding the whole paragraph and dialog principal, > but I try to seek a mapping that suits my needs. Why rebuild the idea, > when you can use it's existing powers for the same result? Can you provide more details wrt how you are integrating to the existing dialog principle in order to achieve this? ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
