CSV and JSON and the most useful file formats to export data between Pharo and any other software.
CSV is for any desktop software (Excel, R, ) and JSON for the web.
Moreover there are easier to read than a XML file.
We use the NeoJSON API for Moose On Web (http://smalltalkhub.com/#!/~VincentBlondeau/MooseOnWeb ) to export the Moose entities through a REST API.
Last week, I have wanted to export some moose data to CSV to do some statistics with it. I searched on smalltalkhub and in the image CSV and I found no CSV writer.
So I wrote it by myself because its faster to write than to search a package in the World Wide Web and I didnt remember Neo
To me, NeoCSV and NeoJSON should be integrated in Moose.
For Artefact, I think PDF is not always used in the Moose projects. The load on demand is a better option.
Vincent
De : moose-dev-bounces@iam.unibe.ch [mailto:moose-dev-bounces@iam.unibe.ch] De la part de Tudor Girba Envoyé : dimanche 30 mars 2014 09:07 À : Moose-related development Objet : [Moose-dev] Re: Artifacts, Neo in the base image?
Exactly. But, at least for CSV we have a need to export groups. So, it would fit.
JSON would also be nice to have by default, just like we have XML.
Doru
On Sun, Mar 30, 2014 at 9:04 AM, Pharo4Stef pharo4Stef@free.fr wrote:
It is much better to have - working configuration - load on demand Else we will end up with spaghetti.
Hi!
I have the impression it makes sense to have Artifact and Neo in the moose
image. These tools are important.
What do you think?
Alexandre
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev