jakarta-taglibs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stu Robertson <srobert...@nvisia.com>
Subject Re: RDC's - running code before submit
Date Thu, 04 Aug 2005 03:39:13 GMT
I noticed we crossed paths over the ether!

Shane and I will implement everything we've brought up.  We're setup  
so we'll be able to submit patches against the RDC dev trunk.  Still  
need to check out the new bugzilla presence, but that shouldn't be a  
problem.  We're going to bounce quite a few design ideas around on  
the list, both as a sanity check and also in an attempt to make  
enhancements we need useful for the library themselves.  Please  
challenge the need for things we bring up, as well as the  
implementation.  We're doing the same on our end.

Btw, I really wish there were a bitkeeper-like way of comparing  
between svn repositories...any suggestions on this would be much  
appreciated.  Right now I've made a local svn copy of the current RDC  
trunk.  We're making changes against our local copy, and can generate  
patches against that.  But obviously that breaks down over time as  
RDCs evolve - assuming not all of our patches make it in that is ;-)

On Aug 3, 2005, at 10:18 PM, Rahul P Akolkar wrote:

> Stu Robertson <srobertson@nvisia.com> wrote on 08/03/2005 11:07:24 PM:
>> This provides a nice hook for all sorts of things developers might
>> want to do when a grammar is matched.  One of the challenges we're
>> bumping into is that without this sort of hook, "app space" is quite
>> limited to functionality directly implemented in the base RDCs.  This
>> approach is appealing because it makes adding "earcons" trivial (in
>> the simple case; we're using it with dynamic config files with earcon
>> includes), and extending RDCs with custom behaviors possible (per-
>> instance client-side validation for instance...or again generalized
>> in app-space through config file includes, as we intend).
>> Anyway, since it's optional and adds needed flexibility it at least
>> fits the general description of things that are nice to support in a
>> framework like RDCs.  We've bounced around different approaches, and
>> this one seems interesting to us.   We're very interested in input.
> Just replied to the original email in this thread, this will be a good
> addition. Would you (or Shane) like to sketch up a list of tasks/ 
> changes
> w.r.t to the code? We can then divide up the work, so it'll get done
> sooner.
>> Stu
> -Rahul

To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org

View raw message