Updated trunk image (Squeak3.11-8472-alpha.zip)

On 12/13/09 11:45 PM, "Andreas Raab" <[hidden email]> wrote:

Here I call some do a decent window and we adopt my "ProcustesEnd" idea or
how we could pack any into MC
See http://vimeo.com/5490107 and http://vimeo.com/5495114

> - Monticello
> - MonticelloConfigurations

I like move SUnit out to next layer, but experiments (SLII an MM) shows for
now we could have here.

We have the choice, but the price of having out is still high.
But could be good all know this become "endangered species" and is on way to
live out on repositories

> Standard Packages: and etc points

As I said, difficult point of agree.
I see in you list some I don't want and some I put out in 3.10 "base" and
could have easily again in Fun.
I always use the Meccano http://www.meccano.com/ metafor.
When I was a kid, this come in different boxes numbered 1 to 5 , being 1 the
most elemental and 5 with which you build amazing things

Maybe

Meccano 1 = Pavel MimimalCore, almost inusable in the last try but good for
start to learn how to load complex things.
Like to see Mason in action....

By the way Pavel if you read this and have the time to do a MinimalCore of
the trunk, I add two more beers for the day we finally met in person.

Meccano 2 = actual MinimalMorphic . Pavel start, I follow, wish any teach me
how load Closures into and we have a killer ready to run and grow

Meccano 3 = Squeak 3.11 as is now, in the way to change and improve.

Meccano 4 Special images, like Fun or Squeakland or Seaside and Aida One
click ones

Meccano 5 Very complex images to come when we have a 64 bit system.

I cook next FunSqueak with VMMaker (following some thread this days) and
with a minimal Pier, meaning almost all
Was inside

Yes, I should clean more, but like to have your attention (and the all
Squeakers), showing I could do the job

We are in business , Squeak is better in each iteration as never before.

Cheers

Edgar

Hi:

2009/12/13 Edgar J. De Cleene <[hidden email]>:
I think that being a product mainly for developers, should include dev tools
in the default image. I'm not talking about web tools, that should be loaded by
the user at his own request, but.....yes about more widely used tools as:

-OmniBrowser (full w/Refactory and tools) (If most people use it)
-AutomaticMethodCategorizer/AutomaticMethodCategorizerOB
-Syntax Highlighting (Shout Workspace / Shout OB / Shout Monticello)
-OCompletion (Alternatively eCompletion/Algernon)
-Some parsers (XML, HTML) ?
-Magritte ?
-Criptography ?
-Others ?


> And what is the default? Actual 3.11 ? Some bigger 'a la Fun' ?
>
>> 3. Packages that should be trivially loadable
>>     (e.g., Seaside, Aida)
>
> Here for the most used we should have info trough www.squeak/
> I think we have, but just in case...
>

I have a doubt if we should maintain a full image bigger with all
packages/web tools and so,
may be is useful to newbies....but is more work (to maintainers) and
need a decision
about what packages to include, I mean: If a web developer uses
Seaside, will not
need Aida and vice-versa.


Then, on my pov, we should have:

-A core image, as small as possible;

-A default image (may be with some developers packages as I'm proposing)

-A full image? Not sure if we should provide officialy (except some
people have time to build it) but we should take care that most of
packages load/unload ok (Well, that is the topic of the most threads
on these days, about what tools/methods use to build images).

Just some ideas to share....

Cheers.
Germán.