Pharo3 issues

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
31 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Pharo3 issues

jannik laval
Hi all,

I am porting Phratch in Pharo 3.0 and I have some problems with the interface.
I uses a one-click Pharo3.0 #30664

Here is a list of what I have:

- in a debugger, it is not possible to do a Cmd-p to evaluate an expression. This appears only if I select with the mouse. If I make the selection with shift-arrow it works.
It means that the selection  with mouse or with shift-arrow are not the same.

- In monticello browser: when I select my project, all the repositories available in Pharo are shown. As in Pharo 2.0, it should show only the concerned repositories (2 or 3 max).

- In a browser, when I did a change in the source code of a method, then I select another method, the changes are lost, without asking if I want to save changes.

Could one confirm that they are bugs (not new features) ? and if they are already reported.

Cheers,
Jannik
Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

EstebanLM

On 30 Dec 2013, at 12:37, jannik.laval <[hidden email]> wrote:

> Hi all,
>
> I am porting Phratch in Pharo 3.0 and I have some problems with the interface.
> I uses a one-click Pharo3.0 #30664
>
> Here is a list of what I have:
>
> - in a debugger, it is not possible to do a Cmd-p to evaluate an expression. This appears only if I select with the mouse. If I make the selection with shift-arrow it works.
> It means that the selection  with mouse or with shift-arrow are not the same.

yes, this is a known bug (I don’t remember number)

>
> - In monticello browser: when I select my project, all the repositories available in Pharo are shown. As in Pharo 2.0, it should show only the concerned repositories (2 or 3 max).

Nope, there is a change with this.
There is no more relation 1->N in MC, now is N->N. There is a preference if you want the old behaviour.

>
> - In a browser, when I did a change in the source code of a method, then I select another method, the changes are lost, without asking if I want to save changes.

yep… also a known bug.

so, 2 bugs, 1 “feature” :)

Esteban

>
> Could one confirm that they are bugs (not new features) ? and if they are already reported.
>
> Cheers,
> Jannik


Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Marcus Denker-4
In reply to this post by jannik laval

On 30 Dec 2013, at 12:38, jannik.laval <[hidden email]> wrote:

> Hi all,
>
> I am porting Phratch in Pharo 3.0 and I have some problems with the interface.
> I uses a one-click Pharo3.0 #30664
>
> Here is a list of what I have:
>
> - in a debugger, it is not possible to do a Cmd-p to evaluate an expression. This appears only if I select with the mouse. If I make the selection with shift-arrow it works.
> It means that the selection  with mouse or with shift-arrow are not the same.
>
yes, known bug.  Introduced by 12144 TextModel>>getSelection. The only solution seems to be to revert tag for now:

https://pharo.fogbugz.com/f/cases/12521/Undo-12144-TextModel-getSelection

This will be in the next update. (I was offline more or less since thursday due to helping my brother moving, so this is not integrated yet)

> - In monticello browser: when I select my project, all the repositories available in Pharo are shown. As in Pharo 2.0, it should show only the concerned repositories (2 or 3 max).
>
Yes, this was made on purpose and there is an issue that questions if that idea was good:

https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
(this issue is from July)


> - In a browser, when I did a change in the source code of a method, then I select another method, the changes are lost, without asking if I want to save changes.
>

https://pharo.fogbugz.com/f/cases/12223/Nautilus-loses-changes
(issue date: 22/11)

In short: if there would be more people *actively* helping on the issue tracker front, you would not even have seen those problems.


        Marcus
Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Nicolai Hess
for issue 12223

please revert the changes done for editing history in Nautilus.
It makes more trouble than it helps.
It is a nice feature, but it is implementation has too many side effects (discard changes on close, lose changes when jump through the
history, history has a limit)
If no one has the time to revert this, just give me a GO, and I'll do it :-)


Nicolai










2013/12/30 Marcus Denker <[hidden email]>

On 30 Dec 2013, at 12:38, jannik.laval <[hidden email]> wrote:

> Hi all,
>
> I am porting Phratch in Pharo 3.0 and I have some problems with the interface.
> I uses a one-click Pharo3.0 #30664
>
> Here is a list of what I have:
>
> - in a debugger, it is not possible to do a Cmd-p to evaluate an expression. This appears only if I select with the mouse. If I make the selection with shift-arrow it works.
> It means that the selection  with mouse or with shift-arrow are not the same.
>
yes, known bug.  Introduced by 12144 TextModel>>getSelection. The only solution seems to be to revert tag for now:

