I'm Grady Laksmono, and I'm working for Moodle IDE project in the Google Summer of Code 2008 program. Now, I'm releasing final version of the Moodle IDE, and I would like to get feedback, comment, and suggestion for improvement.
Moodle IDE 1.0.6
http://download.moodle.org/download.php/ide/Moodle-IDE-Setup.exe
Documentation
http://docs.moodle.org/en/Development:Moodle_IDE
Release Notes
http://docs.moodle.org/en/Student_projects/Moodle_IDE#1.0.6
Please let me know your experience!
Thanks,
Grady Laksmono
Thanks for your continued work on this. I was able to get this working, but there are some difficult areas in the installation that might produce problems for those less familiar with Moodle and Eclipse.
Most important:
For Moodle to install at all with XAMPP, you need to comment out extension=php_domxml.dll in /apache/bin/php.ini. See MDL-15637. This broke the installation for me before I addressed this, and I needed to create a clean database as well.
While you are making changes to the php.ini, I would also enable php_curl.dll and php_openssl.dll. While both are optional, they will give new installation warnings and moodle networking will not function if they are not enabled. You should also change memory_limit = 32M to memory_iimit= 40M as this is the recommended memory for Moodle 1.9.
Some other suggestions:
1. I would open in the PHP perspective, not the Java programmers welcome screen. The idea of perspectives will be difficult for users new to Eclipse and the current setup really arranged for Java.
2. When I did Help->Software updates->Find Install and did an update, the links to start XAMPP and other features broke. I would suggest that you send this out with the latest version of the software. Upgrading should not break things, and as an Eclipes user, the first thing I do is bring things up to date.
3. I found getting the 1.9 Stable branch from CVS very difficult and I very much doubt that anyone one not familar with Eclipse and Moodle's version history and branches would have been able to do this. You may want to consider pre-configuring it so that the currently supported Weekly lables and branches to 1.9, 1.8, 1.7, and 1.6 Stable as ready to checkout. Or at least give very careful instructions for this.
While it would be easier for one to just use the download of a package, that is probably not the best way for developers who will want to keep their code up-to-date and check version history, etc.
You may even want to consider shipping it with 1.9 stable already checked out from CVS.
Thanks for your work on this and I will be happy to check out any future versions you come up with.
--Gary
I believe that I should have note this on the Readme that the user shouldn't install any further updates for the PHPeclipse External Tools plugin because I've extended their version to fulfill our needs (i.e. relative paths compared to absolute, and I added start-up feature, although you don't really need it anymore in this version) So that's the only thing that will break if you do updates to the whole PHPeclipse..
Btw, how do you enable php_curl.dll and php_openssl.dll? Is there documentation through this when you do manual installation? At last, what do you mean by changing the memory_limit = 32M to memory_limit= 40M? How do you do that? Is there documentation?
Thanks,
Grady
Also, if it necessary to break the installation on upgrade (I would try to avoid that), then perhaps you should upgrade your development version first and then apply the changes so that we are working with the most recent version.
--Gary
- Grady
I took a look on this, but where are all of the directories for different version of Moodle stable release stored in the CVS? I'm unable to find them for some reason.. Is it the one in the branches? I read the Readme, and it doesn't seem to be what we wanted:
"This directory is for user-contributed tools and other useful
code that is not yet integrated into the main Moodle distribution."
Sorry for the very late reply on this one.. Thanks!
I'll be looking if there's a way to change the "default" perspective by extending from the eclipse core codes.. But I'm skeptical if we could, unless we want to create our own eclipse version..
Grady,
many thanks for the develop of this IDE.
It's goin' to be easy to use Moodle having a integrated IDE who can help us.
I downloaded Moodle IDE and load an old Moodle Project i was working on (to do this i zipped the whole directory htdocs/MymoodleInstallation and load it as a new Moodle Project - it worked easily).
I followed all the steps, but i can't be able to configure and start XDebug.
I need to debug /mod/quiz/attempt.php; so i firts tagged a breakpoint to index.php and then another into attempt.php.
I configured the Xdebug profile as in the manual (both remote and local script, even if i use my laptop as a local server) and the started the debugger.
Then i right-clicked the file index.php and chosen Open Moodle Browser (there's not way to append the ?XDEBUG_SESSION_START=<Ide Identification String> to the URL than writing it manually into the browser address window), but the debugger doesn't start.
There's something i could have to do more than what is written into the IDE installation manual?
Or something i have to check in the installation?
Thanks
Carlo
thanks for the report. Anthony addressed it at MDLSITE-610 . Some weeks ago we moved all the download.moodle.org to a new server and it seems that we missed some dirs... working on that now.
Anyway, the Moodle IDE should be working ok now at the original URL:
http://download.moodle.org/download.php/ide/Moodle-IDE-Setup.exe
Ciao