[Bug 199681] Review Request: slab

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: slab


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199681


chabotc at xs4all.nl changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chabotc at xs4all.nl




------- Additional Comments From chabotc at xs4all.nl  2006-07-31 08:45 EST -------
Some initial investigation into slab intergration:

The control center is still an old gnome 2.12.3 call, and got changed in 2.14,
this patch (to slab) should solve this problem:

--- control-center/src/control-center.c
+++ control-center/src/control-center.c
@@ -140,7 +140,7 @@
}

AppShellData *app_data =
- appshelldata_new ("preferences.menu", NULL,
+ appshelldata_new ("settings.menu", NULL,
CONTROL_CENTER_PREFIX,
GTK_ICON_SIZE_DIALOG);
generate_categories (app_data);


Second problem is the non working updater, enough discussion already in this
thread about this, so no need to cover that again, short is that it has to be
changed to use pup :-)

Next 'big' problem is the recently used applications, there's 2 ways of dealing
with this that i can think of.

The ubuntu way: 
https://wiki.ubuntu.com/Slab?action=AttachFile&do=get&target=places.patch
It replaces the recently used applications functionality with 'places'
functionality .. not a horrible way to go, but not as fancy as true 'recently
used apps' though :-)

The second option, which i think is the argually 'better way' is to intergrate
the developed patches for the gnome panel and gnome desktop into fedora's .. and
have an actual working 'recent applications' :-) Patches can be viewed here:
http://cvs.gnome.org/viewcvs/slab/patch/



-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.