Note: You are currently viewing documentation for Moodle 1.9. Up-to-date documentation for the latest stable version is available here: Student projects/Moodle IDE.

Student projects/Moodle IDE: Difference between revisions

From MoodleDocs
Line 30: Line 30:
This Windows version will be the first one that will be packed out of the box with the Moodle IDE.
This Windows version will be the first one that will be packed out of the box with the Moodle IDE.


* '''T1''' Develop a plug-in that will ease the user configuration through XAMPP
* '''T1''' Develop a plug-in that will ease the user configuration through XAMPP
* '''T2''' Develop a bridge between the developed plug-in to the Eclipse PDT for the localhost information
* '''T2''' Develop a bridge between the developed plug-in to the Eclipse PDT for the localhost information


'''Optional'''
'''Optional'''

Revision as of 17:34, 6 May 2008

Note: This page outlines ideas for the Moodle IDE project. It's a specification under construction! If you have any comments or suggestions, please add them to the page comments.


This project is about creating a Moodle integrated development environment (IDE), based on Eclipse, so that new developers can begin developing Moodle in less time.

Ideas:

  • First release: Eclipse + Plugins + Moodle splashscreen + CVS Configuration + Apache + MySQL + Moodle CVS code. All preconfigured and ready out of the box.
  • Every X time, it checks for new versions of Moodle and packs it.
  • Check style plug-in alike to follow Moodle Design Guidelines.
  • Development help (can be wiki pages to navigate offline)

Moodle IDE

Eclipse

Selecting the base of the Integrated Development Environment (IDE) is one of the most important thing because it will be the key of the development process. I decided to start out with the latest stable version of the Eclipse PDT.

Splashscreen

Here are some design that interests me to be used as the Splashscreen of the Moodle IDE:

Moodle Web 2.0 Glassy small.png

CVS

CVS plug-ins is already built into Eclipse. The discussion about this is that if there are too many X times of checking the new version of the Moodle and packs it, then there will be a huge server loads, with the addition that not everybody would want to always packs the new version when it's been released. So, creating plug-ins to bridge the user interface and the CVS script is one way that I think is more appropriate, but I'd like to do some more research on the CVS behavior.

  • T1 Research the behavior of CVS in Eclipse

Apache + MySQL

This Windows version will be the first one that will be packed out of the box with the Moodle IDE.

  • T1 Develop a plug-in that will ease the user configuration through XAMPP
  • T2 Develop a bridge between the developed plug-in to the Eclipse PDT for the localhost information

Optional

Plug-ins

See also