<div dir="ltr">I think is ok if we limit what we can save to a staring, at least on a first stage.<div style>We can recommend use json too.</div><div style> </div><div style>About the api proposed, will you get signals when the metadata is updated, </div> <div style>or should be the same "updated" signal as is the file was modified?</div><div style>I am thinking on the modification on title or description in the journal,</div><div style>right now we update the toolbar entries.</div> <div style> </div><div style>Gonzalo</div><div style> </div></div><div class="gmail_extra"> <div class="gmail_quote">On Wed, May 1, 2013 at 7:25 AM, <<a href="mailto:lionel@olpc-france.org" target="_blank">lionel@olpc-france.org</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div lang="FR" link="blue" vlink="purple"><div> Hmmm. Finally, I wonder if we need to keep the file handling in the JavaScript Datastore interface. I’ve wrote 5 Sugar activities. Each time I’ve only used the Datastore via read_file/write_file functions and each time it was not to store a file but to store a "state". And most of the time this state could be translated to a string (JSON, XML, CSV, …). In fact the only case where a file could be interesting is when we handle binary content (like images). But, at worse it could also be translated to string and this string could be store in the state. I’m interested by feedbacks from the list about this point: do you think that file handling is need for the Datastore? Lionel. De : Daniel Narvaez [mailto:<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>] Envoyé : mardi 30 avril 2013 19:06 À : Lionel Laské Cc : <a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank">sugar-devel@lists.sugarlabs.org</a> Objet : Re: [Sugar-devel] DataStore interface for HTML5 Activity <div><div class="h5"> <div>Doesn't seem to be implemented in webkigtk yet and the work sort of stalled apparently <a href="https://bugs.webkit.org/show_bug.cgi?id=58443" target="_blank">https://bugs.webkit.org/show_bug.cgi?id=58443</a> </div><div> <div>On 30 April 2013 18:42, Daniel Narvaez <<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>> wrote: <blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"><div>The firefox guys are apparently not very keen about the w3c File stuff <a href="https://hacks.mozilla.org/2012/07/why-no-filesystem-api-in-firefox/" target="_blank">https://hacks.mozilla.org/2012/07/why-no-filesystem-api-in-firefox/</a></div><div><div><div> <div>On 30 April 2013 18:27, Daniel Narvaez <<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>> wrote:<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"> <div>As you point out, the main problem here is the concept of file. My understanding is that with the new file APIs you are basically requesting a sandboxed filesystem, then you can write and read there as you please. Though I don't know how the shell would then have access to that filesystem, to be able to move the files into the datastore. Chromium must be doing something similar to allow writing stuff to google drive using those interfaces, though they implemented their interfaces directly into Webkit.</div><div> <div><div><div>On 30 April 2013 17:34, <<a href="mailto:lionel@olpc-france.org" target="_blank">lionel@olpc-france.org</a>> wrote:</div></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"> <div><div><div><div>Hi all, As we decided to our IRC meeting last week, I’ve wrote a first draft proposal for the JavaScript DataStore interface [1]. Basically the interface just match the DataStore existing interface. The main issue is related to the concept of "file":- File is at the heart of the DataStore concept: the DataStore is nothing else than a place to store files and metadata related to files, - But: file handling is not a common practice in JavaScript! The good news is that HTML5 comes with few File system and Files handling functions [2][3].I didn’t test it but it should work on WebKit. Do not hesitate to comment/update. Lionel [1] <a href="http://wiki.sugarlabs.org/go/HTML5_activities#Datastore" target="_blank">http://wiki.sugarlabs.org/go/HTML5_activities#Datastore</a> [2] <a href="http://dev.w3.org/2009/dap/file-system/pub/FileSystem/" target="_blank">http://dev.w3.org/2009/dap/file-system/pub/FileSystem/</a> [3] <a href="http://dev.w3.org/2009/dap/file-system/file-writer.html" target="_blank">http://dev.w3.org/2009/dap/file-system/file-writer.html</a> </div></div> </div></div>_______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote></div> -- Daniel Narvaez</div></blockquote></div> </div></div>-- Daniel Narvaez</div></blockquote></div> -- Daniel Narvaez</div></div></div></div></div> _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote></div> </div>