<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<div><br></div><div>Absolutely.</div><div>AW had a very ugly loading screen so I would set the embedding div height to 0 until a js function call on page 1 set it to the correct size.</div><div><br></div><div><br></div><div><div id="SkyDrivePlaceholder"></div>> Date: Wed, 9 May 2012 20:53:34 +0100<br>> From: patrick.lockley@googlemail.com<br>> To: xerte-dev@lists.nottingham.ac.uk<br>> Subject: [Xerte-dev] Re: Proof of concept test<br>> <br>> Well you could do it on page title?<br>> <br>> if(startpage){<br>> <br>> Cover LO while LO loads<br>> move to startpage<br>> uncover LO<br>> <br>> }<br>> <br>> <br>> On Wed, May 9, 2012 at 8:24 PM, Ron Mitchell <ronm@mitchellmedia.co.uk> wrote:<br>> > firstly yes I always encourage people to think granular and not build one<br>> > big LO but sometimes original plans change and even with a relatively small<br>> > LO linking to a specific page can be very useful.<br>> ><br>> > It obviously hasn't ever been available in XOT but for me the simplest would<br>> > be if authors could simply append something like &page=5 or just #page=5 to<br>> > link to page 5. e.g. similar to what you can do with pdf's<br>> > http://www.example.com/myfile.pdf#page=5<br>> ><br>> > Before anyone says "that's not reliable what happens when pages are moved<br>> > around" it's no different to other self-authored resources - the author<br>> > would know the implications of that and re-send or update the deep link if<br>> > pages are re-ordered and in most cases would only be sending deep links to<br>> > established resources unlikely to change or when the deep link is an<br>> > individualised point inWel time reference rather than needing to be a permalink<br>> > etc.<br>> ><br>> > -----Original Message-----<br>> > From: xerte-dev-bounces@lists.nottingham.ac.uk<br>> > [mailto:xerte-dev-bounces@lists.nottingham.ac.uk] On Behalf Of Pat Lockley<br>> > Sent: 09 May 2012 20:05<br>> > To: For Xerte technical developers<br>> > Subject: [Xerte-dev] Re: Proof of concept test<br>> ><br>> > i can't recall where the deep link is shown? how does a teacher find it?<br>> ><br>> > On Wed, May 9, 2012 at 8:01 PM, Dave Burnett <d_b_burnett@hotmail.com><br>> > wrote:<br>> >><br>> >> One objection:<br>> >> Your deep linking examples "moodle resources, pages with websites,<br>> >> specific blog posts etc" are support materials correct?<br>> >><br>> >> So in the flow of a coherent LO, you can pop up some backup or<br>> >> exploratory material.<br>> >> They generally aren't "Abandon the current learning object, jump to<br>> >> this blog post and continue the lesson from there".<br>> >><br>> >> I see the use of being able to send a link via email.<br>> >> As you say, it's all in context. The needs hierarchy. :-)<br>> >><br>> >> Dave<br>> >><br>> >><br>> >><br>> >> ________________________________<br>> >> From: ronm@mitchellmedia.co.uk<br>> >> To: xerte-dev@lists.nottingham.ac.uk<br>> >> Date: Wed, 9 May 2012 19:47:38 +0100<br>> >><br>> >> Subject: [Xerte-dev] Re: Proof of concept test<br>> >><br>> >> I demonstrated the online copy of the test file today as an example of<br>> >> possible features of the upcoming 1.8 release and as expected<br>> >> delegates thought it very useful. In my experience it's something<br>> >> people have wanted for a long time e.g. they often use deep linking to<br>> >> moodle resources, pages with websites, specific blog posts etc and<br>> >> particularly in an FE and ACL context and have often voiced<br>> >> frustration at not being able to do so with Xerte LO's. There are<br>> >> limitations in having to say "follow this link to the first page of<br>> >> this LO and then navigate to page x" especially in areas such a SFL<br>> >> etc. The ability to send a direct link via email or to add a link in<br>> >> another resource to a page within an LO would be very useful in many<br>> >> cases - if it's possible and reliable. It's not a game changer but useful<br>> > on the occasions where it might be used for a particular reason e.g.<br>> >> differentiation and for instance if you take the 560 example<br>> >> http://www.nottingham.ac.uk/toolkits/play_560 there are many occasions<br>> >> where it would be useful to link to a specific page when providing CPD<br>> >> support etc.<br>> >><br>> >><br>> >><br>> >> So if it's unreliable or likely to delay the release then in that<br>> >> context it's not so important but if it can be made to work in a<br>> >> satisfactory way then I can see it being a very useful including the<br>> >> ability to link to new page types within an updated 560 example when<br>> >> highlighting what's new in 1.8.<br>> >><br>> >><br>> >><br>> >> From: xerte-dev-bounces@lists.nottingham.ac.uk<br>> >> [mailto:xerte-dev-bounces@lists.nottingham.ac.uk] On Behalf Of Dave<br>> >> Burnett<br>> >> Sent: 09 May 2012 13:08<br>> >> To: xerte-dev@lists.nottingham.ac.uk<br>> >> Subject: [Xerte-dev] Re: Proof of concept test<br>> >><br>> >><br>> >><br>> >><br>> >><br>> >> Always value in pure research, but just to be a negative Nellie, I've<br>> >> real doubts about a feature like this actually being used, even if the<br>> >> technical issues are addressed.<br>> >><br>> >><br>> >><br>> >> Authorware had "jumpfile", which seamlessly segued between files.<br>> >><br>> >> It was used if you had a router style architecture.<br>> >><br>> >><br>> >><br>> >> Don't remember anyone asking for the ability to jump to a specific page.<br>> >><br>> >> That sounds like a glossary or definition type structure requirement<br>> >> and there's easier ways to accomplish those.<br>> >><br>> >> And without the ability to return to the same place in the calling<br>> >> module (Call and Return), I don't see huge numbers of folks using it.<br>> >><br>> >><br>> >><br>> >> But like I said, futzing around is a great way to stumble across other<br>> >> nuggets.<br>> >><br>> >> :-)<br>> >><br>> >><br>> >><br>> >><br>> >><br>> >> ________________________________<br>> >><br>> >> Date: Wed, 9 May 2012 12:23:32 +0100<br>> >> From: johnathan.kemp@ntlworld.com<br>> >> To: xerte-dev@lists.nottingham.ac.uk<br>> >> Subject: [Xerte-dev] Re: Proof of concept test<br>> >><br>> >> According to my Xerte desktop installation it generates a linkID and<br>> >> not a pageID<br>> >><br>> >><br>> >><br>> >> phew you had me worried there for a minute :-)<br>> >><br>> >><br>> >><br>> >> I know you have referred to "deep linking" before but I was never sure<br>> >> what you meant.<br>> >><br>> >><br>> >><br>> >> The idea here was to create a link using a value known to the learning<br>> >> object author.<br>> >><br>> >><br>> >><br>> >> It was just an experiment. Maybe if it works without the delay in XOT<br>> >> then it would be more acceptable.<br>> >><br>> >><br>> >><br>> >> I can shorten the delay in Xerte but in the absence of a means of<br>> >> knowing when the page array has been fully populated it will always be<br>> >> guess work as to how short the delay can be.<br>> >><br>> >><br>> >><br>> >> Kind regards<br>> >><br>> >><br>> >><br>> >> Johnathan<br>> >><br>> >><br>> >><br>> >> On 9 May 2012 12:05, Julian Tenney <Julian.Tenney@nottingham.ac.uk> wrote:<br>> >><br>> >> No, the wizard automatically produces a pageID in the xml – you’ll<br>> >> have seen it I’m sure. The intention for this was to facilitate deep<br>> > linking, i.e.<br>> >> ?pageID=321234524<br>> >><br>> >><br>> >><br>> >> But when Pat and I tried to get it to work nicely we couldn’t and parked<br>> > it.<br>> >> It may well be we hit the same issue you have hit: the need for the<br>> >> delay, which I don’t think is acceptable to the end user.<br>> >><br>> >><br>> >><br>> >> From: xerte-dev-bounces@lists.nottingham.ac.uk<br>> >> [mailto:xerte-dev-bounces@lists.nottingham.ac.uk] On Behalf Of Kemp<br>> >> Johnathan<br>> >> Sent: 09 May 2012 11:54<br>> >><br>> >><br>> >> To: For Xerte technical developers<br>> >> Subject: [Xerte-dev] Re: Proof of concept test<br>> >><br>> >><br>> >><br>> >> The javascript routine used matches a name to data, so you could just<br>> >> as easily use ?name=titlePage as you could ?pageID=titlePage<br>> >><br>> >><br>> >><br>> >> The problem with using name is that the page name is more likely to be<br>> >> "Title Page" and the use of spaces might cause a problem.<br>> >><br>> >><br>> >><br>> >> It was never intended that this should be an alternative routing<br>> >> internally within a learning object to another page in that learning<br>> >> object. It was only intended to be a means of opening a different<br>> >> learning object, which you can do already using a URL. The only<br>> >> difference here was that someone on one of the postings was lamenting<br>> >> the inability to open a new learning object at a specific page.<br>> >><br>> >><br>> >><br>> >> The version for XOT would have to use the extXML which, from memory,<br>> >> did not suffer the need for a delay before it could be used. But I am<br>> >> quite happy to leave it out of this release as once people were happy<br>> >> it would work OK then it could be added later.<br>> >><br>> >><br>> >><br>> >> I need a little time to finish the XOT demo version anyway and right<br>> >> now I am focusing on an update to the scenario page to make it easier<br>> >> to implement scenarios like the Farmer, the Goose, the Fox and the Bag<br>> >> of Grain on one side of the river.<br>> >><br>> >><br>> >><br>> >> Kind regards<br>> >><br>> >><br>> >><br>> >> Johnathan<br>> >><br>> >><br>> >><br>> >> On 9 May 2012 10:31, Julian Tenney <Julian.Tenney@nottingham.ac.uk> wrote:<br>> >><br>> >> The need for that delay may well be why we decided to leave it last time.<br>> >> It’s disorienting to see the page for that long and then suddenly be<br>> >> moved on. Let’s leave this for another time.<br>> >><br>> >><br>> >><br>> >> From: xerte-dev-bounces@lists.nottingham.ac.uk<br>> >> [mailto:xerte-dev-bounces@lists.nottingham.ac.uk] On Behalf Of Kemp<br>> >> Johnathan<br>> >> Sent: 05 May 2012 10:17<br>> >><br>> >><br>> >> To: For Xerte technical developers<br>> >> Subject: [Xerte-dev] Re: Proof of concept test<br>> >><br>> >><br>> >><br>> >> The delay is because I have had to put a timer in to give Xerte the<br>> >> time to build the rootIcon.pages array - it's a bit of guess work as<br>> >> to how long I need to give it. It would be nice if the onInit event<br>> >> didn't fire until the array had completed being built, then I could<br>> >> remove the timer and the delay would be reduced to the minimum required.<br>> >><br>> >><br>> >><br>> >> In XOT you use a different array so I think the time delay will be<br>> >> insignificant as if I recall correctly the array was already fully<br>> >> available.<br>> >><br>> >><br>> >><br>> >> I'll run some further tests in XOT now that I have the javascript<br>> >> sorted out and then post something for you to try out.<br>> >><br>> >><br>> >><br>> >> Kind regards<br>> >><br>> >><br>> >><br>> >> Johnathan<br>> >><br>> >><br>> >><br>> >> On 5 May 2012 09:44, Ron Mitchell <ronm@mitchellmedia.co.uk> wrote:<br>> >><br>> >> Working fine here too<br>> >> http://vle.jisctechdis.ac.uk/xot/urlTest/index.htm?pageID=menu<br>> >><br>> >> Win 7 64bit<br>> >><br>> >> IE 8.0<br>> >><br>> >> Chrome 18.0<br>> >><br>> >> Safari 5.1.5<br>> >><br>> >> Opera 10.60<br>> >><br>> >> Firefox 12.0<br>> >><br>> >><br>> >><br>> >> Great job Jonathan this will be a very popular feature.<br>> >><br>> >><br>> >><br>> >> From: xerte-dev-bounces@lists.nottingham.ac.uk<br>> >> [mailto:xerte-dev-bounces@lists.nottingham.ac.uk] On Behalf Of Tom<br>> >> Reijnders<br>> >> Sent: 05 May 2012 08:23<br>> >> To: For Xerte technical developers<br>> >> Subject: [Xerte-dev] Re: Proof of concept test<br>> >><br>> >><br>> >><br>> >> Working fine here (although with a noticeable lag, first page is shown<br>> >> and after 1 second the menu page is opened)<br>> >><br>> >> Windows 7, 64 bit IE9, FF12, Chrome 18<br>> >><br>> >> Op 4-5-2012 23:36, Kemp Johnathan schreef:<br>> >><br>> >> Hello Everyone,<br>> >><br>> >><br>> >><br>> >> I have been working (between beta version stuff) on a means of making<br>> >> it possible to open a Xerte project at a specific page, rather than<br>> >> always have them open at the title page.<br>> >><br>> >><br>> >><br>> >> Attached is a simple 3 page desktop Xerte project as a proof of concept.<br>> >><br>> >><br>> >><br>> >> Do not open it in Xerte (at least until you have finished testing it!)<br>> >> If you publish the project, in Xerte, your local copy of rloObject.js<br>> >> will overwrite the one in the project and the code that supports the<br>> >> redirection will be lost.<br>> >><br>> >><br>> >><br>> >> Would you mind unzipping it and then opening index.htm in a web<br>> >> browser - not Xerte.<br>> >><br>> >><br>> >><br>> >> For it to work you will need to set up the folder in which you place<br>> >> it as a trusted location in the Flash player settings (otherwise<br>> >> javascript calls will not work).<br>> >><br>> >><br>> >><br>> >> It should open at a title page.<br>> >><br>> >><br>> >><br>> >> Then add to the url in your browser<br>> >><br>> >><br>> >><br>> >> ?pageID=menu<br>> >><br>> >><br>> >><br>> >> and press enter to reload the page.<br>> >><br>> >><br>> >><br>> >> After a short delay the project should redirect from the title page to<br>> >> the menu page.<br>> >><br>> >><br>> >><br>> >> I have tested this in Firefox, IE8, and Opera.<br>> >><br>> >><br>> >><br>> >> If anyone has other browsers at their disposal I would be keen to know<br>> >> if the redirection works. e.g. Chrome, Safari,<br>> >><br>> >><br>> >><br>> >> Should you examine the project the key stuff that makes it work is a<br>> >> function at the end of rlsObject.js and some code running off the<br>> >> onInitHandler interaction in the entry frame. Because<br>> >> rootIcon.pages.length has not finished being built when the onInit<br>> >> event fires I have added a timer to create a delay to allow time for<br>> >> the array to be built - hence the delay before redirection takes place.<br>> >><br>> >><br>> >><br>> >> Should this prove reliable in your testing I believe the same approach<br>> >> should be applicable to XOT (albeit using a different array to source<br>> >> the page information)<br>> >><br>> >><br>> >><br>> >> Kind regards<br>> >><br>> >><br>> >><br>> >> Johnathan<br>> >><br>> >><br>> >><br>> >><br>> >><br>> >><br>> >><br>> >> This message and any attachment are intended solely for the addressee<br>> >> and may contain confidential information. If you have received this<br>> >> message in error, please send it back to me, and immediately delete<br>> >> it. Please do not use, copy or disclose the information contained in<br>> >> this message or in any attachment. Any views or opinions expressed by<br>> >> the author of this email do not necessarily reflect the views of the<br>> > University of Nottingham.<br>> >><br>> >> This message has been checked for viruses but the contents of an<br>> >> attachment may still contain software viruses which could damage your<br>> > computer system:<br>> >> you are advised to perform your own checks. Email communications with<br>> >> the University of Nottingham may be monitored as permitted by UK<br>> > legislation.<br>> >><br>> >><br>> >><br>> >> _______________________________________________<br>> >><br>> >> Xerte-dev mailing list<br>> >><br>> >> Xerte-dev@lists.nottingham.ac.uk<br>> >><br>> >> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev<br>> >><br>> >><br>> >><br>> >> This message and any attachment are intended solely for the addressee<br>> >> and may contain confidential information. If you have received this<br>> >> message in error, please send it back to me, and immediately delete<br>> >> it. Please do not use, copy or disclose the information contained in<br>> >> this message or in any attachment. Any views or opinions expressed by<br>> >> the author of this email do not necessarily reflect the views of the<br>> > University of Nottingham.<br>> >><br>> >><br>> >><br>> >> This message has been checked for viruses but the contents of an<br>> >> attachment<br>> >><br>> >> may still contain software viruses which could damage your computer<br>> > system:<br>> >><br>> >> you are advised to perform your own checks. Email communications with<br>> >> the<br>> >><br>> >> University of Nottingham may be monitored as permitted by UK legislation.<br>> >><br>> >><br>> >><br>> >><br>> >><br>> >> --<br>> >><br>> >> --<br>> >><br>> >><br>> >><br>> >><br>> >><br>> >> Tom Reijnders<br>> >><br>> >> TOR Informatica<br>> >><br>> >><br>> >><br>> >> Chopinlaan 27<br>> >><br>> >><br>> >><br>> >> 5242HM Rosmalen<br>> >><br>> >> Tel: 073 5226191<br>> >><br>> >> Fax: 073 5226196<br>> >><br>> >><br>> >><br>> >><br>> >> _______________________________________________<br>> >> Xerte-dev mailing list<br>> >> Xerte-dev@lists.nottingham.ac.uk<br>> >> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev<br>> >><br>> >> This message and any attachment are intended solely for the addressee<br>> >> and may contain confidential information. If you have received this<br>> >> message in error, please send it back to me, and immediately delete<br>> >> it. Please do not use, copy or disclose the information contained in<br>> >> this message or in any attachment. Any views or opinions expressed by<br>> >> the author of this email do not necessarily reflect the views of the<br>> > University of Nottingham.<br>> >><br>> >> This message has been checked for viruses but the contents of an<br>> >> attachment may still contain software viruses which could damage your<br>> > computer system:<br>> >> you are advised to perform your own checks. Email communications with<br>> >> the University of Nottingham may be monitored as permitted by UK<br>> > legislation.<br>> >><br>> >><br>> >><br>> >><br>> >> _______________________________________________<br>> >> Xerte-dev mailing list<br>> >> Xerte-dev@lists.nottingham.ac.uk<br>> >> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev<br>> >><br>> >> This message and any attachment are intended solely for the addressee<br>> >> and may contain confidential information. If you have received this<br>> >> message in error, please send it back to me, and immediately delete<br>> >> it. Please do not use, copy or disclose the information contained in<br>> >> this message or in any attachment. Any views or opinions expressed by<br>> >> the author of this email do not necessarily reflect the views of the<br>> > University of Nottingham.<br>> >><br>> >> This message has been checked for viruses but the contents of an<br>> >> attachment may still contain software viruses which could damage your<br>> > computer system:<br>> >> you are advised to perform your own checks. Email communications with<br>> >> the University of Nottingham may be monitored as permitted by UK<br>> > legislation.<br>> >><br>> >><br>> >><br>> >><br>> >> _______________________________________________<br>> >> Xerte-dev mailing list<br>> >> Xerte-dev@lists.nottingham.ac.uk<br>> >> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev<br>> >><br>> >> This message and any attachment are intended solely for the addressee<br>> >> and may contain confidential information. If you have received this<br>> >> message in error, please send it back to me, and immediately delete<br>> >> it. Please do not use, copy or disclose the information contained in<br>> >> this message or in any attachment. Any views or opinions expressed by<br>> >> the author of this email do not necessarily reflect the views of the<br>> > University of Nottingham.<br>> >><br>> >> This message has been checked for viruses but the contents of an<br>> >> attachment may still contain software viruses which could damage your<br>> > computer system:<br>> >> you are advised to perform your own checks. Email communications with<br>> >> the University of Nottingham may be monitored as permitted by UK<br>> > legislation.<br>> >><br>> >><br>> >><br>> >> _______________________________________________ Xerte-dev mailing list<br>> >> Xerte-dev@lists.nottingham.ac.uk<br>> >> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev This message<br>> >> and any attachment are intended solely for the addressee and may<br>> >> contain confidential information. If you have received this message in<br>> >> error, please send it back to me, and immediately delete it. Please do<br>> >> not use, copy or disclose the information contained in this message or<br>> >> in any attachment. Any views or opinions expressed by the author of<br>> >> this email do not necessarily reflect the views of the University of<br>> >> Nottingham. This message has been checked for viruses but the contents<br>> >> of an attachment may still contain software viruses which could damage<br>> >> your computer system: you are advised to perform your own checks.<br>> >> Email communications with the University of Nottingham may be monitored as<br>> > permitted by UK legislation.<br>> >><br>> >><br>> >> _______________________________________________ Xerte-dev mailing list<br>> >> Xerte-dev@lists.nottingham.ac.uk<br>> >> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev This message<br>> >> and any attachment are intended solely for the addressee and may<br>> >> contain confidential information. If you have received this message in<br>> >> error, please send it back to me, and immediately delete it. Please do<br>> >> not use, copy or disclose the information contained in this message or<br>> >> in any attachment. Any views or opinions expressed by the author of<br>> >> this email do not necessarily reflect the views of the University of<br>> >> Nottingham. This message has been checked for viruses but the contents<br>> >> of an attachment may still contain software viruses which could damage<br>> >> your computer system: you are advised to perform your own checks.<br>> >> Email communications with the University of Nottingham may be monitored as<br>> > permitted by UK legislation.<br>> >><br>> >> _______________________________________________<br>> >> Xerte-dev mailing list<br>> >> Xerte-dev@lists.nottingham.ac.uk<br>> >> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev<br>> >><br>> >> This message and any attachment are intended solely for the addressee<br>> >> and may contain confidential information. If you have received this<br>> >> message in error, please send it back to me, and immediately delete<br>> >> it. Please do not use, copy or disclose the information contained in<br>> >> this message or in any attachment. Any views or opinions expressed by<br>> >> the author of this email do not necessarily reflect the views of the<br>> > University of Nottingham.<br>> >><br>> >> This message has been checked for viruses but the contents of an<br>> >> attachment may still contain software viruses which could damage your<br>> > computer system:<br>> >> you are advised to perform your own checks. Email communications with<br>> >> the University of Nottingham may be monitored as permitted by UK<br>> > legislation.<br>> >><br>> >><br>> ><br>> > _______________________________________________<br>> > Xerte-dev mailing list<br>> > Xerte-dev@lists.nottingham.ac.uk<br>> > http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev<br>> ><br>> ><br>> > _______________________________________________<br>> > Xerte-dev mailing list<br>> > Xerte-dev@lists.nottingham.ac.uk<br>> > http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev<br>> <br>> _______________________________________________<br>> Xerte-dev mailing list<br>> Xerte-dev@lists.nottingham.ac.uk<br>> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev<br></div> </div></body>
</html>