rap-dev

+1
welcome

Voting summary: http://portal.eclipse.org/

+1
Awesome work and a valuable member of the RAP community!

Voting summary: http://portal.eclipse.org/

+1
Welcome Austin! Your stuff looks amazing!

Voting summary: http://portal.eclipse.org/

Hello,
I tried unsuccessfully to get my employer to permit me to be a
committer to the RAP incubator.  If possible, I would like to
contribute my Google Visualization widgets to the RAP Incubator
nonetheless.  I would like them to have whatever licensing
restrictions you desire, rather than those of my project (inqle).
Would someone be able to take ownership of these widgets and commit
them to the incubator?
http://code.google.com/p/inqle/source/browse/#svn/trunk/org.inqle.ui.google.widgets
Best,
David Donohue

+1
+1, welcome ;)

Voting summary: http://portal.eclipse.org/

rt.rap.incubator Committers,
This automatically generated message signals that =?UTF-8?Q?R=C3=BCdiger?= Herrmann has
nominated Austin Riddle as a Committer on the rt.rap.incubator project. The
reason given is as follows:

Austin is a valuable member of the community who filed numerous bugs,
provided patches, participated in discussions on the newsgroup, ...
In these [1] postings on the mailing list, he expressed his will to
contribute custom widets. Therefore I
suggest him as a committer for the RAP Incubatpr project.
[1] http://dev.eclipse.org/mhonarc/lists/rap-dev/msg00517.html
http://dev.eclipse.org/mhonarc/lists/rap-dev/msg00511.html

The vote is being held via the MyFoundation portal: voters *must* use the
portal for the votes to be properly recorded.  The voting will continue
until either all 10 existing Committers have voted or until they have been
given enough time to vote, even if they do not do so (defined as at least
one week). Austin Riddle must receive at least three +1s and no -1s for a
successful election.

Eligible Committers must cast their votes through their My Foundation
portal page (do NOT just reply to this email; your vote will not be
correctly recorded unless you use the portal):

    http://portal.eclipse.org/

The project Committers eligible to vote are:

    Frankf Appel
    Istvan Ballok
    Ivan Furnadjiev
    =?UTF-8?Q?R=C3=BCdiger?= Herrmann
    Benjamin Muskalla
    Stefan =?UTF-8?Q?R=C3=B6ck?=
    Mathias Schaeffner
    Holger Staudacher
    Ralf Sternberg
    Elias Volanakis

*NOTE*: Successful elections are left open for a maximum of 60 days to
allow for processing of paperwork.  After that time the election will be
expired, regardless of its current status.  Should papework processing on
the part of the candidate take more time than allowed, a new election will
have to be held.

If you have any questions, please do not hesitate to contact your project
lead, PMC member, or the EMO 

www.eclipsesource.com
Hi Igor,
I wasn't aware that these classes have $Id$ macros. They are exact 
copies of the Batik CSS Parser source code rather than written by us.

However, if you open a bug and provide a patch that removes the 
@version tags along with the $Id$s, I think we can incorporate it.
Cheers,
RÃdiger
ÐÐÐÑÑ ÐÐÐÐÐÐÐÐ wrote:

Hi
Look at the /org.eclipse.rap.rwt/css/org/apache/batik/css/parser/CSSLexicalUnit.java
On the line 26, for example, you can see the string:
$Id: CSSLexicalUnit.java,v 1.1 2008/12/03 15:25:53 rsternber Exp $
In my case it will be converted to smth. like:
$Id: CSSLexicalUnit.java,v 1.1 2009/11/20 10:57:05 ipavlenko Exp $
It is not good for me and for anybody who have to use his own CVS.
Thanks, Igor
_______________________________________________
rap-dev mailing list
rap-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rap-dev

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

Hi

Look at the /org.eclipse.rap.rwt/css/org/apache/batik/css/parser/CSSLexicalUnit.java
On the line 26, for example, you can see the string:
$Id: CSSLexicalUnit.java,v 1.1 2008/12/03 15:25:53 rsternber Exp $

In my case it will be converted to smth. like:
$Id: CSSLexicalUnit.java,v 1.1 2009/11/20 10:57:05 ipavlenko Exp $

It is not good for me and for anybody who have to use his own CVS.

Thanks, Igor

rap-dev

[rap-dev] +1 for Austin Riddle on rt.rap.incubator

[rap-dev] +1 for Austin Riddle on rt.rap.incubator

[rap-dev] +1 for Austin Riddle on rt.rap.incubator

[rap-dev] Google Visualization widgets for RAP Inclubator

[rap-dev] +1 for Austin Riddle on rt.rap.incubator

[rap-dev] Vote for Committer status for Austin Riddle has started

Re: [rap-dev] RAP Incubator Proposal

Re: [rap-dev] (no subject)

[rap-dev] RAP Incubator Proposal

Re[2]: [rap-dev] (no subject)