[Xerte-dev] Re: Export Code (commit of fixes)

Fri May 11 10:43:49 BST 2012

Yes, it does, but we need to find a way of expressing the functionality in words they've seen before and can readily understand, or prefereably make it automatic. In your explanation, you don't say why I might like to choose one option or another: that's what a user needs to know.

From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Ron Mitchell
Sent: 11 May 2012 10:35
To: 'For Xerte technical developers'
Subject: [Xerte-dev] Re: Export Code (commit of fixes)

For me the real value of the local export is this:

User are authoring in the sandpit (or another XOT install) and want to link to Word or PowerPoint documents etc which aren't online so they import them via media and quota and link to them. Whilst learners are accessing from XOT all fine.

Author the exports for use via vle and or locally via USB/CD. Author then needs choice whether those word/ppt links should be converted to local links or not. Sandpit users would have to choose convert to local because there assets would be wiped anyway. In other cases LO's may contain links to lot's of online resources and sites so connectivity is required even when viewing locally and keeping the media folder links pointing back to XOT can be very useful especially where assets are shared or updated regularly.

The checkbox option gives the author control which is great.

From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Tom Reijnders
Sent: 11 May 2012 10:21
To: For Xerte technical developers
Subject: [Xerte-dev] Re: Export Code (commit of fixes)

I would love to oblige, but what do you actually suggest? I mean point 2 contains 2 different exports (Scorm 1.2 and Scorm 2004). Just make those two links in that line?

And what do we do with 'local'

All the code is there (need to debug scorm2004, that's probably a typo somewhere), the actual export done are parameters to export.php. So we only need to figure out how to do the UI right now.

Tom

Op 11-5-2012 11:15, Julian Tenney schreef:
OK, lets do that.

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] On Behalf Of Ron Mitchell
Sent: 11 May 2012 10:15
To: 'For Xerte technical developers'
Subject: [Xerte-dev] Re: Export Code (commit of fixes)

Only listed that order because that's the order that's there now and effectively has been previously but yes probably makes more sense to swap 1 and 3

1. Export for deployment. Contains only the files required for importing into a vle without SCORM tracking, sharing via CD or USB etc or importing into another XOT install
2. Export for SCORM deployment: self contained, SCORM 1.2 or SCORM 2004 enables tracking of Quiz scores e.g. into Moodle gradebook
3. Archive export. Complete backup including offline editing and round-tripping back to toolkits or sharing with other Xerte users.

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] On Behalf Of Julian Tenney
Sent: 11 May 2012 10:01
To: For Xerte technical developers
Subject: [Xerte-dev] Re: Export Code (commit of fixes)

I'd switch the order of 1 and 2 or maybe 1 and 3.

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] On Behalf Of Ron Mitchell
Sent: 11 May 2012 09:52
To: 'For Xerte technical developers'
Subject: [Xerte-dev] Re: Export Code (commit of fixes)

> AFAIK, very few people do the roundtrip thing to xerte on windows.<

I think there's more than you think and more than we know. They aren't developers, they're teachers in all sorts of organisations who might start off with the Techdis sandpit but then learn they can use the same easy to use interface in the developer tool and that becomes the way the create and edit whilst waiting for their own organisation's installation. There were quite a few people at the event on Wednesday who had been using Xerte not XOT but had started on the sandpit and exported. The full export has always been useful in this respect and a selling point. I can see things might need to change in the future but please keep this for now unless there's really good reason not to?

> Export for sharing with another XOT install (maybe the same output as self contained deployment - or is this different?<

In my experience most XOT users export as 'normal zip' rather than scorm and then import into their vle (usually moodle) and link to index.htm. I appreciate that they would be better just linking from XOT but for various reasons many still go the export route and obviously sandpit users do this because of the monthly wiping. Another reason is that display of scorm imports in Moodle in particular are often constrained by the frameset display and/or sitewide scorm module settings so people prefer the non-scorm route where score tracking isn't required. I guess this might change if more page types are tracked with Tom's developments but for now I think there's still a need for non-scorm deployment.

So tweaking your list...

1. Archive export. Complete backup including offline editing and round-tripping back to toolkits or sharing with other Xerte users.
2. Export for deployment. Contains only the files required for importing into a vle without scorm tracking, sharing via CD or USB etc or importing into another XOT install
3. Export for Scorm deployment: self contained, SCORM 1.2 or SCORM 2004 enables tracking of Quiz scores e.g. into Moodle gradebook

HTH
Ron

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] On Behalf Of Julian Tenney
Sent: 11 May 2012 09:17
To: For Xerte technical developers
Subject: [Xerte-dev] Re: Export Code (commit of fixes)

