Yes I think that this is the pattern that we are applying for packageInfo for example
> I said it before: This doesn't solve anything at all. In fact it is > much easier to remove the variable and fork the code. Renaming causes > a ripple effect to lots of methods and makes it impossible to merge > the forks in the future. > > The style variable is just one example of the problem. I am suggesting > that the next time the editor framework is replaced the old code is > left untouched, then deprecated, and different class names are chosen > for the new implementation. Like this both frameworks can coexist for > a while making it much easier to migrate the code. > > The current situation comes from the fact that some existing classes > changed their class layout and API completely making migration really > difficult. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >
