Smalltalk › Squeak › Squeak - Dev

Community Supported Packages

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

Torsten Bergmann

Community Supported Packages

Mariano Martinez Peck wrote on [1]:
>I don't agree here. You DON'T necessary need to have the packages inside the
>image to have a UI.

Please read what I wrote. I did not say that it is impossible
to build the UI when you have an external config - but "it would
be easy to build a UI" when it is already in the image. I'm sure
you will agree here.

However - even when SqueakMap is not well maintained - it's UI
was easy to use and was easy accessible and one could use it
with a few clicks.

Using Monticello tools, loading and evaluating by hand is
currently possible - but this is a step backward in usability
compared to what Squeak has/had. But this is a convenience/tool
issue that has to be solved.

Bye
T.

[1] http://lists.gforge.inria.fr/pipermail/pharo-project/2010-May/026829.html
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

Chris Cunnington

Re: Community Supported Packages

Dear Torsten,

I don't know if you watched all that carefully, but in the last 48 hours we've made our decision. You seem to think we're having a discussion about it.

I think at bottom you are more of a Pharo guy. I think Pharo needs to extend to us the same right of complete autonomy that it has seized for itself. We are not going to have a discussion about how Pharo does things and how we are supposed to make what we do jibe with those plans.

It is good to have a common tool of Metacello in all three: us, you, and GemStone. We have decided to use the tool in a slightly different way. This is no cause for us to start co-oordinating with Pharo to seek a tri-image schema.

Added to which, you say that Pharo has packages to manage? It only has one raison d'etre and that's Seaside. There is now, with cessation of support to Seaside 2.8, no official release of Seaside. Seaside 3.0 is still in alpha. How many official releases do you have over there?

I repeat, you are one step behind the times, Torsten. We have chosen. Colin has just created the first test case.

Chris

Stéphane Ducasse

Re: [Pharo-project] [squeak-dev] Community Supported Packages

In reply to this post by Torsten Bergmann

You may be right.
Now I suggest that we do and learn.

Stef

On May 17, 2010, at 3:12 PM, Torsten Bergmann wrote:

> Mariano Martinez Peck wrote on [1]:
>> I don't agree here. You DON'T necessary need to have the packages inside the
>> image to have a UI.
>
> Please read what I wrote. I did not say that it is impossible
> to build the UI when you have an external config - but "it would
> be easy to build a UI" when it is already in the image. I'm sure
> you will agree here.
>
> However - even when SqueakMap is not well maintained - it's UI
> was easy to use and was easy accessible and one could use it
> with a few clicks.
>
> Using Monticello tools, loading and evaluating by hand is
> currently possible - but this is a step backward in usability
> compared to what Squeak has/had. But this is a convenience/tool
> issue that has to be solved.
>
> Bye
> T.
>
> [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2010-May/026829.html
> --
> GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Colin Putney-2

Re: Community Supported Packages

In reply to this post by Chris Cunnington

On 2010-05-17, at 6:24 AM, Chris Cunnington <[hidden email]> wrote:

> I repeat, you are one step behind the times, Torsten. We have chosen. Colin has just created the first test case.

Easy there. I was hoping the configuration I committed would give us something concrete to talk about; I meant to spur discussion, not end it.

That said, I do like Andreas' proposal, in that it gives us, the Squeak community, a little more control of the package universe that surrounds the core image, and less dependence on package maintainers. It's a bit like the FreeBSD ports tree in that regard.

Colin

Chris Cunnington

Re: Community Supported Packages

In reply to this post by Torsten Bergmann

CP: "Easy there. I was hoping the configuration I committed would give us something concrete to talk about; I meant to spur discussion, not end it."

Sorry about that. Yea, I think I went too far and was kind of insulting to Torsten, who has done lots of things for Squeak, not least of which, gave me a way to understand how Metacello works beyond just using class>>#load. I seem to alternate between saying something useful and then saying something that sort of lowers the tone. My apologies.

Chris