https://pharo.fogbugz.com/f/cases/12521/Undo-12144-TextModel-getSelection

This will be in the next update. (I was offline more or less since thursday due to helping my brother moving, so this is not integrated yet)

> - In monticello browser: when I select my project, all the repositories available in Pharo are shown. As in Pharo 2.0, it should show only the concerned repositories (2 or 3 max).
>
Yes, this was made on purpose and there is an issue that questions if that idea was good:

https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
(this issue is from July)


> - In a browser, when I did a change in the source code of a method, then I select another method, the changes are lost, without asking if I want to save changes.
>

https://pharo.fogbugz.com/f/cases/12223/Nautilus-loses-changes
(issue date: 22/11)

In short: if there would be more people *actively* helping on the issue tracker front, you would not even have seen those problems.


        Marcus

Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Sven Van Caekenberghe-2
Hi Nicolai,

On 30 Dec 2013, at 13:26, Nicolai Hess <[hidden email]> wrote:

> for issue 12223
>
> please revert the changes done for editing history in Nautilus.
> It makes more trouble than it helps.
> It is a nice feature, but it is implementation has too many side effects (discard changes on close, lose changes when jump through the
> history, history has a limit)
> If no one has the time to revert this, just give me a GO, and I'll do it :-)
>
>
> Nicolai

Yes, I think that features has given us a lot of trouble already, I concur with your conclusion: revert.

Another thing I have been wanting to say to you: I am very impressed and very happy to see you tackle so many diverse issues with so much energy. You really embody the ‘just doIt’ tagline.

Thank you very much, I for one, appreciate it a lot !

Regards,

Sven

BTW, from my perspective you seem to have come from nowhere, which makes your contributions even more magical.

>
> 2013/12/30 Marcus Denker <[hidden email]>
>
> On 30 Dec 2013, at 12:38, jannik.laval <[hidden email]> wrote:
>
> > Hi all,
> >
> > I am porting Phratch in Pharo 3.0 and I have some problems with the interface.
> > I uses a one-click Pharo3.0 #30664
> >
> > Here is a list of what I have:
> >
> > - in a debugger, it is not possible to do a Cmd-p to evaluate an expression. This appears only if I select with the mouse. If I make the selection with shift-arrow it works.
> > It means that the selection  with mouse or with shift-arrow are not the same.
> >
> yes, known bug.  Introduced by 12144 TextModel>>getSelection. The only solution seems to be to revert tag for now:
>
> https://pharo.fogbugz.com/f/cases/12521/Undo-12144-TextModel-getSelection
>
> This will be in the next update. (I was offline more or less since thursday due to helping my brother moving, so this is not integrated yet)
>
> > - In monticello browser: when I select my project, all the repositories available in Pharo are shown. As in Pharo 2.0, it should show only the concerned repositories (2 or 3 max).
> >
> Yes, this was made on purpose and there is an issue that questions if that idea was good:
>
> https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
> (this issue is from July)
>
>
> > - In a browser, when I did a change in the source code of a method, then I select another method, the changes are lost, without asking if I want to save changes.
> >
>
> https://pharo.fogbugz.com/f/cases/12223/Nautilus-loses-changes
> (issue date: 22/11)
>
> In short: if there would be more people *actively* helping on the issue tracker front, you would not even have seen those problems.
>
>
>         Marcus
>



--
Sven Van Caekenberghe
Proudly supporting Pharo
http://pharo.org
http://association.pharo.org
http://consortium.pharo.org





Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

EstebanLM
In reply to this post by Nicolai Hess

On 30 Dec 2013, at 13:26, Nicolai Hess <[hidden email]> wrote:

for issue 12223

please revert the changes done for editing history in Nautilus.
It makes more trouble than it helps.
It is a nice feature, but it is implementation has too many side effects (discard changes on close, lose changes when jump through the
history, history has a limit)
If no one has the time to revert this, just give me a GO, and I'll do it :-)

GO! :)



Nicolai










2013/12/30 Marcus Denker <[hidden email]>

On 30 Dec 2013, at 12:38, jannik.laval <[hidden email]> wrote:

