Temple - Revision history

Mdegraauw: /* The inspector */

2019-01-19T10:41:39Z

‎The inspector

Mdegraauw: /* The code editor */

2018-05-16T14:23:48Z

‎The code editor

Ahenket: /* Shortcuts */

2015-11-24T22:00:26Z

‎Shortcuts

Ahenket: /* Bookmarks */

2015-11-24T21:22:02Z

‎Bookmarks

Mdegraauw: /* The inspector */

2015-11-02T15:43:48Z

‎The inspector

Mdegraauw: /* The inspector */

2015-09-14T09:08:59Z

‎The inspector

Mdegraauw: /* Starting Temple */

2015-09-06T15:47:55Z

‎Starting Temple

Mdegraauw: /* The inspector */

2015-09-06T13:38:04Z

‎The inspector

Mdegraauw: /* Editing template and templateAssociation */

2015-09-04T10:08:07Z

‎Editing template and templateAssociation

Mdegraauw at 09:58, 4 September 2015

2015-09-04T09:58:54Z

@@ Line 49: / Line 49: @@
 * 'all:address' or '*:address': Search for artefacts containing 'address' in current project and BBR's referenced in current project.
 * 'demo1:address' : Search for all artefacts containing 'address' in DECOR 'demo1-' project (if available on seerver). This allows searching in other projects than current project.
 ==Bookmarks==

@@ Line 35: / Line 35: @@
 * @valueSet
 when those are referenced by id. The names are discarded again when saving.
 ==The inspector==
 When the cursor is in on any construct containing the name or id of a template, a valueSet or concept, press Ctrl-I to inspect it. Temple will look for an effectiveDate or flexibility on the same line of code and use that, and else will use 'dynamic'. For instance, put the cursor inside the id in:

@@ Line 51: / Line 51: @@
 ==Shortcuts==
-While editing a template, temple will support the following shortcuts:
+While editing a template, temple supports the following shortcuts:
 * The attribute ''cc'' on '''element''' offers a shortcut to adding the most common combinations of @minimumMultiplicity, @maximumMultiplicity, @conformance and @isMandatory. Example:<br/>''cc''="'''1..1 M'''" expands into ''minimumMultiplicity''="'''1'''" ''maximumMultiplicity''="'''1'''" ''isMandatory''="'''true'''"
 * The attribute ''as'' on '''attribute''' offers a shortcut to adding the most common HL7 V3 attributes like classCode and moodCode as name/value pair. Example:<br/>''as''="'''classCode'''" expands into ''name''="'''classCode'''" ''value''=""

← Older revision		Revision as of 21:22, 24 November 2015
Line 49:		Line 49:
	==Bookmarks==		==Bookmarks==
	When editing a template, clicking the 'empty star' button will add a bookmark. The empty star becomes a filled star. The 'Bookmarks' button will show all bookmarked templates in the inspector. Clicking the 'filled star' will remove the bookmark again.		When editing a template, clicking the 'empty star' button will add a bookmark. The empty star becomes a filled star. The 'Bookmarks' button will show all bookmarked templates in the inspector. Clicking the 'filled star' will remove the bookmark again.
		+
		+	==Shortcuts==
		+	While editing a template, temple will support the following shortcuts:
		+	* The attribute ''cc'' on '''element''' offers a shortcut to adding the most common combinations of @minimumMultiplicity, @maximumMultiplicity, @conformance and @isMandatory. Example:<br/>''cc''="'''1..1 M'''" expands into ''minimumMultiplicity''="'''1'''" ''maximumMultiplicity''="'''1'''" ''isMandatory''="'''true'''"
		+	* The attribute ''as'' on '''attribute''' offers a shortcut to adding the most common HL7 V3 attributes like classCode and moodCode as name/value pair. Example:<br/>''as''="'''classCode'''" expands into ''name''="'''classCode'''" ''value''=""

@@ Line 44: / Line 44: @@
 The inspector has a search box which gets all artefacts (concepts, transactions, valueSets and templates) containing a search string. Supported searches are:
 * 'address' : Search for all artefacts containing 'address' in current project.
-* 'demo1:address' : Search for all artefacts containing 'address' in DECOR 'demo1-' project (if available on seerver).
+* 'all:address' or '*:address': Search for artefacts containing 'address' in current project and BBR's referenced in current project.
-* 'all:address' : Search for all artefacts containing 'address' in all  projects on server (synonymous with search for '*:address').
+* 'demo1:address' : Search for all artefacts containing 'address' in DECOR 'demo1-' project (if available on seerver). This allows searching in other projects than current project.
 ==Bookmarks==
 When editing a template, clicking the 'empty star' button will add a bookmark.  The empty star becomes a filled star. The 'Bookmarks' button will show all bookmarked templates in the inspector. Clicking the 'filled star' will remove the bookmark again.

@@ Line 36: / Line 36: @@
 when those are referenced by id. The names are discarded again when saving.
 ==The inspector==
-When the cursor is in on any construct containing the name or id of a template, a valueSet or concept, press Ctrl-S to inspect it. Temple will look for an effectiveDate or flexibility on the same line of code and use that, and else will use 'dynamic'. For instance, put the cursor inside the id in:
+When the cursor is in on any construct containing the name or id of a template, a valueSet or concept, press Ctrl-I to inspect it. Temple will look for an effectiveDate or flexibility on the same line of code and use that, and else will use 'dynamic'. For instance, put the cursor inside the id in:
    <element name="hl7:id" datatype="II.NL.BSN" id="2.16.840.1.113883.3.1937.99.62.3.11.7.1">
