> -----Original Message----- > From: Nick Davis [mailto:[EMAIL PROTECTED] > Sent: Sunday, March 25, 2001 6:10 PM > To: [EMAIL PROTECTED] > Subject: RE: Antidote I want to help > > > Hi, > > I really liked Chris' generic element idea... > > I created a prototype for the idea which uses > the ANT DTD to determine an element's possible > children.
What Ant DTD (I say this facetiously)? If we are going to use an approach that does a one-to-one XML to editor mapping via a (nonexistent) DTD mapping, then we are wasting our time with Antidote, because there are plenty of free XML editors out there. Editing build files (I prefer to call them definitions) is indeed one of the goals of Antidote, but in a way that is supposed to remove the user from the hierachical details of the XML file. That's not evident right now in the current implementation because what's there now is just a hack to get something out there. Ideally, each of the core tasks (and optionals via plugins) would have a JavaBean Customizer developed for it that provides high fidelity editing. Antidote would only resort to introspection (via the DynamicCustomizer) if no customizer was found. I'm not saying that what you have submiited precludes this, but I want to raise the issue of whether we are just developing an XML editor, or something that is persistence neutral. > > I hope you like it. I'll commit it, but please resubmit in the patch format specified by the Jakarta guidelines. sim __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
