Tuesday, December 12, 2006
Thursday, October 12, 2006
Sunday, October 01, 2006
No, I'm not commenting about my lifestyle <g>, I'm just talking about RCP, the Really Cool Platform. Lately I've been annoyed by this tendancy to call anything built on top of eclipse, an RCP application. This is just wrong as it creates confusion around a concept not easy to understand, and it does not promote SWT and/or JFace where they are the real "heros".
So what does it take to be rich? To depend on org.eclipse.ui and org.eclipse.core.runtime (see the wiki).
Now remember that and give credit to the right technology even though it may not market as well (sorry azureus is not rich, it is SWeeT).
Monday, July 10, 2006
Friday, July 07, 2006
The two main motivations were:
- Carefully controlling the set of APIs we use from the JRE and reduce our dependencies
- Express in an API way the fact that some bundles could run on lower configurations than the one recommended by the platform (for example SWT and OSGi can run on foundation)
- At runtime, bundles that do not qualify to run on the VM will not run (for example bundles requiring java 5 will not resolve on a 1.4 VM)
- At build time, PDE Build will set the compilation flags for you and make use of the proper class library (see PDE Build help).
Friday, June 30, 2006
Thanks again Denis, Matt and Nathan for bearing with us in your office while we were drinking your beers and watching you work.
By the way next time, get one of those to make the final push more exiting :-).
Wednesday, June 28, 2006
Thursday, June 22, 2006
Since 3.2, PDE Build provides support to build RCP applications from .product files. For more details, see the help (Plug-in Development Environment Guide > Tasks > Building an RCP Application from a product configuration).
Wednesday, June 21, 2006
What would it be: A work item bringing value add to eclipse, but where the effort would be driven by the community instead of the eclipse teams themselves. Such items should be relatively self contained (for example: implement a new refactoring, implement a new code formater, better high level doc on RCP, provide an simple build infrastructure, provide login infrastructure, etc.).
How would they work: Like any work item they would first be proposed. Then interested members of the community would form a working group responsible for designing and implementing a solution in adherence with the component vision, solution that would find its way in the release. To this extent, it would get assistance from appropriate committers, but it would also be submitted to the same criteria of quality with respect to stability, scalability or being done on time.
Who would submit those items: The PMC or the community, but it would likely have to be approved by the PMC to ensure the cohesion of the vision and appropriate resource is available to assist where needed (of course this is just a proposal).
Why do we need those? Current plan items read as "the team will do it for sure (committed)", "the team is investigating (proposed)". Therefore if you are willing to help you are left with the not so sexy HELPWANTED bugs. What this does is create a focal point and fosters discussions around a particular topic, that would not have necessarily emerged alone from the community. Also it is clear for companies or people willing to contribute code what things are of interest and what their energy could best used at.
In order to discuss that, I have opened bug 148149.