Hi Stef,
Of course the image is a cache, but I do not understand what you are referring to.
We do not develop Moose by copying images around. We load lots of configurations. I agree that we should refactor some of them, and we should remove some of them. Hismo is indeed a good candidate for removing.
But, still the goal of a distribution is to pack together code that brings enough value for a certain audience. And, XML is so pervasive, at least in the projects I was exposed to, that it does not make much sense to claim easy data analysis without supporting it out of the box. Btw, JSON starts to be a candidate as well :).
Btw, from a pragmatic point of view, why do you necessarily need to ignoreImage?
Cheers,Doru
On Thu, Jun 26, 2014 at 4:50 PM, stepharo <stepharo@free.fr> wrote:
This is plain wrong.
Moose is right now bloated because it has two versions of Roassal and two of Graph-ET.
But, XML is a prerequisite in the business of analysis. I am still to encounter a serious analysis project that did not involve some XML. Actually, at this point, as Moose gets to be used in all sorts of non-code related projects, I feel more that FAMIX makes the system bloated.
Load a package when you need it. I would unload Hismo, FAMIX-C, and keep the minimum and not a kitchen sink.
Else you should load also
JSON
and many others.
Even the moose Algos should be loaded on demand.
You are not lucid on the problem. You are like these old smalltalkers that do not understand anything to modularity.
We can have a small moose image where we test that a given list of EXTERNAL packages loads correctly
and run well the tests but are not shipped by default but loadable in one click.
You confuse the system and its cache. Repeat after me: an image is a cache.
Why there is not a metacello browser just for loading moose certified packages?
Because this is the way to go for Pharo and also for Moose.
Moose is becoming untractable. I spent the day trying to find why we cannot snapshot a version of each package
and it I do not find how to make it work with MC. I will go back to my ugly solution (but this is raging because snapshotcello
was an important element) to me it should be part of metacello. But metacello is probably far too complex too.
Stef
Cheers,Doru
On Thu, Jun 26, 2014 at 4:30 PM, stepharo <stepharo@free.fr> wrote:
For me I think that Moose is bloated.
There are far too many packages loaded by default
XML
NeoCSV
....
Stef
On 26/6/14 12:49, Yuriy Tymchuk wrote:
It's on the original Moose job, just another archive called moose-less.zip
The problem is not in Moose. It's even not in the tools, but for now Pharo doesn't provide a good configuration mechanics. I would prefer to be asked when I start the image for the first time if I want to use the alternative theme or tools. And if I don't, I'd prefer to stay with my own setup. We don't have this, and Moose job configures the image for everyone (without asking of course). That's I archive the image before the script is being run, so I can download it and set it up for myself.
For example I use dark theme and apple fonts, but I can't force others to use my configuration.
Uko
Sent from my iPhoneWhere is your ci?
Because
Hi yuri
where is your ci?
Because moose is becoming bloated and I think that we should rethink it.
Stef
The thing is that after loading all packages current build job runs magical script that sets up theme, tools and so on. Now moose-less image is archived before this script is being run. So then I can set up the inspector and so on by myself, while everything other remains like in vanilla pharo.
Uko
Stef
Uko
Stef_______________________________________________
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
"Every thing has its own flow"
_______________________________________________ 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
--
"Every thing has its own flow"
_______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev