re: thread Make validation errors appear before a form is submitted and Tapestry 5 Just a couple of thoughts. I have had a further conversation with gaz (c.f. the other thread. I work with him, so that type of thing is possible -:)). The problem that has been found is to do with the rendering of errors in the validation (sub) framework - field tracking. Field tracking requires a submit for it to be initialised. My thoughts are not about the problem gaz has, but about the Tapestry framework. The error mechanisms would have to be further decoupled. No one would have anticipated that this might be an issue to begin with, but maybe by finding these things it is how frameworks evolve? Would it be possible to treat the validation mechanisms as a completely modular service? Well, I imagine that by Howard developing using an AOP framework all of this sort of thing is anticipated in one fell swoop? I already thought AOP was good using hivemind 1.1, but can see that it can be pushed. I just want to emphasise the usefulness of this re. error checking. Actually, error checking and rules integration is becoming a fundamental part of a more sophisticated app. I know it sounds like hot air, and I don't have a working example, but it seems to me that more formal languages for rules are going to be playing a part here as will the use of tags in some form (maybe I will have Jesse on my side here?) These more formal languages might control workflow, and, going back to the original issue, workflow often has to do with error catching and exception processing. So every little bit that makes it more feasible to implement this in Tapestry moves Tapestry closer to this territory. IMO Tapestry is highly suitable for integration with other open source solutions in this area, but however it is done I anticipate it will be! Adam
On 26/04/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > The basic AOP infrastructure is coming along. I expect the rest to > ramp up pretty quickly once I get that in place, but we're still > talking months. Maybe a useable beta by year's end. > > I think I predicted a big performance boost for Tapestry 4 apps vs. > equivalent Tapestry 3 apps. I believe the difference between 4 and 5 > will be greater. In fact, I expect OGNL support to be an add on, and > the built-in code will be an improved version of tapestry-prop (from > Tapestry @ JavaForge). I want Tapestry to be extremely high > performance, as one of its differentiators from JSF and Rails. > > > On 4/25/06, Brian K. Wallace < [EMAIL PROTECTED]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > First off - this is great news (IMO). It's great to see a new look as > > it's being checked in. > > > > The following is nothing short of my own idle curiosity: when do you / > > would you envision 5 rolling out? [no jumping down the new guy's throat > > - - I'm just curious. I know there's a lot left before anything thrown > out > > would be anything more than conjecture/hope] I'm really looking forward > > to seeing the two sides (Howard's / Jesse's) meeting and pushing > > Tapestry that much farther. > > > > Howard Lewis Ship wrote: > > > I'm having a lot of fun with the tapestry5 code. > > > > > > Back in January 2000, I spent almost two weeks getting Tapestry from > > > an idea to a lame "Hello World". I had to do lots of work and learn > > > many things, including the SAX API, designing and implementing the > > > component specification hierarchy, designing and implementing the > > > component structure, all the reflective instantiation, the initial > > > primitive template parser, and so forth. > > > > > > I think that time was well spent, it "injected energy" into Tapestry > > > that served it well for several years, giving it a powerful core that > > > was quite amenable to change and improvement. > > > > > > I'm putting much more effort into the new code base, along with six > > > years of accumulated experience. It feels like I'm winding it up like > > > > a spring (no pun intended). It's exhilarating. > > > > > > Right now, what I'm building looks more like an AOP system than a web > > > framework ... that'll come later. I need to catch up on Jesse's work > > > on the JSOnRenderer since those ideas should be folded in and > > > improved. > > > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.2.5 (MingW32) > > > > iD8DBQFETwNAaCoPKRow/gARAlfxAKCOquc4t/i/2XbEqBEd+NMDNU8eBgCg2gkd > > GC8fEpi5KxHSfi8xSvXQHsA= > > =9v6P > > -----END PGP SIGNATURE----- > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Howard M. Lewis Ship > Independent J2EE / Open-Source Java Consultant > Creator, Jakarta Tapestry > Creator, Jakarta HiveMind > > Professional Tapestry training, mentoring, support > and project work. http://howardlewisship.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
