December 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Text Indentation in Pharo editor

by Ben Coman

On 8 December 2017 at 11:37, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Torsten Bergmann wrote > > so we do it with different shortcuts than regular editors > > I wonder if it makes sense to allow the standard shortcut. The current one > is a bit like playing twister ;) > We should be different if there is a good reason, but where possible (especially on UI interface) we should align with the majority. I feel this case is the latter. cheers -ben

Dec. 8, 2017

[Pharo 7.0-dev] Build #367: 20839 Super setUp need to be called in NECompletion-Tests

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #367 was: SUCCESS. The Pull Request #589 was integrated: "20839 Super setUp need to be called in NECompletion-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/589 Issue Url: https://pharo.fogbugz.com/f/cases/20839 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 8, 2017

Re: [Pharo-dev] How to get rid of empty XML nodes?

by monty

By "empty XML nodes," do you mean whitespace-only string nodes? Those are included because all in-element whitespace is assumed significant by the spec: https://www.w3.org/TR/xml/#sec-white-space The exception is if the element is declared in the DTD as only having element children ("element content"): https://www.w3.org/TR/xml/#dt-elemcontent For example, if you declare an element like this: <!ELEMENT one (two,three*,four?)> Any whitespace around a "two," "three," or "four" element child of a "one" element is insignificant and ignored (unless #preservesIgnorableWhitespace: is true). Other parsers, like LibXML2 and Xerces, behave the same way. I'll see if I can come up with some easier way to deal with this, like an optional parser setting, new enumeration methods, or maybe a tree transformation. > Sent: Tuesday, December 05, 2017 at 8:29 AM > From: "Stephane Ducasse" <stepharo.self(a)gmail.com> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Subject: [Pharo-dev] How to get rid of empty XML nodes? > > )Hi > > we are manipulating an XML document and I would like to get rid of the > spurious empty string. > We saw that the gt panes are doing it. > > (aNodeWithElements isStringNode > and: [aNodeWithElements isEmpty > or: [aNodeWithElements isWhitespace]] > > Is there a way not to produce empty nodes? > Is there a simple way not to have to handle them > > Now each time we are dealing with a node with have to check. > > Stef > >

Dec. 8, 2017

Re: [Pharo-dev] Crash Dump - GT loaded into 6.1

by Tudor Girba

Hi Sean, Thanks. I noticed this as well, but we do not quite know where the problem comes from. Doru > On Dec 7, 2017, at 6:05 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Different image, another crash dump while quitting the image. Lost a bunch of > data this time. Ouch. > > Segmentation fault Wed Dec 6 22:30:12 2017 > > > VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > Date: Thu Jul 20 12:42:21 2017 -0700 $ > Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git > $ > > C stack backtrace & registers: > eax 0x8bfffee0 ebx 0x00000000 ecx 0x0000000c edx 0x00000007 > edi 0x0000000c esi 0x0000000c ebp 0xbff3fad8 esp 0xbff3fad8 > eip 0x000b2651 > 0 Pharo 0x000b2651 fetchByteofObject + 9 > 1 Pharo 0x00113460 reportStackState + 819 > 2 Pharo 0x001137e6 sigsegv + 163 > 3 libsystem_platform.dylib 0xa778202b _sigtramp + 43 > 4 ??? 0xffffffff 0x0 + 4294967295 > 5 Pharo 0x000dbb9a bytecodePCForstartBcpcin > + 273 > 6 Pharo 0x0009fed8 > mustMapMachineCodePCcontext + 328 > 7 Pharo 0x000a0333 > ensureContextHasBytecodePC + 26 > 8 Pharo 0x000cbb17 makeContextSnapshotSafe + > 46 > 9 Pharo 0x000ab11d > voidVMStateForSnapshotFlushingExternalPrimitivesIf + 518 > 10 Pharo 0x000da477 snapshot + 79 > 11 Pharo 0x000d019d primitiveSnapshot + 20 > 12 Pharo 0x000946e8 interpret + 26051 > 13 Pharo 0x0009db9a > enterSmalltalkExecutiveImplementation + 135 > 14 Pharo 0x0008e3ab interpret + 646 > 15 Pharo 0x001149d9 -[sqSqueakMainApplication > runSqueak] + 476 > 16 Foundation 0x953897ec __NSFirePerformWithOrder > + 432 > 17 CoreFoundation 0x9392a216 > __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 22 > 18 CoreFoundation 0x9392a132 __CFRunLoopDoObservers + > 498 > 19 CoreFoundation 0x9390d5ed __CFRunLoopRun + 1661 > 20 CoreFoundation 0x9390cc41 CFRunLoopRunSpecific + > 641 > 21 CoreFoundation 0x9390c9aa CFRunLoopRunInMode + 122 > 22 HIToolbox 0x92f0dd3b RunCurrentEventLoopInMode > + 321 > 23 HIToolbox 0x92f0d91f ReceiveNextEventCommon + > 454 > 24 HIToolbox 0x92f0d73b > _BlockUntilNextEventMatchingListInModeWithFilter + 71 > 25 AppKit 0x9136538d _DPSNextEvent + 2101 > 26 AppKit 0x91ad6c74 -[NSApplication(NSEvent) > _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 2859 > 27 AppKit 0x91ad6141 -[NSApplication(NSEvent) > nextEventMatchingMask:untilDate:inMode:dequeue:] + 134 > 28 AppKit 0x9135a2e1 -[NSApplication run] + > 763 > 29 AppKit 0x9132c2f2 NSApplicationMain + 1228 > 30 libdyld.dylib 0xa7502711 start + 1 > 31 ??? 0x00000002 0x0 + 2 > > > Smalltalk stack dump: > 0xbff6ac60 I SessionManager>snapshot:andQuit: 0x8489350: a(n) SessionManager > 0xbff6ac90 I [] in SmalltalkImage>snapshot:andQuit: 0x6ea1c50: a(n) > SmalltalkImage > 0x1f943be0 s CurrentExecutionEnvironment class>activate:for: > 0x6806028 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x6806088 s DefaultExecutionEnvironment class>beActiveDuring: > 0x1f943c60 s SmalltalkImage>snapshot:andQuit: > > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > -- www.tudorgirba.com www.feenk.com "What is more important: To be happy, or to make happy?"

Dec. 8, 2017

Re: [Pharo-dev] Text Indentation in Pharo editor

by Sean P. DeNigris

Torsten Bergmann wrote > so we do it with different shortcuts than regular editors I wonder if it makes sense to allow the standard shortcut. The current one is a bit like playing twister ;) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 8, 2017

