- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Thank you for Pharo

by Torsten Bergmann

>Thank you for Pharo â¦. > >I am following the development of Pharo since its fork from Squeak, and i am really impressed what you crazy guys all have archived the last years. It all >evolved to really nice language, a fantastic nice looking live programming environment, cool packages and a growing ecosystems. >I have so much fun using Pharo. Thank you. We all appreciate when Pharo is useful. But it is not yet finished (if it ever will) and you are welcome to help moving it forward as yet another crazy guy. Step by step it goes ... Bye Torsten

Dec. 30, 2013

Re: [Pharo-dev] Pharo3 issues

by Sean P. DeNigris

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-add… > (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.

Dec. 30, 2013

Re: [Pharo-dev] Pharo3 issues

by Esteban Lorenzano

On 30 Dec 2013, at 13:26, Nicolai Hess <nicolaihess(a)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(a)inria.fr> > > On 30 Dec 2013, at 12:38, jannik.laval <jannik.laval(a)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-add… > (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 >

Dec. 30, 2013

Re: [Pharo-dev] Pharo3 issues

by Sven Van Caekenberghe

Hi Nicolai, On 30 Dec 2013, at 13:26, Nicolai Hess <nicolaihess(a)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(a)inria.fr> > > On 30 Dec 2013, at 12:38, jannik.laval <jannik.laval(a)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-add… > (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

Dec. 30, 2013

Re: [Pharo-dev] Are #explorerContents and #hasContentsInExplorer obsolete ?

by Tudor Girba

I know. This is why I am arguing that we should make the optional tools not optional. It would be a more profitable approach :). Cheers, Doru On Mon, Dec 30, 2013 at 11:02 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On 28 Dec 2013, at 13:36, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > Thanks for raising this :). > > > > I now added a simple implementation in the GTInspector to have Pointers > available for all objects. Perhaps it is overdoing it to have it by default > on all objects, but it was cheap to implement in a crude way. I still do > not eliminate all inspector related objects that point to the current > object, but it's a start (see attached the pointers to Smalltalk). > > > > If the inspector that is in Pharo gets a solution for pointers, then we > can directly clean up a lot of old code. > With this being done for tools that are just loadable optionally â> we > still have to keep the old code of the Explorer around. > > Marcus > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 30, 2013

Re: [Pharo-dev] Pharo3 issues

by Nicolai Hess

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(a)inria.fr> > > On 30 Dec 2013, at 12:38, jannik.laval <jannik.laval(a)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-add… > (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 >

Dec. 30, 2013

Re: [Pharo-dev] MessageBrowser doesn't play well with RGCommentDefinition as search results

by Marcus Denker

On 26 Dec 2013, at 17:55, Nicolai Hess <nicolaihess(a)web.de> wrote: > Hi, > > I am about to file in a whole bunch of issues regarding MessageBrowser. > All are related to search result of the kind RGCommentDefinition. These > are collected by SystemNavigation or doing a search: "class comments with it" or "method source with it". > > Most of you may not recognize these bugs, as the typically "senders of it", "implementors of it" > search results doesn't suffer from these. > (and doing search "class comments with it" isn't used that often from all, I think) > > But for newcomers searching strings through "method source with it" is an handy > task for exploring the image. And this search mixes search results of RGCommentDefinition > and RGMethodDefinition. And it is annoying for newcomers to stumble of not working > buttons/menus without realizing that there is actually a difference in the search results. > > These bugs are: > In MessageBrowser, search results of kind RGCommentDefinition > - have no working context menu > - use syntax highlighting for a class comment text > - can not be changed (raising an error on accept) > - Browse button opens the Systembrowser but it does not show the > comment text, but the class definition > - Senders button opens a MessageBrowser for selectors containing the > symbol #Comment > - Implementors button searches for implementors of a "Comment" selector (no search results) > - Version button raises an error > - switch source formatter to "Byte Code" or "Time stamp" raises an error > > I would add all issues under one parent issue (MessageBrowser doesn't play well > with RGCommentDefinition) > > I don't consider all issues as "must fix", some are real bugs (all that raising > an error) and some are more like enhancements (useless syntax highlight for comment text) > > But I would like to fix them all and maybe even all at once. > > What do you think? > > All for Pharo3, none for Pharo3, split them by bugfixes for 3 and > "nice to have" for 4? > good question.. right now I see a bit the thread that we are drowning in issuesâ¦ even with closing hundreds in December, the amount of reported issues is growing. So I would not strive for extreme perfectionâ¦ but be guided by what we can do for realâ¦ Marcus

Dec. 30, 2013

Re: [Pharo-dev] Pharo3 issues

by Marcus Denker

On 30 Dec 2013, at 12:38, jannik.laval <jannik.laval(a)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-add… (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

Dec. 30, 2013

Re: [Pharo-dev] Pharo3 issues

by Esteban Lorenzano

On 30 Dec 2013, at 12:37, jannik.laval <jannik.laval(a)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

Dec. 30, 2013

Pharo3 issues

by 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

Dec. 30, 2013