Can we have NeoCSV, and NeoJSON included in the base image?
I would find it really useful to have some more classes included in the base image. The Neo system would be particularly useful, but I would also find an XML reader valuable. What is the process for deciding which classes get included by default? Cheers Andy
There are arguments on both sides for whether these are included by default. In general, I understand the goal is limit what is distributed with Pharo, since the ConfigurationBrowser makes loading easy. Moose which is based off Pharo comes with a lot more facilities. In the short term, you might try using a personal-Configuration like this... https://marianopeck.wordpress.com/2011/11/19/loading-projects-and-building-y... cheers -ben On Sat, May 2, 2015 at 11:23 PM, Andy Burnett < andy.burnett@knowinnovation.com> wrote:
I would find it really useful to have some more classes included in the base image. The Neo system would be particularly useful, but I would also find an XML reader valuable.
What is the process for deciding which classes get included by default?
Cheers Andy
What to integrate and what to not integrate is a sensitive question. There was a discussion about that last time. Maybe you can take a look of the discussion here http://forum.world.st/QualityAssistant-v0-4-td4821070.html#none That really begin with the answers of stepharo. Le samedi 2 mai 2015, Ben Coman <btc@openinworld.com> a écrit :
There are arguments on both sides for whether these are included by default. In general, I understand the goal is limit what is distributed with Pharo, since the ConfigurationBrowser makes loading easy. Moose which is based off Pharo comes with a lot more facilities.
In the short term, you might try using a personal-Configuration like this...
https://marianopeck.wordpress.com/2011/11/19/loading-projects-and-building-y...
cheers -ben
On Sat, May 2, 2015 at 11:23 PM, Andy Burnett < andy.burnett@knowinnovation.com <javascript:_e(%7B%7D,'cvml','andy.burnett@knowinnovation.com');>> wrote:
I would find it really useful to have some more classes included in the base image. The Neo system would be particularly useful, but I would also find an XML reader valuable.
What is the process for deciding which classes get included by default?
Cheers Andy
-- Cheers Cyril Ferlicot
On 02/05/15 17:23, Andy Burnett wrote:
I would find it really useful to have some more classes included in the base image. The Neo system would be particularly useful, but I would also find an XML reader valuable.
What is the process for deciding which classes get included by default?
You get a lot of people to complain on the mailing list that they need it, then it gets included, unless too many complain that you can easily load a configuration for it and don't always need it. We're working towards a very small core image where everything gets loaded through configurations. With the CI infrastructure we have it is easy to provide personal standard images containing whatever you want. What is stopping you from adding a build 'Andy's Base Image' to the Pharo-Contribution CI? Stephan
Hi Andy do you know that you can load fully packaged projects in one click? You open the configurationBrowser and select the packages you want and you get them. You can also add them in your startup preference. Finally you can also get a ci job that can load what you want in a image ready made for you. I do not get why we would have to integrate external projects when they - are actively maintained - can be loaded simply We will build Pharo distribution with a certification. So why would we trade a small modular system for a system where everything is loaded by default? Stef Le 2/5/15 17:23, Andy Burnett a écrit :
I would find it really useful to have some more classes included in the base image. The Neo system would be particularly useful, but I would also find an XML reader valuable.
What is the process for deciding which classes get included by default?
Cheers Andy
Am 02.05.2015 um 17:23 schrieb Andy Burnett <andy.burnett@knowinnovation.com>:
I would find it really useful to have some more classes included in the base image. The Neo system would be particularly useful, but I would also find an XML reader valuable.
What is the process for deciding which classes get included by default?
It is a discussion that comes up frequently. But the purpose of using the image is rather a subjective thing. I personally don't want to have things in the image I don't use because I need to remove them before going into production. We have metacello configurations which make it easy to load parts of the stack people like to use. Looking at the installation procedure of a debian/ubuntu image you are asked what is the purpose of this installation be it a mail server, web server, etc. Maybe the best way to tackle this is to have a definition of typical stacks and an easy to use selection of a proper metacello configuration that loads everything someone does not know where to get it. That could be integrated in the open window when starting a fresh image. Either by GUI or by evaluating an expression that does the load. If you have ideas for that just go ahead and provide a configuration of the tools you find important and give it a name that is meaningful to others. Norbert
(...) That could be integrated in the open window when starting a fresh image. Either by GUI or by evaluating an expression that does the load. If you have ideas for that just go ahead and provide a configuration of the tools you find important and give it a name that is meaningful to others.
That seems perfect.
participants (7)
-
Andy Burnett -
Ben Coman -
Cyril Ferlicot -
Norbert Hartl -
Sergio Fedi -
Stephan Eggermont -
stepharo