May 2013 - 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-Validation/./label=ma… 1 regressions found. ToolsTest.Debugger.DebuggerTest.testBasic

May 27, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 1 regressions found. ToolsTest.Debugger.DebuggerTest.testBasic

May 27, 2013

[update 3.0] #30170

by Marcus Denker

30170 ----- 10654 Add the --save option to the eval command line handler https://pharo.fogbugz.com/f/cases/10654 10698 add back Block printing https://pharo.fogbugz.com/f/cases/10698 (When Opal is Active) Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-CommandLine-MarcusDenk… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1465.diff

May 27, 2013

Re: [Pharo-dev] [Ann] New TxText version 1.0

by Denis Kudriashov

2013/5/27 Tudor Girba <tudor(a)tudorgirba.com> > I tried to load it, but could not because in the sig repository, the > latest version of the configuration is still 0.6. > > It works for me. I use Pharo 2.0 on Windows 7. And you can see by webbrowser all versions exist at smalltalkhub repository http://www.smalltalkhub.com/#!/~sig/TxText > Cheers, > Doru > > > On May 26, 2013, at 11:09 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > > > Hello. > > > > I finish edit validation logic. So new version 1.0 is available: > > > > Gofer it > > url: 'http://www.smalltalkhub.com/#!/~sig/TxText'; > > package: 'ConfigurationOfTxText'; > > load. > > > > ((Smalltalk at: #ConfigurationOfTxText) project version: '1.0') load: > > #('ALL'). > > > > TxEditValidator is introduced for TxEditor. It validates changes > performed by given block. > > It asks editor to try changes from this block. And if changed text > satisfied text spec validator executes given block to apply changes. > > > > Few text specs implemented: > > -TxAnyTextSpec > > -TxDigitalTextSpec > > -TxDecimalTextSpec > > > > More example of text specs are at TxTextMorph class side: > > - mask with digits only > > - smart numbers which accept only decimal numbers: > > > > m := TxTextMorph new. > > m editDecorator: TxSingleLineEditDecorator smartNumbers. > > m textSpec: (TxDecimalTextSpec maxDecimalDigits: 3). > > m newTextContents: '10000000'. > > m addCursor. > > m beEditable. > > m openInHand > > > > Best regards. > > Denis. > > > > > > -- > www.tudorgirba.com > > "Problem solving efficiency grows with the abstractness level of problem > understanding." > > > > >

May 27, 2013

Re: [Pharo-dev] [Ann] New TxText version 1.0

by Tudor Girba

