On Mon, Sep 20, 2010 at 6:52 AM, <[email protected]> wrote: > > Why do we go back a few steps and figure out what goals we want to > > achieve with this and then we can find the best way to go about it. > > "Simply put, we want to make it possible for an application developer to > write a MeeGo compliant application once and run it on any MeeGo compliant > device." > http://wiki.meego.com/Quality/Compliance >
The trouble is that is a rigid goal and I'd say a slight conflict of interest between that path and the approach of having various profiles (even without the whole dependency story). I mean, that 'any' in the statement already expands to 'with a given architecture and given UX and given hardware'. > The Qt / Qt Mobility / Web Runtime game combined with the different UXs is already more complex than the setup offered by Android and iOS. Then why agree to fight the battle on their terms ? Why go for diversity as your main strength and then try to compete in terms of monolithic development models ? Best regards, Attila
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
