> See notes before; the last thing I want to do is add yet more layers
> of abstraction!  ClientBehaviorSupport was a mistake from the start.
> 
> If you don't want something that works like ProgressiveDisplay, write
> your own.  What's nice now is just how minimal it is; there's almost
> nothing left!

> But if the component is simple enough, you can create a custom one
> that does exactly what you want. I think people too often twist
> themselves, and their code, into knots trying to customize an existing
> component rather than write a few lines of code to create a new one.


I can't just go and replace all components in the project when upgrading to the 
newest version, there are like hundreds of Zone or EventLink components in our 
project. I'm doing exactly what you are suggesting, I'm adding data attributes 
to the existing components, like instead of t:zone I will use data-zone in the 
new code, but in my mind the best solution would be to replace the code inside 
the EventLink. 

I'm just trying to come up with the solution to keep things working. 

> That becomes a key question: we would not need the core/spi layer if
> we just said "Tapestry uses jQuery, live with it". As I've said in the
> past, that is not the best solution for everyone, but I'm willing to
> entertain more discussion on this. It would certainly be easier to
> eliminate core/spi.

I don't have a solution here, it is why I decided to rewrite whole Tapestry 
javascript to pure jQuery. I know it wouldn't be fair to just replace 
everything and switch to another framework.

In your point of view you see an abstraction on the client side, let's have 
some base code and share it between prototype and query specific modules, but 
in my case I want an abstraction at the components layers, so I can just 
replace whole client implementation. I'm not exactly trying to add more 
abstraction from my point of view.

Denis



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to