I tried to load it, but could not because in the sig repository, the latest version of the configuration is still 0.6. Cheers, Doru On May 26, 2013, at 11:09 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hello. > > I finish edit validation logic. So new version 1.0 is available: > > Gofer it > url: 'http://www.smalltalkhub.com/#!/~sig/TxText'; > package: 'ConfigurationOfTxText'; > load. > > ((Smalltalk at: #ConfigurationOfTxText) project version: '1.0') load: > #('ALL'). > > TxEditValidator is introduced for TxEditor. It validates changes performed by given block. > It asks editor to try changes from this block. And if changed text satisfied text spec validator executes given block to apply changes. > > Few text specs implemented: > -TxAnyTextSpec > -TxDigitalTextSpec > -TxDecimalTextSpec > > More example of text specs are at TxTextMorph class side: > - mask with digits only > - smart numbers which accept only decimal numbers: > > m := TxTextMorph new. > m editDecorator: TxSingleLineEditDecorator smartNumbers. > m textSpec: (TxDecimalTextSpec maxDecimalDigits: 3). > m newTextContents: '10000000'. > m addCursor. > m beEditable. > m openInHand > > Best regards. > Denis. > > -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

May 26, 2013

[Ann] New TxText version 1.0

by Denis Kudriashov

Hello. I finish edit validation logic. So new version 1.0 is available: Gofer it url: 'http://www.smalltalkhub.com/#!/~sig/TxText'; package: 'ConfigurationOfTxText'; load. ((Smalltalk at: #ConfigurationOfTxText) project version: '1.0') load: #('ALL'). TxEditValidator is introduced for TxEditor. It validates changes performed by given block. It asks editor to try changes from this block. And if changed text satisfied text spec validator executes given block to apply changes. Few text specs implemented: -TxAnyTextSpec -TxDigitalTextSpec -TxDecimalTextSpec More example of text specs are at TxTextMorph class side: - mask with digits only - smart numbers which accept only decimal numbers: m := TxTextMorph new. m editDecorator: TxSingleLineEditDecorator smartNumbers. m textSpec: (TxDecimalTextSpec maxDecimalDigits: 3). m newTextContents: '10000000'. m addCursor. m beEditable. m openInHand Best regards. Denis.

May 26, 2013

Running coverage breaks the VM

by Frank Shearar

Hi, I wanted to see FileSystem's coverage, so I * downloaded 3.0 via curl http://get.pharo.org/30+vm | bash, * fired up the image, * opened the TestRunner, * highlighted the three FileSystem packages, * "select all"ed, * pressed "Run Coverage" and the VM crashed with a segfault. I tried with a few other packages, and every time I tried to run coverage the VM died with the same message: Segmentation fault Sun May 26 15:46:45 2013 pharo VM version: 3.9-7 #1 Wed Mar 13 18:22:44 CET 2013 gcc 4.4.3 Built from: NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 With: NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 Revision: git://gitorious.org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 Build host: Linux linux-ubuntu-10 2.6.32-38-server #83-Ubuntu SMP Wed Jan 4 11:26:59 UTC 2012 x86_64 GNU/Linux plugin path: /home/frank/Downloads/pharo-3.0/pharo-vm/ [default: /home/frank/Downloads/pharo-3.0/pharo-vm/] C stack backtrace: pharo-vm/pharo[0x80a0c0c] pharo-vm/pharo[0x80a0f28] [0x408410] [0x77744f1e] [0x777447c8] [0x7819010f] [0x777454f9] [0x777447c8] [0x7818e112] [0x777fc687] [0x777456ea] [0x77744668] Smalltalk stack dump: 0xbfc98e4c I [] in InteractiveResolverTest(TestCase)>runCase 0x78f0bfc8: a(n) InteractiveResolverTest 0xbfc98e6c M BlockClosure>ensure: 0x78fa4c34: a(n) BlockClosure 0xbfc98e90 I InteractiveResolverTest(TestCase)>runCase 0x78f0bfc8: a(n) InteractiveResolverTest 0xbfc98eb4 I [] in TestResult>runCase: 0x78f0bdcc: a(n) TestResult 0xbfc98ed0 M BlockClosure>on:do: 0x78fa4a30: a(n) BlockClosure 0xbfc98ef8 I TestResult>runCase: 0x78f0bdcc: a(n) TestResult 0xbfc98f1c I InteractiveResolverTest(TestCase)>run: 0x78f0bfc8: a(n) InteractiveResolverTest 0xbfc98f3c M [] in TestSuite>run: 0x78f0bfb0: a(n) TestSuite 0xbfc98f5c M OrderedCollection>do: 0x78f0bfdc: a(n) OrderedCollection 0xbfc9fdf0 I [] in TestSuite>run: 0x78f0bfb0: a(n) TestSuite 0xbfc9fe10 M BlockClosure>ensure: 0x78fa48e4: a(n) BlockClosure 0xbfc9fe34 I TestSuite>run: 0x78f0bfb0: a(n) TestSuite 0xbfc9fe58 I [] in TestRunner>runSuite: 0x78e405bc: a(n) TestRunner 0xbfc9fe80 I BlockClosure>cull:cull: 0x78f9c050: a(n) BlockClosure 0xbfc9feb0 I [] in TestRunner>executeSuite:as: 0x78e405bc: a(n) TestRunner 0xbfc9fed0 M BlockClosure>ensure: 0x78f9c420: a(n) BlockClosure 0xbfc9fef4 I TestRunner>executeSuite:as: 0x78e405bc: a(n) TestRunner 0xbfc9ff1c I TestRunner>runSuite: 0x78e405bc: a(n) TestRunner 0xbfc9ff3c M [] in TestRunner>collectCoverageFor: 0x78e405bc: a(n) TestRunner 0xbfc9ff5c M BlockClosure>ensure: 0x78f9bfcc: a(n) BlockClosure 0xbfc97e54 M [] in TestRunner>collectCoverageFor: 0x78e405bc: a(n) TestRunner 0xbfc97e74 M BlockClosure>ensure: 0x78f0dd7c: a(n) BlockClosure 0xbfc97ea8 I BlockClosure>valueUnpreemptively 0x78f0dd7c: a(n) BlockClosure 0xbfc97ed4 I TestRunner>collectCoverageFor: 0x78e405bc: a(n) TestRunner 0xbfc97ef8 M TestRunner>runCoverage 0x78e405bc: a(n) TestRunner 0xbfc97f18 I PluggableButtonMorph>performAction: 0x78e6c24c: a(n) PluggableButtonMorph 0xbfc97f38 M [] in PluggableButtonMorph>mouseUp: 0x78e6c24c: a(n) PluggableButtonMorph 0xbfc97f5c M Array(SequenceableCollection)>do: 0x78ed9f14: a(n) Array 0xbfc93e08 M PluggableButtonMorph>mouseUp: 0x78e6c24c: a(n) PluggableButtonMorph 0xbfc93e28 M PluggableButtonMorph(Morph)>handleMouseUp: 0x78e6c24c: a(n) PluggableButtonMorph 0xbfc93e44 M MouseButtonEvent>sentTo: 0x78ed9eec: a(n) MouseButtonEvent 0xbfc93e60 M PluggableButtonMorph(Morph)>handleEvent: 0x78e6c24c: a(n) PluggableButtonMorph 0xbfc93e7c M PluggableButtonMorph(Morph)>handleFocusEvent: 0x78e6c24c: a(n) PluggableButtonMorph 0xbfc93ea4 M [] in HandMorph>sendFocusEvent:to:clear: 0x77b1c270: a(n) HandMorph 0xbfc93ec0 M [] in PasteUpMorph>becomeActiveDuring: 0x7796b824: a(n) PasteUpMorph 0xbfc93edc M BlockClosure>on:do: 0x78ed9e5c: a(n) BlockClosure 0xbfc93f08 M PasteUpMorph>becomeActiveDuring: 0x7796b824: a(n) PasteUpMorph 0xbfc93f2c M HandMorph>sendFocusEvent:to:clear: 0x77b1c270: a(n) HandMorph 0xbfc93f54 M HandMorph>sendEvent:focus:clear: 0x77b1c270: a(n) HandMorph 0xbfc92e44 M HandMorph>sendMouseEvent: 0x77b1c270: a(n) HandMorph 0xbfc92e68 M HandMorph>handleEvent: 0x77b1c270: a(n) HandMorph 0xbfc92e94 M HandMorph>processEvents 0x77b1c270: a(n) HandMorph 0xbfc92eac M [] in WorldState>doOneCycleNowFor: 0x7797ab44: a(n) WorldState 0xbfc92ed0 M Array(SequenceableCollection)>do: 0x77846894: a(n) Array 0xbfc92eec M WorldState>handsDo: 0x7797ab44: a(n) WorldState 0xbfc92f08 M WorldState>doOneCycleNowFor: 0x7797ab44: a(n) WorldState 0xbfc92f24 M WorldState>doOneCycleFor: 0x7797ab44: a(n) WorldState 0xbfc92f40 M PasteUpMorph>doOneCycle 0x7796b824: a(n) PasteUpMorph 0xbfc92f60 I [] in MorphicUIManager>? 0x7797ebd4: a(n) MorphicUIManager 0x77c9891c s [] in BlockClosure>? Most recent primitives class class class class class class class

May 26, 2013

Re: [Pharo-dev] [update 3.0] #30169

by Camillo Bruni

Indeed that is getting very interesting now we just have to plug them properly into the system - direct feedback when writing code - CI feedback for slices On 2013-05-26, at 18:15, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Excellent. I love highly specific rules :). They bring so much more value than the other ones. > > On May 26, 2013, at 2:59 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> 10621 Create a lint rule to make sure UITheme and ThemeIcons are not used anymore >> https://pharo.fogbugz.com/f/cases/10621 > > -- > www.tudorgirba.com > > "Quality cannot be an afterthought." > >

May 26, 2013

Re: [Pharo-dev] [update 3.0] #30169

by Tudor Girba

Excellent. I love highly specific rules :). They bring so much more value than the other ones. Cheers, Doru On May 26, 2013, at 2:59 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 10621 Create a lint rule to make sure UITheme and ThemeIcons are not used anymore > https://pharo.fogbugz.com/f/cases/10621 -- www.tudorgirba.com "Quality cannot be an afterthought."

May 26, 2013

Re: [Pharo-dev] command line handler default options

by Camillo Bruni

On 2013-05-26, at 15:45, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi Camillo, > > On 26 May 2013, at 13:57, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> Currently Pharo runs without a message when started in headless mode: >> >> ./pharo Pharo.image >> >> However I would expect it to give a feedback, so it would behave like this: >> >> ./pharo Pharo.image --help >> >> AFAIK seaside doesn't have a command line handler yet ;), but how would you guys >> perceive it if >> >> - there is a a help message printed, >> - the image stops if there are no commands provided? >> >> We can add a --no-quit option to the default command line handler so the image >> continues running with whatever service there is. > > Yes, but > > - it might be a bit confusing since a normal image with GUI is started like in the first cmd line > - tools that don't print needless information are cool I took care of that in UI mode it - doesn't print anything on the command line - continues running and in headless mode - it prints --help - it quits unless there is --no-quit > - the -no-quit option is useful in the eval case as well to start a server/service added that as well in the same refactoring. Maybe you can have a look at it? https://pharo.fogbugz.com/default.asp?10759 with its proper SLICE in the inbox.

May 26, 2013