Thread: Nokia, document your APIs
View Single Post
qwerty12's Avatar
qwerty12 is offline qwerty12
2010-01-31 , 10:38
Posts: 4,274 | Thanked: 5,358 times | Joined on Sep 2007 @ Looking at y'all and sighing
#3
Originally Posted by jacktanner View Post
Meet bug 6694. Brief summary: Nokia ships proprietary software on the N900 (Media Player) that exploits some internal API to achieve useful behavior. Open source developers of competing applications that want to use the same API ask for documentation and are told to wait... and wait... They propose a workaround, and then are told that their workaround is somehow bad with no further explanation...

Bad Nokia, bad. Document your APIs and stop screwing around.
Yes, that person getting annoyed was me.
Not because I'm told that my way of editing the policy file is wrong, but because I'm not told the "right" way, instead.
The "promised" libplayback documentation that we'd receive with the new Maemo 5 release (PR 1.1) has still hasn't appeared in http://maemo.org/api_refs/5.0/5.0-final/. I think it's because editing the policy file is the only way. It's said on there that the Media Player does it a different way and that D-Bus should be sniffed but I know that's not true as mafw-dbus-wrapper is listed in the policy file (which the Media Player uses). Not to mention my libplayback example causes no sound to be output from the app (libplayback complains in syslog about authorisation or something) until I edit the policy file allowing it.

P.S. I have nothing against the person but they really need to cut the **** and tell it like how it is.
Last edited by qwerty12; 2010-01-31 at 13:15.
 

The Following 5 Users Say Thank You to qwerty12 For This Useful Post: