Smalltalk › Pharo › Pharo Smalltalk Developers

[Ann] Calypso is moved to github

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

12 messages Options

Denis Kudriashov

[Ann] Calypso is moved to github

Hi.

I moved Calypso to github https://github.com/dionisiydk/Calypso. You can load it with following script:

Metacello new
baseline: 'Calypso';
repository: 'github://dionisiydk/Calypso';
load

Now you can fork it and pull requests to dev branch.

New version includes a lot of new features and fixes. You can read overview in my blog http://dionisiydk.blogspot.fr/2017/07/calypso-update-many-improvements-and.html

Best regards,

Denis

Tim Mackinnon

Re: [Ann] Calypso is moved to github

Nice one - my hope is that this can pave the way for much easier collaboration and help particularly for those of us who are recreational helpers (or trying to be).

Hopefully many projects can do this and we can save time and effort by reusing existing open source infrastructure.

We know there are teething problems - but this feels genuinely worth while.

Tim

Sent from my iPhone

On 28 Jul 2017, at 10:58, Denis Kudriashov <[hidden email]> wrote:

Hi.

I moved Calypso to github https://github.com/dionisiydk/Calypso. You can load it with following script:

Metacello new
baseline: 'Calypso';
repository: 'github://dionisiydk/Calypso';
load

Now you can fork it and pull requests to dev branch.

New version includes a lot of new features and fixes. You can read overview in my blog http://dionisiydk.blogspot.fr/2017/07/calypso-update-many-improvements-and.html

Best regards,
Denis

Stephane Ducasse-3

Re: [Ann] Calypso is moved to github

In reply to this post by Denis Kudriashov

Tx denis.

I like the scoped refactoring :).
Do you have settings for all the automatic protocols?

BTW do you kept the inplace edit of protocol? Because it was cool to
double click on it to rename it.

Stef

On Fri, Jul 28, 2017 at 10:58 AM, Denis Kudriashov <[hidden email]> wrote:

> Hi.
>
> I moved Calypso to github https://github.com/dionisiydk/Calypso. You can
> load it with following script:
>
> Metacello new
> baseline: 'Calypso';
> repository: 'github://dionisiydk/Calypso';
> load
>
>
> Now you can fork it and pull requests to dev branch.
>
> New version includes a lot of new features and fixes. You can read overview
> in my blog
> http://dionisiydk.blogspot.fr/2017/07/calypso-update-many-improvements-and.html
>
> Best regards,
> Denis

Denis Kudriashov

Re: [Ann] Calypso is moved to github

2017-07-28 14:12 GMT+02:00 Stephane Ducasse <[hidden email]>:

Tx denis.

I like the scoped refactoring :).
Do you have settings for all the automatic protocols?

No. Now they depends on installed plugins.

But do we need it? because it is like inspector extensions. We have no settings for them.

Maybe setting for critiques will be important because there were lot of problems with updating critic method group. But I hope that this version solves them all.

BTW do you kept the inplace edit of protocol? Because it was cool to
double click on it to rename it.

Also not implemented.

Stef

On Fri, Jul 28, 2017 at 10:58 AM, Denis Kudriashov <[hidden email]> wrote:
> Hi.
>
> I moved Calypso to github https://github.com/dionisiydk/Calypso. You can
> load it with following script:
>
> Metacello new
> baseline: 'Calypso';
> repository: 'github://dionisiydk/Calypso';
> load
>
>
> Now you can fork it and pull requests to dev branch.
>
> New version includes a lot of new features and fixes. You can read overview
> in my blog
> http://dionisiydk.blogspot.fr/2017/07/calypso-update-many-improvements-and.html
>
> Best regards,
> Denis

Denis Kudriashov

Re: [Ann] Calypso is moved to github

BTW do you kept the inplace edit of protocol? Because it was cool to
double click on it to rename it.

It will be implemented with DoubleClickCommandActivator which means that we can apply this way to any other commands.

Denis Kudriashov

Re: [Ann] Calypso is moved to github

In reply to this post by Stephane Ducasse-3

I like the scoped refactoring :).

I hope it was clear that it is in todo. I just shared idea how it will be done.

Thierry Goubier

Re: [Ann] Calypso is moved to github

Hi Denis,

So it's post-refactoring that you scope, not pre-refactoring?

post-refactoring: refactor, then restrict (scope) to what it is applied

pre-refactoring: restrict (scope) first, then refactor, then apply

Or would both be available?

Thierry

2017-07-28 14:43 GMT+02:00 Denis Kudriashov <[hidden email]>:

