Re: [Pharo-dev] [pharo3 issues] down to 17 issues
On 04 Apr 2014, at 18:22, MartinW w...@fastmail.fm wrote: When i add a new bug to the issue tracker it is automatically tagged as fix if time. Am i supposed to change this label to higher priority if i think it's appropriate - Yes! or is someone reviewing new entered bugs and assigning priorities to them? That too, but there is no automatism. People look at the tracker and check and change/sort, and over time some consensus is found what status an issue should have. (it would be nice to have more people looking at the tracker from time to time to help with this) Anyway here's the bug: https://pharo.fogbugz.com/f/cases/13175/ I put it higher so we do not forget to merge it withthe other duplicated reports. Marcus
Re: [Pharo-dev] [pharo3 issues] down to 17 issues
Marcus Denker wrote: Hi, We are down to 17 open issues that are tagged “must fix” or higher: https://pharo.fogbugz.com/f/filters/64/3-0-TODO two of those have code that is in need of review. Marcus That is really great Marcus. Thanks for your efforts and those of the other integrators. cheers -ben
Re: [Pharo-dev] [pharo3 issues] down to 17 issues
When i add a new bug to the issue tracker it is automatically tagged as fix if time. Am i supposed to change this label to higher priority if i think it's appropriate - or is someone reviewing new entered bugs and assigning priorities to them? Anyway here's the bug: https://pharo.fogbugz.com/f/cases/13175/ -- View this message in context: http://forum.world.st/pharo3-issues-down-to-17-issues-tp4752772p4752800.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] [Pharo3] Issues for review and for integration empy
give me 15’ ;) On 09 Jan 2014, at 14:01, Marcus Denker marcus.den...@inria.fr wrote: … so we finally managed to have no issues anymore that are - fix review needed + pre-check by the monkey - fix to integrate Wow.. that never happened before ;-) Marcus
Re: [Pharo-dev] Pharo3 issues
If anyone wants the solution for https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies before Jan 26, please remember Camillo is working on his PhD till then. (needs reviewing) Stephan
Re: [Pharo-dev] Pharo3 issues
I do not get that. As far as I can tell, the fix is already integrated :). Doru On Fri, Jan 3, 2014 at 1:29 PM, Stephan Eggermont step...@stack.nl wrote: If anyone wants the solution for https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies before Jan 26, please remember Camillo is working on his PhD till then. (needs reviewing) Stephan -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] Pharo3 issues
Doru wrote: I do not get that. As far as I can tell, the fix is already integrated :). No, it needs to be resolved to Fix to be included. Stephan
Re: [Pharo-dev] Pharo3 issues
Hmm, strange. It was available in 30666, but it is not available anymore in 30669. Was it reverted because it was not good, or was it because of another issue? Doru On Fri, Jan 3, 2014 at 2:14 PM, Stephan Eggermont step...@stack.nl wrote: Doru wrote: I do not get that. As far as I can tell, the fix is already integrated :). No, it needs to be resolved to Fix to be included. Stephan -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] Pharo3 issues
Doru wrote: Hmm, strange. It was available in 30666, but it is not available anymore in 30669. Was it reverted because it was not good, or was it because of another issue? It was never there. Did you by change load the slice in your 30666? Stephan
Re: [Pharo-dev] Pharo3 issues
Oops :) Doru On Fri, Jan 3, 2014 at 3:04 PM, Stephan Eggermont step...@stack.nl wrote: Doru wrote: Hmm, strange. It was available in 30666, but it is not available anymore in 30669. Was it reverted because it was not good, or was it because of another issue? It was never there. Did you by change load the slice in your 30666? Stephan -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] Pharo3 issues
Brilliant! I tested it, and it works fine. Doru On Thu, Jan 2, 2014 at 4:14 PM, Stephan Eggermont step...@stack.nl wrote: I removed the preference setting, and made it a local action (Issue 10551) Stephan -- www.tudorgirba.com Every thing has its own flow PastedGraphic-1.png
Re: [Pharo-dev] Pharo3 issues
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.duca...@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.den...@inria.frwrote: On 31 Dec 2013, at 11:58, Tudor Girba tu...@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.den...@inria.frwrote: On 30 Dec 2013, at 14:42, Sean P. DeNigris s...@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-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 -- 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
Re: [Pharo-dev] Pharo3 issues
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.duca...@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.den...@inria.fr wrote: On 31 Dec 2013, at 11:58, Tudor Girba tu...@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.den...@inria.fr wrote: On 30 Dec 2013, at 14:42, Sean P. DeNigris s...@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-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 -- 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
Re: [Pharo-dev] Pharo3 issues
On 30 Dec 2013, at 14:42, Sean P. DeNigris s...@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-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
Re: [Pharo-dev] Pharo3 issues
On 30 Dec 2013, at 13:54, Sven Van Caekenberghe s...@stfx.eu wrote: Hi Nicolai, On 30 Dec 2013, at 13:26, Nicolai Hess nicolaih...@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
Re: [Pharo-dev] Pharo3 issues
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.den...@inria.frwrote: On 30 Dec 2013, at 14:42, Sean P. DeNigris s...@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-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 -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] Pharo3 issues
On 31 Dec 2013, at 11:58, Tudor Girba tu...@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.den...@inria.fr wrote: On 30 Dec 2013, at 14:42, Sean P. DeNigris s...@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-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 -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] Pharo3 issues
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
Re: [Pharo-dev] Pharo3 issues
I do not understand this reaction :( Doru On Tue, Dec 31, 2013 at 12:01 PM, Marcus Denker marcus.den...@inria.frwrote: On 31 Dec 2013, at 11:58, Tudor Girba tu...@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.den...@inria.frwrote: On 30 Dec 2013, at 14:42, Sean P. DeNigris s...@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-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 -- www.tudorgirba.com Every thing has its own flow -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] Pharo3 issues
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
Re: [Pharo-dev] Pharo3 issues
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.den...@inria.fr wrote: On 31 Dec 2013, at 11:58, Tudor Girba tu...@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.den...@inria.fr wrote: On 30 Dec 2013, at 14:42, Sean P. DeNigris s...@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-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 -- www.tudorgirba.com Every thing has its own flow -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] Pharo3 issues
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.
Re: [Pharo-dev] Pharo3 issues
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.
Re: [Pharo-dev] Pharo3 issues
Sean wrote: 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... Please go ahead, I won't have any more time to do it today or tomorrow. Design, no choice! Stephan
Re: [Pharo-dev] Pharo3 issues
On 30 Dec 2013, at 12:37, jannik.laval jannik.la...@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
Re: [Pharo-dev] Pharo3 issues
On 30 Dec 2013, at 12:38, jannik.laval jannik.la...@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 TextModelgetSelection. 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
Re: [Pharo-dev] Pharo3 issues
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.den...@inria.fr On 30 Dec 2013, at 12:38, jannik.laval jannik.la...@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 TextModelgetSelection. 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
Re: [Pharo-dev] Pharo3 issues
Hi Nicolai, On 30 Dec 2013, at 13:26, Nicolai Hess nicolaih...@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.den...@inria.fr On 30 Dec 2013, at 12:38, jannik.laval jannik.la...@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 TextModelgetSelection. 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
Re: [Pharo-dev] Pharo3 issues
On 30 Dec 2013, at 13:26, Nicolai Hess nicolaih...@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.den...@inria.fr On 30 Dec 2013, at 12:38, jannik.laval jannik.la...@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 TextModelgetSelection. 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
Re: [Pharo-dev] Pharo3 issues
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 -- 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.
Re: [Pharo-dev] Pharo3 issues
Thank you for your answers guys. Jannik 2013/12/30 Marcus Denker marcus.den...@inria.fr On 30 Dec 2013, at 12:38, jannik.laval jannik.la...@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 TextModelgetSelection. 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/
Re: [Pharo-dev] Pharo3 issues
Hi Nicolai, On 30 Dec 2013, at 13:26, Nicolai Hess nicolaih...@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.den...@inria.fr On 30 Dec 2013, at 12:38, jannik.laval jannik.la...@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 TextModelgetSelection. 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
Re: [Pharo-dev] Pharo3 issues
On 30 Dec 2013, at 12:44, Marcus Denker marcus.den...@inria.fr wrote: On 30 Dec 2013, at 12:38, jannik.laval jannik.la...@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 TextModelgetSelection. 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
