| Re: [e4-dev] AJAX-based Eclipse Project Explorer |
This looks very interesting and there is good overlap with the e4 project goals in a few ones. For one, we're interested in plugins written in languages other than Java. For another, we're interested in how and to what degree Eclipse can move to the web. One logical outcome is an IDE on the web, although there are no plans for that at present.The AJAX-based project explorer could be a big step towards making eclipse an IDE on the web. The only thing you have locally is the eclipse + plugins (similar to browser + extensions). All project data comes from the cloud. Is it already possible to run _javascript_ plugins in eclipse? As for practicalities of getting involved, the e4 project is pretty open and in the end moves in the direction that those who step up want to move it. To get commit rights to the repository you will need to be voted in by the community. In established Eclipse projects with a shipping code base with dependent products, it can take awhile to earn those commit rights. However, in e4 it's really about getting people involved and they get put through pretty quickly. If you have a contact already in this community who is already an e4 committer then it's best for them to help you through the nomination process.To get involved, what I would need is to make contact with people who are interested in the AJAX-based project explorer concept and working on eclipse components that are required for it. At this stage I have no idea what is already possible, what is being worked on and where I would even need to start to get this off the ground. If anyone is interested in being my contact and does not mind doing some hand-holding in the beginning, please let me know. I have plans to develop the _javascript_ and server side of things for this explorer throughout the year anyway (to be used as an extension to Firefox). It would be great to bring along eclipse support at the same time, but as mentioned before, for me to try and build this into eclipse is like climbing a 100 foot wall at the moment. Has anyone thought about the development lifecycle of building UI _javascript_ plugins for eclipse especially when it comes to debugging? One idea might be to build a bridge between eclipse and Firebug (running in Firefox) where eclipse instead of sending and receiving events to and from it's own JS container could instead proxy them to and from a container running within firefox as an extension. The advantage would be the ability to use Firebug to debug and develop eclipse plugins which may reduce the barrier to entry significantly. I am involved with the Firebug Working Group to build an extension ecosystem for firebug and could help in bridging between the two projects. I can be of help in any of these matters and it's always true that others in the community are happy to help too.Thanks for the warm welcome Kevin. Now I just have to find someone who does not mind spending some time helping me along in the beginning. Christoph
| ||||