yeah, i get it now... but it's too complex now. it's a kind of wierd
hybrid between the old push model and your new pull model. i think we
need to refactor again and make it all a really simple, elegant pull
model...
It should be our goal to let people easily create custom feedback
components, not to just have the existing feedback panel and form
component feedback border (which I allways found too specific btw)
work in the way we think it is handy for people. I think we need the
feedback boundary and collection component concepts to ensure
flexibility. And I think such components should *not* be dependent of
our request processing cycle so much.
this much we ALL agree on. have a look at the proposal i just sent
out. i think we can make this whole thing a lot simpler somehow...
Sure, making it simpler is allways good.
Why don't we make a special example app in wicket-examples on the
different feedback scenario's we can think of? We'll have our playground
then, we document the different usages by it, and actual cases make us
think better about what we need.
Eelco
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
