- Pharo-dev - lists.pharo.org

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=wi… 1 regressions found. Zinc.Tests.ZnServerTests.testHeaderLineTooLong

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.1-Validation/label=wi… 1 regressions found. Zinc.Tests.ZnServerTests.testEntityTooLarge

Oct. 14, 2013

Re: [Pharo-dev] https://pharo.fogbugz.com ??

by Camillo Bruni

The full description should be up here: https://pharo.fogbugz.com/default.asp?pre=preLogOff I wish I could update the bugs.pharo.org website :/ On 2013-10-14, at 23:54, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi > > Yes, I dare asking this question. How can I create a login on https://pharo.fogbugz.com ? > I guess this is the website that we use to monitor issues right? > I have created a login on bugs.pharo.org. I am not sure how does this differ from the fogbugz... > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Oct. 14, 2013

https://pharo.fogbugz.com ??

by Alexandre Bergel

Hi Yes, I dare asking this question. How can I create a login on https://pharo.fogbugz.com ? I guess this is the website that we use to monitor issues right? I have created a login on bugs.pharo.org. I am not sure how does this differ from the fogbugz... Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 14, 2013

Re: [Pharo-dev] SS3 with HTTP 503

by Tobias Pape

On 14.10.2013, at 21:56, Torsten Bergmann <astares(a)gmx.de> wrote: > http://ss3.gemtalksystems.com/ Up from hereâ¦

Oct. 14, 2013

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