[Xerte-dev] Re: New modules

Pat Lockley patrick.lockley at googlemail.com
Fri Nov 23 15:52:02 GMT 2012


Did it work?

I can work the 3/4 new ones up into proper templates if easier? Or make a
dummy example one?


On Fri, Nov 23, 2012 at 12:30 PM, Pat Lockley <
patrick.lockley at googlemail.com> wrote:

> Erm, it depends really
>
> If you wanted to make a new xerte template it works as it used to
>
> If you wanted to use a xerte editor but a different preview / play then
> you'd make a different modules/xertenew folder
>
> I can't check in from here - code is at home
>
> new template makes a new folder, and then copies over the folders (media)
> and files (data.xml) needed to make the default xerte template. If you
> don't need to change this, then duplicate it.
>
>
>
> On Fri, Nov 23, 2012 at 12:24 PM, Julian Tenney <
> Julian.Tenney at nottingham.ac.uk> wrote:
>
>> > make a new folder in modules****
>>
>> You mean in modules/xerte/templates?****
>>
>> ** **
>>
>> > Then when you create this template, it will call new template.php in
>> your folder****
>>
>> New_template.php is in modules/xerte. Reading the code I see it copies
>> folders of files. I’m not really sure I understand what’s going on here. I
>> think if you check in the extra templates you’ve done I might be able to
>> figure it out,****
>>
>> ** **
>>
>> *From:* xerte-dev-bounces at lists.nottingham.ac.uk [mailto:
>> xerte-dev-bounces at lists.nottingham.ac.uk] *On Behalf Of *Pat Lockley
>> *Sent:* 23 November 2012 11:25
>>
>> *To:* For Xerte technical developers
>> *Subject:* [Xerte-dev] Re: New modules****
>>
>> ** **
>>
>> make a new folder in modules called "module_name"
>>
>> In this copy all of the files from modules/xerte
>>
>> make a new folder in module_name called the shortname for your template
>> (i.e Nottingham)
>>
>> In this folder put a .info file called the same name as the folder and in
>> that file put the stuff from the Nottingham one (play with some of the
>> settings as you see fit)
>>
>> Then when you create this template, it will call new template.php in your
>> folder
>> Editing will call edit
>> Play play and so on
>>
>> So mod the code to do whatever you want it to do
>>
>> If you are using Xerte as the editor, then you can leave new and edit in
>> tact and just mangle preview and play - but I think most of this is now in
>> module_functions.php****
>>
>> ** **
>>
>> On Fri, Nov 23, 2012 at 10:55 AM, Julian Tenney <
>> Julian.Tenney at nottingham.ac.uk> wrote:****
>>
>> So as a lab rat, if I wanted to use a xwd to create a wizard for creating
>> data to drive a web page built with twitter bootstrap, how would I do that?
>> ****
>>
>>  ****
>>
>> The wizard stuff I can do (obviously) but how do you hook up a new
>> runtime (the base html page) and how is the data passed to it? Then I can
>> use jQuery to build the page from the data…****
>>
>>  ****
>>
>> *From:* xerte-dev-bounces at lists.nottingham.ac.uk [mailto:
>> xerte-dev-bounces at lists.nottingham.ac.uk] *On Behalf Of *Pat Lockley
>> *Sent:* 23 November 2012 10:06****
>>
>>
>> *To:* For Xerte technical developers
>> *Subject:* [Xerte-dev] Re: New modules****
>>
>>  ****
>>
>> The right hand list is built from the database still, if you go to
>> management.php and templates then "update" you'd get them all. They can
>> exist as folders and not be usable.****
>>
>>  ****
>>
>> On Fri, Nov 23, 2012 at 10:02 AM, Julian Tenney <
>> Julian.Tenney at nottingham.ac.uk> wrote:****
>>
>> OK. As time goes on we ought to also move the source code for various
>> things from the xerte svn into the toolkits one, so building the zip will
>> become more complicate than simply zipping up the svn folder. At the
>> moment, does the workspace’s list of templates get built from your modules
>> – i.e. will I see them in the workspace automatically?****
>>
>>  ****
>>
>> *From:* xerte-dev-bounces at lists.nottingham.ac.uk [mailto:
>> xerte-dev-bounces at lists.nottingham.ac.uk] *On Behalf Of *Pat Lockley
>> *Sent:* 23 November 2012 09:38****
>>
>>
>> *To:* For Xerte technical developers****
>>
>> *Subject:* [Xerte-dev] Re: New modules****
>>
>>  ****
>>
>> Can I commit them just for the sake of having a green tick? I guess the
>> zip isn't made directly from the trunk (lots of old Xerte templates)
>>
>> I've also not copied trunk over the top of 1.9, or introduced any of the
>> generic play code talked about the other day.
>>
>> I also realise import isn't modularised, which is a bit of a problem.****
>>
>>  ****
>>
>> On Fri, Nov 23, 2012 at 9:14 AM, Julian Tenney <
>> Julian.Tenney at nottingham.ac.uk> wrote:****
>>
>> Leave them out for now, ****
>>
>>  ****
>>
>> *From:* xerte-dev-bounces at lists.nottingham.ac.uk [mailto:
>> xerte-dev-bounces at lists.nottingham.ac.uk] *On Behalf Of *Pat Lockley
>> *Sent:* 22 November 2012 23:18
>> *To:* For Xerte technical developers
>> *Subject:* [Xerte-dev] New modules****
>>
>>  ****
>>
>> I haven't committed any of my new modules to trunk, but I could do so, on
>> the basis you could leave them out of the 1.9 zip?****
>>
>>  ****
>>
>> Not fussed.****
>>
>>  ****
>>
>>
>> _______________________________________________
>> 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****
>>
>>  ****
>>
>>
>>
>> ****
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte-dev/attachments/20121123/f27576af/attachment.html>


More information about the Xerte-dev mailing list