Maybe it's useful to list the scenarios:

Export for deployment: self contained, SCORM 1.2 or SCORM 2004
Export for sharing with another XOT install (maybe the same output as self contained deployment - or is this different?)
Export for offline editing and round-tripping back to toolkits - this is what you get when you click a source code link in xpert as well?

That's all of them?

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] On Behalf Of Julian Tenney
Sent: 11 May 2012 09:12
To: For Xerte technical developers
Subject: [Xerte-dev] Re: Export Code (commit of fixes)

This is starting to feel like a FWS failure.

In options 1 and 2, the exported project loads media from the originating server? Is that what 'full URL' means, i.e. 'http://ltdev.nottingham.ac.uk/etc/'

Supporting the roundtrip edit -> export -> edit in xerte for windows -> import -> continue editing might be something we want to drop in the future. I don't know how this will work in an HTML5 world. Increasingly, connectivity is everywhere, and there's less need to support this than there was. By far the most useful export is the one for deployment, with a minimal set of files, including only the media used / referenced in the project.

AFAIK, very few people do the roundtrip thing to xerte on windows.

It useful to have an export for sharing with other XOT users at different locations. When these projects are imported, the project folder gets all the models / thumbs etc - this doesn't really need to happen, but I'm not sure why Pat made it work like this - maybe just easy coding, or maybe because we cope with templates the receiving install doesn't know about, or templates that are out of synch with the receiving systems models / engine etc?).

The SCORM zips are for deployment, so I think that's straightforward.

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] On Behalf Of Ron Mitchell
Sent: 10 May 2012 21:44
To: 'For Xerte technical developers'
Subject: [Xerte-dev] Re: Export Code (commit of fixes)

I guess I'm falling into the trap of 'how it used to be' e.g. whatever zip export I had I could extract and edit in Xerte.

However I can understand the advantage of not exporting unused media in terms of file space saving etc but I'm not sure about the value of not including the files required to edit unless including them causes a problem?

Effectively this means If I want to have an offline copy for safe keeping that I can edit as well as import into a vle and track I have to export twice - a full archive and a scorm export whereas previously the scorm export would enable both. Has this been discussed in this context e.g. is there a problem including the .xwd and any other files required to edit as part of all the exports?

Personally no I don't think the links should always be converted to local links in fact quite the opposite. I've been showing people how to re-use assets by creating an lo just for that purpose e.g. if there's media and files used with lots of different LO's then upload to an asset only LO and then use those links in any number of LO's. This also means that linked documents can be updated once in one place so I think having choice of whether to keep the full url links or localise them is useful even if the asset is in the same lo.

Cheers
Ron

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] On Behalf Of Tom Reijnders
Sent: 10 May 2012 21:19
To: For Xerte technical developers
Subject: [Xerte-dev] Re: Export Code (commit of fixes)

The option 2, 3, 4 and 5 miss files you need to be able to edit them. The zip archives just contain the bare minimum.

I wonder if the behaviour with the links of 3 should always happen.... and then get rid of option 3.

Op 10-5-2012 22:03, Ron Mitchell schreef:
Have committed that small mod.

As far as I can tell option 3 works like this...

I upload a file via properties > media & quota and copy that full url link
I then add that link to a text area of the same LO somewhere

export options 1. and 2. include the file in the exported media folder but the link to the file added via media & quota remain full url links

export option 3 changes the link to the file added via media and quota to FileLocation + 'media/filename' rather than full url.

I also wondered what happens if the linked file was added to a different lo and in that case the export retains the full url so I guess the code must check for the LO ID or something and only convert the links to local links if the same lo.

However I'm not sure whether it's just my install of Xerte but at the moment there seems to be a problem when trying to edit an LO exported with option 2 and 3.  If I double click the .rlt xerte fires up but then automatically minimises and can't be restored e.g. can't edit the file. The same lo exported with option 1 edits just fine.

In testing all this I also found another bug - when uploading via properties > media & quota the uploaded file doesn't appear even though it is uploaded.

