607
edits
Changes
Jump to navigation
Jump to search
Line 19:
Line 19: − +
→11 - 17 October 2008
* Wrote a proposal about API stability policy for Glucose. Discussed in the sugar meeting, approved by everyone with minor improvements. Will make the necessary changes and officially post it on the wiki.
* Wrote a proposal about API stability policy for Glucose. Discussed in the sugar meeting, approved by everyone with minor improvements. Will make the necessary changes and officially post it on the wiki.
* Fixed various issues when running multiple Browse instance. Now file pickers and downloads are opened in the right window. Browse needs some code cleanups, I'll try to do so when factoring out things to sugar.web (now unblocked by the API policy decisions)* **
* Fixed various issues when running multiple Browse instance. Now file pickers and downloads are opened in the right window. Browse needs some code cleanups, I'll try to do so when factoring out things to sugar.web (now unblocked by the API policy decisions).
* Started to refactor the zoom levels part of the window management logic, basic on a patch by Benjamin to get rid of flickering in the home view. It's a tricky issue and I'm not fully satisfied about it yet, but I'm making progresses.
* Started to refactor the zoom levels part of the window management logic, basic on a patch by Benjamin to get rid of flickering in the home view. It's a tricky issue and I'm not fully satisfied about it yet, but I'm making progresses.
* Poked OLPC distro developers about the Fedora 10 migration. I hope we can make a call about it soon, because I'd rather use the gtk/gio API to implement standard compliant startup notification. Or maybe we should not bump requirements there until it's widely available on standard distributions? It's possible to implement it using lower level startup-notification API without a lot of effort.
* Poked OLPC distro developers about the Fedora 10 migration. I hope we can make a call about it soon, because I'd rather use the gtk/gio API to implement standard compliant startup notification. Or maybe we should not bump requirements there until it's widely available on standard distributions? It's possible to implement it using lower level startup-notification API without a lot of effort.