[Xerte-dev] Re: 1.9 thinking

[Julian Tenney]

How are you going to use the wizard to create other data formats?

-----Original Message-----
From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
Sent: 11 July 2012 10:59
To: For Xerte technical developers
Subject: [Xerte-dev] Re: 1.9 thinking

Yep, I'd say that or be all valley and use an etherpad

I think my editor almost certainly won't use XML - one or two might
(have three ideas), but all move away from Flash on the edit and the
play side.



On Wed, Jul 11, 2012 at 10:41 AM, Julian Tenney
<Julian.Tenney at nottingham.ac.uk> wrote:
> 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?
>
>
> -----Original Message-----
> 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
>
> Hello,
>
> 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
> module/xerte/play.php)
>
> 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
>
> Thoughts
>
> Pat
>
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>
> This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.
>
> This message has been checked for viruses but the contents of an attachment
> may still contain software viruses which could damage your computer system:
> you are advised to perform your own checks. Email communications with the
> University of Nottingham may be monitored as permitted by UK legislation.
>

_______________________________________________
Xerte-dev mailing list
Xerte-dev at lists.nottingham.ac.uk
http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev