[Xerte-dev] Re: 1.8 Release

Tue Jul 10 17:58:33 BST 2012

debug(_level0.contentXML);

Date: Tue, 10 Jul 2012 16:21:00 +0100
From: johnathan.kemp at ntlworld.com
To: xerte-dev at lists.nottingham.ac.uk
Subject: [Xerte-dev] Re: 1.8 Release

The development aspect I am trying to avoid is anything that requires editing of the original flash files - I am not particularly experienced working in flash and now, when the software is so close to release might not be the best time to start learning.

As a test I have created a File / New type of project and added to the Learning Object an attribute "pages", simply by typing "pages" in the optional attributes box and then clicking the add button.

This adds the "pages" attribute to the LO object in the .rlo file.
    <LO pages="true" name="Learning Object" language="en-GB">

How do I access this in Xerte?
IFC, rootIcon, or level0.engine all fail to return any of the attrributes of the Learning Object.debug rootIcon.XMLElement returns the attributes of the IFC not the LO.

If I can find out how to access the xml attributes of the learning object then I can set up the models accordingly, but at present I have not found a way to test its value from a Xerte script icon.

As far as my Xerte understanding goes, changing the page icon's title attribute value from a script off the entryFrame will be to late to effect the TOC. The changing of the page icon's title attribute value must happen when the edit is completed and the xwd form closes and this can only be made to happen by making changes to the appropriate Flash files. 

I want to help and to minimise any need to call on your time when you are busy.
If you can give me a pointer as to how to access the LO pages attribute that I have added I will add this to the pages.rlo file and update the models accordingly. That will leave the flash related bits to populate the page icon's title attribute to be tidied up.

Kind regards
Johnathan
On 10 July 2012 11:36, Julian Tenney <Julian.Tenney at nottingham.ac.uk> wrote:

You can probably tackle it before I can...

________________________________________

From: xerte-dev-bounces at lists.nottingham.ac.uk [xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Kemp Johnathan [johnathan.kemp at ntlworld.com]

Sent: 10 July 2012 09:55

To: For Xerte technical developers

Subject: [Xerte-dev] Re: 1.8 Release

A pages = true attribute would be a tidy solution.

If you did that I could change the models to test for that instead of rootIcon.projMode which is currently set in the entryFrame script.

I hope your week goes well.

Kind regards

Johnathan

On 10 July 2012 08:07, Julian Tenney <Julian.Tenney at nottingham.ac.uk<mailto:Julian.Tenney at nottingham.ac.uk>> wrote:

I only added it yesterday. You can play around with it now, the basic logic is there. I might think about whether you can set a pages=true attribute on the LO icon to test? I'm busy a lot of this week with graduation,

________________________________________

From: xerte-dev-bounces at lists.nottingham.ac.uk<mailto:xerte-dev-bounces at lists.nottingham.ac.uk> [xerte-dev-bounces at lists.nottingham.ac.uk<mailto:xerte-dev-bounces at lists.nottingham.ac.uk>] On Behalf Of Kemp Johnathan [johnathan.kemp at ntlworld.com<mailto:johnathan.kemp at ntlworld.com>]

Sent: 09 July 2012 14:54

To: For Xerte technical developers

Subject: [Xerte-dev] Re: 1.8 Release

I must have missed something somewhere along the line - I didn't realise that you had added this code.

Both "Pages" projects and ordinary Xerte projects created using file / new will have an ,rlo extension.

File / New projects are named by the author e.g. myProject.rlo whilst "Pages" projects always have the file pages.rlo so testing for the existence of pages.rlo would be unique in all cases save the chance situation in which someone created a File / New project and decided to name their project "pages".

A further possible identifier might be the existence of a folder called "pages" in the project folder. This folder does not exist when you create a "Pages" project. But it is created when you add the first page from the selection of pre-defined pages.

"Pages" projects also have a a setup script that is a child of the entryFrame that includes the line

rootIcon.projMode = "dev";

This sets the variable that is tested for by every model file to identify if the project is a pages project or a XOT / pageTemplate project.

However I am guessing that this will only e set at run time so would not be of use as a value to test for in the editor.

If the optimum route was to add a property to the learning object then there are two approaches I can think of

 1.  The learning object in a pages project has its own xwd form pages.xwd and it would be simple enough to add a property to that form as an identifier.

 2.  A better solution might be to add a new property to the learning object itself - i.e. to show up in the learning object's property panel. (Would this require a change in the code that defines a learning object?)

If either 1 or 2 were implemented as a solution then it might be tidier then to modify the test in the model files to use this value rather than a value set in a setup script.

What do you think is best?

Does any of the above give you the identifier you need?

Kind regards

Johnathan

On 9 July 2012 11:52, Julian Tenney <Julian.Tenney at nottingham.ac.uk<mailto:Julian.Tenney at nottingham.ac.uk><mailto:Julian.Tenney at nottingham.ac.uk<mailto:Julian.Tenney at nottingham.ac.uk>>> wrote:

It’s not beyond your skills…

In the wizard I have added this

//in the change handler for the name field

comp.change = function(obj){

     this.attributes['name'] = htmlToAtt(this.text);

     if (mdm != undefined){

          //set the TOC name in xerte for page projects

          mdm.Forms.editor.callFunction('setNameAttribute', this.text)

     }

}

And in the editor I have added this:

function setNameAttribute(nameString){

     //set the name attribute for page projects

     if (tree.selectedNode.parentNode.childNodes.length > 2){

           tree.selectedNode.attributes.name<http://tree.selectedNode.attributes.name><http://tree.selectedNode.attributes.name> = nameString;

           tree.dispatchEvent({type:"change", target:tree});

     }

}

What I need to know (and have asked before) is how to know it’s  pages project? The bold line isn’t a good test for one…

…but the logic goes

//wizard

If mdm exists we are on window xerte not toolkits, so call the function in the editor to set the attribute

//editor

Ah! Wizard wants to set the name attribute. If this is a pages project, I should go ahead and set it. But how do I know it’s a pages project? It might be a big template…

So, what is the best test? An .rlt extension denotes templates? A data property on LO? Must be easy to find out.

From: xerte-dev-bounces at lists.nottingham.ac.uk<mailto:xerte-dev-bounces at lists.nottingham.ac.uk><mailto:xerte-dev-bounces at lists.nottingham.ac.uk<mailto:xerte-dev-bounces at lists.nottingham.ac.uk>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk<mailto:xerte-dev-bounces at lists.nottingham.ac.uk><mailto:xerte-dev-bounces at lists.nottingham.ac.uk<mailto:xerte-dev-bounces at lists.nottingham.ac.uk>>] On Behalf Of Kemp Johnathan

