Hi, Sebastian
The Journal is saved in regular files. There are two files available
from the datastore class: metadata and an (optional) data-file. Manash
Raja's remotejournal already creates these files using datastore. I
think a part of the problem is trying to describe a problem from a Sugar
developer's perspective which brings in such extraneous notions as
'ping', 'extended attributes', and git. A class is intended to hide
these implentation details.
Tony
On 05/26/2016 01:56 AM, Samuel Greenfeld wrote:
The one problem with extended attributes is that almost everything
touching and/or archiving the files needs to be aware of them. Some
utilities may lack this functionality, and others have to be told to
actively back these up.
By means of example, XO laptops have to work around the fact that the
ping command in Fedora gets the permissions it needs via extended
attributes for the past several years. The XO imaging solution is not
extended attribute aware, and at the time it was developed ping was
still commonly set setuid root.
On May 22, 2016 9:52 AM, "Sebastian Silva" <sebast...@fuentelibre.org
<mailto:sebast...@fuentelibre.org>> wrote:
Hi Utkarsh,
Perhaps this is an area for improvement in Sugar. The journal
datastore was designed to be more than it is now (see the git
backend discussion).
I always found very silly how Sugar tries very hard to hide files
(even from the command line) when, in fact, it stores journal
objects as files.
It should be relatively simple to modify the Journal to save its
objects as regular files, and store the metadata in "filesystem
extended attributes" (please look that up). I believe this would
relieve a lot of confusion (in the ground) around the journal
(like you are having). Perhaps Tony and the community can be
convinced this is a good idea to implement.
Please read in detail the Sugar Human Interface Guidelines, which
describe the Sugar design in detail. Also read James Simmons
Make-Your-Own-Sugar-Activities which describes a good attempt to
make sense of the implementation from a Sugar Activity developer
perspective.
With regards to the Documents directory, /use the source, /look up
in the journal code exactly how it decides. A good, standards
compliant implementation would use the result of the `xdg-user-dir
DOCUMENTS` command. Are you using system Sugar packages or
sugar-build? sugar-build probably overrides this.
Regards,
Sebastian
El 22/05/16 a las 05:55, Tony Anderson escribió:
Hi, Utkarsh
I may not be able to help. I am testing on an XO. However, the
object is not to use direct paths which may vary between SOAS and
Sugar on an XO.
Documents should be ~/Documents.
Journal objects are stored in ~/.sugar/default/datastore.
However, if you only reference the datastore with the datastore
class -that shouldn't be important.
So you can write them with datastore to the Journal. For
Documents, I use ~/Documents but there is a way to change the
'mount' in the datastore to use the
Documents folder (or to use a USB key).
Tony
On 05/22/2016 12:27 PM, Ütkarsh Tiwari wrote:
Hi,
I am unable to find the location where the sugar-build
stores the
Documents and Journal objects. I would also like to know how to
copy
the external files (.html, .txt, .png, .zip files - outside
sugar-build) to Journal or Documents.
P.S- I am on Ubuntu 15.04
Thanks,
Utkarsh Tiwari
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
<mailto:Sugar-devel@lists.sugarlabs.org>
http://lists.sugarlabs.org/listinfo/sugar-devel
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
<mailto:Sugar-devel@lists.sugarlabs.org>
http://lists.sugarlabs.org/listinfo/sugar-devel
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
<mailto:Sugar-devel@lists.sugarlabs.org>
http://lists.sugarlabs.org/listinfo/sugar-devel
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