I'll add these issues to the Google doc.

HTH
Ron

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] On Behalf Of Tom Reijnders
Sent: 10 May 2012 20:27
To: For Xerte technical developers
Subject: [Xerte-dev] Re: Export Code (commit of fixes)

Please do. We still need to figure out what option 3 is doing.... :-)

Op 10-5-2012 21:24, Ron Mitchell schreef:
Hi Tom
on the test server I just replaced the export template with a copy that has <br></br> in the relevant places e.g.
[cid:image001.jpg at 01CD2F62.F32CEA80]

Does that seem ok? If so shall I commit that quick modification?

Cheers
Ron

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] On Behalf Of Ron Mitchell
Sent: 10 May 2012 20:09
To: 'For Xerte technical developers'
Subject: [Xerte-dev] Re: Export Code (commit of fixes)

That looks good to me but I'd be inclined to add a return between each link just so it's less easy to click the wrong link by mistake.

HTH
Ron

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] On Behalf Of Tom Reijnders
Sent: 10 May 2012 19:59
To: For Xerte technical developers
Subject: [Xerte-dev] Re: Export Code (commit of fixes)

How about this for now?

[cid:image002.png at 01CD2F62.F32CEA80]

Op 10-5-2012 18:49, Tom Reijnders schreef:
I think this looks good, and I am happy to explain 3, if I knew what it is doing.

Op 10-5-2012 15:31, Julian Tenney schreef:
Do we need to add some wording to  make this easy to understand: I might not know what 'with references to local files altered' means, so it might read:

---------------------------------------
There are several ways to export a project. An exported project is packaged, but not deleted, into a zip file for you to share with another user, to deploy on the web, or to import into a SCORM compliant LMS or VLE. You can choose whether to export all of the project's files, or just those files used by the project. [Need some explanation around option 3 here].

Export   Zip Archive with all media files from the project
                Zip Archive with just the media files used in the project
                Zip archive suitable for yadda yadda yadda

If you want to export a SCORM package, you can choose to export SCORM 1.2 or SCORM 2004 packages. If you don't know which version of SCORM you need, the SCORM 1.2 package will work in most LMS and VLE systems.

Export   Scorm 1.2 Package
                Scorm 2004 Package.
---------------------------------------

Happy for any ideas / refinements? Also I can't remember what the point of option 3 was..? I'll see if I can find anything in my mail...

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] On Behalf Of Tom Reijnders
Sent: 10 May 2012 09:42
To: For Xerte technical developers
Subject: [Xerte-dev] Re: Export Code (commit of fixes)

Op 9-5-2012 12:33, Julian Tenney schreef:

Yep.

-----Original Message-----

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] On Behalf Of Tom Reijnders

Sent: 09 May 2012 11:30

To: For Xerte technical developers

Subject: [Xerte-dev] Re: Export Code (commit of fixes)

Difference between zip and local? Ehmmm... That's what I asked you guys

last week... :-)

I'll make a quick page first, then we can at least test the

functionality. UI shouldn't be that big of a problems afterwards. Agree?

Op 9-5-2012 11:53, Julian Tenney schreef:

Sorry, whats the difference between local and zip?

Otherwise, yes merge the two 1.2 exports.

I like the idea of a drop down list to select which one.

-----Original Message-----

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] On Behalf Of Tom Reijnders

Sent: 09 May 2012 10:52

To: For Xerte technical developers

Subject: [Xerte-dev] Re: Export Code (commit of fixes)

No, didn't do anything since last time yet. Current state is that there

are 5 exports:

Zip : will only export used media and will export jMolViewer and/or

mapstraction when used. Will not export the viewer because I need to

look at that.

Local zip: Same but with some changes to the urls

SCORM 1.2

SCORM 1.2 with extra meta data

SCORM 2004

As far as I can tell we can bundle the two SCORM exports. (Always use

SCORM with extra MetaData)

Tom

Op 9-5-2012 11:36, Julian Tenney schreef:

I don't want to see this splinter into a complicated page with loads of options. Ideally there might be some code that loops over each filename and sees if it exists anywhere in the xml and then exports it: that would cover hyperlinks too, and the user only has one option.

Otherwise we start ending up with a  slightly baffling local? Scorm? Scorm 2004? Full? Minimal? Deployment? When people just want to get something out.

