Smalltalk › Frameworks & Tools › Moose

Artifacts, Neo in the base image?

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 8 messages Options
abergel
Reply | Threaded
Open this post in threaded view
♦
♦
|

Artifacts, Neo in the base image?

abergel
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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Tudor Girba-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Artifacts, Neo in the base image?

Tudor Girba-2
NEO packages are a target since a while now. But, we need a use case first.

The same goes for Artifact.

Anyone wants to play with this?

Doru


On Sat, Mar 29, 2014 at 11:36 PM, Alexandre Bergel <[hidden email]> wrote:
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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
pharo4Stef@free.fr
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Artifacts, Neo in the base image?

pharo4Stef@free.fr
In reply to this post by abergel
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
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Tudor Girba-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Artifacts, Neo in the base image?

Tudor Girba-2
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 <[hidden email]> 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
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Vincent Blondeau
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Artifacts, Neo in the base image?

Vincent Blondeau

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 it’s faster to write than to search a package in the World Wide Web and I didn’t 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 : [hidden email] [mailto:[hidden email]] 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 <[hidden email]> 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
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



 

--

 

"Every thing has its own flow"


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Stéphane Ducasse
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Artifacts, Neo in the base image?

Stéphane Ducasse
Vincent

I want more: We should integrate all the projects of SmalltalkHub because they are cool and useful.
The point is loading a package is not that complex.
Loading everthing by default is the best recipe to get a fat and monolithic system.
IT IS EASIER TO LOAD THAN UNLOAD a package believe me.

Stef



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 it’s faster to write than to search a package in the World Wide Web and I didn’t 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 : [hidden email] [[hidden email]] De la part deTudor 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 <[hidden email]> 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
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


 
--
 
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
pharo4Stef@free.fr
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Artifacts, Neo in the base image?

pharo4Stef@free.fr
In reply to this post by Vincent Blondeau
Vincent

I want more: We should integrate all the projects of SmalltalkHub because they are cool and useful.
The point is loading a package is not that complex.
Loading everthing by default is the best recipe to get a fat and monolithic system.
IT IS EASIER TO LOAD THAN UNLOAD a package believe me.

I would really like that they there is a consensus on what is loaded or not into moose because this is our system!

Stef


On 30 Mar 2014, at 10:16, Vincent BLONDEAU <[hidden email]> wrote:

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 it’s faster to write than to search a package in the World Wide Web and I didn’t 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 : [hidden email] [[hidden email]] De la part deTudor 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 <[hidden email]> 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
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


 
--
 
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Blondeau Vincent
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Artifacts, Neo in the base image?

Blondeau Vincent

 

De : [hidden email] [mailto:[hidden email]] De la part de Pharo4Stef
Envoyé : mardi 1 avril 2014 08:30
À : Moose-related development
Objet : [Moose-dev] Re: Artifacts, Neo in the base image?

 

Vincent

 

I want more: We should integrate all the projects of SmalltalkHub because they are cool and useful.

 

 

Ok ! So load everything ;)

 

The point is loading a package is not that complex.

Loading everthing by default is the best recipe to get a fat and monolithic system.

IT IS EASIER TO LOAD THAN UNLOAD a package believe me.


I trust you.

 

I would really like that they there is a consensus on what is loaded or not into moose because this is our system!

 

I agree and it is a nice system! I just gave my point of view.

 

By the way, if we won't integrate them by default in moose, maybe we should reference them as "reliable" projects somewhere?
On Smalltalkhub there is not yet search tool to query the project tags or descriptions.


I know there is a meta repo created (https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/). And this is a good step!

But is it planned that we can query it ?

Because there is yet almost 200 projects recorded but I don’t want to see each one to check if its purpose can be helpful to mine…

 

Cheers,

 

Vincent

 

Stef

 

 

On 30 Mar 2014, at 10:16, Vincent BLONDEAU <[hidden email]> wrote:



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 it’s faster to write than to search a package in the World Wide Web and I didn’t 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 : [hidden email] [[hidden email]] De la part deTudor 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 <[hidden email]> 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
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



 

--

 

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

 



Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Free forum by Nabble Edit this page