Comments for Replicating memes

Comment on Avoiding duplicate album art storage on the N9 by pvanhoof

pvanhoof — Sun, 28 Aug 2011 12:59:07 +0000

For no particular reason

Comment on Avoiding duplicate album art storage on the N9 by Thomas Vander Stichele

Thomas Vander Stichele — Fri, 26 Aug 2011 03:08:46 +0000

Why symlinking in the code, instead of just doing hardlinking ? Is it using a file system that doesn’t support hardlinks?

Comment on Avoiding duplicate album art storage on the N9 by pvanhoof

pvanhoof — Fri, 19 Aug 2011 09:40:44 +0000

It does. Afaik it at this moment still makes its own thumbnails from the album-art, instead of using the platform ‘s thumbnailer, but I think that this is being fixed.

However, I do think that the music player teams plans to also only use albums. Right now it uses both album and artist, but I think they want to start using the album part only. Just like on Fremantle.

Perhaps you can influence their decision on this? Tracker doesn’t mind and stores both the album-only and album-artist (if album-artist is different than album-only, a new file is used. When both are the same a symbolic link is created to the album-only file. So music player can use both).

Comment on Avoiding duplicate album art storage on the N9 by Andrew Flegg

Andrew Flegg — Thu, 18 Aug 2011 18:57:27 +0000

Out of interest, does Harmattan’s Media Player better follow the Media Art Storage Spec you reference?

Fremantle had an annoying bug where the artist wasn’t actually used (in violation of the spec, AFAICT) to “solve” the case of compilation albums; unfortunately breaking “Greatest Hits” albums in the process.

https://bugs.maemo.org/show_bug.cgi?id=7263

Comment on Support for null with Tracker’s INSERT OR REPLACE feature. by pvanhoof

pvanhoof — Wed, 10 Aug 2011 10:44:11 +0000

Looks like we do want to support it this way, so I’ll be debugging all the reordering quirks out of it before committing to master and then we’ll just guarantee that it works and make a few unit tests for it to ensure that we’ll forever support it this way.

Comment on Support for null with Tracker’s INSERT OR REPLACE feature. by pvanhoof

pvanhoof — Wed, 10 Aug 2011 03:58:45 +0000

Update on this: I have solved the ordering problem, so right now the null upfront a new set of values for a multivalue property is something that works as expected. But hold on tight; I will discuss this firstly with Jürg and also the other team members before making the decision whether or not we’ll support this that way.

Comment on Support for null with Tracker’s INSERT OR REPLACE feature. by pvanhoof

pvanhoof — Tue, 09 Aug 2011 09:46:30 +0000

Note that for multivalue properties the order in which the triples are processed isn’t guaranteed. So you should not do things like this:

INSERT OR REPLACE { nie:dataSource null ; nie:dataSource ; nie:dataSource }

One could believe that this first resets the list of objects, and then sets a new list with and as objects for the multivalue property. Not necessarily true: the processing order isn’t guaranteed. At least not at this moment; not in the current implementation.

If you want to do this, still use the DELETE:

DELETE { nie:dataSource ?d } WHERE { nie:dataSource ?d }
INSERT { nie:dataSource ; nie:dataSource }

I know that this makes the feature kinda pointless for multivalue properties. So perhaps we’ll review the situation (if it’s possible to get it right in a sane way, as this stuff involves transactions. So certain things aren’t easy to get right).

Comment on Refactoring our writeback system by Philip Van Hoof

Philip Van Hoof — Sat, 23 Jul 2011 15:05:36 +0000

The API will be deprecated and no longer will its use be recommended. But indeed, we can’t break API in 0.10. Flawed design or not.

Comment on Refactoring our writeback system by A. T.

A. T. — Sat, 23 Jul 2011 12:37:29 +0000

are you sure that _any_ API promise is enough excuse for race conditions being almost embedded by design?

Comment on We delivered by บรรจุภัณฑ์อ่อนตัว

บรรจุภัณฑ์อ่อนตัว — Fri, 08 Jul 2011 03:15:28 +0000

I suspect no evidence would ever convince.

Comment on We delivered by Eric

Eric — Tue, 05 Jul 2011 13:55:24 +0000

Congrats on the N9 release, hopefully it will show management that they made the wrong choice with WP7, though I suspect no evidence would ever convince.

The “unofficial” N950 had me reconsidering the never again stance I took on Nokia when the GSM radio in my N900 quit 13 months after purchase and the Nokia service reps wouldn’t let me _pay_ to have them fix it. Their only solution was “buy a new one.” But the N9, without a hardware keyboard, is a no go. I guess I am still stuck with Android until someone makes a decent handset running Meego.

Comment on We delivered by pvanhoof

pvanhoof — Tue, 28 Jun 2011 09:01:24 +0000

Develop software, apps, for it.

Comment on We delivered by Anonymous

Anonymous — Mon, 27 Jun 2011 23:28:08 +0000

Great job. What can we do as community to make N9 a sustainable product?

Comment on We delivered by pvanhoof

pvanhoof — Mon, 27 Jun 2011 00:29:15 +0000

Sorry

Comment on We delivered by pvanhoof

pvanhoof — Sun, 26 Jun 2011 12:39:03 +0000

For your work on QtContacts and its Tracker integration you should feel especially proud, Mathias ;-) The contacts API is used by a lot of software on the device and will probably be used by a lot of apps too. But yeah, I can imagine being exhausted. It was messy before you joined that project, but how it's using Tracker now is a whole lot better.

Comment on We delivered by Mathias Hasselmann

Mathias Hasselmann — Sun, 26 Jun 2011 11:46:22 +0000

Too exhausted to feel proud… Really just way too exhausted.

Comment on We delivered by Leho Kraav

Leho Kraav — Sat, 25 Jun 2011 22:21:33 +0000

@Jon: you make some good points. Yet, at the same time it seems as we are at a rather unique position. Unless getting one of these N9s really breaks the bank, I think it could still be a good bet looking from an ecosystem + effort support and next level idea generation standpoints at the very least. Nobody has said either one has to get it at retail prices, there are surely bound to be some unhappy early adopters letting them loose on the secondhand market. So what if you’re a few months late, cost of all of these gadgets will keep dropping like a stone.

Comment on We delivered by Jon Pritchard

Jon Pritchard — Sat, 25 Jun 2011 20:56:19 +0000

The software on the N9 looks amazing. It’s just some of the hardware choices that have me disappointed. I think it’ll have massive appeal. The only thing that’ll stop people from buying it, is its very uncertain future, or its fatal future, rather.

Well done on all the work you guys put into it though. I hope it fixes some of my annoyances with my N900 :)

Comment on We delivered by pvanhoof

pvanhoof — Sat, 25 Jun 2011 14:14:28 +0000

To the more critical comments of the last few hours: I’m glad the criticism is mostly on Nokia’s management decisions, and not on the product itself. We worked insanely hard to make it happen. And that’s all we can do.

To quote a friend: we did ourselves proud, even if Nokia management didn’t.

Comment on We delivered by pvanhoof

pvanhoof — Sat, 25 Jun 2011 14:09:07 +0000

Yes