| Contributors welcome [message #93472] |
Wed, 10 September 2003 13:38  |
Eclipse User |
|
|
|
Originally posted by: none.us.ibm.com
The GEF team is always looking for contributions from the community.
Ideally, someone who can dedicate some amount of time per week for an
upcoming release of GEF.
If you've been using GEF for a while, contributing is a great way to guide
GEF in the direction needed by your project, or to learn more about features
you don't use yet.
If you are new to GEF, you could still contribute in the form of JUnit
testing, articles, or perhaps even javadoc. You would learn how to use
JUnit, and how the specific API you're testing/doc-ing works (or should work
:-).
|
|
|
|
| Re: Contributors welcome [message #94092 is a reply to message #93472] |
Sat, 13 September 2003 09:20  |
| Eclipse User |
|
|
|
Originally posted by: brian.fernandes.codito.com
Using GEF as against developing my editor directly on eclipse has reduced
the effort I need to put in drastically.
GEF is well designed ... even where it does not do what I want (heheh) it
does not come apart at a "different" implementation.
Logic rocks as well (though I used to abuse it so much when I just started
out.)
Right now I'm in a bit of a tight spot, but as soon as I clear that up, I'll
definitly pitch in some time; JUnit or otherwise.
Thank you,
Brian.
"Randy Hudson" <none@us.ibm.com> wrote in message
news:bjnnh9$50v$1@eclipse.org...
> The GEF team is always looking for contributions from the community.
> Ideally, someone who can dedicate some amount of time per week for an
> upcoming release of GEF.
>
> If you've been using GEF for a while, contributing is a great way to guide
> GEF in the direction needed by your project, or to learn more about
features
> you don't use yet.
>
> If you are new to GEF, you could still contribute in the form of JUnit
> testing, articles, or perhaps even javadoc. You would learn how to use
> JUnit, and how the specific API you're testing/doc-ing works (or should
work
> :-).
>
>
|
|
|
|
|
| Re: Contributors welcome [message #94520 is a reply to message #93586] |
Tue, 16 September 2003 10:34 |
| Eclipse User |
|
|
|
Originally posted by: none.us.ibm.com
Improvements to existing classes could be contributed by opening a bugzilla,
and creating an attachment of the new code. See reply to Alexey's post in
this thread.
"Felix Mayer" <felix.mayer@cingular.com> wrote in message
news:bjo8lq$mua$1@eclipse.org...
> Randy Hudson wrote:
>
> > The GEF team is always looking for contributions from the community.
> > Ideally, someone who can dedicate some amount of time per week for an
> > upcoming release of GEF.
>
> > If you've been using GEF for a while, contributing is a great way to
guide
> > GEF in the direction needed by your project, or to learn more about
features
> > you don't use yet.
>
> > If you are new to GEF, you could still contribute in the form of JUnit
> > testing, articles, or perhaps even javadoc. You would learn how to use
> > JUnit, and how the specific API you're testing/doc-ing works (or should
work
> > :-).
>
> How would I go about contributing something I already have?
> I reworked some of the routing functionality which might be useful
> (AutomaticRouter, FanRouter etc).
>
|
|
|
Powered by
FUDForum. Page generated in 0.26118 seconds
Home