October 2013 - Pharo-dev - lists.pharo.org

SS3 with HTTP 503

by Torsten Bergmann

http://ss3.gemtalksystems.com/

Oct. 14, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.2-MetacelloValidation… 1 regressions found. Metacello.TestsMCA.MetacelloIssue171TestCase.testIssue171a

Oct. 14, 2013

Re: [Pharo-dev] Please contributors fill up this form...

by roberto.minelli＠usi.ch

Here's mine: PharoContributor new name: 'Roberto Minelli'; email: 'roberto.minell(a)usi.ch'; website: 'http://www.inf.usi.ch/phd/minelli'; description: 'PhD Student at REVEAL @ Faculty of Informatics (University of Lugano)'; yourself. On Oct 9, 2013, at 1:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I would like to get > contributors.pharo.org a bit more representative of Pharo. > > We should have Previous contributors and enhance the current list. > Can you please reply to this mail > > PharoContributor new > name: 'Esteban Lorenzano'; > id: 'estebanlm'; > email: 'estebanlm(a)gmail.com'; > website: 'http://smallworks.eu'; > description: 'Pharo core team. Contributor of several projects, including Kernel, DBXTalk, Voyage, Mars, etc. Also I work on the VM.'; > image: 'http://www.gravatar.com/avatar/193af464509ae8fbcc04abad70b72fc0?s=120'; > yourself > > > Stef

Oct. 14, 2013

Re: [Pharo-dev] bug: [4993] Typing cmd+L cancel all typing and we can't undo it [Terminated]

by Marcus Denker

On Oct 14, 2013, at 5:13 PM, kilon <thekilon(a)yahoo.co.uk> wrote: > the dialog does not force you to use the mouse, you just do ctrl+l and then > hit enter to confirm ("yes" is preselected). So essentially it only > introduces one more keyboard key, enter. If you want to cancel the cmd+l is > when you will need to use the mouse (so you choose "No" option). Apparently > arrow keys dont work with the dialog. > > So you can think of it as ctrl+l+enter . Saying that I will have another go > on undo , I really want to understand how undo works not just for this fix > but generally. I agree that the fix is not ideal as it is but unfortunately > my understanding of Pharo is very limited right now. We should add this now and then the people who use ctrl-l a lot can do a fix with putting the content in the undo. Marcus

Oct. 14, 2013

Re: [Pharo-dev] Case 11835 - Cannot revert <Make uncloseable>

by Benjamin

Ben On Oct 14, 2013, at 5:04 PM, btc(a)openInWorld.com wrote: > In 2.0 when you choose <Make unclosable> from the SystemWindow menu (downward-pointing triangle in the top right of each window), the next invocation of that menu would instead have the opposite function <Make closable>. > > In 3.0 it does not change to <Make closable> so you cannot revert the feature. I have isolated this to PragmaMenuBuilder's ivar 'itemList' being cached, and describe a a fix at https://pharo.fogbugz.com/default.asp?11835 > > However I am not comfortable with my awareness of the architectural implications and so I seek a wider discussion of this. Two queries leap to mind: > > > 1. What is the philosophy behind caching the pragma-menus? To what degree did menu performance suffer in practice? Since pragmas are spread all over the system, each time the PragmaBuilder collects the pragmas, it iterates over all the methods. This can be a pain :) > > 2. What consideration has been given to dynamic elements in other pragma-menus? I think there is a way to provide the name as a dynamically evaluable object (a block or a message send). I am not 100% sure of that. > > 3. Suggestions for alternative resolution paths to follow? A less drastic approach would be to flush the cache when you click on <Make closable>/<Make unclosable> Ben > > cheers -ben >

Oct. 14, 2013

Re: [Pharo-dev] bug: [4993] Typing cmd+L cancel all typing and we can't undo it [Terminated]

by kilon