Are these changes on the test server now?

-----Original Message-----

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] On Behalf Of Tom Reijnders

Sent: 05 May 2012 19:23

To: For Xerte technical developers

Subject: [Xerte-dev] Re: Export Code (commit of fixes)

That's why I proposed a small(er) Deployment Export and a Full export,

The Deployment export would be a new choice. That started the

export/download discussion.

Op 5-5-2012 20:13, Ron Mitchell schreef:

Hi

Only just catching up on discussions that I couldn't follow on Thurs&

Friday...

Personally I think export/download whatever it's called should include all

the media in the media folder not just used media. The reason being

sometimes files are uploaded via media and quota to simply link to via text

hyperlink (and that hyperlink might even be in a linked document rather than

a xerte page) or when trying different content as part of a particular page

or project, so just because these show as not used doesn't mean they might

not be required or used in future. I know that links like this might not

work in the exported project but I think an author naturally assumes that

export includes all their media and if it's a matter of reducing size they

can delete unwanted media via media&    quota before exporting. e.g. owner

should control what's exported and the reason for exporting might simply be

as a backup of the whole project.

HTH

Ron

-----Original Message-----

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] On Behalf Of Tom Reijnders

Sent: 03 May 2012 16:25

To: For Xerte technical developers

Subject: [Xerte-dev] Export Code (commit of fixes)

I just committed an update to the export code:

Fixes and additions for export

     - Should copy all the language .xml files from the top of the /language

folder

     - Should enable scorm2004 compliant export

     - Should copy JMolViewer and/or mapstraction folders if and only if those

models are used

     - Should ONLY export the used media, the rest is not copied

     - small fixes in htaccess.conf

     - small fixes in library/Xerte/Authentication/Db.php

     - get rid of superfuous scorm files

     - move MainPreloader.swf, rloObject.js and resources.swf out of scorm in

in their own folder (modules/xerte/export)

I wonder whether we should prevent exporting the thumbs folder as well...

David (Goodwin), I used the Db method and had to fix two typos. Comitted

thos as well. BTW, with the current code it is NOT that easy to set a

password in the database... ;-)

Tom

Op 3-5-2012 14:25, Pat Lockley schreef:

i couldn't see them failing, was just wondering if the scorm one might

conflict.

On Thu, May 3, 2012 at 1:20 PM, Tom Reijnders<reijnders at tor.nl><mailto:reijnders at tor.nl>     wrote:

I will, but they are really simple.

Op 3-5-2012 14:01, Pat Lockley schreef:

Tom, could you check the rewrite rules work - worried the scorm ones

might have hungry regexs?

On Thu, May 3, 2012 at 12:57 PM, David Goodwin<david at palepurple.co.uk><mailto:david at palepurple.co.uk>

     wrote:

On 3 May 2012, at 12:48, Pat Lockley wrote:

i like to leave the odd bug in to encourage other developers

Nice.... thanks for making me laugh :)

David.

Pale Purple Ltd.  (Company No: 5580814) 'Business Web Application

Development and Training in PHP'

http://www.palepurple.co.uk

Office: 0845 0046746     Mobile: 07792380669

Follow us on Twitter: @PalePurpleLtd

_______________________________________________

Xerte-dev mailing list

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:

you are advised to perform your own checks. Email communications

with the University of Nottingham may be monitored as permitted by

UK legislatio

_______________________________________________

Xerte-dev mailing list

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:

you are advised to perform your own checks. Email communications

with the University of Nottingham may be monitored as permitted by UK

legislation.

--

--

Tom Reijnders

TOR Informatica

Chopinlaan 27

5242HM Rosmalen

Tel: 073 5226191

Fax: 073 5226196

_______________________________________________

Xerte-dev mailing list

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

you are advised to perform your own checks. Email communications with

the University of Nottingham may be monitored as permitted by UK

legislation.

--

--

Tom Reijnders

TOR Informatica

Chopinlaan 27

5242HM Rosmalen

Tel: 073 5226191

Fax: 073 5226196

_______________________________________________

Xerte-dev mailing list

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

http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev

--

--

Tom Reijnders

TOR Informatica

Chopinlaan 27

5242HM Rosmalen

Tel: 073 5226191

Fax: 073 5226196

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>

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: