[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[ve-dev] Re: How to be a contributor to the VE project (was Re: VE Question.)
|
I've added a link under Development Resources [1] in the VE wiki to a
bugzilla query for all open VE bugs.
Please subscribe to the ve-dev@xxxxxxxxxxx mailing list [2] and cc: your
responses there, so others can benefit from this discussion.
Thanks,
Nick
[1]http://wiki.eclipse.org/Visual_Editor_Project#Development_Resources
[2]https://dev.eclipse.org/mailman/listinfo/ve-dev
Snyman, Marius M wrote:
Well,
My first steps include getting a plugin that extends VE for our custom product.
I have added a Preferences Page and is busy setting up the drawer with our buttons
Also Included in our product is support for Synth, which I am still investigating on how to add the support to the WorkBench with the plugin.
In Addition to this I need to add/extend the wizard which creates a new Visual Class to show our Panel and Frame. Our use case developers will use these instead of the Bean lookup. So I still need to figure that out as well.
I find that working through the JFC plugin source helps tremendously .
I expect it will give me sufficient insight into what goes on in the inner workings of VE so as to start contributing.
Due to pressure on the customer side I have to focus on this first.
As soon as the pressure lifts somewhat I shall start contributing with bug fixes.
By the way, where do I access the bug list?
As I go along, I am preparing documentation to help others get coding quickly. As I complete them done I shall contribute these as well. Is there a recommeded way for contributing tutorials?
Kind Regards
Marius Snyman
Marius.Snyman@xxxxxxxxxxxxxxxxxx
+27123257133
-----Original Message-----
From: Nick Boldt [mailto:nickboldt@xxxxxxxxx]
Sent: 07 October 2009 06:28 PM
To: Snyman, Marius M; Discussions people developing code for the Visual Editor project
Subject: Re: How to be a contributor to the VE project (was Re: VE Question.)
Glad it helped!
So, are you planning to contribute something to the VE 1.5 development?
Or patches on the 1.4 stream?
Just curious,
Nick
Snyman, Marius M wrote:
10Q for the Link
I have in the meantime discovered the main culprit for my errors was a dependency on the dependencies tab of plugin.xml.
I had errors because the version of com.ibm.icu on Galileo is 4.0.1 and the expected dependency was 3.something
All the project now compile successfully.
-----Original Message-----
From: Nick Boldt [mailto:nickboldt@xxxxxxxxx]
Sent: 05 October 2009 10:32 PM
To: Snyman, Marius M; Discussions people developing code for the Visual Editor project
Subject: How to be a contributor to the VE project (was Re: VE Question.)
Marius:
To answer your question, I've created a wiki page to capture how best to
set up a workspace for building VE (and JEM, since we build that as well).
http://wiki.eclipse.org/VE/Building
Let me know if that helps! (Or if anything's missing.)
--
As every project is run a bit differently, the best advice I can give
you is to talk to the project leads &/or active developers, read the
mailing list posts to see what's going on in the project, etc. Get
involved! As people learn your name, and see what you're capable of
(eg., fixing bugs, submitting patches, contributing to architectural
discussions/planning), you'll rise from 'interested user' to
'contributor' and maybe eventually committer.
I've copied your question to the ve-dev@ mailing list so other active
participants can chime in with what they would like to see from new
members, and so other interested contributors can test out the wiki'd
instructions above and see if they work for them.
(I'm the guy who pokes the builds & website from time to time, but I'm
not actively involved in the planning, development, or management of
this project beyond that.)
Joe? Yves? Anything to add?
Nick
Snyman, Marius M wrote:
Nick, I noticed you did the VE 1.4.0 R build. If you would be so kind to
assist me in getting started with the VE stuff.
I have never before been a contributor to open-source. The primary
reason is that I do not know howe to get started.
I have checked out the VE-ALL projects. There are sub-projects under
some other projects.
If I open the projects in Eclipse I have a lot of errors regarding
dependencies for logging and concurrency, etc..
I would like to understand this.
Must the project structures remain exactly as checked out?
Must I download the dependencies from their respective web-sites? I have
done this for the concurrency.jar and when I included it in the project
I get deprecation errors on the JDT sources.
Are there some basic guidelines somewhere on how to get actively
involved in a project.
Kind regards.
Marius Snyman
Marius.Snyman@xxxxxxxxxxxxxxxxxxx
011 269 5591
**
**
*Standard Bank email disclaimer and confidentiality note*
Please go to
http://www.standardbank.co.za/site/homepage/emaildisclaimer.html to read
our email disclaimer and confidentiality note. Kindly email
disclaimer@xxxxxxxxxxxxxxxxxx <mailto:disclaimer@xxxxxxxxxxxxxxxxxx> (no
content or subject line necessary) if you cannot view that page and we
will email our email disclaimer and confidentiality note to you.
--
Nick Boldt :: http://nick.divbyzero.com
Release Engineer :: Eclipse Modeling & Dash Athena
