>From: "Ryan Wynn" <[EMAIL PROTECTED]> > > On 6/7/06, Gary VanMatre wrote: > > >From: > > > > > > Hi > > > > > > What would be really nice is if you would make the plugin publically > available. > > > > > I was intending to make it available. I had intended to get some > basic functionality working before I did so. Right now it is at the > stage where it visits your eclipse project and parses all the clay > config files. It attempts every xml file even those that are included > in jars. If it is not a clay xml it just keeps chugging along. The > reason I chose this approach over having to have the user point to > clay configs is that I wanted it to 'just work'. Based on what it > find it creates a tree view that mimics the inheritance of the > components. Each node has an icon and a label (the jsfid) which have > some pretty stock images (folder, resource) next to them. I was > hoping to be able to incorporate more descriptive images, but images > are not my speciality unfortunately. Maybe after I donate a graphic > oriented person could enhance them. > > When you click a node the description from the clay xml is show below > the tree. You can drag a component from the tree into a clay xml. At > this point you enter a wizard that asks whether you want to create a > new component extending the one that you dragged or whether you want > to use the dragged component as a child element. You can also edit > the description - the text area defaults to the description of the > component you dragged. The wizard is not finished yet and I wanted it > to be able to optionally run through the gamet of adding children, > adding listeners, validators, etc. When you finish the wizard the > component is dropped as xml into your config file. Eclipse resource > change listeners are registered to make sure that when you save, > delete, etc the visual component tree is updated. > > I also have an xml editor that supports auto complete based on the > available clay components in your workspace. However, currently this > has yet to be completely incorporated. > > I am fairly new to contributing to open source projects. Should I > contribute the code in it's non-working state or wait until I get > basic working plugin before I donate? >
That's a fair question. I know that if you want to donate it here, you will be asked to sign a CLA (http://www.apache.org/licenses/#clas). Another consideration is that the donation doesn't give you commit rights meaning that if you contribute it, you will have to work on it by submitting patches until you earn your karam. This is how I earned mine. They just got sick of me submitting patches :--) Martin, Ted or Craig would give a better summary on the apache way. I'd like to see it here. We do have the shale-designtime project for Creator. Gary > Thanks, > Ryan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
