[Xerte-dev] Re: Question about workflow when working with the Xerte branch code

[Ron Mitchell]

Hi John
I suspect everyone works slightly differently so I'm not sure there's a definitive answer but I'll summarise what I tend to do...

Checkout XOT and Xerte svn's to local copies on ext HDD
Export XOT to one or more localhost installations and test locally
Where appropriate also maintain a production and test install on live servers e.g. for testing updates on live server after first testing locally
Copy any changes back to local svn files and commit from there
For Xerte 2 again I tend to work with an exported copy and also export the runtime folder to the local programme files installation
You don't need Flex for Xerte 2 - just Xerte desktop and perhaps your chosen script editor. Obviously if you plan to make changes to the various .fla files you'll need Flash
Xerte 3 is a different kettle of fish but It's only really Julian who messes with that! ;-)
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 Smith, John
Sent: 20 October 2012 16:26
To: xerte-dev at lists.nottingham.ac.uk
Subject: [Xerte-dev] Question about workflow when working with the Xerte branch code
Importance: High

Hi,

Looking for a bit of advice here about how you all work on developing the trunk code.

I've only been working on the Xenith code so far, but have just checked it out and then copied to the webroot so that I can run it from localhost. However when it comes to XOT there's slightly more needs done to take care of permissions and possibly update to the database. Now I'm going to have xot installed on a server back in Glasgow but want to work on improving the code if required and this is where i'm wondering what other people do...

Do you check the source out of the SVN straight onto a server (or to a laptop/desktop to work on and copy from there to the server) and then what do you do each time you do this to make sure everything still runs? I'm assuming that most people will have a stable production server running the branch and then have a development one either on the same server or locally on a desktop/laptop - am I right?

Also, regarding desktop Xerte, what tools do I need to run/compile the source for this? Just Flex or anything else?

I'd rather get this right from the start so that I can spend more time developing rather than debugging my setup problems so any advice welcome!!

Regards,

John Smith | Learning Technologist
Room A251, Govan Mbeki Building | School of Health & Life Sciences | Glasgow Caledonian University Cowcaddens Road | Glasgow | G4 0BA

Glasgow Caledonian University is a registered Scottish charity, number SC021474

Winner: Times Higher Education’s Widening Participation Initiative of the Year 2009 and Herald Society’s Education Initiative of the Year 2009.
http://www.gcu.ac.uk/newsevents/news/bycategory/theuniversity/1/name,6219,en.html

Winner: Times Higher Education’s Outstanding Support for Early Career Researchers of the Year 2010, GCU as a lead with Universities Scotland partners.
http://www.gcu.ac.uk/newsevents/news/bycategory/theuniversity/1/name,15691,en.html
_______________________________________________
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.