Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.
Amir E. Aharoni
Jan Ploski mentioned in his post "Next release of EPIC" that he's about to write an "EPIC Developer's Guide in the plug-in org.epic.doc, as a central place for information for those who wish to become involved with the project".
I looked for it in that directory, but found only User's Guide and perltidy guide. The Java code in the CVS tree doesn't look too complicated and i would really like to help solve bugs in this much-needed project, but i've never programmed Eclipse plugins.
The current source text for the Developer's Guide is also contained in org.epic.doc, in the file devguide.xml. You can view the HTML version of it online at http://e-p-i-c.sf.net/devguide/devguide.html
It is incomplete in comparison with what I originally planned, but it should be sufficient to get a working development environment in which to learn and experiment.
Regarding Eclipse plug-in development: a good place to start is Eclipse's online help (the Platform Plug-in Developer Guide) and introductory articles from the Eclipse corner on their web site. There are also books available. The most important skill for plug-in development seems being able to locate and understand the source code of already implemented features in the workbench or JDT. In many cases, all that is left for an EPIC developer then is careful imitation.
Amir E. Aharoni
Thanks for the link.
I found devguide.xml in the CVS, but it is not in the distribution which is installed through Eclipse' update mechanism (i have 0.5.29).
BTW, the link to "Browse CVS" at http://e-p-i-c.sourceforge.net/ is wrong. And while we're on it - can you add "Website" as a category to the bug tracker? Thanks.