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
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
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
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 ...
-
Hi,
On Jan 12, 2008 5:31 PM, Lukas Lipka [EMAIL PROTECTED] wrote:
Voila, my ongoing effort is almost finished.
http://beagle-project.org/Properties_Hack_Week
There is still a small amount of stuff that needs to be finished before
we can fire off this event. Stay tuned.
Changing these
provide us with an overview of current Beagle
properties. It would help to align all filters properties (if they mean
the same, they sould have the same name).
3) Finally, with this list, we could quickly create a Beagle ontology.
Here, I am thinking of the currently ongoing rdf branch and metadata
