Thread: [java-gnome-hackers] Useful lists
Brought to you by:
afcowie
Menu
▾
▴
java-gnome-hackers
|
From: Andrew C. <an...@op...> - 2010-10-30 18:59:54
|
Just a passing comment: as major API changes are happening in GTK towards 3.0, useful mailing lists to be subscribed to are: http://mail.gnome.org/mailman/listinfo/gtk-devel-list http://mail.gnome.org/mailman/listinfo/desktop-devel-list A recent email on gtk-devel-list pointed to http://library.gnome.org/devel/gtk/unstable/gtk-migrating-2-to-3.html which I hadn't known about until now. Cheers, AfC Granada |
|
From: Alexander B. <ab...@ro...> - 2010-11-16 15:14:25
|
lör 2010-10-30 klockan 19:55 +0200 skrev Andrew Cowie: > Just a passing comment: as major API changes are happening in GTK > towards 3.0, useful mailing lists to be subscribed to are: Yup, this already happened with the Fedora package in rawhide (the future F15 release) as libnotify was updated to 0.7.0 and java-gnome won't build with that. (So I need a snapshot, rc or release which does.) Possibly I can provide a patch myself, as the changes seem rather trivial but it needs to be done in a way that'll still work with older libnotify releases. Is it ok to change the API exposed to the Java side? IIRC java-gnome isn't declare API stable but it'd be weird to have different APIs depending on which libnotify version it was compiled with. I guess the simplest solution is to change the API for all java-gnome users regardless of which libnotify it was compiled with... > From: Matthias Clasen <mc...@re...> > Datum: Mon, 01 Nov 2010 21:12:47 -0400 > Here is an overview of the api changes: > > notify_notification_new_with_status_icon is gone > notify_notification_attach_to_status_icon is gone > notify_notification_attach_to_widget is gone > notify_notification_set_geometry_hints is gone > notify_notification_new has lost its widget argument > > A typical patch will look like this one: > https://bugzilla.gnome.org/review?bug=632327&attachment=172525 > > For some background on these changes, see > http://live.gnome.org/GnomeShell/Design/Guidelines/MessageTray/Compatibility /Alexander |
|
From: Serkan K. <se...@ge...> - 2010-11-17 05:36:48
|
As immediate intervation we should restrict libnotify version in our configure script to < 0.7.0 and deprecate the removed methods. Then I may introduce a branch that does the opposite and removes the deprecated methods. 2010/11/16 Alexander Boström <ab...@ro...>: > lör 2010-10-30 klockan 19:55 +0200 skrev Andrew Cowie: >> Just a passing comment: as major API changes are happening in GTK >> towards 3.0, useful mailing lists to be subscribed to are: > > Yup, this already happened with the Fedora package in rawhide (the > future F15 release) as libnotify was updated to 0.7.0 and java-gnome > won't build with that. (So I need a snapshot, rc or release which does.) > > Possibly I can provide a patch myself, as the changes seem rather > trivial but it needs to be done in a way that'll still work with older > libnotify releases. > > Is it ok to change the API exposed to the Java side? IIRC java-gnome > isn't declare API stable but it'd be weird to have different APIs > depending on which libnotify version it was compiled with. > > I guess the simplest solution is to change the API for all java-gnome > users regardless of which libnotify it was compiled with... > > >> From: Matthias Clasen <mc...@re...> >> Datum: Mon, 01 Nov 2010 21:12:47 -0400 > >> Here is an overview of the api changes: >> >> notify_notification_new_with_status_icon is gone >> notify_notification_attach_to_status_icon is gone >> notify_notification_attach_to_widget is gone >> notify_notification_set_geometry_hints is gone >> notify_notification_new has lost its widget argument >> >> A typical patch will look like this one: >> https://bugzilla.gnome.org/review?bug=632327&attachment=172525 >> >> For some background on these changes, see >> http://live.gnome.org/GnomeShell/Design/Guidelines/MessageTray/Compatibility > > > /Alexander > > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today > http://p.sf.net/sfu/msIE9-sfdev2dev > _______________________________________________ > java-gnome-hackers mailing list > jav...@li... > https://lists.sourceforge.net/lists/listinfo/java-gnome-hackers > |
|
From: Serkan K. <se...@ge...> - 2011-01-16 20:09:49
Attachments:
libnotify-0.7.0-old-latest.patch
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 17-11-2010 07:36, Serkan Kaba wrote: > As immediate intervation we should restrict libnotify version in our > configure script to < 0.7.0 and deprecate the removed methods. Then I > may introduce a branch that does the opposite and removes the > deprecated methods. I'm attaching a patch that deprecates methods that will be removed when we link against 0.7.0 and check that libnotify < 0.7.0 exists. Guillaume will be working on libnotify-0.7.0 branch for Debian packaging (Debian unstable has libnotify 0.7.0) But as 0.7.0 is breaking a lot of reverse dependencies, it will take time for it to go mainstream. So this branch will stay experimental for some time and won't be merged to mainline until libnotify 0.7.0 is mainstream. - -- Sincerely, Serkan KABA -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0zUH4ACgkQRh6X64ivZaIGFwCfd3ke6ASK+Ya2JMbD5NoFTCTV AOAAnj8DabByDt7ZaXW7sxqmjSNQN43K =PAhq -----END PGP SIGNATURE----- |
|
From: Andrew C. <an...@op...> - 2011-01-17 00:07:12
|
On Sun, 2011-01-16 at 22:09 +0200, Serkan Kaba wrote: > I'm attaching a patch that deprecates methods that will be removed when > we link against 0.7.0 and check that libnotify < 0.7.0 exists. Merged to 'mainline' AfC Sydney |
|
From: Serkan K. <se...@ge...> - 2011-01-17 16:44:56
Attachments:
libnotify-0.7.0-old-latest-2.patch
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I forgot to deprecate one method. Here's another bundle that deprecated the last missing method. - -- Sincerely, Serkan KABA -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk00cfwACgkQRh6X64ivZaJdyQCfZWPF0AryTbWMWUVkeV0agtHV ZPMAnR1ByWV/bcvbKJclzsFeSNWMuVXI =rpOl -----END PGP SIGNATURE----- |
|
From: Serkan K. <se...@ge...> - 2011-01-17 08:51:43
|
I want to explain the roadmap for libnotify 0.7.0 support here. As discussed in release planning thread, 4.0 series will stick with gtk+/gnome 2. Since libnotify-0.7 depends on gtk3, >=libnotify-0.7.0 work will be done in 4.1 series, where all gtk3 work is done. Regards, Serkan |
|
From: Serkan K. <se...@ge...> - 2011-01-19 17:31:21
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 17-01-2011 10:51, Serkan Kaba wrote: > I want to explain the roadmap for libnotify 0.7.0 support here. > > As discussed in release planning thread, 4.0 series will stick with > gtk+/gnome 2. Since libnotify-0.7 depends on gtk3, >=libnotify-0.7.0 > work will be done in 4.1 series, where all gtk3 work is done. Carefully examining configure.ac I see that only tests depend on gtk3 and libnotify 0.7.x depends on >=glib-2.26, is it possible to support glib-2.26 in gtk2 branch? If so I may reconsider removal when gtk2 branch is bumped to glib-2.26 Sorry for misinforming you guys. - -- Sincerely, Serkan KABA -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk03H9oACgkQRh6X64ivZaIWEgCeJ4cIBvMgvl4CeMpOAUklQ/xb ChMAn1WzaEaQ7a5kase1rYklOSj91YjM =mjZy -----END PGP SIGNATURE----- |
|
From: Serkan K. <se...@ge...> - 2011-01-31 18:07:44
Attachments:
libnotify-0.7-new.patch
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 16-11-2010 16:56, Alexander Boström wrote: > lör 2010-10-30 klockan 19:55 +0200 skrev Andrew Cowie: >> Just a passing comment: as major API changes are happening in GTK >> towards 3.0, useful mailing lists to be subscribed to are: > > Yup, this already happened with the Fedora package in rawhide (the > future F15 release) as libnotify was updated to 0.7.0 and java-gnome > won't build with that. (So I need a snapshot, rc or release which does.) > > Possibly I can provide a patch myself, as the changes seem rather > trivial but it needs to be done in a way that'll still work with older > libnotify releases. > > Is it ok to change the API exposed to the Java side? IIRC java-gnome > isn't declare API stable but it'd be weird to have different APIs > depending on which libnotify version it was compiled with. > > I guess the simplest solution is to change the API for all java-gnome > users regardless of which libnotify it was compiled with... > > >> From: Matthias Clasen <mc...@re...> >> Datum: Mon, 01 Nov 2010 21:12:47 -0400 > >> Here is an overview of the api changes: >> >> notify_notification_new_with_status_icon is gone >> notify_notification_attach_to_status_icon is gone >> notify_notification_attach_to_widget is gone >> notify_notification_set_geometry_hints is gone >> notify_notification_new has lost its widget argument >> >> A typical patch will look like this one: >> https://bugzilla.gnome.org/review?bug=632327&attachment=172525 >> >> For some background on these changes, see >> http://live.gnome.org/GnomeShell/Design/Guidelines/MessageTray/Compatibility > > > /Alexander I'm attaching a patch that can be applied to v4.0.18 to nuke all these methods. I'll keep this branch as "to be merged later" (probably until mainline distros have it in their stable versions). Samuli will be testing it for Gentoo (And applying the patch based on libnotify version being linked against). I remember Guillaume hitting the same issue with Debian/Ubuntu packaging in unstable/experimental branch. - -- Sincerely, Serkan KABA Gentoo Developer Java/GNOME Developer -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1G+mIACgkQRh6X64ivZaL8fACeNCkTJB3PJOpIX15M0HRYhFk5 zJcAnRuGGjOP9VJgUY8y5XjnreopgFTa =9kjq -----END PGP SIGNATURE----- |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X