August 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] ifTrue ifFalse shortcuts

by Franck Warlouzet

Ok then I will add it to Rubric Franck > Date: Sat, 8 Aug 2015 03:54:02 -0700 > From: sean(a)clipperadams.com > To: pharo-dev(a)lists.pharo.org > Subject: Re: [Pharo-dev] ifTrue ifFalse shortcuts > > Peter UhnÃ¡k wrote > > I would also appreciate if it was readded, as I've been using it > > regularly. > > +1. Of course hopefully one day soon our dream of fully customizable > shortcuts will be realized and we can each have the exact shortcuts we want > :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ifTrue-ifFalse-shortcuts-tp4841604p4841618.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Aug. 8, 2015

Re: [Pharo-dev] ifTrue ifFalse shortcuts

by Sean P. DeNigris

Peter UhnÃ¡k wrote > I would also appreciate if it was readded, as I've been using it > regularly. +1. Of course hopefully one day soon our dream of fully customizable shortcuts will be realized and we can each have the exact shortcuts we want :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/ifTrue-ifFalse-shortcuts-tp4841604p4841618.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 8, 2015

Re: [Pharo-dev] ifTrue ifFalse shortcuts

by Peter UhnÃ¡k

I would also appreciate if it was readded, as I've been using it regularly. Peter On Sat, Aug 8, 2015 at 12:21 PM, ThomasHeniart <heniart.thomas(a)gmail.com> wrote: > I think it could be nice to keep this shortcut :) > > > On 08/08/2015 12:12, Franck Warlouzet wrote: > > Hi, > > Yes it was not on purpose. It is not implemented in Rubric, but I can do > it if there is a need of it (which seems to be the case). > > Franck > > ------------------------------ > Date: Sat, 8 Aug 2015 12:09:22 +0200 > From: i.uhnak(a)gmail.com > To: pharo-dev(a)lists.pharo.org > Subject: [Pharo-dev] ifTrue ifFalse shortcuts > > Hi, > > was removal of ifTrue/ifFalse shortcuts on purpose, or by accident? > > https://pharo.fogbugz.com/f/cases/16125/Nautilus-doesn-t-recognize-the-cmd-… > (maybe was caused by switch to Rubric?) > > Peter > > >

Aug. 8, 2015

Re: [Pharo-dev] ifTrue ifFalse shortcuts

by ThomasHeniart

I think it could be nice to keep this shortcut :) On 08/08/2015 12:12, Franck Warlouzet wrote: > Hi, > > Yes it was not on purpose. It is not implemented in Rubric, but I can > do it if there is a need of it (which seems to be the case). > > Franck > > ------------------------------------------------------------------------ > Date: Sat, 8 Aug 2015 12:09:22 +0200 > From: i.uhnak(a)gmail.com > To: pharo-dev(a)lists.pharo.org > Subject: [Pharo-dev] ifTrue ifFalse shortcuts > > Hi, > > was removal of ifTrue/ifFalse shortcuts on purpose, or by accident? > https://pharo.fogbugz.com/f/cases/16125/Nautilus-doesn-t-recognize-the-cmd-… > (maybe was caused by switch to Rubric?) > > Peter

Aug. 8, 2015

Re: [Pharo-dev] ifTrue ifFalse shortcuts

by Franck Warlouzet

Hi, Yes it was not on purpose. It is not implemented in Rubric, but I can do it if there is a need of it (which seems to be the case). Franck Date: Sat, 8 Aug 2015 12:09:22 +0200 From: i.uhnak(a)gmail.com To: pharo-dev(a)lists.pharo.org Subject: [Pharo-dev] ifTrue ifFalse shortcuts Hi, was removal of ifTrue/ifFalse shortcuts on purpose, or by accident?https://pharo.fogbugz.com/f/cases/16125/Nautilus-doesn-t-recognize… (maybe was caused by switch to Rubric?) Peter

Aug. 8, 2015

ifTrue ifFalse shortcuts

by Peter UhnÃ¡k

Hi, was removal of ifTrue/ifFalse shortcuts on purpose, or by accident? https://pharo.fogbugz.com/f/cases/16125/Nautilus-doesn-t-recognize-the-cmd-… (maybe was caused by switch to Rubric?) Peter

Aug. 8, 2015

Multi Line labels/texts [New-Line/Line-Feed help required]