-and press Ctrl-S to inspect the referenced concept(s). Within the inspector one can also inspect further, for instance to inspect the parent of a concept or an included template.
+and press Ctrl-S to inspect the referenced concept(s). Within the inspector one can also inspect further, for instance to inspect the parent of a concept or an included template. Searchable id's are color-coded. When inspecting something on id (and effectiveDate) a global search in the DECOR repository is done. When searching on name, a local search in current project is done.
-The inspector has a search box which gets all contructs starting with search string. The inspector also supports searching BBR's with this syntax: "prefix:string". When inspecting something on id (and effectiveDate) a global search in the DECOR repository is done. When searching on name, a local search in current project is done (project either defined by the project in the code editor or the prefix in search box).
+The inspector has a search box which gets all artefacts (concepts, transactions, valueSets and templates) containing a search string. Supported searches are:

@@ Line 3: / Line 3: @@
 Temple may be opened from the template viewer in ART, with the 'Temple' button, or directly. In the latter case, an editor with just some boilerplate template in it is opened. If opened from a browser with:
-   {hostname}/temple/modules/temple.xquery?prefix=demo1-&language=nl-NL&mode=edit
+   {hostname}/temple/modules/temple.xquery?language=nl-NL
-temple will be opened for demo1- project. If opened from ART, the template being viewed is opened. Temple is not an Orbeon XForms application, but eXist + HTML. This means that you need to be logged in to eXist to use Temple. Temple (or more correctly, your browser) may ask credentials when opening Temple.
+temple will be opened with empty template. Search for templates in a project using the search box in the inspector with prefix:searchstring notation. If opened like this:
 ==The code editor==

← Older revision		Revision as of 13:38, 6 September 2015
Line 37:		Line 37:

	and press Ctrl-S to inspect the referenced concept(s). Within the inspector one can also inspect further, for instance to inspect the parent of a concept or an included template.		and press Ctrl-S to inspect the referenced concept(s). Within the inspector one can also inspect further, for instance to inspect the parent of a concept or an included template.
		+
		+	The inspector has a search box which gets all contructs starting with search string. The inspector also supports searching BBR's with this syntax: "prefix:string". When inspecting something on id (and effectiveDate) a global search in the DECOR repository is done. When searching on name, a local search in current project is done (project either defined by the project in the code editor or the prefix in search box).

@@ Line 7: / Line 7: @@
 temple will be opened for demo1- project. If opened from ART, the template being viewed is opened. Temple is not an Orbeon XForms application, but eXist + HTML. This means that you need to be logged in to eXist to use Temple. Temple (or more correctly, your browser) may ask credentials when opening Temple.
-==Editing template and templateAssociation==
+==The code editor==
 When opening a template, the corresponding templateAssociation is automatically retrieved. If it does not exist, it is created in Temple (though not saved yet). The attributes @templateId and @effectiveDate are not shown on templateAssociation. On saving, Temple will copy them from the template. (If you add them manually, they will be overwritten on save.)
@@ Line 23: / Line 23: @@
 * If templateAssociation does not exist, it is created (maybe empty, if no concepts are provided).
-When saving, Temple will validate against the DECOR schema. If there are errors, those will be displayed. In most modern browsers, hitting the back button will take you back to the template to fix those. If the template is valid, after saving you will stay on the edited template page, thus allowing to Save and continue working. Only when creating a template with @id='new', you will be redirected to an empty page, and will havev to navigate to the new template from ART (where you might need to refresh the page you were on).
+When saving, Temple will validate against the DECOR schema. If there are errors, those will be displayed. This will land you on an error page, so go back in the browser to edit further. It's also possible to validatte without saving. If the template is valid, after saving you will stay on the edited template page, thus allowing to Save and continue working. Only when creating a template with @id='new', you will be redirected to an empty page, and will have to navigate to the new template from ART (where you might need to refresh the page you were on).
 Temple will add names to:
@@ Line 31: / Line 31: @@
 * @valueSet
 when those are referenced by id. The names are discarded again when saving.

@@ Line 1: / Line 1: @@
 ==Starting Temple==
-Temple may be opened from the template viewer in ART, with the 'Temple' button, or directly. In the latter case, an editor with just some boilerplate template in it is opened. If opened from ART, the template being viewed is opened. Temple is not an Orbeon XForms application, but eXist + HTML. This means that you need to be logged in to eXist to use Temple. Temple (or more correctly, your browser) may ask credentials when opening Temple.
+Temple may be opened from the template viewer in ART, with the 'Temple' button, or directly. In the latter case, an editor with just some boilerplate template in it is opened. If opened from a browser with:
 ==Editing template and templateAssociation==
@@ Line 19: / Line 24: @@
 When saving, Temple will validate against the DECOR schema. If there are errors, those will be displayed. In most modern browsers, hitting the back button will take you back to the template to fix those. If the template is valid, after saving you will stay on the edited template page, thus allowing to Save and continue working. Only when creating a template with @id='new', you will be redirected to an empty page, and will havev to navigate to the new template from ART (where you might need to refresh the page you were on).