[ http://jira.magnolia.info/browse/MAGNOLIA-1294?page=comments#action_13146 ] Oliver Lietz commented on MAGNOLIA-1294: ----------------------------------------
First there should be a way to share templates (config) between different instances with a minimum of data required in a human readable form. The meta data in a system view contains a lot of information which makes it difficult. The jcr: and mgnl: stuff is totally unrelated to data in a different instance (other client - whatever). But using general templates for different clients/instances is a common request. If you setup a new instance you have to fiddle around with bootstrap files and it is a PITA with the existing method of using system views. You don't start from scratch with creating templates, paragraphs and dialogs for every new client. The current way of creating templates, paragraphs and dialogs is sufficient for developers if you are able to reuse/import existing templates. I prefer the Unix way of doing things with plain files instead of shiny wizards which deny direct access to all information. Do you really want to go through all steps of a wizard when creating new templates? I don't think so. Imagine you are developing a new template and have always go through a wizard to change a single value which is on page three of the wizard. *This* is not a good solution in the sense of usability. Whether you use Schema, RELAX NG, DTD or any other method of validating input there should be proper documentation of these options/properties. I start collecting relating information in the wiki because I was unable to find something useful in the source and the docs. > Simplify external handling of Templates, Paragraphs and Dialogs > --------------------------------------------------------------- > > Key: MAGNOLIA-1294 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1294 > Project: Magnolia > Issue Type: New Feature > Components: templating > Affects Versions: Ideas > Reporter: Oliver Lietz > Assigned To: Philipp Bracher > Priority: Minor > > This is an attempt to simplify the (external) handling of Templates, > Paragraphs and Dialogs. > * a Template, Paragraph and Dialog is represented by a human readable XML > document (examples below) > * the XML documents are valid against the appropriate schemas > * the XML documents are imported into a running Magnolia instance and setup > properly > * they can be exported into a valid XML document from the repository > <?xml version="1.0" encoding="UTF-8"?> > <template version="3.0" xmlns="http://magnolia.info/xml/ns/3.0/template";> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://magnolia.info/xml/ns/3.0/template > http://magnolia.info/xml/ns/3.0/template.xsd"/> > <name>mytemplate</name> > <path>/templates/mytemplate.jsp</path> > <title>template.mytemplate.title</title> > <type>jsp</type> > <visible>true</visible> > </template> > <?xml version="1.0" encoding="UTF-8"?> > <paragraph version="3.0" xmlns="http://magnolia.info/xml/ns/3.0/paragraph";> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://magnolia.info/xml/ns/3.0/paragraph > http://magnolia.info/xml/ns/3.0/paragraph.xsd"/> > <name>myparagraph</name> > <description>paragraph.myparagraph.description</description> > <dialog>dialogNode</dialog> > <templatePath>/paragraph/paragraph.jsp</templatePath> > <title>paragraph.myparagraph.title</title> > <type>jsp</type> > </paragraph> > The system view is hard to read and blowed up by meta data. Maybe the > document view makes handling easier but I was unable to find useful > information and samples. > The goal is to share general templates between different clients and > developers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
