On Thu, Jul 3, 2008 at 10:02 AM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > On Thu, Jul 3, 2008 at 12:47 AM, Matej Knopp <[EMAIL PROTECTED]> wrote: >> Ligther? Does it meen with no Compund and ComponentAssignedModel? >> Wouldn't that feel more like crippled? >> The default model slot doesn't take any runtime space when you don't >> use it, property would. And removing four methods from component will >> hardly make it much lighter. > Big +1 on that :)
> I wasn't just thinking about models though. *I* would like us to go > through the API when we start on 1.5 and remove anything that isn't > necessary. Remove all the the deprecations and convenience methods > that have (easy) alternatives. All the while keeping an easy upgrade > path in mind of course. > > Of course, things like compound property models are pretty cool, and > we should keep supporting the types of models we are supporting now. > But maybe we can find a way to add this kind of support to components > without needing it to be built in. Or maybe not and in the end our > conclusion will be to stick with 1.4's model. But lets try to be > creative before we give up on that :-) Creative is ok for me. Destructive isn't :) > > We're getting a bit ahead of ourselves now though, unless we already > want to start coding on 1.5. It is probably a better idea to finalize > 1.4 first, and decide on what to generify by default based on the > likeliness it will help users for this version. Yeah, agree on this as well. -Matej > > Eelco > > --------------------------------------------------------------------- > 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]
