[Sugar-devel] Call for testing and feedback: alternative Journal implementation

[Christophe Guéret]

Dear everyone,

I've updated the installation bundle for SemanticXO and also fixed a few
bugs reported on this mail thread.
To play around with the code:
* go to http://git.sugarlabs.org/semanticxo/main/trees/master/patch_my_xo
* put the files "patch_my_xo.py" and "semanticxo.tgz" somewhere on the XO
* login as root, set patch_my_xo.py to be executable and type
"./patch_my_xo.py setup"
* reboot

It's a very harsh script that will just overwrite the standard Journal code
and erase all the content. I've tested it on a couple of XO-1. If
everything works fine, you won't see any difference.
To see what happens in the back-end, open a web browser to
http://<IP_OF_THE_XO>:8080
to see the content of the triple store.

I'd now like to implement something to remotely query an XO triple store
from an activity.
Does anyone know if it is possible to get an IP of a neighbour returned by
the presence service?
Or, shall I better wrap external calls to the triple store in a DBus API,
even if that is all plain HTTP?

Christophe

On 2 July 2012 17:38, Christophe Guéret <c.d.m.gueret at vu.nl> wrote:

> Hi Aleksey,
>
> I've packaged redstore to SD:Factory repos
>> (
>> https://packages.sugarlabs.org/project/monitor?project=SweetsDistribution:Factory
>> )
>> the package is "redstore" that provides "redstore" command and
>> "redstored" init.d script.
>
> Great! Many thanks :)
>
>
>> I didn't make it autorun in case if you will use it in
>> the same way as Journal (and Sugar Network database), i.e., keep
>> database in ~/.sugar/<PROFILE> and start daemon from current user's
>> session.
>>
> Could you point me to an example on how to set this up?
> Currently I set the database system wide and start the daemon at boot time
> but switching to a user session would make sens.
>
>
>> btw, it might be useful to create SemanticXO package as well and make it
>> pluggable like it was done with Sugar Network (checkbox in "Sweets
>> Distribution" Control Panel component). i.e., it should regular DBus
>> service that provides the same Dbus API as sugar-datastore. If you will
>> do that, I think it will be possible to plug either sugar-datastore or
>> SemanticXO in runtime.
>>
> It is already the case, on my test machines I remove sugar-datastore to
> put the one provided by SemanticXO instead.
> That one uses the same DBUS API and service name. I will look into
> packaging it.
>
> I was slowed down on SemanticXO recently, I hope to be able to get back in
> speed soon...
>
> Christophe
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20120707/5e0253ea/attachment.html>