Very prescient; I'm current working through ideas about how this could work in a practical, efficient system. I've called this "aspect oriented templating" (something of a throwaway term), and have started thinking about component "facets"; such as an autocompleter facet that wraps around a text field.
On 2/1/06, Leonardo Quijano Vincenzi <[EMAIL PROTECTED]> wrote: > You're getting me wrong. You're talking about monolithic components, I'm > talking about component composition. > I don't know what's the *best* way of doing this, design-wise, so please > don't jump in conclusions. I'm talking about why Ajaxcompleter has the > Textfield functionality copied. > > So, instead of having 2 TextFields, one with standard functionality, and > one with autocomplete, we'd have some "component parts", or whatever you > should call it, that we "compose" together and build a full featured > TextField with 30+ functions. > > It's not that the base component has 30+ functions. Is the *composition* > of components that has it. > Aren't validators and translators pluggable ? Why don't do the same with > Ajax?? Tacos is already doing it, I'm just talking about making it official. > > -- > Ing. Leonardo Quijano Vincenzi > DTQ Software > > > > > --------------------------------------------------------------------- > 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]
