[ http://jira.magnolia.info/browse/MAGNOLIA-1294?page=comments#action_13145 ] Philipp Bracher commented on MAGNOLIA-1294: -------------------------------------------
I like the idea of defining what really belongs to a node and what not, but in my opinion a schema is not really the best approach. You do not necessarily work with bootstrap-files nor is it a good idea to externalize config definitions to xml files at any other place. But we could achieve proper definitions by using proper jcr node types for dialogs, paragraphs, ... Anyway the current config tree is more to look at as a jcr browser and properties editor. In future we need better solutions for creating dialogs, ... We should create wizards including the proper validation. Means even if it sounds good in the first place, I think this won't lead to a good solution in the sense of usability. > 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 ----------------------------------------------------------------
