[Xerte-dev] Re: Exporting Deployment Zip
Julian Tenney
Julian.Tenney at nottingham.ac.uk
Tue Jul 17 14:49:31 BST 2012
OK, let's leave it. It's got us this far.
-----Original Message-----
From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
Sent: 17 July 2012 14:49
To: For Xerte technical developers
Subject: [Xerte-dev] Re: Exporting Deployment Zip
don't delete the gif as it is used elsewhere
i am not sure how easy getting the size of the template is - perhaps
cobble something together from one of the publish scripts already
(must be a check in website_code/php/publish)
On Tue, Jul 17, 2012 at 2:40 PM, Julian Tenney
<Julian.Tenney at nottingham.ac.uk> wrote:
> if(data.size != public.size)
> OK, let's do that.
>
> Or we could just leave it, as it's fairly obvious what's happened. But if data.size and public.size are readily available to the code, then a message box would be nice and friendly.
>
> -----Original Message-----
> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
> Sent: 17 July 2012 14:33
> To: For Xerte technical developers
> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>
> i wondered about this, but I think some people want an export just to
> work on data - no harm in making a publish, but why bother?
>
> I could see a case for if(data.size != public.size) warn people message
>
> On Tue, Jul 17, 2012 at 2:31 PM, Julian Tenney
> <Julian.Tenney at nottingham.ac.uk> wrote:
>> Related thing: should we force an invisible publish if you export? Export implies 'I want this published' to me, so why not just publish when exporting?
>>
>>
>> -----Original Message-----
>> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
>> Sent: 17 July 2012 13:51
>> To: For Xerte technical developers
>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>
>> ok change the if to be !="Private" then
>>
>> On Tue, Jul 17, 2012 at 1:43 PM, Ron Mitchell <ronm at mitchellmedia.co.uk> wrote:
>>> That does seem to fix it. But why does it require the project to be public
>>> to be able to publish via that route? I know that's always been the case but
>>> I think it should be possible to publish without needing to be public.
>>>
>>> -----Original Message-----
>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
>>> Sent: 17 July 2012 13:31
>>> To: For Xerte technical developers
>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>
>>> the problem is in here
>>>
>>> http://code.google.com/p/xerteonlinetoolkits/source/browse/trunk/website_cod
>>> e/php/properties/publish.php
>>>
>>> there is a load of old code from the WebCT powerlink left in
>>>
>>> if you remove lines 86-94 and 98-102 it might work
>>>
>>> On Tue, Jul 17, 2012 at 1:24 PM, Julian Tenney
>>> <Julian.Tenney at nottingham.ac.uk> wrote:
>>>> Fair enough. We've got the wind in our sails now, so if someone else
>>>> can have a look, then we'll take it off your hands.
>>>>
>>>>
>>>>
>>>> If the problem is as simple as un-hiding the button it shouldn't be
>>>> too hard.
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat
>>>> Lockley
>>>> Sent: 17 July 2012 13:24
>>>>
>>>>
>>>> To: For Xerte technical developers
>>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> i can fix this, but the reason I half don't want to is I have shed
>>>> loads of other stuff to work on
>>>>
>>>> On Tue, Jul 17, 2012 at 1:14 PM, Ron Mitchell
>>>> <ronm at mitchellmedia.co.uk>
>>>> wrote:
>>>>
>>>> I've compared how this currently works with 1.8 and previous versions
>>>> but wouldn't really know where to start to fix it...
>>>>
>>>>
>>>>
>>>> In previous versions and in 1.8 clicking publish via the editor window
>>>> or by clicking ok when prompted to publish after closing the editor
>>>> window works fine and works whether the project is set to public or
>>>> not. e.g. works as it should.
>>>>
>>>>
>>>>
>>>> However in 1.8 when clicking publish with the project selected in the
>>>> workspace the publishproperties window opens but the publish button is
>>>> inactive if the project is private and when set to public the publish
>>>> button disappears altogether.
>>>>
>>>>
>>>>
>>>> In 1.7 when clicking publish with the project selected in the
>>>> workspace the publishproperties window opens and the publish button is
>>>> inactive if the project is private but when set to public the publish
>>>> button is then active and works.
>>>>
>>>>
>>>>
>>>> I think publish should work whether the project is public or not - as
>>>> it does when publishing via the editor window. e.g. the owner might
>>>> want to export and deploy outside of toolkits rather than making
>>>> public from toolkits.
>>>>
>>>>
>>>>
>>>> Not sure why the button now disappears when the LO is made public in 1.8.
>>>> However opening the project in the editor and publishing from there
>>>> works fine.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Julian
>>>> Tenney
>>>> Sent: 17 July 2012 12:45
>>>>
>>>>
>>>> To: For Xerte technical developers
>>>>
>>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> Ron, is it within your skills / time constraints to have a look a this
>>>> publishing stuff? This seems like the big outstanding issue on the
>>>> toolkits side.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Ron
>>>> Mitchell
>>>> Sent: 12 July 2012 11:21
>>>> To: 'For Xerte technical developers'
>>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> Have been testing further and don't think this is a xampp issue...
>>>>
>>>>
>>>>
>>>> Create a project click publish in the editor - export works fine
>>>>
>>>> Create a project click play but not publish in the editor, close the
>>>> editor and click ok when prompted to publish - export works fine
>>>>
>>>> Create a project click play but not publish in the editor, close the
>>>> editor and click cancel when prompted to publish - LO isn't published
>>>> so export creates a zip but when viewing LO is empty or doesn't
>>>> contain latest changes
>>>> - this is as expected
>>>>
>>>>
>>>>
>>>> Create a project click play but not publish in the editor, close the
>>>> editor and click cancel when prompted to publish then click publish
>>>> button in workspace - panel opens but publish button is greyed out -
>>>> so if exported at this stage LO is empty or latest changes not shown.
>>>> This greyed out publish button in the pop-up panel is the same in 1.7.
>>>> re-edit the project and click publish in the editor - export is fine.
>>>>
>>>>
>>>>
>>>> So I wonder if this issue has always been there or at least for quite
>>>> a while?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Julian
>>>> Tenney
>>>> Sent: 12 July 2012 10:52
>>>> To: For Xerte technical developers
>>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> We still need to test it on Xampp.
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Ron
>>>> Mitchell
>>>> Sent: 12 July 2012 10:49
>>>> To: 'For Xerte technical developers'
>>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> The test install is updated with revision 373 now and deployment
>>>> export works fine for me.
>>>>
>>>>
>>>>
>>>> Fay - I've sent you a link to the google doc offlist - because it's
>>>> set to allow anyone to edit and obviously the list archives are
>>>> public. Please all remember to initialize any entries and also to
>>>> confirm when issues are fixed.
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Julian
>>>> Tenney
>>>> Sent: 12 July 2012 10:41
>>>> To: For Xerte technical developers
>>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> Keep your own lists for now, and we'll put them somewhere common,
>>>> thanks,
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Fay
>>>> Cross
>>>> Sent: 12 July 2012 10:33
>>>> To: For Xerte technical developers
>>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> I'm just going through all the page types now and have found a few
>>>> small problems - are we emailing everything we find to the list or
>>>> putting them on the google doc somewhere? Where is that?
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Julian
>>>> Tenney
>>>> Sent: 12 July 2012 10:27
>>>> To: For Xerte technical developers
>>>> Cc: Alistair McNaught (Alistair.McNaught at HEAcademy.ac.uk)
>>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> Here's a good example of the level of detail we need to test. I create
>>>> a bullets page:
>>>>
>>>>
>>>>
>>>> The default for delay is 10 seconds. This doesn't seem appropriate for
>>>> a default.
>>>>
>>>> The label is confusing: what does Delay (in 0.1 seconds) mean?
>>>>
>>>> The gaps between the bullets on the page are too big, should be 20
>>>> pixels to be consistent with other spacing.
>>>>
>>>>
>>>>
>>>> And that's just bullets.
>>>>
>>>>
>>>>
>>>> Guys, we really need to test this properly. I don't know how we do
>>>> this, because we are all busy. But if we don't, we might as well not
>>>> have bothered.
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Julian
>>>> Tenney
>>>> Sent: 12 July 2012 10:17
>>>> To: For Xerte technical developers
>>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> OK, I'm making a list of the things I find that's wrong, because when
>>>> the list gets busy like this it's impossible to keep track of what's going
>>> on.
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat
>>>> Lockley
>>>> Sent: 12 July 2012 10:16
>>>> To: For Xerte technical developers
>>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> Sounds like a logic fail in the code (will check at lunch)
>>>>
>>>> On Thu, Jul 12, 2012 at 10:13 AM, Julian Tenney
>>>> <Julian.Tenney at nottingham.ac.uk> wrote:
>>>>
>>>> Yes, there was.
>>>>
>>>>
>>>>
>>>> Back to that publishing thing: if a project is private, I see a greyed
>>>> out publish button: if I set it to publics, there's no button
>>>>
>>>>
>>>>
>>>> Error! Filename not specified.
>>>>
>>>>
>>>>
>>>> Then after making publis
>>>>
>>>>
>>>>
>>>> Error! Filename not specified.
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat
>>>> Lockley
>>>> Sent: 12 July 2012 10:11
>>>>
>>>>
>>>> To: For Xerte technical developers
>>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> no, when you publish it creates a copy of data.xml in the folder for
>>>> that project in USER-FILES
>>>>
>>>> On Thu, Jul 12, 2012 at 10:06 AM, Julian Tenney
>>>> <Julian.Tenney at nottingham.ac.uk> wrote:
>>>>
>>>> The export folder?
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat
>>>> Lockley
>>>> Sent: 12 July 2012 10:03
>>>>
>>>>
>>>> To: For Xerte technical developers
>>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> well if there a publish.xml in the folder?
>>>>
>>>> On Thu, Jul 12, 2012 at 10:01 AM, Julian Tenney
>>>> <Julian.Tenney at nottingham.ac.uk> wrote:
>>>>
>>>> Told me it did.
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat
>>>> Lockley
>>>> Sent: 12 July 2012 10:01
>>>>
>>>>
>>>> To: For Xerte technical developers
>>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> Has it published?
>>>>
>>>> On Thu, Jul 12, 2012 at 9:58 AM, Julian Tenney
>>>> <Julian.Tenney at nottingham.ac.uk> wrote:
>>>>
>>>> This needs looking at. If I create a LO, add a page, preview, and quit
>>>> the wizard, I get prompted to publish. I say 'yes'.
>>>>
>>>>
>>>>
>>>> Then export fails.
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Julian
>>>> Tenney
>>>> Sent: 12 July 2012 09:52
>>>>
>>>>
>>>> To: For Xerte technical developers
>>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> Erm, silly question time, but when I click the publish button, I get
>>>> this
>>>> form: but there is no 'publish' button? So how do I publish it?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Error! Filename not specified.
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat
>>>> Lockley
>>>> Sent: 12 July 2012 09:49
>>>> To: For Xerte technical developers
>>>> Subject: [Xerte-dev] Re: Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> I think you fix it by making sure you publish the project before
>>>> exporting... (just a guess)
>>>>
>>>> On Thu, Jul 12, 2012 at 9:47 AM, Julian Tenney
>>>> <Julian.Tenney at nottingham.ac.uk> wrote:
>>>>
>>>> Same goes for all the export options. Tom, how do I fix this?
>>>>
>>>>
>>>>
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Julian
>>>> Tenney
>>>> Sent: 12 July 2012 09:45
>>>> To: For Xerte technical developers
>>>> Subject: [Xerte-dev] Exporting Deployment Zip
>>>>
>>>>
>>>>
>>>> I make a simple project, graphics and sound page: looks like this:
>>>>
>>>> Error! Filename not specified.
>>>>
>>>>
>>>>
>>>> Export a deployment zip, I get this:
>>>>
>>>> Error! Filename not specified.
>>>>
>>>>
>>>>
>>>> Not good. We need to test everything again now, please, I need
>>>> everyone's help, because if we start deploying stuff with problems
>>>> it's just going to be a massive PITA for everyone, and we'll lose people.
>>>>
>>>>
>>>>
>>>> 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
>>>>
>>>> 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
>>>>
>>>> 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
>>>>
>>>> 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.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 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
>>>>
>>>> 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
>>>>
>>>> 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
>>>>
>>>> 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
>>>>
>>>> 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
>>
>> _______________________________________________
>> 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
More information about the Xerte-dev
mailing list