On Sat, 07 Jun 2008, Igor Vaynberg wrote: > so as far as i can see, and this is only my opinion, our options are: > > continue 1.4 as it is now with fully typed components > remove component type but make the api ugly ( i will let matej explain ) > attempt to fix 1.4 by decoupling model from component - 1.4 takes a > lot longer and is not a simple "drop-in/upgrade/whatever" > > thoughts and ideas?
Am I right in assuming everyone to agree that on the long run - IModel must be parametrised - the default model (setModel / getModel) must be removed from Component - Component without its default model must not be parametrised ? Given these, _and_ that we prove with a spike solution that removing IModel from Component can be done feasibly, I would rank the options like this: > continue 1.4 as it is now with fully typed components - no, because the long term goal is to remove typing from Component, so the sooner the better? > remove component type but make the api ugly ( i will let matej explain > ) - yes, because here the paradigm is the same as the long term goal, and the ugliness is temporary (will be removed in 1.5) > attempt to fix 1.4 by decoupling model from component - 1.4 takes a > lot longer and is not a simple "drop-in/upgrade/whatever" - no, because then people enjoying Java 5 features with 1.4 need to wait for a stable version for longer, and I don't know if we can really drop 1.3 support then. As overwhelming majority (largest vote ever?-)) was in favor of Java 5 and generics over 1.3 (and Java 1.4) support, it would be great to get it out soon. Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations Oy <URL: http://www.ri.fi/ >
