Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Google Summer of Code 2009 Ideas/WebTriggeredPluginInstallation"
m (→Goal) |
(→Goal) |
||
| Line 1: | Line 1: | ||
This page documents my (Maximilian Angerbauer) project proposal for the Google Summer of Code 2009. I'd like to participate in the development of a web triggered plugin installation mechanism for Eclipse and the Equinox/p2 project, as suggested in Eclipse's Summer of Code list of ideas (http://wiki.eclipse.org/Google_Summer_of_Code_2009_Ideas). | This page documents my (Maximilian Angerbauer) project proposal for the Google Summer of Code 2009. I'd like to participate in the development of a web triggered plugin installation mechanism for Eclipse and the Equinox/p2 project, as suggested in Eclipse's Summer of Code list of ideas (http://wiki.eclipse.org/Google_Summer_of_Code_2009_Ideas). | ||
The contents in this page present an estimate on the steps and milestones involved to complete this project, a rough timeline and feature sketch. | The contents in this page present an estimate on the steps and milestones involved to complete this project, a rough timeline and feature sketch. | ||
| + | |||
| + | __TOC__ | ||
== Goal == | == Goal == | ||
Revision as of 12:18, 3 April 2009
This page documents my (Maximilian Angerbauer) project proposal for the Google Summer of Code 2009. I'd like to participate in the development of a web triggered plugin installation mechanism for Eclipse and the Equinox/p2 project, as suggested in Eclipse's Summer of Code list of ideas (http://wiki.eclipse.org/Google_Summer_of_Code_2009_Ideas). The contents in this page present an estimate on the steps and milestones involved to complete this project, a rough timeline and feature sketch.
Contents
Goal
The aim of this project is to facilitate plugin installation through the possibility to acquire new plugins by clicking a single link on a webpage. In extension to the current mechanisms through Equinox/p2, web triggered installation can ease plugin installation. Through this the need to deal with update site and other configuration tasks can be avoided which may suit new users and simplify matters for experienced users.
Timeline and Tasks
The GSoC duration is about 12 weeks. For the following tasks I've roughly estimated their duration and assigned Milestones to them.
- General Reconnaissance (2 to 3 weeks)
I'd like to get acquainted with Equinox/p2 and Eclipse development. Further I'd like to look into some of the technologies that could be used in this project. This should help to make a good decision on what technology to base the web triggered installation process on. Maybe I can provide help to a few minor bugs from the bugtracker during this period.
- Determine method to trigger installation from web & first prototype (2 weeks) - 1.st Milestone
First prototyping of possible installation methods. The Java Web Start technology was the first thing that came to my mind when I read the project idea but this is probably a very important decision and should be based on good research and discussion. Once this choice is made, work on the installation process can start.
- Communication with Eclipse instances & plugin installation (3 weeks) - 2nd Milestone
Setup communication with running Eclipse instances and determine best way to access given APIs. Implement the installation process of the plugin and an error handling mechanism. A verfication process of transferred files may be needed (like MD5 checksums or SHA). Provide 'Accept', 'Cancel' (or something similar) Methods.
- UI Design / "Look and Feel" of the installation process, Bug Fixing (2 weeks) - 3rd Milestone
There's probably no need for excessive UI design, but the shown dialogues and windows should match and fit into the general application layout. Also testing and bug fixing take place in this final phase.