Hello Arjan, > From: Arjan van de Ven [mailto:[email protected]] > Sent: 22 March, 2011 23:44 > the libcommhistory package is not even in any of the images... how can > you claim that it's actually this critical?
Critical in the handset case at least when you need to build Qt models for conversation history and call history. Historically sqlite and tracker storage backends have been supported. I assume it would be usable for tablets and even netbooks (for messaging). Whether it is in the images, it's up to you, the code is there. You can also reinvent it, if needed. > Does the MeeGo dialer even use it? When I spoke with the owner of the > dialer app (which is supposedly the key user of all this), > this really did not come up as something that is currently in use and > working... quite the opposite. I guess this is again up to the dialer owner. Unfortunately we could not open any UI related stuff, and there was no time doing a nice separation of strictly UI related and middleware components, so there are a few internal interfaces which have not been opened but might have made your life much easier. This was mainly because program pressure on this side, we were too busy doing phones. I guess it was frustrating to see code just thrown over the fence, without clear indications how to use it. > (it might work in your maemo OS, but that is of no consideration) :). I can understand why you are moving back to Moblin in these dark times ;). But there are a number of things Maemo got right in the handset case, and it would be pity dumping them and reinventing the pain, since that's going to delay things. (I am not talking about tracker here :). It is important to realize how different the handset case is from the rest. So just not considering it is a mistake. > The MeeGo architecture team made these decisions in consultation with > the various handset and tablet architects. It looks like it was an internal Intel decision (or at least without Nokia). I can't blame you on that, but if the governance model changed in the background, would you state that on meego.com, just to avoid fights coming from false assumptions? > I know it's not popular with you and some other @nokia.com folks... but > so be it. And the reason for this mainly was the way the decision was made, communicated, and how questions, facts and measurements were ignored. Don't you think if it was correctly made, it wouldn't have created such a mail-storm? It was not according to http://wiki.meego.com/Architecture (there was no discussion, just announcement, with all feedback ignored). It was confusing and frustrating to see this secrecy and dictatorial decision making, with no criteria to measure it. I think it would take just a little bit of positive/cooperative attitude to do it much better. Maybe you didn't have much time and for some reason you had to make a quick big decision, I don't know. But please always state what is the goal and how will it be measured. In this tracker-EDS case: data sets, performance tests, measurements. (I have struggled enough with tracker vs sqlite to learn this lesson well. If you think I am on tracker's side, it's wrong: I am on the side of correct technical approach). Then you can choose a solution to the problem, and not vice versa. Regards, Zoltan
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
