[Xerte-dev] Re: Nomenclature

[Pat @ Pgogy]

They are mostly my fault

Page type: Correct
Template: Correct (though the PHP confuses this at times)
Module: A collection of templates presented in a particular way (eg. Xerte
template = general elearning, Site template = Bootstrap website)

Some questions:

- I'm unclear on what the other templates inside the Xerte module are for,
or why you'd need them?

Xerte is an engine, and you can send it a wizard to do different things, so
by giving it a path parameter it will load and style differently. Since
Xenith, the RSS template has gone cold a little

- What's the difference between parent_templates and templates? In what way
is one a parent?

The parent, is because that is what is copied to instantiate a new
template. So some of the template is the template (common files across all
users projects), whereas parent templates is the block of the template
copied into USER-FILES when a new project is made

- Can we rename the Nottingham template to something more meaningful - like
SCORM-starter?

You could, but each folder in USER-FILES has the template in its name
(which was stupid, and we should stop) so rename a template and you have to
rename a lot of folders

- Can we rename the Xerte module to something more meaningful - like SCORM?

You could do, not sure what it gains, and calling it SCORM seems to deny
anything else the right to be scorm?

- When would you plugin a module as opposed to a template?

When you have an existing module which has code which can be repurposed. So
you could create a D3 module (for visualisations) and use it to display
different templates


On Tue, Dec 3, 2013 at 4:55 PM, Mark Berthelemy <
mberthelemy at wyversolutions.co.uk> wrote:

>  Hi all,
>
> I'm just checking my understanding of some of the Xerte nomenclature:
>
> Page type: A way of presenting a chunk of information or an interaction
> (eg. graphic + text, multi-choice question, hot spot graphic) - stored as
> an html file (for the output), and an XML description (for the editor)
> inside a template
> Template: A package of page types and associated files designed for a
> specific purpose (eg. the Nottingham template for general elearning)
> Module: A collection of templates presented in a particular way (eg.
> Xerte template = general elearning, Site template = Bootstrap website)
>
> Some questions:
>
> - I'm unclear on what the other templates inside the Xerte module are for,
> or why you'd need them?
> - What's the difference between parent_templates and templates? In what
> way is one a parent?
> - Can we rename the Nottingham template to something more meaningful -
> like SCORM-starter?
> - Can we rename the Xerte module to something more meaningful - like SCORM?
> - When would you plugin a module as opposed to a template?
>
> If someone has already documented these structures, please could you point
> me in the right direction, to save reinventing the wheel.
>
> Thanks,
>
> Mark
>
>
>
> --
> Mark Berthelemy
> Managing Director
> Tel: 01773 318 962
> Mob: 07922 146 761
> Web: www.wyversolutions.co.uk
>
> Wyver Solutions Ltd | Company number: 5731173 Registered in England |
> Registered address: First Floor, 6 Bridge Street, Belper, Derbyshire,
> DE56 1AX
>
>
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte-dev/attachments/20131203/e24d90c1/attachment-0001.html>