Re: Beagle Properties
There is still a small amount of stuff that needs to be finished before we can fire off this event. Stay tuned. Changing these properties is pretty dangerous, because we will effectively be changing a string API. That means that apps that use Beagle will still compile, but they will silently break when their old string mappings don't line up to the new ones. So I think it is important for us to take the initiative ourselves to fix the applications and add-on backends and filters that use Beagle. I think it would be helpful to collect a list of these on the wiki page and have it be a core part of this work. That sounds overwhelming ! There are only a few that are within our reach ... yelp, nautilus (and possibly brassero) in gnome cvs and kerry in kde svn. There are more to which we dont have direct access. Isnt there a standard way of making string changes in a way to automatically make applications aware of it ? Can these changes qualify as breaking binary incompatibility; then we can increase library versions for both libbeagle1 and beagle-0.0. - dBera -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle Properties
Hi, On Feb 10, 2008 10:49 AM, Debajyoti Bera [EMAIL PROTECTED] wrote: That sounds overwhelming ! There are only a few that are within our reach ... yelp, nautilus (and possibly brassero) in gnome cvs and kerry in kde svn. There are more to which we dont have direct access. Sure, but we could provide patches. In general it's probably a pretty good exercise anyway to find out who the consumers of our APIs are so that we can find out how good they are, where they could use improvement, etc. Isnt there a standard way of making string changes in a way to automatically make applications aware of it ? Can these changes qualify as breaking binary incompatibility; then we can increase library versions for both libbeagle1 and beagle-0.0. We could do this, yeah. We could bump the API versions of the C# assemblies and the so number of the libbeagle shared libraries. This is probably a good idea. And not to sound like a broken record, but this stuff should probably go on a branch (or create a 0.3.x branch and continue on trunk) so that we don't find ourselves in another rut. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle Properties
is probably a good idea. And not to sound like a broken record, but this stuff should probably go on a branch (or create a 0.3.x branch and continue on trunk) so that we don't find ourselves in another rut. IIRC, there is already a branch dedicated to this ... don't remember the name right now, you can check it in websvn. - dBera -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle Properties
We could do this, yeah. We could bump the API versions of the C# assemblies and the so number of the libbeagle shared libraries. This And maybe also bump beagle version to 1.0 :) OSNews Headline Open source project finally leaves beta. We're doomed! Ok, ok ... I know I am dreaming ... - dBera -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
