[OE-core] [RFC PATCH 00/12] Sato desktop upgrade (Gtk3 etc.)
Otavio Salvador
otavio.salvador at ossystems.com.br
Fri Mar 11 18:53:55 UTC 2016
On Fri, Mar 11, 2016 at 10:12 AM, Jussi Kukkonen
<jussi.kukkonen at intel.com> wrote:
> Here's a snapshot of the Sato upgrade I've been working on (YOCTO
> #3169). It's based on Ross' work from 2.5 years back. The bigger
> changes currently live as my forks of the upstream projects (gtk3
> branches of various projects at https://github.com/jku), and the
> patchset here modifies recipes to temporarily use those forks:
> this is intended to make testing and review possible but also
> means this is just an RFC: once the upstream changes are merged,
> I'll update this patchset.
>
>
> For those not familiar with it, the goal of the exercise is to
> 1. Bring Sato desktop closer to this decade (Don't depend on
> ancient components, remove deprecated code)
> 2. Focus more on delivering an environment for validating and
> testing oe-core, less on building a DE for mobile devices
>
>
> Major changes:
> * Ports to GTK3: matchbox-desktop, matchbox-panel-2,
> connman-gnome, sato-screenshot, xsettings-daemon
> * GTK+ theme is Adwaita (upstream default)
> * Matchbox WM theme modified to somewhat resemble Adwaita (boring
> gray instead of in-your-face green)
> * Matchbox panel is no longer drawn on top of application titlebars
> because that fails badly with client side decorations. Instead
> it's a thinner panel always on top of screen, like gnome2 panel.
> * Custom GTK theme engine is dropped
> Here's a screenshot showing the panel and window decoration:
> http://imgur.com/noqptiu
>
>
> Regressions:
> * on-screen keyboard: I've not looked very closely but I
> believe this requires IM work for GTK3
> * startup notification
>
>
> Questions:
> * Schedule: this is for Yocto 2.1 in bugzilla (now M3) but got
> delayed. it's a bigger change and isn't ready to merge
> (as the upstream patches need review). Should I aim for next
> release instead?
> * How should we do review on this? The upstreams are mostly on
> yoctoproject.org so I could send patches to some YP mailing list...
> but testing many of the patches is impossible without the patches
> for the other projects.
> * Are the regressions listed above blockers?
> * Anything I've missed? Theme design bikeshedding?
Is matchbox still the way to go? To test OE-Core maybe a custom GTK3
app might be better.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
More information about the Openembedded-core
mailing list