Smalltalk › Pharo › Pharo Smalltalk Developers

[squeak-dev] Community Supported Packages

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Torsten Bergmann

[squeak-dev] 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

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Stéphane Ducasse

Re: [squeak-dev] Community Supported Packages

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

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Mariano Martinez Peck

Re: [squeak-dev] Community Supported Packages

In reply to this post by Torsten Bergmann

On Mon, May 17, 2010 at 3:12 PM, Torsten Bergmann <[hidden email]> 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 never, never, answer an email without reading. Ever.

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.

Probably. But then you have to create a new tools with a UI, update (you will need to update the configurations, etc).

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.

Ok...but I still think there is not too much difference: In SM you have to:
- first do always an update
- browse categories, search the pacakge , select it, then select the version (hopefully you know which version works in THAT verion of squeak)

Is this really too different to browse a repo with MonticelloBrowser and just load it ? The only thing we don't have is categories.

Using Monticello tools, loading and evaluating by hand is

Not necessary. We can put a class side method initialize that does a self project version: 'theVersionThatWorksInPharo1.0' load
and wala! not necessary even to create load method. No need to evaluate nothing by hand. Just browse, select a package, and click load button. And there, you are SURE you will load the version that works with that Pharo version.

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.

I even think that maybe managing projects "polymorphicly" with the same tool (Monticello Browser) is a nice idea. At least for a first step. If this infrastructure works well, there will be probably someone with time and willing to do a particular tool for what you want.

Cheers

Mariano

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