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

What to integrate and what to not integrate is a sensitive question.

--

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 <[hidden email]>:
>
> 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

On 02/05/15 23:28, Andy Burnett wrote:
>     Stephan Eggermont said:
>     What is stopping you from adding a build 'Andy's Base Image' to the
>     Pharo-Contribution CI?
>
> Ignorance :-)

Always the same lame excuse :)

> I had no idea such a thing was possible.  It sounds like the ideal
> solution.  Is the process documented somewhere?

Create yourself an account at ci.inria.fr, ask to be added to
pharo-contribution, create a new build by copying one that looks
somewhat similar. Once you are a member, you can browse all the
different build configurations. You probably want to copy from
a build that generates both Pharo4 and Pharo5 images (and older
ones for the things you haven't migrated yet). A build just
needs a configuration.

Stephan

Hi Andy,

I personally almost solely use Moose, as it contains many of the tools I need. Let us know about your experience with Moose.

Cheers
Alexandre

I like the idea I read recently about an easy way to create images so we
can tell what Pharo means to us. I started using Moose 5.0 and 5.1
exclusively, but now with the release of Pharo 4 and the incorporation
of the GTPlayground and Spotter on it, I'm trying to put the data
visualization stuff I would like to use on my daily experience (Roassal,
GT Tools, scrapping and some databases). Hopefully we will learn how to
reach as community that modular moldable, loadable tools for a more
diverse set of images, without having the kitchen sink. Both approaches
are valuable.

Cheers,

Offray

El 03/05/15 a las 10:31, Alexandre Bergel escribió:

we can ask christophe to create a Copy one because some patterns changed. I should sit with him.

Stephan Eggermont said:
<<<

What is stopping you from adding a build 'Andy's Base Image' to the
Pharo-Contribution CI?
>>>

Ignorance :-)

I had no idea such a thing was possible.  It sounds like the ideal solution.  Is the process documented somewhere?

Cheers

Andy