eLAIX as an independent application that uses Word documents

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.

1 Initial Problem

eLAIX has been a plugin for LibreOffice/OpenOffice so far. Since both applications are getting more and more independent it is hard to keep the plugin running for both LibreOffice and OpenOffice. In addition to that, with version 5.2 LibreOffice changed the internal representation of graphics fundementally, with the result, that eLAIX is no longer compatible to Version 5.2 or higher.

2 Conceptual Summary

The problem can be solved by developing a new eLAIX as an independant application, which doesn't require the LibreOffice or OpenOffice API.  Instead it opens a word processing document and exports a package that can be imported as an ILIAS learning module. Since most users are using MS Word for their text processing documents, it is obvious that the new eLAIX uses Word documents for the content creation. Based on the export as an ILIAS learning module, eLAIX can be extended later to be able to export other ILIAS objects like glossaries or tests. eLAIX will be written in Python. It will be available for Windows, OS X and Linux.

3 User Interface Modifications

The graphical user interface has to be developed from the scratch, since the new eLAIX will be an independent application.

3.1 List of Affected Views

Since eLAIX is an independent software, ILIAS views are not affected.

3.2 User Interface Details

The user interface of the new eLAIX will be very similar to the existing eLAIX plugin. However new features like opening a Word document will be implemented.

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Privacy Information

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Contact

• Author of the Request: 
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: 

7 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

8 Discussion

9 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.