Last summer, when the full impact and agony of Spindle 4T4 was
unclear. I was thinking about how to write a plugin for HM. Didn't get
very far but I have a solid approach down in my head.

Spindle parses all the files and builds a model of the Tapestry
artifacts in the project.

A HM plugin could do the same and use the model as a source for all
kinds of interesting things like validation, syntax completion and
even doc generation.

Mimicking the registry builder is the tricky part. Pretty tricky as
devlopers can customize what modules are picked up and from where. My
thinking was to go along the lines of project sets in Eclipse, the
default set being all the /META-INF/hivemodule.xml. User would be able
to add/remove files to/from a set or create new sets containing
modules from anywhere (reasonable - I don't see a module coming from
an rdbms in an IDE).

User tells plugin, "use this set" and it runs off building
models/validating like mad.

Unlike Spindle I was not interested in making the plugin dependant on
the HM library itself. Rather I was going to use EMF to build the
model. Much more insulated from HM api changes (a painful part of
keeping Spindle up to date but not the most painful by far.).

EMF has its own learing curve (fairly steep I found out).

Plus with the work already done to decouple Spindle from Eclipse I can
easily see how this could be done with a HM plugin (an IDE agnostic
core used by an implementation targetted to a specific IDE).

Building IDE support for HM in it's current incarnation would be many
times easier than doing Spindle 4T4 - it would be fun (for me). If I
was free of Tapestry I'm sure I could push out an alpha in less than 6
weeks.

Several things lead me to shelve the effort (it was mostly a brain
exercise, there is no code to share).

1. Spindle 4T4 came to consume everything.

2. I'm sure that Howard will steer HM down similar paths as Tapestry
at some point, and I'm not interested in doubling my pain. Having
every major version "change the world" is tiring after a few times. If
it was my day job I'd love the challenge. It's not my day job.

3. No free time
4. Did I say no free time?

Geoff




On 2/24/06, James Carman <[EMAIL PROTECTED]> wrote:
>
>
>
> Oh, I understand.  I was trying to give you a quick/dirty way to get the
> validation built.  Creating an XML editor (or borrowing from an existing
> one) should be quite easy.  All you have to do is plug in your own
> validation.
>
>
>
>  ________________________________
>
>
> From: Andrea Chiumenti [mailto:[EMAIL PROTECTED]
>  Sent: Friday, February 24, 2006 9:07 AM
>  To: [email protected]
>  Subject: [Norton AntiSpam] Re: Re: providin a dtd to hivemind xml files
>
>
>
>
> This is not what we would like. What you suggested is only a validator, what
> we are speacking about is a full featured editor
>
>
>
>
> On 2/24/06, James Carman <[EMAIL PROTECTED]> wrote:
>
>
> Couldn't you just write a custom errorhandler which collects all errors into
> a list and you display that?  Then, run
> RegistryBuilder.constructDefaultRegistry()?
>
>
>
>
>  ________________________________
>
>
> From: Hugo Palma [mailto:[EMAIL PROTECTED]
>  Sent: Friday, February 24, 2006 8:51 AM
>  To: [email protected]
>  Subject: [Norton AntiSpam] Re: providin a dtd to hivemind xml files
>
>
>
>
> I actually have something like that in the roadmap of the Tapestry plugin
> for IntelliJ i'm implementing. Of couse this component would be indepedent
> of Tapestry and would work any any other kind of project.
>
>  The bad news is that i won't have time in the near future to implement this
> as i'll be implement other more Tapestry specific features. But if anyone
> wants to implement such editor i can help with all the free time i can get.
>
>
>  Cheers
>
>  Hugo
>
>
> On 24/02/06, Domsch, Christian < [EMAIL PROTECTED]> wrote:
>
> Hi,
>
>
>
> I proposed this some time ago: It is possible to write an editor (or an ide
> plugin) that reads all hivemodule.xml (like the registrybuilder does) and
> the parse all configuration points and there corresponding schema
> definitions. And from theses schemas enforce the correct editing of the
> contributions. Its all there, you just have to write that "little" editor
> :-)
>
>
>
> Btw, this would be a great improvment!
>
>
>
> Greetings,
>
>
>
> Christian.
>
>
>
>
>  ________________________________
>
>
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>  Gesendet: Freitag, 24. Februar 2006 14:07
>  An: '[email protected]'
>  Betreff: RE: providin a dtd to hivemind xml files
>
>
>
> depends. The point is, the structure of a <contribution> element depends on
> it's configuration-id attribute. That's not possible to enforce in either
> dtd or schema afaik.
>
>
> But if you have a sub-module that contributes to only one schema that'll not
> be a problem.
>
>
> -----Original Message-----
>  From: Andrea Chiumenti [mailto:[EMAIL PROTECTED]
>  Sent: Friday, February 24, 2006 1:58 PM
>  To: [email protected]
>  Subject: providin a dtd to hivemind xml files
>
> Hi!
>
>  To help my customers to configure services I'd like to drive them with dtd
> validation. So for example
>  for file auth.xml included into my hivemodule.xml i'd like to provide an
> auth.dtd file to validate the xml correctness.
>
>  Is it possible ?
>
>  Thanks in advance,
>  kiuma
>
>
>
>


--
The Spindle guy.          http://spindle.sf.net
Get help with Spindle:   
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Blog:                     http://jroller.com/page/glongman
Feature Updates:          http://spindle.sf.net/updates

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to