> Hi all,
>
> I am porting Phratch in Pharo 3.0 and I have some problems with the interface.
> I uses a one-click Pharo3.0 #30664
>
> Here is a list of what I have:
>
> - in a debugger, it is not possible to do a Cmd-p to evaluate an expression. This appears only if I select with the mouse. If I make the selection with shift-arrow it works.
> It means that the selection  with mouse or with shift-arrow are not the same.
>
yes, known bug.  Introduced by 12144 TextModel>>getSelection. The only solution seems to be to revert tag for now:

https://pharo.fogbugz.com/f/cases/12521/Undo-12144-TextModel-getSelection

This will be in the next update. (I was offline more or less since thursday due to helping my brother moving, so this is not integrated yet)

> - In monticello browser: when I select my project, all the repositories available in Pharo are shown. As in Pharo 2.0, it should show only the concerned repositories (2 or 3 max).
>
Yes, this was made on purpose and there is an issue that questions if that idea was good:

https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
(this issue is from July)


> - In a browser, when I did a change in the source code of a method, then I select another method, the changes are lost, without asking if I want to save changes.
>

https://pharo.fogbugz.com/f/cases/12223/Nautilus-loses-changes
(issue date: 22/11)

In short: if there would be more people *actively* helping on the issue tracker front, you would not even have seen those problems.


        Marcus


Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Sean P. DeNigris
Administrator
In reply to this post by Marcus Denker-4
Marcus Denker-4 wrote
> - In monticello browser: when I select my project, all the repositories available in Pharo are shown. As in Pharo 2.0, it should show only the concerned repositories (2 or 3 max).
>
Yes, this was made on purpose and there is an issue that questions if that idea was good:

https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
(this issue is from July)
I commented in the issue:
+1. I don't like this change at all. Would someone comment on whether there is an unseen purpose or this is a bug?
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

jannik laval
In reply to this post by Marcus Denker-4
Thank you for your answers guys.

Jannik


2013/12/30 Marcus Denker <[hidden email]>

On 30 Dec 2013, at 12:38, jannik.laval <[hidden email]> wrote:

> Hi all,
>
> I am porting Phratch in Pharo 3.0 and I have some problems with the interface.
> I uses a one-click Pharo3.0 #30664
>
> Here is a list of what I have:
>
> - in a debugger, it is not possible to do a Cmd-p to evaluate an expression. This appears only if I select with the mouse. If I make the selection with shift-arrow it works.
> It means that the selection  with mouse or with shift-arrow are not the same.
>
yes, known bug.  Introduced by 12144 TextModel>>getSelection. The only solution seems to be to revert tag for now:

https://pharo.fogbugz.com/f/cases/12521/Undo-12144-TextModel-getSelection

This will be in the next update. (I was offline more or less since thursday due to helping my brother moving, so this is not integrated yet)

> - In monticello browser: when I select my project, all the repositories available in Pharo are shown. As in Pharo 2.0, it should show only the concerned repositories (2 or 3 max).
>
Yes, this was made on purpose and there is an issue that questions if that idea was good:

https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
(this issue is from July)


> - In a browser, when I did a change in the source code of a method, then I select another method, the changes are lost, without asking if I want to save changes.
>

https://pharo.fogbugz.com/f/cases/12223/Nautilus-loses-changes
(issue date: 22/11)

In short: if there would be more people *actively* helping on the issue tracker front, you would not even have seen those problems.


        Marcus



--

~~Jannik Laval~~
École des Mines de Douai
Enseignant-chercheur
http://www.jannik-laval.eu
http://car.mines-douai.fr/

Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Stéphane Ducasse
In reply to this post by Marcus Denker-4

On 30 Dec 2013, at 12:44, Marcus Denker <[hidden email]> wrote:

>
> On 30 Dec 2013, at 12:38, jannik.laval <[hidden email]> wrote:
>
>> Hi all,
>>
>> I am porting Phratch in Pharo 3.0 and I have some problems with the interface.
>> I uses a one-click Pharo3.0 #30664
>>
>> Here is a list of what I have:
>>
>> - in a debugger, it is not possible to do a Cmd-p to evaluate an expression. This appears only if I select with the mouse. If I make the selection with shift-arrow it works.
>> It means that the selection  with mouse or with shift-arrow are not the same.
>>
> yes, known bug.  Introduced by 12144 TextModel>>getSelection. The only solution seems to be to revert tag for now:
>
> https://pharo.fogbugz.com/f/cases/12521/Undo-12144-TextModel-getSelection

