Blueprint changed by Christopher Adams: Whiteboard changed: WE need to support the old one too. I would recommend that we check the version number and use the new one past a certain time and the old one for older widgets, unless you can insure that the new one will work for old widgets, which could be very difficult. I also think widgets are way too complicated, but, we should talk about all this more... Agree, this code is super convoluted! + + Speaking as an Open Font Library developer and maintainer, I don't care + about a new parser maintaining backwards compatibility. I would be + satisfied with a clear upgrade guide and would be willing to change all + my widgets by hand, in exchange for a new parser that is vastly better, + easier to use and maintain. When Aiki Framework hits 1.0 (and if it + seriously deserves to be called 1.0), I don't think it's asking too much + to have to "port" older sites to the 1.0 scheme, whatever that may be. + ~~~~Christopher
-- New parser process https://blueprints.launchpad.net/aikiframework/+spec/new-parser _______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
