[Xerte-dev] Re: Option 3

Julian Tenney Julian.Tenney at nottingham.ac.uk
Fri May 11 10:32:26 BST 2012


Do we need to have the option to 'convert to local links'. That, as we have demonstrated to ourselves, is not FWS.


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:23
To: 'For Xerte technical developers'
Subject: [Xerte-dev] Re: Option 3


Just been having another look at what we have right now and is on the test install. Why not stick with that and in that order but as Tom suggested last night replace option 3 with a checkbox e.g. convert to local links where possible?



[cid:image001.jpg at 01CD2F61.5C347F90]



-----Original Message-----
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:12
To: 'For Xerte technical developers'
Subject: [Xerte-dev] Re: Option 3



> I take it this is just URLs linked to on <ahref="blah">? So in option 1,

links point back to the originating server? Have I got this right?<



Yep I think so - haven't checked if it converts a similar link added to the

browse for media field wrapped with '' but same thing anyway.



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

From: 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:58

To: For Xerte technical developers

Subject: [Xerte-dev] Re: Option 3



Ahh, I get it now, it's because the paths are different in toolkits than in

xerte.



I take it this is just URLs linked to on <ahref="blah">? So in option 1,

links point back to the originating server? Have I got this right?



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

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 09:02

To: 'For Xerte technical developers'

Subject: [Xerte-dev] Re: Option 3



As far as I can tell it does the opposite! Read my responses last night - it

changes any full url's to assets in the same lo to local links. Any urls to

things outside of the same lo remain full url's.



The option 1 export retains full url's regardless.



HTH

Ron



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

From: 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 08:52

To: For Xerte technical developers

Subject: [Xerte-dev] Option 3



Trying to shed some light on that option 3 export: here's what I've been

able to find in my mail - there's a thread about it.



It seems we wanted to export and leave the media on the exporting server,

and then have the piece link to them and include them from there in some

situations. Is that what option 3 does? Generate an output with hardcoded

urls pointing back to the exporting server?



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

From: Tenney Julian

Sent: 05 March 2009 15:04

To: Julian Tenney; RonM; Patrick Lockley

Subject: RE: Testing Request



Hmm. Thinking it thorough a bit more, I'm not sure how we could easily make

that work. We can create relative paths, but those paths are different when

ran as a standalone exported piece than when ran in toolkits.



I suppose if you leave the full path in there, then the files will till get

served from the original server if there is connectivity.





_______________________________________________

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



_______________________________________________

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/20120511/dc402c81/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 26370 bytes
Desc: image001.jpg
URL: <http://lists.nottingham.ac.uk/pipermail/xerte-dev/attachments/20120511/dc402c81/attachment-0001.jpg>


More information about the Xerte-dev mailing list