Smalltalk › Squeak › Squeak - Dev

Scripy

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

8 messages Options

Chris Cunnington

Scripy

For fun, I built a script repo.

If you'd like to store a script there, please do.

http://www.scripy.org

Chris

Chris Muller-3

Re: Scripy

You went from "going to tell everyone about the pages I wrote up for
How-To-Publish software for 4.3" (via SqueakMap) to essentially
creating an entirely new tool to try to kill SM?

I just can't believe it..

On Wed, Dec 28, 2011 at 7:43 AM, Chris Cunnington
<[hidden email]> wrote:
> For fun, I built a script repo.
> If you'd like to store a script there, please do.
>
> http://www.scripy.org
>
> Chris
>
>
>

Darius Clarke

Re: Scripy

But a current SqueakMap refresh in 4.3 has almost none of the prior applications in it any more. It's been neglected too by the community.

He did say script repo was for fun, an experiment as it were.

On Wed, Dec 28, 2011 at 8:08 AM, Chris Muller <[hidden email]> wrote:

You went from "going to tell everyone about the pages I wrote up for
How-To-Publish software for 4.3" (via SqueakMap) to essentially
creating an entirely new tool to try to kill SM?

I just can't believe it..

On Wed, Dec 28, 2011 at 7:43 AM, Chris Cunnington
<[hidden email]> wrote:
> For fun, I built a script repo.
> If you'd like to store a script there, please do.
>
> http://www.scripy.org
>
> Chris
>
>
>

Darius Clarke

Re: Scripy

On Wed, Dec 28, 2011 at 9:16 AM, Darius Clarke <[hidden email]> wrote:

But a current SqueakMap refresh in 4.3 has almost none of the prior applications in it any more. It's been neglected too by the community.

Correction: With the "Safe To Install" filter turned on by default.

Darius

Frank Shearar-3

Re: Scripy

On 28 December 2011 17:38, Darius Clarke <[hidden email]> wrote:
>
> On Wed, Dec 28, 2011 at 9:16 AM, Darius Clarke <[hidden email]> wrote:
>
>>
>> But a current SqueakMap refresh in 4.3 has almost none of the prior
>> applications in it any more. It's been neglected too by the community.
>
>
> Correction: With the "Safe To Install" filter turned on by default.

Given that 4.3 is 3 days old, isn't that to be expected? Quoting from
Swiki (http://wiki.squeak.org/squeak/2726),

"With Squeak 4.2, the SqueakMap Catalog opens without the rot showing.
Whenever a new version of Squeak is released, all of the packages that
were visible in the list in the prior version no longer appear in the
new version. This is because the SqueakMap process requires authors to
re-designate their applications as working in the new Squeak release."

Now one could have some kind of server sitting somewhere taking a
fresh image and running install scripts with some kind of script
verifying that the package loaded correctly (say, by running the
package's tests), and on a green light marking the SM package as "Safe
To Install". But at any rate, right now it's up to the package owner
to perform this task.

frank

> Darius
>
>
>

Edgar De Cleene

Re: Scripy

In reply to this post by Darius Clarke

On 12/28/11 3:16 PM, "Darius Clarke" <[hidden email]> wrote:

> But a current SqueakMap refresh in 4.3 has almost none of the prior
> applications in it any more. It's been neglected too by the community.
>
SqueakMap should go to Museum of ThingsWeUsedALongTimeAgo.

Pharo do not have it and we do need it IMHO

Monticello is how modern Squeak load packages.

And wiki for documentation.

Edgar

Frank Shearar-3

Re: Scripy

On 28 December 2011 20:24, Edgar J. De Cleene <[hidden email]> wrote:

>
>
>
> On 12/28/11 3:16 PM, "Darius Clarke" <[hidden email]> wrote:
>
>> But a current SqueakMap refresh in 4.3 has almost none of the prior
>> applications in it any more. It's been neglected too by the community.
>>
> SqueakMap should go to Museum of ThingsWeUsedALongTimeAgo.
>
> Pharo do not have it and we do need it IMHO
>
> Monticello is how modern Squeak load packages.

Monticello is an SCM. It tracks how some piece of software changes. It
is not a thing used to find a package. Monticello on its own is
nowhere near sufficient. That's why the Pharo people use Metacello.
And how do we find out where ConfigurationOfYourPackage lives? Google?
Oh, right, we'd need a site that listed packages that could load in
some version of Squeak. We happen to have that: it's called SqueakMap.

frank

> And wiki for documentation.
>
> Edgar
>
>
>

Darius Clarke

Re: Scripy

In reply to this post by Frank Shearar-3

No doubt. That would be perfect, so long as beginners and folks new to the update know how to find that.

So, it seems to make sense for the SM app to have a link to the wiki page for those who want more info. so that everyone can be on the same page (literally and figuratively).

And, it seems logical for the SM app to have an indicator to say that the Safe to Install filter is on, and provide a way to turn it off in case a programmer needs to find old code to test.

There's nothing to indicate what 'SqueakMap Package Loader (7 shown out of 773 packages)' means.

- Darius

On Wed, Dec 28, 2011 at 12:10 PM, Frank Shearar <[hidden email]> wrote:

On 28 December 2011 17:38, Darius Clarke <[hidden email]> wrote:
>
> On Wed, Dec 28, 2011 at 9:16 AM, Darius Clarke <[hidden email]> wrote:
>
>>
>> But a current SqueakMap refresh in 4.3 has almost none of the prior
>> applications in it any more. It's been neglected too by the community.
>
>
> Correction: With the "Safe To Install" filter turned on by default.

Given that 4.3 is 3 days old, isn't that to be expected? Quoting from
Swiki (http://wiki.squeak.org/squeak/2726),

"With Squeak 4.2, the SqueakMap Catalog opens without the rot showing.
Whenever a new version of Squeak is released, all of the packages that
were visible in the list in the prior version no longer appear in the
new version. This is because the SqueakMap process requires authors to
re-designate their applications as working in the new Squeak release."

Now one could have some kind of server sitting somewhere taking a
fresh image and running install scripts with some kind of script
verifying that the package loaded correctly (say, by running the
package's tests), and on a green light marking the SM package as "Safe
To Install". But at any rate, right now it's up to the package owner
to perform this task.

frank

> Darius
>
>
>