Hi Did you ever do this Gary?
Hermod -----Original Message----- From: Opstvedt, Hermod Sent: Monday, June 12, 2006 7:39 AM To: user@struts.apache.org Subject: RE: [shale] extending clay Hi Sounds like a great plugin. I guess one should wait until it is at a V1 stage before commiting (At least that is what I have done when committing to opensource), but if you someone to help you test it I would be more than willing. Hermod -----Original Message----- From: Ryan Wynn [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 07, 2006 7:07 PM To: Struts Users Mailing List Subject: Re: [shale] extending clay On 6/7/06, Gary VanMatre <[EMAIL PROTECTED]> wrote: > >From: <[EMAIL PROTECTED]> > > > > 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? Thanks, Ryan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This email with attachments is solely for the use of the individual or entity to whom it is addressed. Please also be aware that DnB NOR cannot accept any payment orders or other legally binding correspondence with customers as a part of an email. This email message has been virus checked by the anti virus programs used in the DnB NOR Group. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