I tried during 3 hours to get the integration up and running and this entry was the first one on my list :)

>
> This will be in the next update. (I was offline more or less since thursday due to helping my brother moving, so this is not integrated yet)
>
>> - In monticello browser: when I select my project, all the repositories available in Pharo are shown. As in Pharo 2.0, it should show only the concerned repositories (2 or 3 max).
>>
> Yes, this was made on purpose and there is an issue that questions if that idea was good:
>
> https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
> (this issue is from July)
>
>
>> - In a browser, when I did a change in the source code of a method, then I select another method, the changes are lost, without asking if I want to save changes.
>>
>
> https://pharo.fogbugz.com/f/cases/12223/Nautilus-loses-changes
> (issue date: 22/11)
>
> In short: if there would be more people *actively* helping on the issue tracker front, you would not even have seen those problems.
>
>
> Marcus


Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Stéphane Ducasse
In reply to this post by Sven Van Caekenberghe-2

Hi Nicolai,

On 30 Dec 2013, at 13:26, Nicolai Hess <[hidden email]> wrote:

for issue 12223

please revert the changes done for editing history in Nautilus.
It makes more trouble than it helps.
It is a nice feature, but it is implementation has too many side effects (discard changes on close, lose changes when jump through the
history, history has a limit)
If no one has the time to revert this, just give me a GO, and I'll do it :-)


Nicolai

Yes, I think that features has given us a lot of trouble already, I concur with your conclusion: revert.

Please :)


Another thing I have been wanting to say to you: I am very impressed and very happy to see you tackle so many diverse issues with so much energy. You really embody the ‘just doIt’ tagline. 

+ 1 :)

Thank you very much, I for one, appreciate it a lot !

Yes me too.


Regards,

Sven

BTW, from my perspective you seem to have come from nowhere, which makes your contributions even more magical.


2013/12/30 Marcus Denker <[hidden email]>

On 30 Dec 2013, at 12:38, jannik.laval <[hidden email]> wrote:

Hi all,

I am porting Phratch in Pharo 3.0 and I have some problems with the interface.
I uses a one-click Pharo3.0 #30664

Here is a list of what I have:

- in a debugger, it is not possible to do a Cmd-p to evaluate an expression. This appears only if I select with the mouse. If I make the selection with shift-arrow it works.
It means that the selection  with mouse or with shift-arrow are not the same.

yes, known bug.  Introduced by 12144 TextModel>>getSelection. The only solution seems to be to revert tag for now:

https://pharo.fogbugz.com/f/cases/12521/Undo-12144-TextModel-getSelection

This will be in the next update. (I was offline more or less since thursday due to helping my brother moving, so this is not integrated yet)

- In monticello browser: when I select my project, all the repositories available in Pharo are shown. As in Pharo 2.0, it should show only the concerned repositories (2 or 3 max).

Yes, this was made on purpose and there is an issue that questions if that idea was good:

https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
(this issue is from July)


- In a browser, when I did a change in the source code of a method, then I select another method, the changes are lost, without asking if I want to save changes.


https://pharo.fogbugz.com/f/cases/12223/Nautilus-loses-changes
(issue date: 22/11)

In short: if there would be more people *actively* helping on the issue tracker front, you would not even have seen those problems.


       Marcus




--
Sven Van Caekenberghe
Proudly supporting Pharo
http://pharo.org
http://association.pharo.org
http://consortium.pharo.org

Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Marcus Denker-4
In reply to this post by Sean P. DeNigris

On 30 Dec 2013, at 14:42, Sean P. DeNigris <[hidden email]> wrote:

> Marcus Denker-4 wrote
>>> - In monticello browser: when I select my project, all the repositories
>>> available in Pharo are shown. As in Pharo 2.0, it should show only the
>>> concerned repositories (2 or 3 max).
>>>
>> Yes, this was made on purpose and there is an issue that questions if that
>> idea was good:
>>
>> https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
>> (this issue is from July)
>
> I commented in the issue:
> +1. I don't like this change at all. Would someone comment on whether there
> is an unseen purpose or this is a bug?
>

I think we should set the default of the preference to be the opposite, then it’s fixed with no
problems for those wanting the other behaviour.

        Marcus
Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Marcus Denker-4
In reply to this post by Sven Van Caekenberghe-2