Sent: 08 July 2012 08:02

To: For Xerte technical developers

Subject: [Xerte-dev] Re: 1.8 Release

Are we looking to release Xerte desktop at the same time as XOT?

If so there are a few issues remaining with desktop Xerte, which are listed on Ron's spreadsheet.

The most critical is the current inability to capture the page title for display in the TOC and on the displayed page.

This is something that is outside of my skill set to rectify.

Kind regards

Johnathan

On 7 July 2012 17:53, Tom Reijnders <reijnders at tor.nl<mailto:reijnders at tor.nl><mailto:reijnders at tor.nl<mailto:reijnders at tor.nl>>> wrote:

I am not going to commit anything global before the next release.

All changes will be part of the 'language pack'.

So, as far as I am concerned, nothing is prohibiting a release.

Regards,

Tom

Op 7-7-2012 15:46, Kemp Johnathan schreef:

Many thanks.

JK

On 7 July 2012 08:47, Tom Reijnders <reijnders at tor.nl<mailto:reijnders at tor.nl><mailto:reijnders at tor.nl<mailto:reijnders at tor.nl>>> wrote:

Sorry for the mistake. Corrected the spelling of your name :-).

Tom

Op 7-7-2012 6:45, Kemp Johnathan schreef:

OK, I successfully downloaded it this morning.

Thanks for the mention on the copyright notice on the installer.

Would you mind correcting the spelling of "Jonathan" in the copyright listing

correct is "Johnathan"

Kind regards

Johnathan

On 6 July 2012 20:19, Tom Reijnders <reijnders at tor.nl<mailto:reijnders at tor.nl><mailto:reijnders at tor.nl<mailto:reijnders at tor.nl>>> wrote:

No, my mistake, sorry.

Please try again.

Tom

Op 6-7-2012 16:26, Kemp Johnathan schreef:

Hello Tom,

I just tried to download the new xerte 1.8 beta from

http://www.xerte.org.uk/beta/xerte-beta.exe

but got an Access forbidden! Error 403 message displayed.

Has the url changed or have I made a mistake in the url I am trying to use?

Kind regards

Johnathan

On 6 July 2012 09:51, Tom Reijnders <reijnders at tor.nl<mailto:reijnders at tor.nl><mailto:reijnders at tor.nl<mailto:reijnders at tor.nl>>> wrote:

Xertetrans is operational again

Latest xerte-beta is uploading as we speak....

Will commit last changes to xot (if not too dangerous) later today.

As far as I am concerned, xerte standalone is ready for (beta) release.

Julian, I committed my inno setup file as well (it contains one line to include the Dutch translation of the wizards, but you might want to skip that)

Op 6-7-2012 9:11, Tom Reijnders schreef:

I'll finish up today.

Op 5-7-2012 12:36, Kemp Johnathan schreef:

I have just downloaded the current beta from Tom's site, installed it and run a few tests.

The beta is not using the latest models from svn/runtime/pages/models.

Also the issues currently identified in Ron's spreadsheet remain.

I am am sorry but other than test them there is not much I can do about them.

I have completed a range of pdt files to provide some support for the new stuff, with perhaps two omissions

1.      How the language features work

2.      How to create a new page in Xerte and add it to XOT (I wasn't sure if this would soon become obsolete in the light of the HTML5 developments.)

Kind regards

Johnathan

On 5 July 2012 10:20, Julian Tenney <Julian.Tenney at nottingham.ac.uk<mailto:Julian.Tenney at nottingham.ac.uk><mailto:Julian.Tenney at nottingham.ac.uk<mailto:Julian.Tenney at nottingham.ac.uk>>> wrote:

Fellow completer-finishers,

Before we get distracted with new stuff, let’s finish off the existing stuff: did all the outstanding things that various people were going to do get done and are we ready to go?

J

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<mailto:Xerte-dev at lists.nottingham.ac.uk><mailto:Xerte-dev at lists.nottingham.ac.uk<mailto: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: