If the type of component is getting in the way doesn't that mean the problem (non-trivial) component may need to be redesigned?
- Brill Pappin On Wed, Jun 4, 2008 at 2:50 AM, Jan Kriesten <[EMAIL PROTECTED]> wrote: > > >> i was of the "generify component and model" mind while i was >> generifying the framework, but after coding against it i began to see >> some of the ugliness and now my mind is almost changed. > > yep, day to day usage is the main point. > > i came to that conclusion as well when i was trying to migrate somewhat > non-trivial use of wicket to 1.4 base. the standard components like link et > al aren't the real problem (though it doesn't look pretty), it gets > complicated when you're using "non-trivial" components (like datatable and > their dependents) where the type on the component gets in your way. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