On 30 Dec 2013, at 13:54, Sven Van Caekenberghe <[hidden email]> wrote:

> Hi Nicolai,
>
> On 30 Dec 2013, at 13:26, Nicolai Hess <[hidden email]> wrote:
>
>> for issue 12223
>>
>> please revert the changes done for editing history in Nautilus.
>> It makes more trouble than it helps.
>> It is a nice feature, but it is implementation has too many side effects (discard changes on close, lose changes when jump through the
>> history, history has a limit)
>> If no one has the time to revert this, just give me a GO, and I'll do it :-)
>>
>>
>> Nicolai
>
> Yes, I think that features has given us a lot of trouble already, I concur with your conclusion: revert.
>
> Another thing I have been wanting to say to you: I am very impressed and very happy to see you tackle so many diverse issues with so much energy. You really embody the ‘just doIt’ tagline.
>
> Thank you very much, I for one, appreciate it a lot !
>

Indeed! I really enjoy your contributions… amazing.

        Marcus


Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Tudor Girba-2
In reply to this post by Marcus Denker-4
I think this should not be a global preference at all. Most of the time, you actually want to commit in the same repository where you always do. Only from time to time do you need to switch and copy to another repo. So, the preference should be per browser, not global.

Cheers,
Doru


On Tue, Dec 31, 2013 at 11:55 AM, Marcus Denker <[hidden email]> wrote:

On 30 Dec 2013, at 14:42, Sean P. DeNigris <[hidden email]> wrote:

> Marcus Denker-4 wrote
>>> - In monticello browser: when I select my project, all the repositories
>>> available in Pharo are shown. As in Pharo 2.0, it should show only the
>>> concerned repositories (2 or 3 max).
>>>
>> Yes, this was made on purpose and there is an issue that questions if that
>> idea was good:
>>
>> https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
>> (this issue is from July)
>
> I commented in the issue:
> +1. I don't like this change at all. Would someone comment on whether there
> is an unseen purpose or this is a bug?
>

I think we should set the default of the preference to be the opposite, then it’s fixed with no
problems for those wanting the other behaviour.

        Marcus



--

"Every thing has its own flow"
Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Marcus Denker-4

On 31 Dec 2013, at 11:58, Tudor Girba <[hidden email]> wrote:

I think this should not be a global preference at all. Most of the time, you actually want to commit in the same repository where you always do. Only from time to time do you need to switch and copy to another repo. So, the preference should be per browser, not global.


consider that the issue was open since July. How likely is it that what you describe will ever be done?

Cheers,
Doru


On Tue, Dec 31, 2013 at 11:55 AM, Marcus Denker <[hidden email]> wrote:

On 30 Dec 2013, at 14:42, Sean P. DeNigris <[hidden email]> wrote:

> Marcus Denker-4 wrote
>>> - In monticello browser: when I select my project, all the repositories
>>> available in Pharo are shown. As in Pharo 2.0, it should show only the
>>> concerned repositories (2 or 3 max).
>>>
>> Yes, this was made on purpose and there is an issue that questions if that
>> idea was good:
>>
>> https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
>> (this issue is from July)
>
> I commented in the issue:
> +1. I don't like this change at all. Would someone comment on whether there
> is an unseen purpose or this is a bug?
>

I think we should set the default of the preference to be the opposite, then it’s fixed with no
problems for those wanting the other behaviour.

        Marcus



--

"Every thing has its own flow"

Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Stephan Eggermont-3
In reply to this post by jannik laval
Jannik wrote
>- In a browser, when I did a change in the source code of a method,
> then I select another method, the changes are lost, without asking if I want to save changes.

Thanks Nicolai, for the fast results. I retested.

Resolved, Fix to Include

