[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[rap-dev] RAP Incubator Proposal
|
Hello Jochen,
Thanks for your guidance about the contributions and becoming a
committer. I have been very happy with the RAP team and the community
and I am looking forward to contribute however I can.
In your post you mentioned something that really resounds in my mind;
the separation of concerns regarding the wrapping of commercial code in
RAP ("glue code"). I would like to think that the RAP incubator is
suited for custom RAP widgets that "can" integrate with commercial
software that is not necessarily compatible with the EPL. Since there
is a clear stratification between what is RAP "wrapper" code and the
external software, they could be kept separate.
In the case of the Emprise charts, I have decomposed the bundles into
external api and rap custom widgets:
org.eclipse.rap.rwt.charts - home grown framework/charting interfaces.
org.eclipse.rap.rwt.charts.emprise - contains the custom widget code
org.eclipse.rap.rwt.charts.emprise.api - contains or references the
external software (RAP resource registry)
The last bundle is a fragment and is very simple, so it could be simply
not included in the incubator, or the external software could just have
to be dropped in by the user.
In any case, my goal is not to make waves in the licensing dept. I just
think that it would be useful for the community to have a "shelf" in the
incubator for custom widgets that harnass to external software that may
not necessarily be compatible with the EPL.
The reason that I chose the Emprise contribution first is because,
although I have received verbal approval for the others, they will take
a bit longer to get final approval for.
I am planning to upload the Empise bundles to a bug report soon, I am
just tidying up a few things first.
-------------------------------
Here is my bundle breakout for the proposed contributions:
org.eclipse.rap.rwt.custom.utils - contains utilities for aiding in the
development of LCAs.
org.eclipse.rap.rwt.excanvas - the Google ExplorerCanvas (it is high
time we had a separate plugin for this thing since many of our custom
widgets rely on it, and you don't want every custom widget registering it).
org.eclipse.rap.rwt.choosers - contains 2 "chooser" widgets; carousel
and "cover flow" (Image flow)
- Carousel is something I wrote. It just uses the canvas object.
- Image flow is a project by Finn Rudolph
(http://finnrudolph.de/). His JS code is in the bundle.
org.eclipse.rap.rwt.choosers.demo
org.eclipse.rap.rwt.timeline.simile - the simile timeline integration.
Simile code is in the bundle. Everything is self contained.
org.eclipse.rap.rwt.timeline.simile.demo
org.eclipse.rap.rwt.map.openlayers - open layers map integration. Open
Layers code is in the bundle. Everything is self contained.
org.eclipse.rap.rwt.map.openlayers.demo
org.eclipse.rap.rwt.charts - home grown framework/charting interfaces.
org.eclipse.rap.rwt.charts.emprise - emprise charts integration code
org.eclipse.rap.rwt.charts.emprise.api - contains the Emprise personal
edition JS (RAP resource registry)
org.eclipse.rap.rwt.charts.emprise.demo
To be fair, I want to give credit to my teammate Cole Markham for
writing the Open Layers Map widget, and assisting in the development of
some of the other widgets.
----------------------------------------------
So what are the actual steps to committerhood in the RAP project?
When and how does that happen and become official?
Thanks,
Austin Riddle
Software Engineer
Computing and Information Technology Division
Texas Center for Applied Technology
Texas Engineering Experiment Station
Ph. 979-458-7680
