Re: Call to maintainers: GNOME 2.31 to ship GTK 2.90

2010-06-12 Thread Bastien Nocera
On Fri, 2010-06-11 at 18:36 +0200, Xavier Claessens wrote:
 Le 10/06/10 13:27, Richard Hughes a écrit :
  On 10 June 2010 12:24, Andre Klapperak...@gmx.net  wrote:
  This requires module maintainers to port their modules now (if you don't
  want an angry release-team mob soon in front of your house).
 
  So, should we be requesting gtk3= 2.90 in configure.ac now? At least
  for Fedora rawhide the lack of gtk-engines makes all the gtk3-using
  application look fugly.
 
 To make Empathy build with gtk3 we need:
 
   - libcanberra-gtk-3
   - libchamplain-gtk-3
   - libclutter-gtk-3
   - libunique-3 (or drop gtk2 compatibility and use GtkApplication)

https://bugzilla.gnome.org/show_bug.cgi?id=618473

Emmanuele could do a release.

   - libwebkit-3
 
 Once they are all released and parallel installable (we would like to 
 not lose gtk2 compatibility), we are ready to make the move :-)

Why is losing GTK2 compatibility a problem? It shouldn't matter. You
could create a gnome-2-32 branch and make changes there if you wanted.

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Call to maintainers: GNOME 2.31 to ship GTK 2.90

2010-06-12 Thread Sandy Armstrong
On Sat, Jun 12, 2010 at 5:49 AM, Bastien Nocera had...@hadess.net wrote:
 On Fri, 2010-06-11 at 18:36 +0200, Xavier Claessens wrote:
 Once they are all released and parallel installable (we would like to
 not lose gtk2 compatibility), we are ready to make the move :-)

 Why is losing GTK2 compatibility a problem? It shouldn't matter. You
 could create a gnome-2-32 branch and make changes there if you wanted.

I can't speak for Xavier, but some of us maintain applications for
which the latest version is commonly in demand from users of older
distros, and maintaining a separate branch is a fair amount of work if
you're the only one doing testing, QA, and release management.

There's no way I can consider dropping GTK2 compatibility from Tomboy
for the next year or so, for example.  I don't have the resources to
maintain two versions.

A separate but related issue is that unless somebody plans to update
gtk-sharp, Tomboy may not be GTK3 compatible this cycle (I don't know
off-hand what parts of gtk-sharp may be incompatible with GTK3).  Do
other non-C apps have similar issues, or is this just a problem with
the Mono bindings?

Sandy
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Call to maintainers: GNOME 2.31 to ship GTK 2.90

2010-06-12 Thread Xavier Claessens

Le 12/06/10 14:49, Bastien Nocera a écrit :

On Fri, 2010-06-11 at 18:36 +0200, Xavier Claessens wrote:

Le 10/06/10 13:27, Richard Hughes a écrit :

On 10 June 2010 12:24, Andre Klapperak...@gmx.net   wrote:

This requires module maintainers to port their modules now (if you don't
want an angry release-team mob soon in front of your house).


So, should we be requesting gtk3= 2.90 in configure.ac now? At least
for Fedora rawhide the lack of gtk-engines makes all the gtk3-using
application look fugly.


To make Empathy build with gtk3 we need:

   - libcanberra-gtk-3
   - libchamplain-gtk-3
   - libclutter-gtk-3
   - libunique-3 (or drop gtk2 compatibility and use GtkApplication)


https://bugzilla.gnome.org/show_bug.cgi?id=618473

Emmanuele could do a release.


   - libwebkit-3

Once they are all released and parallel installable (we would like to
not lose gtk2 compatibility), we are ready to make the move :-)


Why is losing GTK2 compatibility a problem? It shouldn't matter. You
could create a gnome-2-32 branch and make changes there if you wanted.


Ubuntu told me that Maverick (the next ubuntu release) is not going to 
ship GTK3, and if we can't build Empathy with GTK2 then they'll just 
keep Empathy 2.30.x... tbh I think that's a bad decision from Ubuntu, 
but it would be really sad to not ship the latest empathy...


But I guess if the whole GNOME 2.32 depends on GTK3 then they'll change 
their mind.



Regards,
Xavier Claessens.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Call to maintainers: GNOME 2.31 to ship GTK 2.90