by Jigyasa Grover

Hi I have made an accordion widget for my application *searchQuick* ( https://github.com/jig08/sQuick_new ), an offline text search application using Expander Morphs I was trying to insert a multi-line content in it , but in vain. The new-line methods don't seem to have the desired effect. *I have tried the following ways:* *1. dialog newExpander: (result title asString, Character cr asString , result content asString ) * *2. dialog newExpander: (result title asString, '\' withCRs, result content asString)* *3. dialog newExpander: (result title asString, String crlf , result content asString ) * *[ result is the array item representing a document having the search string ]* Could anyone pls point out the error in my approach ? It would be a great help. Thank You Jigyasa

Aug. 8, 2015

Re: [Pharo-dev] Launcher Issues

by Damien Cassou

Sean P. DeNigris <sean(a)clipperadams.com> writes: > For "Issue 16115: Launcher: Update Common Tools for Moose 5.1 Release" > (https://pharo.fogbugz.com/default.asp?16115) the fix has been picked up by > the CI and I verified that it works. What is the process here? Shall I close > the issue with something like "in build #51"? I released 0.2.8 from your code. Thanks. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Aug. 8, 2015

System Windows not closing on using #close

by Jigyasa Grover

Hi I am using *SystemWindow* to open a Morph in my application *searchQuick*. ( https://github.com/jig08/sQuick_new ) On clicking a button, a new screen opens up but the prev window fails to close, though I have tried using #close methods. The code snippets are as: *------------------------------------------------------------------------------------------------------------------* *IndexInterface>>**#initialize* *. . . . . .* * boxWindow := SystemWindow new.* * box position: 150(a)0.* * boxWindow addMorph: box.* * boxWindow extent: World extent.* * boxWindow openInWindowLabeled: 'searchQuick'.* * boxWindow fullscreen.* * boxWindow color: Color black.* *. . . . . . .* browseBtn on: #click send: #value to: [self boxWindow window close. IndexInterface delete. BrowseFiles open]. *-------------------------------------------------------------------------------------------------------------------* *IndexInterface>>#delete* * box isNil ifFalse: [ self boxWindow window close. * * self boxWindow window delete . * * self boxWindow close. * * box window close .* * self boxWindow delete. * * box delete.].* * box := nil.* * self boxWindow window close. * * self boxWindow window delete .* * self boxWindow close. * * self boxWindow delete.* * boxWindow := nil.* *-------------------------------------------------------------------------------------------------------------------* Help appreciated. Regards Jigyasa

Aug. 8, 2015

Re: [Pharo-dev] Is Metacello in Pharo 5.0 up-to-date? and project locking

by Dale Henrichs

On 08/07/2015 01:08 AM, Christophe Demarey wrote: > Le 6 aoÃ»t 2015 Ã 22:49, Dale Henrichs a Ã©crit : > >> For the Metacello tests themselves, the version of Metacello under test is installed on top of the version present in the image, using the "standard Metacello update code" ... failures at this point indicate Metacello upgrade problems ... then the unit tests are run ... > ok, I found hat is missing. > Metacello update through the BaselineOfMetacello works ... but the code used for the bootsrap of Metacello in BuilderCI uses the ConfigurationOfMetacelloPreview and load the stable version that is currently 1.0.0-beta.32.17. The change I made to builderCI[1] involves skipping the bootstrap of Metacello (via ConfigurationOfMetacelloPreview) completely. The Metacello bootstrap was been skipped for Pharo3.0 and Pharo4.0 and we just missed that detail when adding Pharo5.0. [1] https://github.com/dalehenrich/builderCI/commit/0394467e5d13c7e99500fd30175… > I think when there is already a version of Metacello able to load through the baseline, builderCi should use the Baseline to update Metacello. > WDYT? builderCI only ensures that there is a Metacello available, I don't think that it should upgrade Metacello ... I use builderCI to test the upgrade/update of Metacello to a new version so to have builderCI automatically update would defeat the purpose and mask issues. Also if there are issues in the shipped version of Metacello that show up when loading a particular project, then those issues should be revealed, since the standard workflow for loading into an image should not include lading the latest Metacello first... If a project chooses to test with the latest version of Metacello (something I often do for GemStone tests) then the project itself should do the upgrade ... Dale

Aug. 7, 2015