Hi, I'm using STON, precisely for its textual nature, because for collaborative writing it would be nice to have a diff friendly storage format. Still I haven't had the time to make my ston grafoscopio notebooks diff friendly when long lines appear (they're treated by fossil as binaries) but seems not to difficult to do (is mostly about having time to play with it). Cheers, Offray On 29/11/15 10:56, Sven Van Caekenberghe wrote:

Fuel is binary, faster and store more special kinds of objects. STON is textual, you can read and edit it, better suited for model objects.

...

On 29 Nov 2015, at 16:35, Johan Fabry <jfabry@dcc.uchile.cl> wrote:

Hi,

have a look at Fuel, It’s included in the image. See http://files.pharo.org/books/enterprisepharo/book/Fuel/Fuel.html for more info.

...

On Nov 29, 2015, at 11:57, Dimitris Chloupis <kilon.alios@gmail.com> wrote:

Just wondering what my options are about sharing data between images, should I use Ston ? A database ? something else ?

I would prefer options that have as few dependencies as possible and something that does not require from my users to install external stuff.

For now Ston looks like a good option but I am very new to all this so I would welcome any advice from the pharo experts.

---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

I do, but I have not made them diff friendly, because I store "documents" on them, so is easy to have long lines inside them that are treated as binaries in my DVCS (fossil). Sven have told me some approaches to deal with this, but I haven't had the time to explore them. Cheers, Offray On 30/11/15 12:37, Dimitris Chloupis wrote:

you wanna version control your STON files ? sound reasonable.

On Mon, Nov 30, 2015 at 6:56 PM Offray Vladimir Luna Cárdenas <offray@riseup.net <mailto:offray@riseup.net>> wrote:

Hi,

I'm using STON, precisely for its textual nature, because for collaborative writing it would be nice to have a diff friendly storage format. Still I haven't had the time to make my ston grafoscopio notebooks diff friendly when long lines appear (they're treated by fossil as binaries) but seems not to difficult to do (is mostly about having time to play with it).

Cheers,

Offray

On 29/11/15 10:56, Sven Van Caekenberghe wrote: > Fuel is binary, faster and store more special kinds of objects. STON is textual, you can read and edit it, better suited for model objects. > >> On 29 Nov 2015, at 16:35, Johan Fabry <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote: >> >> Hi, >> >> have a look at Fuel, It’s included in the image. See http://files.pharo.org/books/enterprisepharo/book/Fuel/Fuel.html for more info. >> >>> On Nov 29, 2015, at 11:57, Dimitris Chloupis <kilon.alios@gmail.com <mailto:kilon.alios@gmail.com>> wrote: >>> >>> Just wondering what my options are about sharing data between images, should I use Ston ? A database ? something else ? >>> >>> I would prefer options that have as few dependencies as possible and something that does not require from my users to install external stuff. >>> >>> For now Ston looks like a good option but I am very new to all this so I would welcome any advice from the pharo experts. >> >> >> ---> Save our in-boxes! http://emailcharter.org <--- >> >> Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/%7Ejfabry> >> PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile >> > >

" have a look at Fuel, It’s included in the image. See http://files.pharo.org/books/enterprisepharo/book/Fuel/Fuel.html for more info." FUEL !!! Lol how I forgot about it ? Nice , I think its exactly what I was looking for , thanks. "Fuel is binary, faster and store more special kinds of objects. STON is textual, you can read and edit it, better suited for model objects." Yeah both options look very good, I think I may need something fast because I may end up with a lot of data (3d graphics data). So I will go with Fuel. The nice thing about STON is that because is JSON it will be easier to move between different languages. But then nothing stops me from choosing Fuel and making also a JSON exporter with STON. "I used message pack before. Nice thing is that you can easily also integrate to other environments." Thanks will take a look at this as well.