I like the scoped refactoring :).

I hope it was clear that it is in todo. I just shared idea how it will be done.

Denis Kudriashov

Re: [Ann] Calypso is moved to github

Hi Thierry

2017-07-28 15:01 GMT+02:00 Thierry Goubier <[hidden email]>:

Hi Denis,

So it's post-refactoring that you scope, not pre-refactoring?

post-refactoring: refactor, then restrict (scope) to what it is applied
pre-refactoring: restrict (scope) first, then refactor, then apply

Post/pre distinction looks strange because they both not change anything in image.

But I understand what you are talking about. So it will be pre-refactoring on current scope (full image by default).

And change browser will allow choose different scope which will reevaluate refactoring again and update shown changes.

Or would both be available?

Thierry

2017-07-28 14:43 GMT+02:00 Denis Kudriashov <[hidden email]>:
I like the scoped refactoring :).

I hope it was clear that it is in todo. I just shared idea how it will be done.

Thierry Goubier

Re: [Ann] Calypso is moved to github

Hi Denis,

2017-07-28 15:29 GMT+02:00 Denis Kudriashov <[hidden email]>:

Hi Thierry

2017-07-28 15:01 GMT+02:00 Thierry Goubier <[hidden email]>:
Hi Denis,

So it's post-refactoring that you scope, not pre-refactoring?

post-refactoring: refactor, then restrict (scope) to what it is applied
pre-refactoring: restrict (scope) first, then refactor, then apply

Post/pre distinction looks strange because they both not change anything in image.

They do change the way you plan your tasks, as a user.

But I understand what you are talking about. So it will be pre-refactoring on current scope (full image by default).
And change browser will allow choose different scope which will reevaluate refactoring again and update shown changes.

Understood. Will enlarging the original scope be possible?

Regards,

Thierry

Or would both be available?

Thierry

2017-07-28 14:43 GMT+02:00 Denis Kudriashov <[hidden email]>:
I like the scoped refactoring :).

I hope it was clear that it is in todo. I just shared idea how it will be done.

Denis Kudriashov

Re: [Ann] Calypso is moved to github

But I understand what you are talking about. So it will be pre-refactoring on current scope (full image by default).
And change browser will allow choose different scope which will reevaluate refactoring again and update shown changes.

Understood. Will enlarging the original scope be possible?

Yes.

When new method browser is spawned it includes all scopes of original browser.

If you spawn senders from class references which are restricted by package then new browser will show senders in scope of this package. But it will also include all scopes of original browser in scopes list. So you are always able switch to full image or other scope which you are used in other "parent windows".

Thierry Goubier

Re: [Ann] Calypso is moved to github

2017-07-28 16:11 GMT+02:00 Denis Kudriashov <[hidden email]>:

But I understand what you are talking about. So it will be pre-refactoring on current scope (full image by default).
And change browser will allow choose different scope which will reevaluate refactoring again and update shown changes.

Understood. Will enlarging the original scope be possible?

Yes.
When new method browser is spawned it includes all scopes of original browser.
If you spawn senders from class references which are restricted by package then new browser will show senders in scope of this package. But it will also include all scopes of original browser in scopes list. So you are always able switch to full image or other scope which you are used in other "parent windows".

I'll be interested by first impressions (first few times trying it) / expert impressions (once comfortable working with it) with this feature.

Who has already switched to Calypso as it's main / only system browser?

Regards,

Thierry

John Brant-2

Re: [Ann] Calypso is moved to github

In reply to this post by Denis Kudriashov

On 07/28/2017 08:29 AM, Denis Kudriashov wrote:

> Hi Thierry
>
> 2017-07-28 15:01 GMT+02:00 Thierry Goubier <[hidden email]
> <mailto:[hidden email]>>:
>
> Hi Denis,
>
> So it's post-refactoring that you scope, not pre-refactoring?
>
> post-refactoring: refactor, then restrict (scope) to what it is applied
> pre-refactoring: restrict (scope) first, then refactor, then apply
>
>
> Post/pre distinction looks strange because they both not change anything
> in image.
> But I understand what you are talking about. So it will be
> pre-refactoring on current scope (full image by default).
> And change browser will allow choose different scope which will
> reevaluate refactoring again and update shown changes.

I haven't been keeping up on the discussion so I may be way off...
However, if you are using the scoping that is already built into the
RB's refactorings, then it is pre-refactoring (i.e., they don't look at
code outside the scope).

BTW, if you use post-refactoring, then things like safe remove method
wouldn't work since calls outside the scope would cause the refactoring
to abort without removing the method.

John Brant