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
On 30 Dec 2013, at 12:37, jannik.laval <jannik.laval@gmail.com> 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
On 30 Dec 2013, at 12:38, jannik.laval <jannik.laval@gmail.com> 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-adde... (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
for issue 12223 <https://pharo.fogbugz.com/default.asp?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 <marcus.denker@inria.fr>
On 30 Dec 2013, at 12:38, jannik.laval <jannik.laval@gmail.com> 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-adde... (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
Hi Nicolai, On 30 Dec 2013, at 13:26, Nicolai Hess <nicolaihess@web.de> 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 <marcus.denker@inria.fr>
On 30 Dec 2013, at 12:38, jannik.laval <jannik.laval@gmail.com> 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-adde... (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
Hi Nicolai,
On 30 Dec 2013, at 13:26, Nicolai Hess <nicolaihess@web.de> 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 <marcus.denker@inria.fr>
On 30 Dec 2013, at 12:38, jannik.laval <jannik.laval@gmail.com> 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-adde... (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
On 30 Dec 2013, at 13:54, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Hi Nicolai,
On 30 Dec 2013, at 13:26, Nicolai Hess <nicolaihess@web.de> 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
On 30 Dec 2013, at 13:26, Nicolai Hess <nicolaihess@web.de> 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 <marcus.denker@inria.fr>
On 30 Dec 2013, at 12:38, jannik.laval <jannik.laval@gmail.com> 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-adde... (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
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-adde... (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 -- View this message in context: http://forum.world.st/Pharo3-issues-tp4733048p4733067.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On 30 Dec 2013, at 14:42, Sean P. DeNigris <sean@clipperadams.com> 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-adde... (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
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 <marcus.denker@inria.fr>wrote:
On 30 Dec 2013, at 14:42, Sean P. DeNigris <sean@clipperadams.com> 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-adde...
(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
-- www.tudorgirba.com "Every thing has its own flow"
On 31 Dec 2013, at 11:58, Tudor Girba <tudor@tudorgirba.com> 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 <marcus.denker@inria.fr> wrote:
On 30 Dec 2013, at 14:42, Sean P. DeNigris <sean@clipperadams.com> 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-adde... (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
-- www.tudorgirba.com
"Every thing has its own flow"
I do not understand this reaction :( Doru On Tue, Dec 31, 2013 at 12:01 PM, Marcus Denker <marcus.denker@inria.fr>wrote:
On 31 Dec 2013, at 11:58, Tudor Girba <tudor@tudorgirba.com> 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 <marcus.denker@inria.fr>wrote:
On 30 Dec 2013, at 14:42, Sean P. DeNigris <sean@clipperadams.com> 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-adde...
(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
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
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 <marcus.denker@inria.fr> wrote:
On 31 Dec 2013, at 11:58, Tudor Girba <tudor@tudorgirba.com> 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 <marcus.denker@inria.fr> wrote:
On 30 Dec 2013, at 14:42, Sean P. DeNigris <sean@clipperadams.com> 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-adde... (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
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
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 -- View this message in context: http://forum.world.st/Pharo3-issues-tp4733048p4733316.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
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 -- View this message in context: http://forum.world.st/Pharo3-issues-tp4733048p4733318.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Now, that the issue was fixed without me doing anything, I can reply. I think we are going too much in the direction of discouraging opinions and ideas on the basis that no code comes with them. In our particular case, it seems to me that it was my little suggestion that triggered the energy to produce the actual solution. Sometimes, the obvious solution is not so obvious (actually, I posted my remark precisely because I finally figured out what was bothering me about the issue). We should encourage people to think out loud and we might end up with better solutions at the end. Cheers, Doru On Tue, Dec 31, 2013 at 5:01 PM, Stéphane Ducasse <stephane.ducasse@inria.fr
wrote:
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 <marcus.denker@inria.fr>wrote:
On 31 Dec 2013, at 11:58, Tudor Girba <tudor@tudorgirba.com> 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 <marcus.denker@inria.fr>wrote:
On 30 Dec 2013, at 14:42, Sean P. DeNigris <sean@clipperadams.com> 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-adde...
(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
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
Now, that the issue was fixed without me doing anything, I can reply.
I think we are going too much in the direction of discouraging opinions and ideas on the basis that no code comes with them.
Let us try to understand a bit. we have a LOT LOT LOT of duties for Pharo and in addition we have our normal work. Now people can express whatever they want. Now Marcus just mentionned that if people wants a chance to get their ideas getting real then they are not that many options. If people thinking that something is important do not put the energy on the table then why would other people with different agendas would do it.
In our particular case, it seems to me that it was my little suggestion that triggered the energy to produce the actual solution. Sometimes, the obvious solution is not so obvious (actually, I posted my remark precisely because I finally figured out what was bothering me about the issue). We should encourage people to think out loud and we might end up with better solutions at the end.
Yes but doru I have a HUGE HUGE wish list. So should I send all the items to the list and do nothing? No I should take a little one and do it even slowly. Then go to the next one. And continue. For example, even you when is the last time that you submit a fix for Pharo? Stef
Cheers, Doru
On Tue, Dec 31, 2013 at 5:01 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote: 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 <marcus.denker@inria.fr> wrote:
On 31 Dec 2013, at 11:58, Tudor Girba <tudor@tudorgirba.com> 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 <marcus.denker@inria.fr> wrote:
On 30 Dec 2013, at 14:42, Sean P. DeNigris <sean@clipperadams.com> 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-adde... (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
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
Thank you for your answers guys. Jannik 2013/12/30 Marcus Denker <marcus.denker@inria.fr>
On 30 Dec 2013, at 12:38, jannik.laval <jannik.laval@gmail.com> 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-adde... (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/
On 30 Dec 2013, at 12:44, Marcus Denker <marcus.denker@inria.fr> wrote:
On 30 Dec 2013, at 12:38, jannik.laval <jannik.laval@gmail.com> 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-adde... (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
participants (9)
-
Esteban Lorenzano -
jannik laval -
jannik.laval
-
Marcus Denker -
Nicolai Hess -
Sean P. DeNigris -
Stéphane Ducasse -
Sven Van Caekenberghe -
Tudor Girba