Nothing was "shot down", Frank.
Perhaps I wasn't as accurate as I could have been Ted... it was shot down in the form I initially presented it. To be fair, what you write here about developing it and growing a community and maybe eventually becoming a subproject was stated then as well. But as it was presented and where I was proposing going with it was, in my view, most definitely shot down. Please read no bitterness into that by the way, there is none!
Now, if at this time it goes off in another direction, that's perfectly fine too, and it in line with what you are saying here.
> I believe many of us feel the idea has
significant merit. I'd like to see it happen, but I'm frying other fish right now, and I don't have any more hours to volunteer. I'd venture that the other Struts Committers are in the same boat.
I am happy to hear that there is interest! I think it is fair to say we saw a decent amount of interest on the users list today as well, certainly enough to make me want to put some more effort in to it. I don't have as much free time as I did a while back unfortunately, but I'm going to find some time to work on this as soon as I can.
People work on what they want to work on. If you want to work on a
Ajax revolution, you can do that on SourceForge and talk about it on
the Struts Dev list, if you like.
This is the one thing I am not at all sure was understood during the initial discussion, and I take the seeming desire by everyone (based on the comments and ideas tossed around at the time) to initiate some new all-encompasing front-end thingamajig based on AJAX (maybe) as evidence of that.
I was never, and still am not, proposing anything revolutionary or indeed anything especially new or novel. My proposal was, in my opinion, very much evolutionary. All I have ever proposed is what I view as a relatively minor enhancement to the existing HTML taglib. I would certainly have interest in something more grandiose, but I am not at this point clear on what form it would or should take, so I am not going down the road at this point.
I never viewed it as something worthy of ever being a subproject, nor did I frankly view it as something even worthy of being its own independant anything.
That was why I was trying to get support before finishing all the work... The original goal was a modification of the existing taglib, which I felt implicitly needed support from all of you folks to succeed. Now, there have been some subsequent ideas tossed around about doing more of an extension, independant in a sense of the existing tags, and I am OK with that and intend to look into doing it that way.
If the codebase is developed, and attracts a community, then it could be proposed as as subproject, or a new HTML taglibs head, or whatever else might be appropriate under the circumstances.
That wasn't what I had in mind when I started, but I can't think of a good reason not to persue it with that mindset now. Indeed, when I ask myself what is better, to do nothing because it didn't turn out as I originally envisioned, or give something to the community in a slightly different form that is still potentially very useful, the later is most definitely the right answer as far as I'm concerned.
* For more, see the Rules for Revolutionaries -- http://incubator.apache.org/learn/rules-for-revolutionaries.html
Tiles, Validator, Nested, EL, declarative security, Flow, Shale, Scripting, all started this way. People did the work, and *then* we brought the component into the project.
And I think that is great when it is something more revolutionary... but you would agree that you don't take a patch and start a project on SF and wait for a community to build around it before applying it, right? If you accept my original thesis that what I was doing amounted to not much more than a slightly more complex patch, or at most a somewhat minor upgrade, then the same argument should hold, should it not?
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