Re: [Pharo-dev] Text Indentation in Pharo editor

by Torsten Bergmann

Hi Pavel, so we do it with different shortcuts than regular editors - but at least it is there. Thanks for the hint! Bye T. Â Â Gesendet:Â Donnerstag, 07. Dezember 2017 um 16:22 Uhr Von:Â "Pavel Krivanek" <pavel.krivanek(a)gmail.com> An:Â "Pharo Development List" <pharo-dev(a)lists.pharo.org> Betreff:Â Re: [Pharo-dev] Text Indentation in Pharo editor Â 2017-12-07 16:19 GMT+01:00 Torsten Bergmann <astares@gmx.de[mailto:astares@gmx.de]>:Hi, in most code editors I know one can select a (multiline) block of code/text and then hit TAB to indent and move it from the position to the right side. Using SHIFT+TAB one can move it back to the left. In Pharo the selected text unfortunately is always deleted instead of moved/indented when hitting TAB. Is such an editor mode or special key combination available? If not could this easily be brought into the current text/code editor(s) in Pharo 7? Or will a possible upcoming Bloc text/code editor support such behavior? Â Ctrl + Shift + L or Ctrl + Shift + R Â -- PavelÂ This would be really nice to have and move Pharo editor away from being like Notepad. Because editors in Eclipse, NetBeans, VS, Brackets, Atom, Notepad++ all support this TAB Indentation out of the box. ;) Thanks T. Â

Dec. 7, 2017

Re: [Pharo-dev] Release: Conveniently browse, deactivate and reactivate halts and breakpoints with the HaltManager

by Stephane Ducasse

This is cool that you can scope using calypso. I have to try it! On Wed, Dec 6, 2017 at 11:03 AM, Thomas Dupriez <thomas.dupriez(a)ens-paris-saclay.fr> wrote: > Hello, > > I have developed a package to assist developers managing their halts and > breakpoints: HaltManager. > > HaltManager provides a window showing all the breakpoints and halt messages > of the system, and allows one to toggle them on/off with a simple click. > Halt messages can also be toggled via source code rewriting. The > deactivation/reactivation feature is available in all code browsers, not > only in the HaltManager window. > > It is available here, with installation instructions and pictures: > https://github.com/dupriezt/HaltManager > > Feedback welcome. > > Cheers, > Thomas Dupriez > >

Dec. 7, 2017

Re: [Pharo-dev] Release: Conveniently browse, deactivate and reactivate halts and breakpoints with the HaltManager

by Stephane Ducasse

Thanks Thomas and you put screenshots so this is cool. I have a simple question if there is only a self halt in the code why you propose to change metalinks? Stef On Wed, Dec 6, 2017 at 11:03 AM, Thomas Dupriez <thomas.dupriez(a)ens-paris-saclay.fr> wrote: > Hello, > > I have developed a package to assist developers managing their halts and > breakpoints: HaltManager. > > HaltManager provides a window showing all the breakpoints and halt messages > of the system, and allows one to toggle them on/off with a simple click. > Halt messages can also be toggled via source code rewriting. The > deactivation/reactivation feature is available in all code browsers, not > only in the HaltManager window. > > It is available here, with installation instructions and pictures: > https://github.com/dupriezt/HaltManager > > Feedback welcome. > > Cheers, > Thomas Dupriez > >

Dec. 7, 2017

Re: [Pharo-dev] ANN: Pharo6.1 new release (I do not remember how this subject was)

by Stephane Ducasse

Tx esteban Stef On Wed, Dec 6, 2017 at 5:33 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > So, I made a couple of changes: > > 20784 update Metacello since last update failed > https://pharo.fogbugz.com/f/cases/20784 > > and from a previous integration: > > 20176 Error in ByteArray>>booleanAt: > https://pharo.fogbugz.com/f/cases/20176 > > 20762 Pharo 6.1 has `pharo6.0.x` platform attribute instead of `pharo6.1.x` > https://pharo.fogbugz.com/f/cases/20762 > > 20103 Minor glitch in source code diff tool > https://pharo.fogbugz.com/f/cases/20103 > > > So, the recent problems should be fixed. Now I can backport iceberg 0.6.4 :) > > cheers! > Esteban

Dec. 7, 2017

Re: [Pharo-dev] Is Pharo spying on me?

by Stephane Ducasse

Now people can load shoreLine. We want to make sure that we lower the load. I would like for example to have the excellent tool of yuriy to understand variables of RB pattern matcher in the image. Stef On Wed, Dec 6, 2017 at 6:49 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > On Wed, Dec 6, 2017 at 10:50 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: >> >> ShoreLIne is already removed from Pharo 7 >> >> -- Pavel > > > Good to know since I've just started using it. :)

Dec. 7, 2017