the dialog does not force you to use the mouse, you just do ctrl+l and then hit enter to confirm ("yes" is preselected). So essentially it only introduces one more keyboard key, enter. If you want to cancel the cmd+l is when you will need to use the mouse (so you choose "No" option). Apparently arrow keys dont work with the dialog. So you can think of it as ctrl+l+enter . Saying that I will have another go on undo , I really want to understand how undo works not just for this fix but generally. I agree that the fix is not ideal as it is but unfortunately my understanding of Pharo is very limited right now. btc wrote > <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 > Transitional//EN"> > > > > > > > Alexandre Bergel wrote: > > Hi! > > Thanks Kilon for working on the Contr-l key binding. I use this control > key binding a lot, and actually, it is really rare when I do a mistake. > Having to press OK whenever I do this sounds like a regression to me. Why > not always inserting the text in the undo queue before replacing the text? > > Alexandre > > > > I originally had the same opinion, and I had a go getting undo to work > but failed.Â So I tested kilon's slice and it seemed to not adversely > affect my workflow.Â I wonder if a compromise might be the ability to > acknowledge the alert dialog with <ctrl-l> - so you don't have to > move your fingers from the shortcut, and still provides a guard against > accidental reset. > -ben > > > > > > Le 13-10-2013 Ã 8:08, kilon < > thekilon@.co > > a Ã©crit : > > This is my first pharo bug fix so be gentle :D > > https://pharo.fogbugz.com/f/cases/4993/Typing-cmd-L-cancel-all-typing-and-w… > <https://pharo.fogbugz.com/f/cases/4993/Typing-cmd-L-cancel-all-typing-and-we-can-t-undo-it> > > As I explain in the link and in my commit log , I have added a confirm > dialog so the user in case he accidentally pressed CMD+L will click no and > his changes will not be lost. I have verified the bug fix with the latest > pharo build. > > > > -- > View this message in context: > http://forum.world.st/bug-4993-Typing-cmd-L-cancel-all-typing-and-we-can-t-… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. -- View this message in context: http://forum.world.st/bug-4993-Typing-cmd-L-cancel-all-typing-and-we-can-t-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 14, 2013

Case 11835 - Cannot revert <Make uncloseable>

by btc＠openinworld.com

In 2.0 when you choose <Make unclosable> from the SystemWindow menu (downward-pointing triangle in the top right of each window), the next invocation of that menu would instead have the opposite function <Make closable>. In 3.0 it does not change to <Make closable> so you cannot revert the feature. I have isolated this to PragmaMenuBuilder's ivar 'itemList' being cached, and describe a a fix at https://pharo.fogbugz.com/default.asp?11835 However I am not comfortable with my awareness of the architectural implications and so I seek a wider discussion of this. Two queries leap to mind: 1. What is the philosophy behind caching the pragma-menus? To what degree did menu performance suffer in practice? 2. What consideration has been given to dynamic elements in other pragma-menus? 3. Suggestions for alternative resolution paths to follow? cheers -ben

Oct. 14, 2013

Re: [Pharo-dev] bug: [4993] Typing cmd+L cancel all typing and we can't undo it [Terminated]

by btc＠openinworld.com

Oct. 14, 2013

Re: [Pharo-dev] bug: [4993] Typing cmd+L cancel all typing and we can't undo it [Terminated]

by Marcus Denker

On Oct 14, 2013, at 3:06 PM, kilon <thekilon(a)yahoo.co.uk> wrote: > Definetly not a regression. If you make a mistake your work is gone, bye bye, > hasta la vista baby. Personally I dont use, or see myself using CMD+L on a > daily basis. Its highly unlikely that I will code in several lines of code > and will want to discard them completely. In 99/100 cases I just slightly > change, edit the code. So we definitely have a different workflow on this > one. > > You are much better coders than me, so I understand you may use that feature > heavily. > > Undo was my first goal too, but trying to understand how undo is implemented > felt like hammering my face on a wall. The amount of spaggetication in the > code is beyond understanding for me, on the 1 hour I invested of finding a > bug fix. So I spent like 50 minutes trying to understand undo, failed > miserably, spent rest 10 implementing the dialog box. And yes I am not very > smart or good coder. > > I will try to take another look at undo today and have another go at this, > but If I found no solution I will leave the fix as it is. Chances are I wont > figure this out, so don't hold your breath. > > Bottom line is that in case of proper software the user should not allowed > to do things that are unrecoverable without a prompt. So not implementing a > fix at all, at least for me is considered very bad. But this is just my > personal opinion. > I am 100% with you on this :-) Marcus

Oct. 14, 2013

Re: [Pharo-dev] bug: [4993] Typing cmd+L cancel all typing and we can't undo it [Terminated]

by kilon

Definetly not a regression. If you make a mistake your work is gone, bye bye, hasta la vista baby. Personally I dont use, or see myself using CMD+L on a daily basis. Its highly unlikely that I will code in several lines of code and will want to discard them completely. In 99/100 cases I just slightly change, edit the code. So we definitely have a different workflow on this one. You are much better coders than me, so I understand you may use that feature heavily. Undo was my first goal too, but trying to understand how undo is implemented felt like hammering my face on a wall. The amount of spaggetication in the code is beyond understanding for me, on the 1 hour I invested of finding a bug fix. So I spent like 50 minutes trying to understand undo, failed miserably, spent rest 10 implementing the dialog box. And yes I am not very smart or good coder. I will try to take another look at undo today and have another go at this, but If I found no solution I will leave the fix as it is. Chances are I wont figure this out, so don't hold your breath. Bottom line is that in case of proper software the user should not allowed to do things that are unrecoverable without a prompt. So not implementing a fix at all, at least for me is considered very bad. But this is just my personal opinion. -- View this message in context: http://forum.world.st/bug-4993-Typing-cmd-L-cancel-all-typing-and-we-can-t-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 14, 2013