[Xerte-dev] Re: 1.9 thinking
Julian.Tenney at nottingham.ac.uk
Wed Jul 11 10:41:22 BST 2012
They sound like good ideas. I have always seen toolkits as a highly versatile xml editor, the runtime largely independent of that, although of course we have used Xerte to date. We ought to start a list somewhere of these ideas, maybe a google doc again?
From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
Sent: 04 July 2012 11:45
To: For Xerte technical developers
Subject: [Xerte-dev] 1.9 thinking
Given 1.8 seems "done", I have some purely PHP / MySQL ideas for 1.9
1) Allow each module to define it's own capabilities, so for example :-
I have some PHP that can make quite nice learning objects
I'd like to build a new module to support this (explicitly nothing Xerte)
But it won't export very well, so I want no export options
So, I would suggest abstracting the export function away from website
code and placing it within the module (a bit like
This way if a module doesn't support export, there is no option for it.
2) Also allow the module itself to define it's name and it's
desription (so they don't need to be stored in the database) thus
reducing the templatedetails table to a more basic structure.
These two changes offer one big advantage - it turns the basic XOT
structure / system into a generic LO creation management system (which
means developers can do more with it).
My thinking is I have some code which would be useful - but it doesn't
have a "wizard" interface, and I don't really need to write a new XOT
/ moodle plugin, when I can just modify XOT to do it.
Only issue is that the X in XOT starts to feel a bit weird....
If we are modifying the database, then I can see a case for also
1) Restructure / replace the sitedetails table with a more logical structure
Xerte-dev mailing list
Xerte-dev at lists.nottingham.ac.uk
More information about the Xerte-dev