What do you want opened in Diablo? - Part 2
 

With some recent actions, I think there is an additional issue to consider to those in http://talk.maemo.org/showthread.php?t=32448.

1) In December, Nokia indicated some criteria for opening Diablo components:
Nurturing application development: There is a strong argument proving that opening a component will bring more and better apps for end users.
Spread of Maemo driven technologies to other platforms: A component fits well in a gap existing in other Linux/OSS based projects and there is a concrete interest on collaborating and contributing to a component if it's opened.
Better architecture: A closed component is sitting in the middle of open components making things more difficult that needed to developers interested in that area.

2) We now have data on the openness of components in Diablo thanks to stskeeps
http://mer-project.blogspot.com/2010...-pr11-and.html

3) There is now concrete method proposed for requesting opening components (also thanks to stskeeps)
http://talk.maemo.org/showthread.php?t=44127

4) Meego announced as replacement for Harmattan on mulitple devices and (unlike Harmattan) will continue to support GTK+ (www.meego.com)

5) There is hope that hildon apps might be made to work on MeeGo:
http://talk.maemo.org/showpost.php?p...0&postcount=19

So this raises a new question in my mind, what components should be opened for helping Hildon apps (and related technologies) to work on MeeGo devices? This, of course, implicates the issue of whether getting Hildon to work on MeeGo devices is achievable goal(by adding upstream to MeeGo or forking), but perhaps a GTK+ or Maemo GTK+ expert can start another thread on that topic.

(Please, no idealogical discussions on open source generally or Nokia's openness, etc.,)

Re: What do you want opened in Diablo? - Part 2
 

Link 2) is wrong.

Re: What do you want opened in Diablo? - Part 2
 

Now fixed.

Re: What do you want opened in Diablo? - Part 2
 

Bug 4520 is marked Maemo 5; is it equally applicable to Diablo?

Also, should we also file a similar bug for hildon-control-panel too since it has similar problem that it can't be built on open source platform without libcodelockui1-dev?

Re: What do you want opened in Diablo? - Part 2
 

iphb is not relevant to diablo, and anyway libiphb could be implemented from scratch in an hour or two.

Re: What do you want opened in Diablo? - Part 2
 

OK. Thanks. I voted for opening it anyway.

Back to the question of what Diablo components should be opened up to facilitate easily porting Diablo apps to run on top of Meego? (released soon with UI supported by gtk+/clutter) What is blocking? What are the dependencies? etc.