2010-06-12 Thread Bastien Nocera
On Sat, 2010-06-12 at 17:31 +0200, Xavier Claessens wrote:
 Le 12/06/10 14:49, Bastien Nocera a écrit :
  On Fri, 2010-06-11 at 18:36 +0200, Xavier Claessens wrote:
  Le 10/06/10 13:27, Richard Hughes a écrit :
  On 10 June 2010 12:24, Andre Klapperak...@gmx.net   wrote:
  This requires module maintainers to port their modules now (if you don't
  want an angry release-team mob soon in front of your house).
 
  So, should we be requesting gtk3= 2.90 in configure.ac now? At least
  for Fedora rawhide the lack of gtk-engines makes all the gtk3-using
  application look fugly.
 
  To make Empathy build with gtk3 we need:
 
 - libcanberra-gtk-3
 - libchamplain-gtk-3
 - libclutter-gtk-3
 - libunique-3 (or drop gtk2 compatibility and use GtkApplication)
 
  https://bugzilla.gnome.org/show_bug.cgi?id=618473
 
  Emmanuele could do a release.
 
 - libwebkit-3
 
  Once they are all released and parallel installable (we would like to
  not lose gtk2 compatibility), we are ready to make the move :-)
 
  Why is losing GTK2 compatibility a problem? It shouldn't matter. You
  could create a gnome-2-32 branch and make changes there if you wanted.
 
 Ubuntu told me that Maverick (the next ubuntu release) is not going to 
 ship GTK3, and if we can't build Empathy with GTK2 then they'll just 
 keep Empathy 2.30.x... tbh I think that's a bad decision from Ubuntu, 
 but it would be really sad to not ship the latest empathy...

And you're telling me that your decision on keeping a GTK+ 2.x version
is based on one distributor's dubious decision? GNOME 3.x will be based
on GTK+ 3.x.

 But I guess if the whole GNOME 2.32 depends on GTK3 then they'll change 
 their mind.

I know that all my modules will.

Cheers

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Shell + Tracker + Zeitgeist

2010-06-12 Thread Seif Lotfy
Looking at the mockups by McCann I am looking for a Tracker + Zeitgeist
integration in Shell.


Except for Frequent, and Conversations I think everything else can be done
over Tracker...
I would love to know how Frequent will be categorized... I hope in frequency
you could cluster into today, last week, etc...

I would encourage using Tracker to get the data on the desktop... And then
when asking for frequent and Conversations to ask Zeitgeist.

But as an alternative to ease integration I think Tracker guys should look
into supporting our ontology... This way Zeitgeist could use its extensions
to push into Tracker. This way Tracker will know about the events we have
and I think it would make it easier for the shell developers to only query
Tracker for frequent stuff etc... What do you think? We already have the
extensions ready for you guys thanks to Rob Taylor.

Let me know what you think :)

Cheers
Seif
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

API changes in GLib master

2010-06-12 Thread Matthias Clasen
Just a quick note:

There have been a few API changes in GLib master that will probably
affect a few modules:
The g_bus_watch_proxy API has been replaced by a more flexible
GDBusProxy construction.
You can now construct proxies for well-known names instead of unique
names. For more details,
see
http://git.gnome.org/browse/glib/commit/?id=32f2e9a85beedeea36ac7623f68f6eb878465d44

Some more API changes that may land in the next GLib release are outlined in

https://bugzilla.gnome.org/show_bug.cgi?id=621266 GSettings context
clarification
https://bugzilla.gnome.org/show_bug.cgi?id=620952
g_application_register_with_data is an ugly API
https://bugzilla.gnome.org/show_bug.cgi?id=621002 [GApplication]
Switch to using variants for timestamps, split out signals
https://bugzilla.gnome.org/show_bug.cgi?id=621361 Improve GApplication
quit semantics

I know this is inconvenient, and I apologize for it, but we are trying
to land enormous amounts of new functionality this cycle, so please
bear with us while we shake out the warts of the new API.


Matthias
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Call to maintainers: GNOME 2.31 to ship GTK 2.90

2010-06-12 Thread Michael Terry
On 12 June 2010 11:31, Xavier Claessens xclae...@gmail.com wrote:
 Ubuntu told me that Maverick (the next ubuntu release) is not going to ship
 GTK3

I don't think that's true.  I was at the planning session for coming
changes in GNOME at UDS Maverick, and the plan of record was to
include GTK+ and GNOME 3.0.

https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-gnome

-mt
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Call to maintainers: GNOME 2.31 to ship GTK 2.90

2010-06-12 Thread Sandy Armstrong
On Sat, Jun 12, 2010 at 7:36 PM, Michael Terry m...@mterry.name wrote:
 On 12 June 2010 11:31, Xavier Claessens xclae...@gmail.com wrote:
 Ubuntu told me that Maverick (the next ubuntu release) is not going to ship
 GTK3

 I don't think that's true.  I was at the planning session for coming
 changes in GNOME at UDS Maverick, and the plan of record was to
 include GTK+ and GNOME 3.0.

 https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-gnome

Hmm, a Canonical employee approached me just the other day.  He was
told not to include in Maverick packages that depended on GTK3, and
wanted to check with me that Tomboy would remain GTK2-compatible this
cycle, so that he could get our latest unstable releases into
Maverick.

Sandy
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list