Stephan
Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Tudor Girba-2
In reply to this post by Marcus Denker-4
I do not understand this reaction :(

Doru


On Tue, Dec 31, 2013 at 12:01 PM, Marcus Denker <[hidden email]> wrote:

On 31 Dec 2013, at 11:58, Tudor Girba <[hidden email]> wrote:

I think this should not be a global preference at all. Most of the time, you actually want to commit in the same repository where you always do. Only from time to time do you need to switch and copy to another repo. So, the preference should be per browser, not global.


consider that the issue was open since July. How likely is it that what you describe will ever be done?

Cheers,
Doru


On Tue, Dec 31, 2013 at 11:55 AM, Marcus Denker <[hidden email]> wrote:

On 30 Dec 2013, at 14:42, Sean P. DeNigris <[hidden email]> wrote:

> Marcus Denker-4 wrote
>>> - In monticello browser: when I select my project, all the repositories
>>> available in Pharo are shown. As in Pharo 2.0, it should show only the
>>> concerned repositories (2 or 3 max).
>>>
>> Yes, this was made on purpose and there is an issue that questions if that
>> idea was good:
>>
>> https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
>> (this issue is from July)
>
> I commented in the issue:
> +1. I don't like this change at all. Would someone comment on whether there
> is an unseen purpose or this is a bug?
>

I think we should set the default of the preference to be the opposite, then it’s fixed with no
problems for those wanting the other behaviour.

        Marcus



--

"Every thing has its own flow"




--

"Every thing has its own flow"
Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Stephan Eggermont-3
In reply to this post by jannik laval
Marcus wrote:
>On 31 Dec 2013, at 11:58, Tudor Girba <[hidden email]> wrote:
>
> >I think this should not be a global preference at all. Most of the time, you actually want to commit in the same repository where >you always do. Only from time to time do you need to switch and copy to another repo. So, the preference should be per >browser, not global.
> >
>
>consider that the issue was open since July. How likely is it that what you describe will ever be done?

Oh, I'm quite positive. I took a look at the code in 30664. Changing view preference is already in the right-click menu on the
repositories, and it is global. I *never* found it there before. Though it has something to do with repositories, putting it in the
repositories menu is not helpful, as its context is not a single repository. The same problem exists with the package side,
the sort methods don't belong in the context menu of individual packages.

I'd suggest adding a dropdown-menu on a button in the searchfield-row for both the packages and the repositories,
allowing the setting of all-package and all-repository properties. And of course removing the preference and moving
it to the instance side.

Stephan




Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Stéphane Ducasse
In reply to this post by Tudor Girba-2
Doru 

The point of marcus is that we cannot take into account all wishes of everybody: else we would not do anything else.
So if somebody thinks that something that is not in our critical path should be changed he should submit code.
I have tons of ideas that could be implemented now since we do not have infinite ressources we focus on the important 
ones. 

Stef

I do not understand this reaction :(

Doru


On Tue, Dec 31, 2013 at 12:01 PM, Marcus Denker <[hidden email]> wrote:

On 31 Dec 2013, at 11:58, Tudor Girba <[hidden email]> wrote:

I think this should not be a global preference at all. Most of the time, you actually want to commit in the same repository where you always do. Only from time to time do you need to switch and copy to another repo. So, the preference should be per browser, not global.


consider that the issue was open since July. How likely is it that what you describe will ever be done?

Cheers,
Doru


On Tue, Dec 31, 2013 at 11:55 AM, Marcus Denker <[hidden email]> wrote:

On 30 Dec 2013, at 14:42, Sean P. DeNigris <[hidden email]> wrote:

> Marcus Denker-4 wrote
>>> - In monticello browser: when I select my project, all the repositories
>>> available in Pharo are shown. As in Pharo 2.0, it should show only the
>>> concerned repositories (2 or 3 max).
>>>
>> Yes, this was made on purpose and there is an issue that questions if that
>> idea was good:
>>
>> https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
>> (this issue is from July)
>
> I commented in the issue:
> +1. I don't like this change at all. Would someone comment on whether there
> is an unseen purpose or this is a bug?
>

I think we should set the default of the preference to be the opposite, then it’s fixed with no
problems for those wanting the other behaviour.

        Marcus



--

"Every thing has its own flow"




--

"Every thing has its own flow"

Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Sean P. DeNigris
Administrator
Stéphane Ducasse wrote
So if somebody thinks that something that is not in our critical path should be changed he should submit code.
+1... and here is that person. The question in my post was: "will anyone speak up for this 'feature'?" If not, I will be happy to revert to the old behavior. While Marcus' suggestion will quickly fix the problem, every setting we add makes the system more complex to understand...
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Pharo3 issues

Sean P. DeNigris
Administrator
Sean P. DeNigris wrote
and here is that person
I would've fixed it already, but since someone went through the trouble to add a setting, I figured maybe there was a use case I was missing...
Cheers,
Sean
12