EXELearning Tinkering Beneath the Awning

 27 June 13:44   = What is eXeLearning? =

    eXeLearning is a program to advice agents aftermath acquirements agreeable (courses) and deliver them online via web pages, and LMSs and offline via CDRoms.

    = Why tinker? =

    EXELearning is an accessible antecedent project. Adaptation 1 is bieng adjourned by the New Zealand Admiral of Apprenticeship up until 31 April 2006. Afterwards this of advance the activity will administer for added funding, but absolutely it will be association that will advice eXe to grow.

    = Move 1: Accepting the antecedent =

    The antecedent for exe can be begin on the exe SVN server. Youll charge an SVN applicant program in adjustment to download the source.

    For Windows users I acclaim using Tortoise SVN (http://tortoisesvn.tigris.org).

    1. Download and install Tortoise SVN.

    2. Make an abandoned binder alleged exe

    3. Appropriate bang the binder and baddest Tortoise SVN checkout

    4. In the URL type: http://exelearning.org/svn/exe/trunk

    5. Acute OK will make a archetype of the block antecedent cipher in a sub binder alleged trunk

    Later you can get additional updates to the antecedent by appropriate beat the block binder and selecting Tortoise SVN update.

    Most linux distributions appear with an SVN command band client.

    1. In your home agenda create a binder alleged projects or antecedent or plan or whatever, (Mine is ~/work/projects).

    2. Change to that agenda (eg. cd ~/work/projects)

    3. Type: svn co http://exelearning.org/svn/exe/trunk exe

    This will make subdirectory alleged exe (~/work/projects/exe in my case) absolute the source.

    = Get the dependencies =

    Please advice in bushing out this section. Basically dependencies are:

    python

    twisted

    nevow

    firefox

    emerge python askance nevow

    = Application Askance =

    Twisted 2.0 doesnt accept some of the appearance that exe needs, so we charge to add them.

    cd ~/work/projects/exe

    patch /usr/lib/python2.4/site-packages/twisted/spread/jelly.py patches/jelly.patch

    = Run exe from antecedent =

    If you accept a bifold adaptation of exe installed, you charge to abolish the old config files or the antecedent adaptation will be accepting agreeable from the bifold adaptation and if you change the antecedent adaptation you wont see your changes if you run it.

    1. Start, Run

    2. Appliance Data

    3. Actuality you may charge to create hidden and arrangement files visible. I anticipate it is in the accoutrement card or something...

    4. Annul the exe folder

    Beware that this will annul all your custom idevices too, sorry.

    rm -rf ~/.exe

    Change to the exe subdirectory of area you downloaded the antecedent and run the program.

    1. Start, Run

    2. cmd

    3. cd Desktopexe runkexe

    4. python exe

    1. cd ~/work/projects/exe/exe

    2. ./exe

    = Tinkering =

    EXEs antecedent timberline is laid out something like this:

    exe

     |_patches

     |_installs

     | |_windows

     | |_redhat

     | |_debian

     | |_ubuntu

     |_doc

     |_exe

     |_engine

     |_webui

     |_xului

    The absolute cipher is mostly in the exe/exe subdirectory.

    All the business argumentation is in engine, this is area anniversary Idevice is defined, however, these objects, dont understand how to render/show themselves (they understand annihilation of HTML) they alone understand how to save and amount their data, and how to behave/what that data means.

    Each Idevice is create up of fields. There are two types of Idevice, accustomed ones and all-encompassing ones. All-encompassing Idevices are what one can adapt in the Idevice editor; they accept no appropriate behaviour, they are just a accumulating of fields.

    All the apprehension is done in webui. An Idevice is rendered with by block. A acreage is rendered by and element; at the moment all the aspect classes are authentic in one book alleged element.py.

    The being alfresco of the assembly page (the airheaded and toolbars and treeviews etc.) are handled by the files in xului.

    Lets change how a Idevice titles are rendered: