tag:blogger.com,1999:blog-6145140879520785870.post8902788985351315231..comments2022-07-08T11:09:44.844+02:00Comments on thp on Maemo: The Qt promise and what Maemo 5 needsthphttp://www.blogger.com/profile/04893729285856691511noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-6145140879520785870.post-1987743760152411542010-12-15T23:35:33.072+01:002010-12-15T23:35:33.072+01:00There are even more versioning problems when you s...There are even more versioning problems when you start introducing wide, cross-platform promises to developers: "Your app will run on all of these Qt platforms!"<br />What if a commercial app needs to perform a workaround for a bug in a particular version of Qt, and then the whole Qt platform gets upgraded? Oops, that app is broken! And oh no, they're not in business anymore! Oh no, twelve thousand people are running that app (and depending on it!) on Symbian, Maemo, MeeGo, etc! What do those people do? Not upgrade Qt when the official-channel update comes? Add yet another parallel version to their device?Qole Pejorianhttps://www.blogger.com/profile/01124013338592146940noreply@blogger.comtag:blogger.com,1999:blog-6145140879520785870.post-45134987723927948572010-12-15T23:18:53.502+01:002010-12-15T23:18:53.502+01:00Attila: I forgot about runtime memory footprint - ...Attila: I forgot about runtime memory footprint - thanks for the input :)thphttps://www.blogger.com/profile/04893729285856691511noreply@blogger.comtag:blogger.com,1999:blog-6145140879520785870.post-47898981690747200632010-12-15T21:49:55.403+01:002010-12-15T21:49:55.403+01:00The downside of multiple Qt versions is that you a...The downside of multiple Qt versions is that you also multiplying the memory footprint, disk usage is not really the question here. I agree that since Qt is the platform, it should be always upgradeable, but unfortunately it was moving so fast in the last year or so (arguably even now) that compatibility promises were really-really hard to make, and the make-pretend maemo5 widget wrapper thingy is not making it any easier.Attila Csipahttps://www.blogger.com/profile/11082060370940070595noreply@blogger.comtag:blogger.com,1999:blog-6145140879520785870.post-13867015293802336452010-12-15T19:40:41.659+01:002010-12-15T19:40:41.659+01:00Indeed, i agree !Indeed, i agree !Khertanhttps://www.blogger.com/profile/03572788291460748044noreply@blogger.comtag:blogger.com,1999:blog-6145140879520785870.post-23737291629251943962010-12-15T14:12:14.812+01:002010-12-15T14:12:14.812+01:00Khertan: In that case, have two builds of Qt insta...Khertan: In that case, have two builds of Qt installed: The one that is used by the built-in, closed-source apps (this one can be as old as they want) and another one for third party apps. It's better to "waste" some space on the internal memory than to have a broken/fragmented development platform.<br /><br />And this is a non-issue for Maemo 5 where no built-in app depends on Qt (AFAICT).thphttps://www.blogger.com/profile/04893729285856691511noreply@blogger.comtag:blogger.com,1999:blog-6145140879520785870.post-59717229109109293562010-12-15T13:54:47.413+01:002010-12-15T13:54:47.413+01:00The problem i think will not be to release this ne...The problem i think will not be to release this new qt version. But what happen with closed source app made by Manufacturer (here Nokia) which depends on Qt.<br /><br />They ll probably need to test them again the new Qt Version. And if there is a break in the API, they should probably re release a new version. But this will probably be a problem if they don't want to maintain the plateform.Khertanhttps://www.blogger.com/profile/03572788291460748044noreply@blogger.com