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

Re: [Pharo-dev] Two tables that share the same data source!?

by Stephane Ducasse

Hi Elhamer where can we find the code of the improvements you did on FastTable? Stef On Tue, Aug 8, 2017 at 2:42 AM, Elhamer <abdelkhalekdev(a)gmail.com> wrote: > Hi Alex and thank you for your reply :)) > > Good to know that bloc already supports that, I am definitely moving to work > on/with it after that :)) > > I've never encounter that scenario on a a Pharo package too, but since i was > working on improving FTs, i thought why not!, besides, in apps with multiple > tables, it might be handy to define a single large data source and assign > columns to each table instead of defining a ds for each table, something > like that: > > ```` > |pane table1 table2 ds| > ds:=FTCellSampleDataSource new:10. > table1 := FTTableMorph new > extent: 500@500; > selectionMode: #column; > addColumn: (FTColumn id: 'column1'); > addColumn: (FTColumn id: 'column2'); > addColumn: (FTColumn id: 'column6'); > dataSource: ds; > selectRowIndex: 1; > showFirstRowSelection; > beMultipleSelection; > yourself. > table2 := FTTableMorph new > extent: 500@500; > selectionMode: #column; > addColumn: (FTColumn id: 'column3'); > addColumn: (FTColumn id: 'column4'); > addColumn: (FTColumn id: 'column5'); > dataSource: ds; > selectRowIndex: 1; > showFirstRowSelection; > beMultipleSelection; > layoutInset: 10; > yourself. > pane := Morph new. > pane layoutPolicy: TableLayout new. > pane listDirection: #leftToRight. > pane listCentering: #center. > pane wrapCentering: #center. > pane hResizing: #spaceFill. > pane layoutInset: 10@10. > pane cellInset:10@10. > pane color: Color red. > > pane addMorph: table1. > pane addMorph: table2. > pane openInWindow . > > ``` > <http://forum.world.st/file/n4959160/two_tables_single_ds.png> > > > > > -- > View this message in context: http://forum.world.st/Two-tables-that-share-the-same-data-source-tp4959153p… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Dec. 9, 2017

metalink injection into closures ?

by Ben Coman

When we execute this... counter "Greeter new counter" | count | count := 0. [100 timesRepeat: [count := count + 1. self inform: count + 1 printString. 2 seconds wait]] forkNamed: 'Count de Money' and in the dubgger correct and save the code we normally get the message... "Method for block not found on stack, can't edit and continue." and I wonder if anything with Metalinks would facilitate inject the corrected bytecode into the Process so that it oculd continue. cheers -ben

Dec. 9, 2017

About margin and 16969

by Stephane Ducasse

Hi henrik I started to rescue your fix on wrong use of rectangle. Then I noticed that you change the height of a margin. We defined it as height ^ self bottom + self top Since we were considering that the height of a margin is the total amount of space around. and you as height ^ self bottom - self top Do you have a strong reason for that? Stef

Dec. 9, 2017

Re: [Pharo-dev] [Moose-dev] [ann] gtmondrian

by StÃ©phane Ducasse

Super super cool. > On 9 Dec 2017, at 08:14, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > We are happy to announce GT Mondrian, a graph visualization engine built on top of Bloc. > > It is similar to the original Mondrian and the Mondrian from Roassal, but it is different in that it is built directly out of Bloc elements. This is interesting because it allows us to combine typical widgets with visualizations. The other interesting thing about it is that it validates the design of Bloc: right now, the implementation has 509 lines of code (excluding graph-specific layouts). The goal is to make visualization a first class citizen and an integral part of the IDE. > > The key ingredient that made this happen is that Bloc can now treat graph layouts, such as tree or force based, behave under the same rules as typical widget layouts, such as grid or flow. The challenge comes from the fact that a graph layout depends on the notion of edges between elements, and we did not want to have elements know about edges in the core of Bloc. > > The solution was to split the typical edge implementation in graph visualization libraries into two distinct concepts: > â¢ Line is an element that draws the connections. > â¢ Edge defines constraints imposed by connections between elements. Can you give an example? BTW doru did you think about having a bloc layer on top of telescope model? Because from that perspective telescope offers a visualisation model while roassal/mondrian like design are more a pen-oriented metaphor. I wanted to do it to learn Bloc but Iâm running against time and trying to flush pilling duties (I want to also release the book that we wrote with luc and olivier and convert the seaside book and and andâ¦.. :( > > Thus, edges form constraints, and constraints are what layouts deal with. That is one reason why elements in bloc have the ability of defining layout-specific constraints. Using this, we can nicely define edges between elements as a plugin to Bloc, but still be able to connect arbitrary elements. What's more, it turns out that we need constraints for other layouts as well. For example, an element in a grid layout might specify the span. > > The API of GT Mondrian is similar to the one from Roassal, but there are a few differences as well. These are described in the Pillar documentation available in the GitHub repo. > > The best way to experience GT Mondrian and its documentation is to load the GToolkit as described here: > https://github.com/feenkcom/gtoolkit <https://github.com/feenkcom/gtoolkit> > > If you download the GT code through Iceberg, the documentation can be experienced live by inspecting: > './pharo-local/iceberg/feenkcom/gtoolkit-visualizer/doc/mondrian/index.pillar' asFileReference > > > <mondrian-doc.png> > > > > > > Cheers, > The feenk team > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > www.feenk.com > > "Quality cannot be an afterthought." > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Dec. 9, 2017

[ann] gtmondrian

by Tudor Girba

Hi, We are happy to announce GT Mondrian, a graph visualization engine built on top of Bloc. It is similar to the original Mondrian and the Mondrian from Roassal, but it is different in that it is built directly out of Bloc elements. This is interesting because it allows us to combine typical widgets with visualizations. The other interesting thing about it is that it validates the design of Bloc: right now, the implementation has 509 lines of code (excluding graph-specific layouts). The goal is to make visualization a first class citizen and an integral part of the IDE. The key ingredient that made this happen is that Bloc can now treat graph layouts, such as tree or force based, behave under the same rules as typical widget layouts, such as grid or flow. The challenge comes from the fact that a graph layout depends on the notion of edges between elements, and we did not want to have elements know about edges in the core of Bloc. The solution was to split the typical edge implementation in graph visualization libraries into two distinct concepts: â¢ Line is an element that draws the connections. â¢ Edge defines constraints imposed by connections between elements. Thus, edges form constraints, and constraints are what layouts deal with. That is one reason why elements in bloc have the ability of defining layout-specific constraints. Using this, we can nicely define edges between elements as a plugin to Bloc, but still be able to connect arbitrary elements. What's more, it turns out that we need constraints for other layouts as well. For example, an element in a grid layout might specify the span. The API of GT Mondrian is similar to the one from Roassal, but there are a few differences as well. These are described in the Pillar documentation available in the GitHub repo. The best way to experience GT Mondrian and its documentation is to load the GToolkit as described here: https://github.com/feenkcom/gtoolkit If you download the GT code through Iceberg, the documentation can be experienced live by inspecting: './pharo-local/iceberg/feenkcom/gtoolkit-visualizer/doc/mondrian/index.pillar' asFileReference Cheers, The feenk team -- www.tudorgirba.com www.feenk.com "Quality cannot be an afterthought."

Dec. 9, 2017

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

by Stephane Ducasse

Ok I see quite sophisticated. I did not have the time to check. Did you explain this in the class comments? Tx thomas. On Fri, Dec 8, 2017 at 10:57 AM, Thomas Dupriez <thomas.dupriez(a)ens-paris-saclay.fr> wrote: > HaltManager proposes the deactivation by metalink even on self halt because > you may want to deactivate the halt without changing the source code and > completely recompiling the method. > > Thomas > > > Le 07/12/2017 Ã 21:00, Stephane Ducasse a Ã©crit : >> >> 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. 9, 2017

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

by Norbert Hartl

> Am 08.12.2017 um 21:24 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > Hi Stef, > > Do you get the debugger issue even in a plain Pharo image? > I do Norbert > Doru > > >> On Dec 8, 2017, at 3:40 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> I would love to have Ctrl E and Ctrl A. >> And yes we should not be different for the sake of it. >> For the moment the reason is simple: we are full of work and even more. >> >> FYI: I'm starting at regular crash of the VM and regular superbad >> behavior of the debugger (like hundred of debuggers, like spawing many >> process) >> there is a really bad problem there. >> >> Setf >> >>> On Fri, Dec 8, 2017 at 10:52 AM, Ben Coman <btc(a)openinworld.com> wrote: >>> >>> >>>> 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 >>> >>> >> > > -- > www.tudorgirba.com > www.feenk.com > > "Don't give to get. Just give."

Dec. 9, 2017

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

by Tudor Girba

Hi Stef, Do you get the debugger issue even in a plain Pharo image? Doru > On Dec 8, 2017, at 3:40 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > I would love to have Ctrl E and Ctrl A. > And yes we should not be different for the sake of it. > For the moment the reason is simple: we are full of work and even more. > > FYI: I'm starting at regular crash of the VM and regular superbad > behavior of the debugger (like hundred of debuggers, like spawing many > process) > there is a really bad problem there. > > Setf > > On Fri, Dec 8, 2017 at 10:52 AM, Ben Coman <btc(a)openinworld.com> wrote: >> >> >> 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 >> >> > -- www.tudorgirba.com www.feenk.com "Don't give to get. Just give."

Dec. 8, 2017

[Pharo 7.0-dev] Build #373: 20713 Cleanup RBRefactoringChangeTests

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

There is a new Pharo build available! The status of the build #373 was: SUCCESS. The Pull Request #594 was integrated: "20713 Cleanup RBRefactoringChangeTests" Pull request url: https://github.com/pharo-project/pharo/pull/594 Issue Url: https://pharo.fogbugz.com/f/cases/20713 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 8, 2017

[Pharo 7.0-dev] Build #372: 20842-create-clear-image-entry-point-

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

There is a new Pharo build available! The status of the build #372 was: SUCCESS. The Pull Request #592 was integrated: "20842-create-clear-image-entry-point-" Pull request url: https://github.com/pharo-project/pharo/pull/592 Issue Url: https://pharo.fogbugz.com/f/cases/20842 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 Norbert Hartl

> Am 08.12.2017 um 14:21 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > Hi monty > > >> On Fri, Dec 8, 2017 at 9:03 AM, monty <monty2(a)programmer.net> wrote: >> By "empty XML nodes," do you mean whitespace-only string nodes? > > Yes > >> Those are included because all in-element whitespace is assumed significant by the spec: https://www.w3.org/TR/xml/#sec-white-space > > I know. There was a discussion a while ago. I just lost a couple of > hours understanding that :( > > But this is a super super super annoying practices. > We had to test each nodes to see if it is a empty nodes so it makes > everything a lot more complex without real justification > beside the fact that these standardizers probably never implemented > some real cases. > This standard is a really out of reality from that perspective. Are you sure you do not oversimplify things? XML would be even more complex if these cases would be in the standard. It is not easy to decide if a whitespace is important or not. Where do this whitespaces in your case come from? Most probably because the XML is pretty printed. That is inserting whitespaces into the serialized text. So why not just stopping to pretty print and your problem is gone. Norbert > >> 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 > > Well the XML files that I had (I did not choose XML because I would > have prefer JSON :) ), had no DTD :( > > So at the end of the day, this wonderful standard puts all the stress > and burden to people. > >> >> 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. > > It would be A HUGE PLUS!!!!!!!!!!!!!!!!!! > > > Because reality is that people have XML files with just nodes and no > empty nodes and they are forced to > Let me know because I could try. > > I was showing how to use Pharo to import code to pharo learners and > this was a big drag. > > Stef > > > I tried to set some values in the parser but it did not work. > BTW I saw that the configuration logic forces to write the following > > | parser doc visitor | > parser := XMLDOMParser new > on: self xmlContents; > preservesIgnorableWhitespace: true. > > and not > > | parser doc visitor | > parser := XMLDOMParser new > preservesIgnorableWhitespace: true. > on: self xmlContents; > > >> >>> 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] Text Indentation in Pharo editor

by Stephane Ducasse

I would love to have Ctrl E and Ctrl A. And yes we should not be different for the sake of it. For the moment the reason is simple: we are full of work and even more. FYI: I'm starting at regular crash of the VM and regular superbad behavior of the debugger (like hundred of debuggers, like spawing many process) there is a really bad problem there. Setf On Fri, Dec 8, 2017 at 10:52 AM, Ben Coman <btc(a)openinworld.com> wrote: > > > 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

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

by Stephane Ducasse

Hi monty On Fri, Dec 8, 2017 at 9:03 AM, monty <monty2(a)programmer.net> wrote: > By "empty XML nodes," do you mean whitespace-only string nodes? Yes > Those are included because all in-element whitespace is assumed significant by the spec: https://www.w3.org/TR/xml/#sec-white-space I know. There was a discussion a while ago. I just lost a couple of hours understanding that :( But this is a super super super annoying practices. We had to test each nodes to see if it is a empty nodes so it makes everything a lot more complex without real justification beside the fact that these standardizers probably never implemented some real cases. This standard is a really out of reality from that perspective. > 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 Well the XML files that I had (I did not choose XML because I would have prefer JSON :) ), had no DTD :( So at the end of the day, this wonderful standard puts all the stress and burden to people. > > 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. It would be A HUGE PLUS!!!!!!!!!!!!!!!!!! Because reality is that people have XML files with just nodes and no empty nodes and they are forced to Let me know because I could try. I was showing how to use Pharo to import code to pharo learners and this was a big drag. Stef I tried to set some values in the parser but it did not work. BTW I saw that the configuration logic forces to write the following | parser doc visitor | parser := XMLDOMParser new on: self xmlContents; preservesIgnorableWhitespace: true. and not | parser doc visitor | parser := XMLDOMParser new preservesIgnorableWhitespace: true. on: self xmlContents; > >> 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

[Pharo 7.0-dev] Build #371: 20734-Nested-Structures-using-Platform-longs-fails

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

There is a new Pharo build available! The status of the build #371 was: SUCCESS. The Pull Request #519 was integrated: "20734-Nested-Structures-using-Platform-longs-fails" Pull request url: https://github.com/pharo-project/pharo/pull/519 Issue Url: https://pharo.fogbugz.com/f/cases/20734 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 8, 2017

Report period: 24 November 2017 to 8 December 2017

by Stephane Ducasse

Report period: 24 November 2017 to 8 December 2017 * 20734-Nested-Structures-using-Platform-longs-fails >> Adding implementation of platform dependent longs in FFIExternalStructureReferenceHandle. >> >> Fixes https://pharo.fogbugz.com/f/cases/20734/Nested-Structures-using-Platform-lo… Issue URL: https://pharo.fogbugz.com/f/cases/20734 PR URL: https://github.com/pharo-project/pharo/pull/519 Diff URL: https://github.com/pharo-project/pharo/pull/519/files Thanks to tesonep * 20847 Super setUp need to be called in various test classes (Part 2) >> - call super setUp in HiNodesAndLinksIteratorWithOneLinkModelTest >> - call super setUp in GuideTest >> - call super setUp in SMTPClientTest >> - call super setUp in SocketStreamTest >> - call super setUp in SocketTest >> - call super setUp in ZipArchiveTest >> - call super setUp in TonelRepositoryTest >> - call super setUp in SlotMethodRecompilationTest >> - call super setUp in SmalllintManifestCheckerTest >> - call super setUp in OmSessionStoreNameStrategyTest >> - call super setUp in PharoBootstrapRuleTest >> - call super setUp in PharoIssueTest >> - call super setUp in PharoTutorialTestGoOnMockTutorial >> - call super setUp in PharoTutorialTestNavigation >> - call super setUp in UUIDGeneratorTest >> - call super setUp in TestObjectsAsMethods >> - call super setUp in TutorialPlayerTestWithMockTutorial >> - call super setUp in PNGReadWriterTest >> - call super setUp in PragmaTest >> - call super setUP in QuotedPrintableMimeConverterTest >> - call super setUP in RandomTest >> - call super setUP in RectangleTest >> - call super setUP in RecursionStopperTest >> - call super setUp in ResumableTestFailureTestCase >> - call super setUp in MTDependencyTest >> - call super setUp in MTDevelopmentWorkfowTestWithXMLParser >> - call super setUp in NautilusTest >> - call super setUp in NautilusUITest >> - call super setUp in SimpleTestResourceTestCase >> - call super setUp in SUnitTest >> - call super setUp in SimpleTestResource >> - call super setUp in GTDebuggerSmokeTest >> - call super setUp in GTPlaygroundBasicTest >> - call super setUp in GTSpotterCandidatesListTest >> - call super setUp in ZdcPluginSSLSessionTest >> - call super setUp in ZnStaticFileServerDelegateTests >> - call super setUp in ZnStaticFileServerDelegateTests >> - call super setUp in GLMAnnouncementPropagationTest >> - call super setUp in GLMAnnouncerTest >> - call super setUp in GLMExplicitBrowserCopyTest >> - call super setUp in GLMPagerModelTest >> - call super setUp in GLMUpdateMorphicTest >> - call super setUp in GLMPagerMorphTest >> >> https://pharo.fogbugz.com/f/cases/20847/Super-setUp-need-to-be-called-in-va… Issue URL: https://pharo.fogbugz.com/f/cases/20847 Super setUp need to be called in various test classes (Part 2) PR URL: https://github.com/pharo-project/pharo/pull/593 Diff URL: https://github.com/pharo-project/pharo/pull/593/files Thanks to astares * 20840 Super setUp need to be called in various test classes (Part 1) >> - call super setUp in AbstractNautilusUITest >> - call super setUp in AndreasSystemProfilerTest >> - call super setUp in ArrayTest >> - call super setUp in AssociationTest >> - call super setUp in ASTCacheResetTest >> - call super setUp in BagTest >> - call super setUp in Base64MimeConverterTest >> - call super setUp in BuilderManifestTest >> - call super setUp in CairoUTF8ConverterTest >> - call super setUp in ChangesBrowserTest >> - call super setUp in ChangeSetClassChangesTest >> - call super setUp in ClassRenameFixTest >> - call super setUp in ClassTest >> - call super setUp in TraitsResource >> - call super setUp in CollectionValueHolderTest >> - call super setUp in CommandLineArgumentsTest >> - call super setUp in CopyVisitorTest >> - call super setUp in FreeTypeCacheTest >> - call super setUp in HashAndEqualsTestCase >> - call super setUp in HeapTest >> - call super setUp in SortedCollectionTest >> - call super setUp in SortHierarchicallyTest >> - call super setUp in SetTest >> - call super setUp in StackTest >> - call super setUp in StringTest >> - call super setUp in SymbolTest >> - call super setUp in FloatArrayTest >> - call super setUp in SHStyleElementTest >> - call super setUp in HistoryIteratorTest >> - call super setUp in IntervalTest >> - call super setUp in OrderedCollectionTest >> - call super setUp in LazyTabGroupTest >> - call super setUp in MatrixTest >> - call super setUp in RPackageTestCase >> - call super setUp in ScheduleTest >> - call super setUp in SendsDeprecatedMethodToGlobalRuleTest >> - call super setUp in MorphTest >> - call super setUp in MorphicEventHandlerTest >> - call super setUp in MorphicAdapterTest >> - call super setUp in MorphicUIBugTest >> - call super setUp in CircleMorphTest Issue URL: https://pharo.fogbugz.com/f/cases/20840 Super setUp need to be called in various test classes (Part 1) PR URL: https://github.com/pharo-project/pharo/pull/590 Diff URL: https://github.com/pharo-project/pharo/pull/590/files Thanks to astares * 20838 Super setUp need to be called in System-SessionManager package tests >> - call super setUp in SessionErrorHandlingTest >> - call super setUp in SessionManagerRegistrationTest >> - call super setUp in SessionManagerUnregistrationTest >> >> https://pharo.fogbugz.com/f/cases/20838/Super-setUp-need-to-be-called-in-Sy… Issue URL: https://pharo.fogbugz.com/f/cases/20838 Super setUp need to be called in System PR URL: https://github.com/pharo-project/pharo/pull/588 Diff URL: https://github.com/pharo-project/pharo/pull/588/files Thanks to astares * 20839 Super setUp need to be called in NECompletion-Tests >> - call super setUp in NECControllerTest >> - call super setUp in NECOverrideModelTest >> - call super setUp in NECUntypedModelTest >> >> https://pharo.fogbugz.com/f/cases/20839/ Issue URL: https://pharo.fogbugz.com/f/cases/20839 Super setUp need to be called in NECompletion PR URL: https://github.com/pharo-project/pharo/pull/589 Diff URL: https://github.com/pharo-project/pharo/pull/589/files Thanks to astares * 20826 Super setup need to be called in DependencyAnalyser tests >> - call super setUp in DADependencyCheckerTest >> - call super setUp in DAMessageSendAnalyzerTest >> - call super setUp in DAPackageCycleDetectorTest (with some formatting cleanups in setUp) >> - call super setUp in DAPackageCycleTest >> - call super setUp in DAPackageDependencyTest >> - call super setUp in DAPackageDependencyWrapperTest >> - call super setUp in DAPackageRelationGraphDiffTest >> - call super setUp in DAPackageRelationGraphTest (with some formatting cleanups in setUp) >> - call super setUp in DAPackageTest (with some formatting cleanups in setUp) >> - call super setUp in DATarjanAlgorithmTest (with some formatting cleanups in setUp) >> Also add some tags to to better categorize the test classes in package "Tool-Dependency-Analyse-Test" Issue URL: https://pharo.fogbugz.com/f/cases/20826 Super setup need to be called in DependencyAnalyser tests PR URL: https://github.com/pharo-project/pharo/pull/579 Diff URL: https://github.com/pharo-project/pharo/pull/579/files Thanks to astares * 20791-World-menu-help-not-shown-in-the-menu >> Set balloonText after the spec's help. Issue URL: https://pharo.fogbugz.com/f/cases/20791 PR URL: https://github.com/pharo-project/pharo/pull/575 Diff URL: https://github.com/pharo-project/pharo/pull/575/files Thanks to luque * 20830 Super setup need to be called in Monticello tests and other cleanups (comments, tags) >> - call super setUp in MCChangeNotificationTest >> - call super setUp in MCClassDefinitionTest >> - call super setUp in MCDictionaryRepositoryTest >> - call super setUp in MCDirectoryRepositoryTest >> - call super setUp in MCFileInTest >> - call super setUp in MCMczInstallerTest >> - call super setUp in MCMethodDefinitionTest >> - call super setUp in MCPatchTest >> - call super setUp in MCSnapshotBrowserTest >> - call super setUp in MCSnapshotTest >> - call super setUp in MCStWriterTest >> - call super setUp in MCVersionTest >> - call super setUp in MCSnapshotResource (test resource) >> >> - categorize the three test methods in MCPackageManagerTest >> - Add a comment to uncommented MCTestCase >> - Add a comment to uncommented MCRepositoryTest >> - Add a comment to uncommented MCSnapshotResource >> - Add a comment to uncommented MCMockDependency >> >> - add some tags to structure the many test classes in the package better >> >> >> https://pharo.fogbugz.com/f/cases/20830/Super-setup-need-to-be-called-in-Mo… Issue URL: https://pharo.fogbugz.com/f/cases/20830 Super setup need to be called in Monticello tests and other cleanups (comments, tags) PR URL: https://github.com/pharo-project/pharo/pull/583 Diff URL: https://github.com/pharo-project/pharo/pull/583/files Thanks to astares * 20816 Typo in DateAndTimeEpochTest and DateAndTimeUnixEpochTest tearDown >> fix typo >> >> https://pharo.fogbugz.com/f/cases/20816/Typo-in-DateAndTimeEpochTest-and-Da… Issue URL: https://pharo.fogbugz.com/f/cases/20816 Typo in DateAndTimeEpochTest and DateAndTimeUnixEpochTest tearDown PR URL: https://github.com/pharo-project/pharo/pull/572 Diff URL: https://github.com/pharo-project/pharo/pull/572/files Thanks to astares * 20822 Cleanup AbstractKeymappingTest >> - override #isAbstract as it is an abstract test superclass >> - call super setUp >> - call super tearDown >> - set default to nil in tearDown to avoid further referencing Issue URL: https://pharo.fogbugz.com/f/cases/20822 Cleanup AbstractKeymappingTest PR URL: https://github.com/pharo-project/pharo/pull/577 Diff URL: https://github.com/pharo-project/pharo/pull/577/files Thanks to astares * 20820 Better formatting of TestSuite setUp >> - one blank instead of two >> - format to be more readable >> >> https://pharo.fogbugz.com/f/cases/20820/Better-formatting-of-TestSuite-setUp Issue URL: https://pharo.fogbugz.com/f/cases/20820 Better formatting of TestSuite setUp PR URL: https://github.com/pharo-project/pharo/pull/574 Diff URL: https://github.com/pharo-project/pharo/pull/574/files Thanks to astares * 20825 Super setUp need to be called in Opal Compiler tests >> - call super setUp in OCBytecodeDecompilerTest >> - call super setUp in OCClosureCompilerTest >> - call super setUp in OCCompilerExceptionTest >> - call super setUp in OCCompilerNotifyingTest >> - call super setUp in OCCompilerTest Issue URL: https://pharo.fogbugz.com/f/cases/20825 Super setUp need to be called in Opal Compiler tests PR URL: https://github.com/pharo-project/pharo/pull/578 Diff URL: https://github.com/pharo-project/pharo/pull/578/files Thanks to astares * 20819 Fix variable assignment in RBScanner>>stripComment >> https://pharo.fogbugz.com/f/cases/20819/Fix-variable-assignment-in-RBScanne… Issue URL: https://pharo.fogbugz.com/f/cases/20819 Fix variable assignment in RBScanner>>stripComment PR URL: https://github.com/pharo-project/pharo/pull/573 Diff URL: https://github.com/pharo-project/pharo/pull/573/files Thanks to astares * Fix potential dangling reference to a released FT_Face >> This is issue https://pharo.fogbugz.com/f/cases/20776/Potential-dangling-ref-to-freed-FT_… >> >> Technical details: >> >> A cairo_font_face could still be referenced from external heap and further used. >> Thus we must NOT release the FT_Face until the external reference count drops to 1. >> >> Thus the CairoFontFace is not a good place for retaining a strong reference to the FT2Face, because the reference will vanish as soon as the Smalltalk object is garbage collected, while some external cairo_font_face still point on it. >> It's better to have the strong reference in the executor, and avoid garbageCollecting the executor while there are external references to the resource data... >> >> The solution is to use a specific CairoFontFaceExecutor. >> If the resource is shared, then we have no other choice than regularly polling the ref count in a new Process. >> This process must stop whenever the session change. >> >> Please review carefully and pass some tests. Issue URL: https://pharo.fogbugz.com/f/cases/Fix potential dangling reference to a released FT_Face PR URL: https://github.com/pharo-project/pharo/pull/565 Diff URL: https://github.com/pharo-project/pharo/pull/565/files Thanks to nicolas-cellier-aka-nice * 20821 Remove unused ivar from RBKeywordToken and RBIdentifierToken >> Remove >> - unused ivar stopPosition in RBIdentifierToken and >> - unused ivar stopPosition in RBKeywordToken >> >> https://pharo.fogbugz.com/f/cases/20821/Remove-unused-ivar-from-RBKeywordTo… Issue URL: https://pharo.fogbugz.com/f/cases/20821 Remove unused ivar from RBKeywordToken and RBIdentifierToken PR URL: https://github.com/pharo-project/pharo/pull/576 Diff URL: https://github.com/pharo-project/pharo/pull/576/files Thanks to astares * 20828 Super setup need to be called in Versionner tests >> - call super setUp in MBAbstractTest >> - call super setUp in MBPackageInfoTest >> >> https://pharo.fogbugz.com/f/cases/20828/Super-setup-need-to-be-called-in-Ve… Issue URL: https://pharo.fogbugz.com/f/cases/20828 Super setup need to be called in Versionner tests PR URL: https://github.com/pharo-project/pharo/pull/581 Diff URL: https://github.com/pharo-project/pharo/pull/581/files Thanks to astares * 20829 Super setup need to be called in Spec tests >> - call super setUp in MorphicLabelAdapterTest >> - call super setUp in MorphicTreeAdapterTest >> - call super setUp in SpecInterpreterTest >> - call super setUp in SpecTestCase >> >> https://pharo.fogbugz.com/f/cases/20829/Super-setup-need-to-be-called-in-Sp… Issue URL: https://pharo.fogbugz.com/f/cases/20829 Super setup need to be called in Spec tests PR URL: https://github.com/pharo-project/pharo/pull/582 Diff URL: https://github.com/pharo-project/pharo/pull/582/files Thanks to astares * 20827 Super setUp need to be called RBParseTreeRewriterTest and RBParseTreeSearcherTest >> - call super setUp in RBParseTreeRewriterTest >> - call super setUp in RBParseTreeSearcherTest Issue URL: https://pharo.fogbugz.com/f/cases/20827 Super setUp need to be called RBParseTreeRewriterTest and RBParseTreeSearcherTest PR URL: https://github.com/pharo-project/pharo/pull/580 Diff URL: https://github.com/pharo-project/pharo/pull/580/files Thanks to astares * 20814 Add release check that we have no protocols left without methods >> Check that we have no protocols left without methods >> >> https://pharo.fogbugz.com/f/cases/20814/Add-release-check-that-we-have-no-p… Issue URL: https://pharo.fogbugz.com/f/cases/20814 Add release check that we have no protocols left without methods PR URL: https://github.com/pharo-project/pharo/pull/570 Diff URL: https://github.com/pharo-project/pharo/pull/570/files Thanks to astares * 20815 Add a release test ensuring that there are no empty packages in the i >> Add a release test ensuring that there are no empty packages in the image left >> >> https://pharo.fogbugz.com/f/cases/20815/Release-check-so-that-we-have-no-em… Issue URL: https://pharo.fogbugz.com/f/cases/20815 Add a release test ensuring that there are no empty packages in the i PR URL: https://github.com/pharo-project/pharo/pull/571 Diff URL: https://github.com/pharo-project/pharo/pull/571/files Thanks to astares * 20786-halt-messages-are-not-highlighted-in-red-as-the-other-flavours-of-halt-messages >> Added haltIfNil to the selectors to be highlighted by HaltIconStyler. >> Changed the structure of the shouldStyleNode method's code to increase clarity. Issue URL: https://pharo.fogbugz.com/f/cases/20786 PR URL: https://github.com/pharo-project/pharo/pull/569 Diff URL: https://github.com/pharo-project/pharo/pull/569/files Thanks to dupriezt * 20781-update-to-iceberg-064 >> closes issue #20781 Issue URL: https://pharo.fogbugz.com/f/cases/20781 PR URL: https://github.com/pharo-project/pharo/pull/560 Diff URL: https://github.com/pharo-project/pharo/pull/560/files Thanks to estebanlm * 20793-During-Bootstrap-if-a-baseline-installation-fails-it-should-cancel-the-process >> This PR introduces two changes to handle the errors during the bootstrap: >> >> 1. The Whole process now has a timeout of 60 minutes. >> 2. After initializing the world in BaselineOfMorphic the UIManager is restored to the correct UIManager depending the system state. If it is headless then the NonInteractiveManager is used, otherwise the MorphicUIManager. Issue URL: https://pharo.fogbugz.com/f/cases/20793 PR URL: https://github.com/pharo-project/pharo/pull/567 Diff URL: https://github.com/pharo-project/pharo/pull/567/files Thanks to tesonep * 20800-do-not-open-welcome-window-for-now >> https://pharo.fogbugz.com/f/cases/20800/do-not-open-welcome-window-for-now >> >> do not open the welcome window Issue URL: https://pharo.fogbugz.com/f/cases/20800 PR URL: https://github.com/pharo-project/pharo/pull/568 Diff URL: https://github.com/pharo-project/pharo/pull/568/files Thanks to pavel-krivanek * 20786-halt-messages-are-not-highlighted-in-red-as-the-other-flavours-of-halt-messages >> Created HaltColonIconStylerClass, to style `halt:` message nodes with red highlighting in code browsers. Issue URL: https://pharo.fogbugz.com/f/cases/20786 PR URL: https://github.com/pharo-project/pharo/pull/564 Diff URL: https://github.com/pharo-project/pharo/pull/564/files Thanks to dupriezt * 20782-CompiledCode-misses-an-abstract-sourcePointer-method >> introduced CompiledCode>>sourcePointer as an abstract method Issue URL: https://pharo.fogbugz.com/f/cases/20782 PR URL: https://github.com/pharo-project/pharo/pull/561 Diff URL: https://github.com/pharo-project/pharo/pull/561/files Thanks to LucFabresse * -20785/Fix-the-names-of-uploaded-bootstrap-zip-files >> https://pharo.fogbugz.com/f/cases/20785/Fix-the-names-of-uploaded-bootstrap… Issue URL: https://pharo.fogbugz.com/f/cases/ PR URL: https://github.com/pharo-project/pharo/pull/563 Diff URL: https://github.com/pharo-project/pharo/pull/563/files Thanks to pavel-krivanek * 20783-upload-temporary-building-files-into-a-separate-repository >> https://pharo.fogbugz.com/f/cases/20783/upload-temporary-building-files-int… Issue URL: https://pharo.fogbugz.com/f/cases/20783 PR URL: https://github.com/pharo-project/pharo/pull/562 Diff URL: https://github.com/pharo-project/pharo/pull/562/files Thanks to pavel-krivanek * 20777-Fix-instVarAt-instVarAt-put-comment >> https://pharo.fogbugz.com/f/cases/20777/Fix-instVarAt-instVarAt-put-comment >> >> http://forum.world.st/Problem-with-primitive-instVarAt-instVarAt-put-what-s… Issue URL: https://pharo.fogbugz.com/f/cases/20777 PR URL: https://github.com/pharo-project/pharo/pull/559 Diff URL: https://github.com/pharo-project/pharo/pull/559/files Thanks to clementbera * 20772 - Unused temps in MBConfigurationInfo, MethodDictionaryTest,... >> Fix unused temps in >> >> MethodDictionaryTest>>#testIdentityKeyAtNonExistantValueReturnsFailBlock >> MBConfigurationInfo>>#buildStringOrText >> MBPackageInfo>>#versions >> MCFileTreeRepository class>>#parseName:extension: >> MCWorkingCopyBrowser>>#addRepositoryToPackage >> MethodDictionaryTest>>#testGrowPreservesElements Issue URL: https://pharo.fogbugz.com/f/cases/20772 PR URL: https://github.com/pharo-project/pharo/pull/557 Diff URL: https://github.com/pharo-project/pharo/pull/557/files Thanks to astares * 20745-cleanup-unused-methods-OCOptimizedBlockScope >> cleanup unused methods OCOptimizedBlockScope >> >> https://pharo.fogbugz.com/f/cases/20745/cleanup-unused-methods-OCOptimizedB… Issue URL: https://pharo.fogbugz.com/f/cases/20745 PR URL: https://github.com/pharo-project/pharo/pull/556 Diff URL: https://github.com/pharo-project/pharo/pull/556/files Thanks to MarcusDenker * 20700-translateToUTC-does-not-work-on-Month-and-Year >> 20700 translateToUTC does not work on Month and Year >> >> Update Year>>starting:duration: and Month>>starting:duration: to keep the supplied DateAndTime's offset. >> >> Add automated tests to Year, Month and Week to confirm correct operation. Issue URL: https://pharo.fogbugz.com/f/cases/20700 PR URL: https://github.com/pharo-project/pharo/pull/545 Diff URL: https://github.com/pharo-project/pharo/pull/545/files Thanks to akgrant43 * 20770-Open-WelcomeHelp-window-at-startup >> https://pharo.fogbugz.com/f/cases/20770/Open-WelcomeHelp-window-at-startup >> >> open WelcomeHelp on startup Issue URL: https://pharo.fogbugz.com/f/cases/20770 PR URL: https://github.com/pharo-project/pharo/pull/555 Diff URL: https://github.com/pharo-project/pharo/pull/555/files Thanks to pavel-krivanek * 20769-DateAndTime-now-returns-summer-time-in-winter-France-time-zone >> https://pharo.fogbugz.com/f/cases/20769/DateAndTime-now-returns-summer-time… >> >> add missing startup list registrations Issue URL: https://pharo.fogbugz.com/f/cases/20769 PR URL: https://github.com/pharo-project/pharo/pull/553 Diff URL: https://github.com/pharo-project/pharo/pull/553/files Thanks to pavel-krivanek * 19304-anyOne-comment-should-be-improved >> https://pharo.fogbugz.com/f/cases/19304/ >> >> improve #anyOne comment Issue URL: https://pharo.fogbugz.com/f/cases/19304 PR URL: https://github.com/pharo-project/pharo/pull/552 Diff URL: https://github.com/pharo-project/pharo/pull/552/files Thanks to pavel-krivanek * 20768-remove-GLMWatcherMorphicTest >> https://pharo.fogbugz.com/f/cases/20768/remove-GLMWatcherMorphicTest >> >> remove GLMWatcherMorphicTest Issue URL: https://pharo.fogbugz.com/f/cases/20768 PR URL: https://github.com/pharo-project/pharo/pull/551 Diff URL: https://github.com/pharo-project/pharo/pull/551/files Thanks to pavel-krivanek * 20738 dictionarystore string generates incorrect source code when a negative number is in values Issue URL: https://pharo.fogbugz.com/f/cases/20738 dictionarystore string generates incorrect source code when a negative number is in values PR URL: https://github.com/pharo-project/pharo/pull/538 Diff URL: https://github.com/pharo-project/pharo/pull/538/files Thanks to juliendelplanque * 20767-Decrease-retry-times-for-failing-jobs >> https://pharo.fogbugz.com/f/cases/20767/Decrease-retry-times-for-failing-jo… Issue URL: https://pharo.fogbugz.com/f/cases/20767 PR URL: https://github.com/pharo-project/pharo/pull/550 Diff URL: https://github.com/pharo-project/pharo/pull/550/files Thanks to pavel-krivanek * 20758-Slot-should-have-explicit-property-definingClass2 >> definingClass is added to Slot. >> It is initialized in ClassDescription>>superclass:layout: >> SlotIntegrationTest>>testSlotsAreInitializedWithDefiningAnonimousClass covers that initialization is performed. >> >> https://pharo.fogbugz.com/f/cases/20758/Slot-should-have-explicit-property-… Issue URL: https://pharo.fogbugz.com/f/cases/20758 PR URL: https://github.com/pharo-project/pharo/pull/543 Diff URL: https://github.com/pharo-project/pharo/pull/543/files Thanks to dionisiydk * 20747-Date-comparisons-without-time-zone >> 20747 Date comparisons without time zone >> >> Add time zone independent comparisons to Date. Issue URL: https://pharo.fogbugz.com/f/cases/20747 PR URL: https://github.com/pharo-project/pharo/pull/544 Diff URL: https://github.com/pharo-project/pharo/pull/544/files Thanks to akgrant43 * 20766-Increase-priority-of-FreeType-initialization >> https://pharo.fogbugz.com/f/cases/20766/Increase-priority-of-FreeType-initi… >> >> increase priority of FreeType initialization Issue URL: https://pharo.fogbugz.com/f/cases/20766 PR URL: https://github.com/pharo-project/pharo/pull/548 Diff URL: https://github.com/pharo-project/pharo/pull/548/files Thanks to pavel-krivanek * 20699-Convenience-method-for-creating-typed-buffers-to-pass-by-ref-through-FFI- >> https://pharo.fogbugz.com/f/cases/20699/Convenience-method-for-creating-typ… Issue URL: https://pharo.fogbugz.com/f/cases/20699 PR URL: https://github.com/pharo-project/pharo/pull/508 Diff URL: https://github.com/pharo-project/pharo/pull/508/files Thanks to estebanlm * 20759 Unused temps in Metacello classes >> Fix unused temps >> >> MetacelloMCProjectSpec>>#determineCurrentVersionForLoad >> MetacelloToolBox class>>#defaultTopic:for: >> MetacelloToolBox>>#commitBaselineOfMethod >> MetacelloToolBox>>#commitMethod >> MetacelloToolBox>>#updateVersionMethodForVersion:projectAttributes:updateProjects:updatePackages:versionSpecsDo: >> MetacelloToolBoxConstructor>>#extractSymbolicVersionSpecsFor: >> MetacelloVersionSpec>>#configMethodOn:last:indent: >> MetacelloMCVersion>>#executeLoadFromArray: >> MetacelloMCVersionValidator>>#validateProjectVersionLoad:loads: >> MetacelloMemberListSpec>>#mergeSpec: >> MetacelloPackageSpec>>#currentPackageLoaded:notLoaded:using: >> MetacelloPackageSpec>>#mergeSpec: >> MetacelloProject>>#version: >> MetacelloScriptEngine>>#lookupProjectSpecFor: >> MetacelloSemanticVersionNumber class>>#fromString:forPattern: Issue URL: https://pharo.fogbugz.com/f/cases/20759 Unused temps in Metacello classes PR URL: https://github.com/pharo-project/pharo/pull/546 Diff URL: https://github.com/pharo-project/pharo/pull/546/files Thanks to astares * 20763 ExternalAddress>>finalize should be in finalization protocol >> Put finalize into finalization category to satisfy ProperMethodCategorizationTest >> >> https://pharo.fogbugz.com/f/cases/edit/20763/ExternalAddress-finalize-shoul… Issue URL: https://pharo.fogbugz.com/f/cases/20763 ExternalAddress>>finalize should be in finalization protocol PR URL: https://github.com/pharo-project/pharo/pull/547 Diff URL: https://github.com/pharo-project/pharo/pull/547/files Thanks to astares * 20061-Explicit-isAbstract-is-needed-instead-of-using-hasAbstractMethods-in-tools2 >> https://pharo.fogbugz.com/f/cases/20061/Explicit-isAbstract-is-needed-inste… >> >> Few things are done: >> - Behavior and friends define isAbstract method with optimized logic. >> It gives 50 milliseconds for the test: >> [50 timesRepeat: [ PluggableTextMorph isAbstract]] timeToRun. >> 50 items is much more then we able to see in browser class list. So it should not affect browser speed. >> - BehaviorTest>>testIsAbstract >> - CompiledMethod>>isAbstract is now take into account traits explicit and implicit requirement. >> - Nautilus uses #isAbstract instead of hasAbstractMethods to mark abstract classes Issue URL: https://pharo.fogbugz.com/f/cases/20061 PR URL: https://github.com/pharo-project/pharo/pull/541 Diff URL: https://github.com/pharo-project/pharo/pull/541/files Thanks to dionisiydk * 20740-Work-Needed-isAbstract-not-working-correctly-on-64bit >> Fixed markerOrNil to work on both bytecode sets for 64 bits and 32 bits. >> >> https://pharo.fogbugz.com/f/cases/20740 Issue URL: https://pharo.fogbugz.com/f/cases/20740 PR URL: https://github.com/pharo-project/pharo/pull/537 Diff URL: https://github.com/pharo-project/pharo/pull/537/files Thanks to clementbera * 20176-Error-in-ByteArraybooleanAt >> Fix ByteArray>>#booleanAt: to actually return true when the byte at the querried position in the ByteArray is a non-zero integer Issue URL: https://pharo.fogbugz.com/f/cases/20176 PR URL: https://github.com/pharo-project/pharo/pull/539 Diff URL: https://github.com/pharo-project/pharo/pull/539/files Thanks to dupriezt * 20756-Secondary-selections-are-dark-after-switch-to-the-white-theme-in-Pharo-7 >> https://pharo.fogbugz.com/f/cases/20756/Secondary-selections-are-dark-after… >> >> change default secondary selection color Issue URL: https://pharo.fogbugz.com/f/cases/20756 PR URL: https://github.com/pharo-project/pharo/pull/540 Diff URL: https://github.com/pharo-project/pharo/pull/540/files Thanks to pavel-krivanek * 20690-assertequals >> https://pharo.fogbugz.com/f/cases/20690/assert-equals >> >> - swap actual and experted sides in comparig inside assert:equals: >> - deprecate assert:descriptionBlock: Issue URL: https://pharo.fogbugz.com/f/cases/20690 PR URL: https://github.com/pharo-project/pharo/pull/533 Diff URL: https://github.com/pharo-project/pharo/pull/533/files Thanks to pavel-krivanek * 20729-Monticello-history-browser-should-enable-diffing-with-parent >> This is issue https://pharo.fogbugz.com/f/cases/20729/Monticello-history-browser-should-e… >> Such option is really handy when cherry picking changes from other branches >> Pick the implementation from Squeak (fbs, eem) and adapt to Pharo Issue URL: https://pharo.fogbugz.com/f/cases/20729 PR URL: https://github.com/pharo-project/pharo/pull/513 Diff URL: https://github.com/pharo-project/pharo/pull/513/files Thanks to nicolas-cellier-aka-nice

Dec. 8, 2017

[Pharo 7.0-dev] Build #370: 20847 Super setUp need to be called in various test classes (Part 2)

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

There is a new Pharo build available! The status of the build #370 was: SUCCESS. The Pull Request #593 was integrated: "20847 Super setUp need to be called in various test classes (Part 2)" Pull request url: https://github.com/pharo-project/pharo/pull/593 Issue Url: https://pharo.fogbugz.com/f/cases/20847 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 8, 2017

[Pharo 7.0-dev] Build #369: 20840 Super setUp need to be called in various test classes (Part 1)

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

There is a new Pharo build available! The status of the build #369 was: SUCCESS. The Pull Request #590 was integrated: "20840 Super setUp need to be called in various test classes (Part 1)" Pull request url: https://github.com/pharo-project/pharo/pull/590 Issue Url: https://pharo.fogbugz.com/f/cases/20840 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 8, 2017

[Pharo 7.0-dev] Build #368: 20838 Super setUp need to be called in System-SessionManager package tests

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

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

Dec. 8, 2017

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

by Marcus Denker

A note: It seems we do not get mails like this for all PR merges. E.g. yesterday I merged around 12 pull requests, but we got only 5 messages to the list. This seems to happen when merges happen very quicklyâ¦ to be analysed. Marcus > On 8 Dec 2017, at 10:42, ci-pharo-ci-jenkins2(a)inria.fr wrote: > > 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] Release: Conveniently browse, deactivate and reactivate halts and breakpoints with the HaltManager

by Thomas Dupriez

HaltManager proposes the deactivation by metalink even on self halt because you may want to deactivate the halt without changing the source code and completely recompiling the method. Thomas Le 07/12/2017 Ã 21:00, Stephane Ducasse a Ã©critÂ : > 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. 8, 2017

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

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

by Sean P. DeNigris

Pavel Krivanek-3 wrote > Ctrl + Shift + L or Ctrl + Shift + R Mac: Cmd + â¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 7, 2017

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

by Sean P. DeNigris

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

Dec. 7, 2017

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

by Pavel Krivanek

2017-12-07 16:19 GMT+01:00 Torsten Bergmann <astares(a)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

Text Indentation in Pharo editor

by Torsten Bergmann

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? 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

[Pharo 7.0-dev] Build #366: 20826 Super setup need to be called in DependencyAnalyser tests

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

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

Dec. 7, 2017

Re: [Pharo-dev] [Pharo-users] [TechTalk] Topics Wanted for 2018!

by Marcus Denker

What about Tuesday 30th Jan? > On 7 Dec 2017, at 02:06, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Hi Marcus! > > Thanks for pushing the community! > If there is a free slot at the end of January, I can do another tech talk on AI technique. I am thinking about a lecture on Genetic Algorithm and Genetic Programming. > > Let me know... > > Alexandre > > >> On Dec 1, 2017, at 7:58 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hi, >> >> As you know, we are trying to have one Pharo tech-talk per month. >> >> The idea is to use this for >> -> mini âLecturesâ >> -> Demos of interesting Projects >> -> Just some interesting topic to discuss with audio chat on Discord >> >> You can see the past topics here: >> >> http://pharo.org/TechTalk >> >> We will soon define the dates for the first half of 2018. If you want to do a techtalk >> yourself (give a presentation / Demo or moderate a discussion), feel free to contact >> me! You are able to pick a date that works best for you. >> >> >> Marcus > >

Dec. 7, 2017

[Pharo 7.0-dev] Build #365: 20830 Super setup need to be called in Monticello tests and other cleanups (comments, tags)

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

There is a new Pharo build available! The status of the build #365 was: SUCCESS. The Pull Request #583 was integrated: "20830 Super setup need to be called in Monticello tests and other cleanups (comments, tags)" Pull request url: https://github.com/pharo-project/pharo/pull/583 Issue Url: https://pharo.fogbugz.com/f/cases/20830 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 7, 2017

[Pharo 7.0-dev] Build #364: 20816 Typo in DateAndTimeEpochTest and DateAndTimeUnixEpochTest tearDown

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

There is a new Pharo build available! The status of the build #364 was: FAILURE. The Pull Request #572 was integrated: "20816 Typo in DateAndTimeEpochTest and DateAndTimeUnixEpochTest tearDown" Pull request url: https://github.com/pharo-project/pharo/pull/572 Issue Url: https://pharo.fogbugz.com/f/cases/20816 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 7, 2017

Re: [Pharo-dev] Running tests in MCMethodDefinitionTest

by Nicolas Cellier

Thanks, very good find! I reviewed the PR yesterday, all good to my eyes. I backported the fix to Squeak where I just experienced the random failure when debugging opensmalltalk-vm test failures https://github.com/hpi-swa/smalltalkCI/issues/350 2017-12-07 13:53 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > Very nice! I am reviewing the change now. > > Thanks, > > Marcus > > > On 6 Dec 2017, at 23:42, Torsten Bergmann <astares(a)gmx.de> wrote: > > > > Hi, > > > > a little story: while working on cleaning up MCMethodDefinitionTest (see > https://pharo.fogbugz.com/f/cases/20830) > > I noticed that from time to time you have trouble when running the test > methods in this class one after the other > > several times. So sometimes it worked and sometimes not. > > > > I wondered since the latest Pharo 7 build #70360 is definitely green on > CI, so the tests seem to work. > > > > After investigating I've noticed that in MCMethodDefinitionTest>>tearDown > a package "FooBarBaz" which > > is used during the tests is unregistered and (when you run another test > from this suite right afterwards) > > is not found anymore. Because in the test initialization it is not. > > > > This is easily fixed with setting the package up in the #setUp method > which is unregistered in #tearDown > > and one can easily run the tests several times independently. > > > > So if one had trouble in Pharo 6 and Pharo 7 with sporadic fails in > Monticello tests this might have been > > the cause. > > > > The fix is part of PR https://github.com/pharo-project/pharo/pull/583 > > > > Bye > > T. > > > > > > >

Dec. 7, 2017

Re: [Pharo-dev] Running tests in MCMethodDefinitionTest

by Marcus Denker

Very nice! I am reviewing the change now. Thanks, Marcus > On 6 Dec 2017, at 23:42, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > a little story: while working on cleaning up MCMethodDefinitionTest (see https://pharo.fogbugz.com/f/cases/20830) > I noticed that from time to time you have trouble when running the test methods in this class one after the other > several times. So sometimes it worked and sometimes not. > > I wondered since the latest Pharo 7 build #70360 is definitely green on CI, so the tests seem to work. > > After investigating I've noticed that in MCMethodDefinitionTest>>tearDown a package "FooBarBaz" which > is used during the tests is unregistered and (when you run another test from this suite right afterwards) > is not found anymore. Because in the test initialization it is not. > > This is easily fixed with setting the package up in the #setUp method which is unregistered in #tearDown > and one can easily run the tests several times independently. > > So if one had trouble in Pharo 6 and Pharo 7 with sporadic fails in Monticello tests this might have been > the cause. > > The fix is part of PR https://github.com/pharo-project/pharo/pull/583 > > Bye > T. > >

Dec. 7, 2017

[Pharo 7.0-dev] Build #363: 20825 Super setUp need to be called in Opal Compiler tests

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

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

Dec. 7, 2017

[Pharo 7.0-dev] Build #362: 20819 Fix variable assignment in RBScanner>>stripComment

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

There is a new Pharo build available! The status of the build #362 was: SUCCESS. The Pull Request #573 was integrated: "20819 Fix variable assignment in RBScanner>>stripComment" Pull request url: https://github.com/pharo-project/pharo/pull/573 Issue Url: https://pharo.fogbugz.com/f/cases/20819 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 7, 2017

Next OpenSmalltalkVM Release Planned For February 1

by Torsten Bergmann

see http://forum.world.st/ANN-Next-OpenSmalltalkVM-Release-Planned-For-February… What does it mean for Pharo-VM and release planning? Thx T.

Dec. 7, 2017

[Pharo 7.0-dev] Build #361: 20827 Super setUp need to be called RBParseTreeRewriterTest and RBParseTreeSearcherTest

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

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

Dec. 7, 2017

Re: [Pharo-dev] [TechTalk] Topics Wanted for 2018!

by Alexandre Bergel

Hi Marcus! Thanks for pushing the community! If there is a free slot at the end of January, I can do another tech talk on AI technique. I am thinking about a lecture on Genetic Algorithm and Genetic Programming. Let me know... Alexandre > On Dec 1, 2017, at 7:58 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > As you know, we are trying to have one Pharo tech-talk per month. > > The idea is to use this for > -> mini âLecturesâ > -> Demos of interesting Projects > -> Just some interesting topic to discuss with audio chat on Discord > > You can see the past topics here: > > http://pharo.org/TechTalk > > We will soon define the dates for the first half of 2018. If you want to do a techtalk > yourself (give a presentation / Demo or moderate a discussion), feel free to contact > me! You are able to pick a date that works best for you. > > > Marcus

Dec. 7, 2017

Running tests in MCMethodDefinitionTest

by Torsten Bergmann

Hi, a little story: while working on cleaning up MCMethodDefinitionTest (see https://pharo.fogbugz.com/f/cases/20830) I noticed that from time to time you have trouble when running the test methods in this class one after the other several times. So sometimes it worked and sometimes not. I wondered since the latest Pharo 7 build #70360 is definitely green on CI, so the tests seem to work. After investigating I've noticed that in MCMethodDefinitionTest>>tearDown a package "FooBarBaz" which is used during the tests is unregistered and (when you run another test from this suite right afterwards) is not found anymore. Because in the test initialization it is not. This is easily fixed with setting the package up in the #setUp method which is unregistered in #tearDown and one can easily run the tests several times independently. So if one had trouble in Pharo 6 and Pharo 7 with sporadic fails in Monticello tests this might have been the cause. The fix is part of PR https://github.com/pharo-project/pharo/pull/583 Bye T.

Dec. 6, 2017

Re: [Pharo-dev] Corrupt method source in Pharo 6.1 (stable)

by Ben Coman

Perhaps PharoV60.sources got corrupted when downloaded. Try to replacing any you can find on your system... http://files.pharo.org/sources/PharoV60.sources.zip cheers -ben On 6 December 2017 at 14:55, Bernhard Pieber <bernhard(a)pieber.com> wrote: > Hi Sean, > > Thanks for taking the time to try to confirm this. Did you use Pharo > Launcher? I just tried it using get.pharo.org and donât see the > corruption. So it seems to be specific to Launcher somehow. :-/ > > Bernhard > > > Am 06.12.2017 um 01:04 schrieb Sean P. DeNigris <sean(a)clipperadams.com>: > > > > bpi wrote > >> Can anyone else confirm that? > > > > It seems okay for me: > > > > <http://forum.world.st/file/t128965/Screenshot_2017-12-05_19.jpeg> > > > > Image > > ----- > > Pharo6.0 > > Latest update: #60524 > > Unnamed > > > > Virtual Machine > > --------------- > > ~/Documents/Pharo/vms/61-x86/Pharo.app/Contents/MacOS/Pharo > > CoInterpreter VMMaker.oscog-eem.2254 uuid: > > 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 > > StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: > > 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 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 $ > > > > Mac OS X built on Jul 20 2017 21:45:23 UTC Compiler: 4.2.1 Compatible > Apple > > LLVM 6.1.0 (clang-602.0.53) > > VMMaker versionString 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 $ > > CoInterpreter VMMaker.oscog-eem.2254 uuid: > > 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 > > StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: > > 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 > > > > Operating System/Hardware > > ------------------------- > > Mac OS 1013.1 intel > > > > > > > > ----- > > Cheers, > > Sean > > -- > > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837. > html > > > > >

Dec. 6, 2017

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

by Peter UhnÃ¡k

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. 6, 2017

Re: [Pharo-dev] Corrupt method source in Pharo 6.1 (stable)

by Sean P. DeNigris

bpi wrote > Did you use Pharo Launcher? Yes ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 6, 2017

ANN: Pharo6.1 new release (I do not remember how this subject was)

by Esteban Lorenzano

So, I made a couple of changes: 20784 update Metacello since last update failed https://pharo.fogbugz.com/f/cases/20784 <https://pharo.fogbugz.com/f/cases/20784> and from a previous integration: 20176 Error in ByteArray>>booleanAt: https://pharo.fogbugz.com/f/cases/20176 <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 <https://pharo.fogbugz.com/f/cases/20762> 20103 Minor glitch in source code diff tool https://pharo.fogbugz.com/f/cases/20103 <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. 6, 2017

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

by Sean P. DeNigris

Same image, another crash dump while resizing a window showing the result of on of the GtMondrianBasicExamples. Segmentation fault Wed Dec 6 11:06:43 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 0xffffffff ebx 0x00138c13 ecx 0x1ef52000 edx 0xffffffff edi 0xffffffff esi 0xffffffff ebp 0xbff2cc58 esp 0xbff2cc00 eip 0x0013a43d 0 Pharo 0x0013a43d copyBits + 6200 1 Pharo 0x00126460 reportStackState + 819 2 Pharo 0x001267e6 sigsegv + 163 3 libsystem_platform.dylib 0xa778202b _sigtramp + 43 4 ??? 0xffffffff 0x0 + 4294967295 5 Pharo 0x0013a9db primitiveCopyBits + 50 6 ??? 0x0646c258 0x0 + 105300568 7 Pharo 0x000a13ab interpret + 646 8 Pharo 0x001279d9 -[sqSqueakMainApplication runSqueak] + 476 9 Foundation 0x953897ec __NSFirePerformWithOrder + 432 10 CoreFoundation 0x9392a216 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 22 11 CoreFoundation 0x9392a132 __CFRunLoopDoObservers + 498 12 CoreFoundation 0x9390d5ed __CFRunLoopRun + 1661 13 CoreFoundation 0x9390cc41 CFRunLoopRunSpecific + 641 14 CoreFoundation 0x9390c9aa CFRunLoopRunInMode + 122 15 HIToolbox 0x92f0dd3b RunCurrentEventLoopInMode + 321 16 HIToolbox 0x92f0d91f ReceiveNextEventCommon + 454 17 HIToolbox 0x92f0d73b _BlockUntilNextEventMatchingListInModeWithFilter + 71 18 AppKit 0x9136538d _DPSNextEvent + 2101 19 AppKit 0x91ad6c74 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 2859 20 AppKit 0x91ad6141 -[NSApplication(NSEvent) nextEventMatchingMask:untilDate:inMode:dequeue:] + 134 21 AppKit 0x9135a2e1 -[NSApplication run] + 763 22 AppKit 0x9132c2f2 NSApplicationMain + 1228 23 libdyld.dylib 0xa7502711 start + 1 Smalltalk stack dump: 0xbff3d93c M GrafPort>copyBits 0x66b2540: a(n) GrafPort 0xbff3d954 M GrafPort>image:at:sourceRect:rule: 0x66b2540: a(n) GrafPort 0xbff3d97c M FormCanvas>image:at:sourceRect:rule: 0x66b2528: a(n) FormCanvas 0xbff3d9ac I FormCanvas(Canvas)>drawImage:at:sourceRect: 0x66b2528: a(n) FormCanvas 0xbff3d9d8 I FormCanvas(Canvas)>drawImage:at: 0x66b2528: a(n) FormCanvas 0xbff3d9fc M [] in BlMorphicSpaceMorph>drawOn: 0x6603cf0: a(n) BlMorphicSpaceMorph 0xbff3da18 M FormCanvas>clipBy:during: 0x66b1910: a(n) FormCanvas 0xbff3da40 M [] in BlMorphicSpaceMorph>drawOn: 0x6603cf0: a(n) BlMorphicSpaceMorph 0xbff3da60 M BlockClosure>ensure: 0x66b2260: a(n) BlockClosure 0xbff3da84 M [] in Mutex>critical: 0x6609470: a(n) Mutex 0xbff3daa4 M [] in Semaphore>critical: 0x6610008: a(n) Semaphore 0xbff3dac4 M BlockClosure>ensure: 0x66b2370: a(n) BlockClosure 0xbff3dae4 M Semaphore>critical: 0x6610008: a(n) Semaphore 0xbff3db04 M Mutex>critical: 0x6609470: a(n) Mutex 0xbff3db24 M BlMorphicSpaceMorph>drawOn: 0x6603cf0: a(n) BlMorphicSpaceMorph 0xbff3db40 M FormCanvas(Canvas)>draw: 0x66b1910: a(n) FormCanvas 0xbff3db5c M FormCanvas(Canvas)>drawMorph: 0x66b1910: a(n) FormCanvas 0xbff3db7c M [] in BlMorphicSpaceMorph(Morph)>fullDrawOn: 0x6603cf0: a(n) BlMorphicSpaceMorph 0xbff3db94 M FormCanvas>roundCornersOf:in:during: 0x66b1910: a(n) FormCanvas 0xbff3dbb8 M FormCanvas(Canvas)>roundCornersOf:during: 0x66b1910: a(n) FormCanvas 0xbff3dbdc M [] in BlMorphicSpaceMorph(Morph)>fullDrawOn: 0x6603cf0: a(n) BlMorphicSpaceMorph 0xbff3dbf4 M BlockClosure>on:do: 0x66b1bc0: a(n) BlockClosure 0xbff3dc14 M BlMorphicSpaceMorph(Morph)>fullDrawOn: 0x6603cf0: a(n) BlMorphicSpaceMorph â¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 6, 2017

[Pharo 7.0-dev] Build #360: 20814 Add release check that we have no protocols left without methods

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

There is a new Pharo build available! The status of the build #360 was: SUCCESS. The Pull Request #570 was integrated: "20814 Add release check that we have no protocols left without methods" Pull request url: https://github.com/pharo-project/pharo/pull/570 Issue Url: https://pharo.fogbugz.com/f/cases/20814 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 6, 2017

[Pharo 7.0-dev] Build #359: 20815 Add a release test ensuring that there are no empty packages in the i

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

There is a new Pharo build available! The status of the build #359 was: SUCCESS. The Pull Request #571 was integrated: "20815 Add a release test ensuring that there are no empty packages in the i" Pull request url: https://github.com/pharo-project/pharo/pull/571 Issue Url: https://pharo.fogbugz.com/f/cases/20815 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 6, 2017

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

by Ben Coman

On 6 December 2017 at 04:43, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > anyway *no data is collected without asking first* > > I demanded that and if someone sneaked in without permission, I will be > very very upset. > +10^10 Thx Esteban. Its good to know you champion this. No need to panic, but its easy to get complacent on this. Of course researcher's *need* data and know themselves to be trustworthy But even with the best intentions, its not just about "doing the right thing", but "being seen to do the right thing". Credibility is hard to earn and easy to destroy. Some people are overly sensitive about this... ;-) "How Target Figured Out A Teen Girl Was Pregnant Before Her Father Did" * https://www.forbes.com/sites/kashmirhill/2012/02/16/how- target-figured-out-a-teen-girl-was-pregnant-before-her- father-did/#4cee9cb66668 Having a setting to enable this buried deep in Settings is probably not ideal. Such a setting *must* be off-by-default, even though I'm personally happy to enable i, I'm not so enthusiastic to go to the trouble navigating to Settings to enable it each time I start a new image. Perhaps the Welcome window should have a Privacy tab describing what data is being gathered by who, with a tick box there to enable it. I'd probably enable it more often if it was only two clicks away. cheers -ben > Esteban > > On 5 Dec 2017, at 21:39, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > I understand it. For that reason there are settings. > > Cheers, > Juraj > > On Dec 5, 2017, at 17:34, Sean Glazier <sglazier456(a)gmail.com> wrote: > > Personally, I know of work places where this is not going to be allowed. I > understand they need the data, but you need to be able to turn it off. A > secure facility would not allow the transmission out in any case. > > > Kind Regards, > > Sean Glazier > > > On Tue, Dec 5, 2017 at 2:45 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> > wrote: > >> Check Privacy section in Settings Browser. >> If you ever send anything, data are anonymized. >> Developers use it to be able to evaluate their research (PhD) work. It is >> a requirement in the research field. >> By sending the anonymized data, you help developers to understand how >> their tools are used. >> In particular, I am aware of Spotter, Quality Assistant, GT tools, and >> Roassal. >> >> Cheers, >> Juraj >> >> > On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com> wrote: >> > >> > I just found a file named org.pharo.global-identifiers.ston in my >> preferences folder. It contains a #secretUUID and a #computerUUID. :-( What >> is this information used for? More importantly, how can I turn it off? >> > >> > Bernhard >> >> >> > > >

Dec. 6, 2017

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

by Thomas Dupriez

Thanks. :) I think "rewriting" has to be there to indicate it changes the source code and recompiles the method, which you may not want. I agree that users don't necessarily need to now that the other deactivation option is done with metalinks. I could replace "deactivate by metalink" with just "deactivate" to make it less technical and keep the "deactivate by rewriting" as is. Cheers, Thomas Le 06/12/2017 Ã 13:06, Juraj Kubelka a Ã©critÂ : > Hi Thomas, > > nice project. > > Maybe âdeactivate by metalink/rewritingâ is too technical? > > Cheers, > Juraj > >> On Dec 6, 2017, at 07:03, 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. 6, 2017

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

by Juraj Kubelka

Hi Thomas, nice project. Maybe âdeactivate by metalink/rewritingâ is too technical? Cheers, Juraj > On Dec 6, 2017, at 07:03, 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. 6, 2017

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

by Tudor Girba

Hi, An interesting point. However, just because other people behave less nicely does not mean we should be the same. Principles should always remain principles regardless of how inconvenient or apparently insignificant the situation is. Cheers, Doru > On Dec 6, 2017, at 12:00 PM, Benoit St-Jean via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Benoit St-Jean <bstjean(a)yahoo.com> > Subject: Re: [Pharo-dev] Is Pharo spying on me? > Date: December 6, 2017 at 12:00:31 PM GMT+1 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Reply-To: Benoit St-Jean <bstjean(a)yahoo.com> > > > Let's not panic here! > > Funny to see people worry so much about privacy from a tool that collects technical data anonymously when a gazillion agencies (especially NSA) keep track of every email and phone call we do!!! > > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > > > From: Tudor Girba <tudor(a)tudorgirba.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Sent: Wednesday, December 6, 2017 1:13 AM > Subject: Re: [Pharo-dev] Is Pharo spying on me? > > Hi, > > What exactly are we removing? > > Cheers, > Doru > > > > On Dec 5, 2017, at 9:41 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > but you are asked to share it, this is not collected automatically without asking before. > > > > anyway, we are removing that (if not removed yet) > > > >> On 5 Dec 2017, at 21:34, Sean Glazier <sglazier456(a)gmail.com> wrote: > >> > >> Personally, I know of work places where this is not going to be allowed. I understand they need the data, but you need to be able to turn it off. A secure facility would not allow the transmission out in any case. > >> > >> > >> Kind Regards, > >> > >> Sean Glazier > >> > >> > >> On Tue, Dec 5, 2017 at 2:45 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > >> Check Privacy section in Settings Browser. > >> If you ever send anything, data are anonymized. > >> Developers use it to be able to evaluate their research (PhD) work. It is a requirement in the research field. > >> By sending the anonymized data, you help developers to understand how their tools are used. > >> In particular, I am aware of Spotter, Quality Assistant, GT tools, and Roassal. > >> > >> Cheers, > >> Juraj > >> > >> > On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com> wrote: > >> > > >> > I just found a file named org.pharo.global-identifiers.ston in my preferences folder. It contains a #secretUUID and a #computerUUID. :-( What is this information used for? More importantly, how can I turn it off? > >> > > >> > Bernhard > >> > >> > >> > > > > -- > www.tudorgirba.com > www.feenk.com > > "Next time you see your life passing by, say 'hi' and get to know her." > > > > > > > > Virus-free. www.avg.com > > -- www.tudorgirba.com www.feenk.com "What we can governs what we wish."

Dec. 6, 2017

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

by Benoit St-Jean

Let's not panic here! Funny to see people worry so much about privacy from a tool that collects technical data anonymously when a gazillion agencies (especially NSA) keep track of every email and phone call we do!!! Â ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein) From: Tudor Girba <tudor(a)tudorgirba.com> To: Pharo Development List <pharo-dev(a)lists.pharo.org> Sent: Wednesday, December 6, 2017 1:13 AM Subject: Re: [Pharo-dev] Is Pharo spying on me? Hi, What exactly are we removing? Cheers, Doru > On Dec 5, 2017, at 9:41 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > but you are asked to share it, this is not collected automatically without asking before. > > anyway, we are removing that (if not removed yet) > >> On 5 Dec 2017, at 21:34, Sean Glazier <sglazier456(a)gmail.com> wrote: >> >> Personally, I know of work places where this is not going to be allowed. I understand they need the data, but you need to be able to turn it off. A secure facility would not allow the transmission out in any case. >> >>Â >> Kind Regards, >>Â >> Sean Glazier >>Â >> >> On Tue, Dec 5, 2017 at 2:45 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: >> Check Privacy section in Settings Browser. >> If you ever send anything, data are anonymized. >> Developers use it to be able to evaluate their research (PhD) work. It is a requirement in the research field. >> By sending the anonymized data, you help developers to understand how their tools are used. >> In particular, I am aware of Spotter, Quality Assistant, GT tools, and Roassal. >> >> Cheers, >> Juraj >> >> > On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com> wrote: >> > >> > I just found a file named org.pharo.global-identifiers.ston in my preferences folder. It contains a #secretUUID and a #computerUUID. :-( What is this information used for? More importantly, how can I turn it off? >> > >> > Bernhard >> >> >> > -- www.tudorgirba.com www.feenk.com "Next time you see your life passing by, say 'hi' and get to know her." | | Virus-free. www.avg.com |

Dec. 6, 2017

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

by Guillermo Polito

Ah this is cool I'm downloading 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 > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Dec. 6, 2017

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

by Esteban Lorenzano

> On 6 Dec 2017, at 11:11, Torsten Bergmann <astares(a)gmx.de> wrote: > > I understand that ShoreLine is removed in Pharo 7. > > But why do we want to remove Quality Assistant? Are we not interested > in code quality anymore? we are not removing QA we are removing QA reporting issues to Yuriy Esteban > > We can currently use it to display code problems in Nautilus and AFAIK > also Calypso shows the code problems. > > Or did I miss something? > > Thanks > T. > >> Gesendet: Mittwoch, 06. Dezember 2017 um 10:43 Uhr >> Von: "Esteban Lorenzano" <estebanlm(a)gmail.com> >> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> Betreff: Re: [Pharo-dev] Is Pharo spying on me? >> >> >> >>> On 6 Dec 2017, at 07:12, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> What exactly are we removing? >> >> shoreline and QA. >> both phd are finished :) >> >> Esteban >> >>> >>> Cheers, >>> Doru >>> >>> >>>> On Dec 5, 2017, at 9:41 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> but you are asked to share it, this is not collected automatically without asking before. >>>> >>>> anyway, we are removing that (if not removed yet) >>>> >>>>> On 5 Dec 2017, at 21:34, Sean Glazier <sglazier456(a)gmail.com> wrote: >>>>> >>>>> Personally, I know of work places where this is not going to be allowed. I understand they need the data, but you need to be able to turn it off. A secure facility would not allow the transmission out in any case. >>>>> >>>>> >>>>> Kind Regards, >>>>> >>>>> Sean Glazier >>>>> >>>>> >>>>> On Tue, Dec 5, 2017 at 2:45 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: >>>>> Check Privacy section in Settings Browser. >>>>> If you ever send anything, data are anonymized. >>>>> Developers use it to be able to evaluate their research (PhD) work. It is a requirement in the research field. >>>>> By sending the anonymized data, you help developers to understand how their tools are used. >>>>> In particular, I am aware of Spotter, Quality Assistant, GT tools, and Roassal. >>>>> >>>>> Cheers, >>>>> Juraj >>>>> >>>>>> On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com> wrote: >>>>>> >>>>>> I just found a file named org.pharo.global-identifiers.ston in my preferences folder. It contains a #secretUUID and a #computerUUID. :-( What is this information used for? More importantly, how can I turn it off? >>>>>> >>>>>> Bernhard >>>>> >>>>> >>>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "Next time you see your life passing by, say 'hi' and get to know her." >>> >>> >>> >>> >>> >> >> >>

Dec. 6, 2017

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

by Torsten Bergmann

I understand that ShoreLine is removed in Pharo 7. But why do we want to remove Quality Assistant? Are we not interested in code quality anymore? We can currently use it to display code problems in Nautilus and AFAIK also Calypso shows the code problems. Or did I miss something? Thanks T. > Gesendet: Mittwoch, 06. Dezember 2017 um 10:43 Uhr > Von: "Esteban Lorenzano" <estebanlm(a)gmail.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] Is Pharo spying on me? > > > > > On 6 Dec 2017, at 07:12, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > Hi, > > > > What exactly are we removing? > > shoreline and QA. > both phd are finished :) > > Esteban > > > > > Cheers, > > Doru > > > > > >> On Dec 5, 2017, at 9:41 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> > >> but you are asked to share it, this is not collected automatically without asking before. > >> > >> anyway, we are removing that (if not removed yet) > >> > >>> On 5 Dec 2017, at 21:34, Sean Glazier <sglazier456(a)gmail.com> wrote: > >>> > >>> Personally, I know of work places where this is not going to be allowed. I understand they need the data, but you need to be able to turn it off. A secure facility would not allow the transmission out in any case. > >>> > >>> > >>> Kind Regards, > >>> > >>> Sean Glazier > >>> > >>> > >>> On Tue, Dec 5, 2017 at 2:45 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > >>> Check Privacy section in Settings Browser. > >>> If you ever send anything, data are anonymized. > >>> Developers use it to be able to evaluate their research (PhD) work. It is a requirement in the research field. > >>> By sending the anonymized data, you help developers to understand how their tools are used. > >>> In particular, I am aware of Spotter, Quality Assistant, GT tools, and Roassal. > >>> > >>> Cheers, > >>> Juraj > >>> > >>>> On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com> wrote: > >>>> > >>>> I just found a file named org.pharo.global-identifiers.ston in my preferences folder. It contains a #secretUUID and a #computerUUID. :-( What is this information used for? More importantly, how can I turn it off? > >>>> > >>>> Bernhard > >>> > >>> > >>> > >> > > > > -- > > www.tudorgirba.com > > www.feenk.com > > > > "Next time you see your life passing by, say 'hi' and get to know her." > > > > > > > > > > > > >

Dec. 6, 2017

Release: Conveniently browse, deactivate and reactivate halts and breakpoints with the HaltManager

by Thomas Dupriez

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. 6, 2017

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

by Pavel Krivanek

ShoreLIne is already removed from Pharo 7 -- Pavel 2017-12-06 10:43 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > > > On 6 Dec 2017, at 07:12, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > Hi, > > > > What exactly are we removing? > > shoreline and QA. > both phd are finished :) > > Esteban > > > > > Cheers, > > Doru > > > > > >> On Dec 5, 2017, at 9:41 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> > >> but you are asked to share it, this is not collected automatically > without asking before. > >> > >> anyway, we are removing that (if not removed yet) > >> > >>> On 5 Dec 2017, at 21:34, Sean Glazier <sglazier456(a)gmail.com> wrote: > >>> > >>> Personally, I know of work places where this is not going to be > allowed. I understand they need the data, but you need to be able to turn > it off. A secure facility would not allow the transmission out in any case. > >>> > >>> > >>> Kind Regards, > >>> > >>> Sean Glazier > >>> > >>> > >>> On Tue, Dec 5, 2017 at 2:45 PM, Juraj Kubelka < > juraj.kubelka(a)icloud.com> wrote: > >>> Check Privacy section in Settings Browser. > >>> If you ever send anything, data are anonymized. > >>> Developers use it to be able to evaluate their research (PhD) work. It > is a requirement in the research field. > >>> By sending the anonymized data, you help developers to understand how > their tools are used. > >>> In particular, I am aware of Spotter, Quality Assistant, GT tools, and > Roassal. > >>> > >>> Cheers, > >>> Juraj > >>> > >>>> On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com> > wrote: > >>>> > >>>> I just found a file named org.pharo.global-identifiers.ston in my > preferences folder. It contains a #secretUUID and a #computerUUID. :-( What > is this information used for? More importantly, how can I turn it off? > >>>> > >>>> Bernhard > >>> > >>> > >>> > >> > > > > -- > > www.tudorgirba.com > > www.feenk.com > > > > "Next time you see your life passing by, say 'hi' and get to know her." > > > > > > > > > > > > >

Dec. 6, 2017

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

by Esteban Lorenzano

> On 6 Dec 2017, at 07:12, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > What exactly are we removing? shoreline and QA. both phd are finished :) Esteban > > Cheers, > Doru > > >> On Dec 5, 2017, at 9:41 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> but you are asked to share it, this is not collected automatically without asking before. >> >> anyway, we are removing that (if not removed yet) >> >>> On 5 Dec 2017, at 21:34, Sean Glazier <sglazier456(a)gmail.com> wrote: >>> >>> Personally, I know of work places where this is not going to be allowed. I understand they need the data, but you need to be able to turn it off. A secure facility would not allow the transmission out in any case. >>> >>> >>> Kind Regards, >>> >>> Sean Glazier >>> >>> >>> On Tue, Dec 5, 2017 at 2:45 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: >>> Check Privacy section in Settings Browser. >>> If you ever send anything, data are anonymized. >>> Developers use it to be able to evaluate their research (PhD) work. It is a requirement in the research field. >>> By sending the anonymized data, you help developers to understand how their tools are used. >>> In particular, I am aware of Spotter, Quality Assistant, GT tools, and Roassal. >>> >>> Cheers, >>> Juraj >>> >>>> On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com> wrote: >>>> >>>> I just found a file named org.pharo.global-identifiers.ston in my preferences folder. It contains a #secretUUID and a #computerUUID. :-( What is this information used for? More importantly, how can I turn it off? >>>> >>>> Bernhard >>> >>> >>> >> > > -- > www.tudorgirba.com > www.feenk.com > > "Next time you see your life passing by, say 'hi' and get to know her." > > > > >

Dec. 6, 2017

Re: [Pharo-dev] How to get a Moose Model

by Tudor Girba

Hi, Thanks for the question. Please address this to the moose-dev mailing list (in CC): https://www.list.inf.unibe.ch/listinfo/moose-dev I just answered it there. Cheers, Doru > On Dec 5, 2017, at 4:44 PM, Moussa Saker via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Moussa Saker <sak_moussa(a)yahoo.fr> > Subject: How to get a Moose Model > Date: December 5, 2017 at 4:44:31 PM GMT+1 > To: "pharo-dev(a)lists.pharo.org" <pharo-dev(a)lists.pharo.org> > Reply-To: Moussa Saker <sak_moussa(a)yahoo.fr> > > > Hello everyone > > we are working on a Moose project and we need a script to import the Moose Model, right now we use: > > MooseModel root first , > > but it's not really practical, Any suggestions ? > > Moussa Saker > LISCO Laboratory > Badji Mokhtar-Annaba University, > P.O. Box 12, Annaba 23000, Algeriai n > > -- www.tudorgirba.com www.feenk.com "To lead is not to demand things, it is to make them happen."

Dec. 6, 2017

Re: [Pharo-dev] Corrupt method source in Pharo 6.1 (stable)

by Bernhard Pieber

Hi Sean, Thanks for taking the time to try to confirm this. Did you use Pharo Launcher? I just tried it using get.pharo.org and donât see the corruption. So it seems to be specific to Launcher somehow. :-/ Bernhard > Am 06.12.2017 um 01:04 schrieb Sean P. DeNigris <sean(a)clipperadams.com>: > > bpi wrote >> Can anyone else confirm that? > > It seems okay for me: > > <http://forum.world.st/file/t128965/Screenshot_2017-12-05_19.jpeg> > > Image > ----- > Pharo6.0 > Latest update: #60524 > Unnamed > > Virtual Machine > --------------- > ~/Documents/Pharo/vms/61-x86/Pharo.app/Contents/MacOS/Pharo > CoInterpreter VMMaker.oscog-eem.2254 uuid: > 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: > 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 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 $ > > Mac OS X built on Jul 20 2017 21:45:23 UTC Compiler: 4.2.1 Compatible Apple > LLVM 6.1.0 (clang-602.0.53) > VMMaker versionString 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 $ > CoInterpreter VMMaker.oscog-eem.2254 uuid: > 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: > 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 > > Operating System/Hardware > ------------------------- > Mac OS 1013.1 intel > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Dec. 6, 2017

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

by Tudor Girba

Hi, What exactly are we removing? Cheers, Doru > On Dec 5, 2017, at 9:41 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > but you are asked to share it, this is not collected automatically without asking before. > > anyway, we are removing that (if not removed yet) > >> On 5 Dec 2017, at 21:34, Sean Glazier <sglazier456(a)gmail.com> wrote: >> >> Personally, I know of work places where this is not going to be allowed. I understand they need the data, but you need to be able to turn it off. A secure facility would not allow the transmission out in any case. >> >> >> Kind Regards, >> >> Sean Glazier >> >> >> On Tue, Dec 5, 2017 at 2:45 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: >> Check Privacy section in Settings Browser. >> If you ever send anything, data are anonymized. >> Developers use it to be able to evaluate their research (PhD) work. It is a requirement in the research field. >> By sending the anonymized data, you help developers to understand how their tools are used. >> In particular, I am aware of Spotter, Quality Assistant, GT tools, and Roassal. >> >> Cheers, >> Juraj >> >> > On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com> wrote: >> > >> > I just found a file named org.pharo.global-identifiers.ston in my preferences folder. It contains a #secretUUID and a #computerUUID. :-( What is this information used for? More importantly, how can I turn it off? >> > >> > Bernhard >> >> >> > -- www.tudorgirba.com www.feenk.com "Next time you see your life passing by, say 'hi' and get to know her."

Dec. 6, 2017

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

by Tudor Girba

Hi, Indeed privacy is an important issue. When we introduced the collection of data in Spotter we made sure that: - the collection of data is off by default - you are asked explicitly to turn it on - and, even when you send the data, you are sending technical tool data or at most, anonymized data. In other words, we want people to send data, but they should be in control and sending data should always be an opt-in and as transparent as possible. Right now, there is a central Privacy setting holder that is being used to guard the usage of the GTEventRecorder. To check that this is the case, take a look at the result of this query: (SystemNavigation new allReferencesTo: GTEventRecorder binding) \ (SystemNavigation new allReferencesTo: Privacy binding) ==> GtExamplesReleaseTest>>#testAllMissingInternalExamples GTEventRecorderHelp class>>#client GTEventRecorderTest>>#setUp GTEventCollector>>#register These are only test, help and registration methods, which are fine. We should make a QA rule out of this. In the future, we would like to work on a more obvious signal that data is being collected. Cheers, Doru > On Dec 5, 2017, at 9:43 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > anyway *no data is collected without asking first* > > I demanded that and if someone sneaked in without permission, I will be very very upset. > > Esteban > >> On 5 Dec 2017, at 21:39, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: >> >> I understand it. For that reason there are settings. >> >> Cheers, >> Juraj >> >>> On Dec 5, 2017, at 17:34, Sean Glazier <sglazier456(a)gmail.com> wrote: >>> >>> Personally, I know of work places where this is not going to be allowed. I understand they need the data, but you need to be able to turn it off. A secure facility would not allow the transmission out in any case. >>> >>> >>> Kind Regards, >>> >>> Sean Glazier >>> >>> >>> On Tue, Dec 5, 2017 at 2:45 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: >>> Check Privacy section in Settings Browser. >>> If you ever send anything, data are anonymized. >>> Developers use it to be able to evaluate their research (PhD) work. It is a requirement in the research field. >>> By sending the anonymized data, you help developers to understand how their tools are used. >>> In particular, I am aware of Spotter, Quality Assistant, GT tools, and Roassal. >>> >>> Cheers, >>> Juraj >>> >>> > On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com> wrote: >>> > >>> > I just found a file named org.pharo.global-identifiers.ston in my preferences folder. It contains a #secretUUID and a #computerUUID. :-( What is this information used for? More importantly, how can I turn it off? >>> > >>> > Bernhard >>> >>> >>> >> > -- www.tudorgirba.com www.feenk.com "Value is always contextual."

Dec. 6, 2017

Re: [Pharo-dev] Corrupt method source in Pharo 6.1 (stable)

by Sean P. DeNigris

bpi wrote > Can anyone else confirm that? It seems okay for me: <http://forum.world.st/file/t128965/Screenshot_2017-12-05_19.jpeg> Image ----- Pharo6.0 Latest update: #60524 Unnamed Virtual Machine --------------- ~/Documents/Pharo/vms/61-x86/Pharo.app/Contents/MacOS/Pharo CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 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 $ Mac OS X built on Jul 20 2017 21:45:23 UTC Compiler: 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53) VMMaker versionString 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 $ CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 Operating System/Hardware ------------------------- Mac OS 1013.1 intel ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 6, 2017

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

by Pavel Krivanek

2017-12-05 20:30 GMT+01:00 Bernhard Pieber <bernhard(a)pieber.com>: > I just found a file named org.pharo.global-identifiers.ston in my > preferences folder. It contains a #secretUUID and a #computerUUID. :-( What > is this information used for? More importantly, how can I turn it off? > There is nothing evil on it. It is used for resolving if the preferences should be reloaded. See SystemSettingsPersistence class>>#resumeSystemSettings -- Pavel > > Bernhard >

Dec. 5, 2017

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

by Esteban Lorenzano

anyway *no data is collected without asking first* I demanded that and if someone sneaked in without permission, I will be very very upset. Esteban > On 5 Dec 2017, at 21:39, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > I understand it. For that reason there are settings. > > Cheers, > Juraj > >> On Dec 5, 2017, at 17:34, Sean Glazier <sglazier456(a)gmail.com <mailto:sglazier456@gmail.com>> wrote: >> >> Personally, I know of work places where this is not going to be allowed. I understand they need the data, but you need to be able to turn it off. A secure facility would not allow the transmission out in any case. >> >> >> Kind Regards, >> >> Sean Glazier >> >> >> On Tue, Dec 5, 2017 at 2:45 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com <mailto:juraj.kubelka@icloud.com>> wrote: >> Check Privacy section in Settings Browser. >> If you ever send anything, data are anonymized. >> Developers use it to be able to evaluate their research (PhD) work. It is a requirement in the research field. >> By sending the anonymized data, you help developers to understand how their tools are used. >> In particular, I am aware of Spotter, Quality Assistant, GT tools, and Roassal. >> >> Cheers, >> Juraj >> >> > On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com <mailto:bernhard@pieber.com>> wrote: >> > >> > I just found a file named org.pharo.global-identifiers.ston in my preferences folder. It contains a #secretUUID and a #computerUUID. :-( What is this information used for? More importantly, how can I turn it off? >> > >> > Bernhard >> >> >> >

Dec. 5, 2017

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

by Esteban Lorenzano

but you are asked to share it, this is not collected automatically without asking before. anyway, we are removing that (if not removed yet) > On 5 Dec 2017, at 21:34, Sean Glazier <sglazier456(a)gmail.com> wrote: > > Personally, I know of work places where this is not going to be allowed. I understand they need the data, but you need to be able to turn it off. A secure facility would not allow the transmission out in any case. > > > Kind Regards, > > Sean Glazier > > > On Tue, Dec 5, 2017 at 2:45 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com <mailto:juraj.kubelka@icloud.com>> wrote: > Check Privacy section in Settings Browser. > If you ever send anything, data are anonymized. > Developers use it to be able to evaluate their research (PhD) work. It is a requirement in the research field. > By sending the anonymized data, you help developers to understand how their tools are used. > In particular, I am aware of Spotter, Quality Assistant, GT tools, and Roassal. > > Cheers, > Juraj > > > On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com <mailto:bernhard@pieber.com>> wrote: > > > > I just found a file named org.pharo.global-identifiers.ston in my preferences folder. It contains a #secretUUID and a #computerUUID. :-( What is this information used for? More importantly, how can I turn it off? > > > > Bernhard > > >

Dec. 5, 2017

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

by Juraj Kubelka

I understand it. For that reason there are settings. Cheers, Juraj > On Dec 5, 2017, at 17:34, Sean Glazier <sglazier456(a)gmail.com> wrote: > > Personally, I know of work places where this is not going to be allowed. I understand they need the data, but you need to be able to turn it off. A secure facility would not allow the transmission out in any case. > > > Kind Regards, > > Sean Glazier > > > On Tue, Dec 5, 2017 at 2:45 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com <mailto:juraj.kubelka@icloud.com>> wrote: > Check Privacy section in Settings Browser. > If you ever send anything, data are anonymized. > Developers use it to be able to evaluate their research (PhD) work. It is a requirement in the research field. > By sending the anonymized data, you help developers to understand how their tools are used. > In particular, I am aware of Spotter, Quality Assistant, GT tools, and Roassal. > > Cheers, > Juraj > > > On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com <mailto:bernhard@pieber.com>> wrote: > > > > I just found a file named org.pharo.global-identifiers.ston in my preferences folder. It contains a #secretUUID and a #computerUUID. :-( What is this information used for? More importantly, how can I turn it off? > > > > Bernhard > > >

Dec. 5, 2017

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

by Sean Glazier

Personally, I know of work places where this is not going to be allowed. I understand they need the data, but you need to be able to turn it off. A secure facility would not allow the transmission out in any case. Kind Regards, Sean Glazier On Tue, Dec 5, 2017 at 2:45 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > Check Privacy section in Settings Browser. > If you ever send anything, data are anonymized. > Developers use it to be able to evaluate their research (PhD) work. It is > a requirement in the research field. > By sending the anonymized data, you help developers to understand how > their tools are used. > In particular, I am aware of Spotter, Quality Assistant, GT tools, and > Roassal. > > Cheers, > Juraj > > > On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com> wrote: > > > > I just found a file named org.pharo.global-identifiers.ston in my > preferences folder. It contains a #secretUUID and a #computerUUID. :-( What > is this information used for? More importantly, how can I turn it off? > > > > Bernhard > > >

Dec. 5, 2017

Corrupt method source in Pharo 6.1 (stable)

by Bernhard Pieber

I did the following in Pharo Launcher: 1. Select Official distributions > Pharo 6.1 (stable) 2. Click Create Image 3. Launch created image 4. Browse GLMAccumulator 5. Click on any method, e.g. activeEntity => method source is corrupt, e.g. mp: âtg 2/2/2010 22:03' I tried it twice, also with the Pharo 6.0 > latest image. Can anyone else confirm that? Bernhard

Dec. 5, 2017

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

by Juraj Kubelka

Check Privacy section in Settings Browser. If you ever send anything, data are anonymized. Developers use it to be able to evaluate their research (PhD) work. It is a requirement in the research field. By sending the anonymized data, you help developers to understand how their tools are used. In particular, I am aware of Spotter, Quality Assistant, GT tools, and Roassal. Cheers, Juraj > On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com> wrote: > > I just found a file named org.pharo.global-identifiers.ston in my preferences folder. It contains a #secretUUID and a #computerUUID. :-( What is this information used for? More importantly, how can I turn it off? > > Bernhard

Dec. 5, 2017

Is Pharo spying on me?

by Bernhard Pieber

I just found a file named org.pharo.global-identifiers.ston in my preferences folder. It contains a #secretUUID and a #computerUUID. :-( What is this information used for? More importantly, how can I turn it off? Bernhard

Dec. 5, 2017

Crash Dump - GT loaded into 6.1

by Sean P. DeNigris

Let me know if you need any other infoâ¦ Image ----- Pharo6.0 Latest update: #60523 Unnamed Virtual Machine --------------- ~/Documents/Pharo/vms/61-x86/Pharo.app/Contents/MacOS/Pharo CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 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 $ Mac OS X built on Jul 20 2017 21:45:23 UTC Compiler: 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53) VMMaker versionString 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 $ CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 *Here's the top part of the dmp:* Bus error 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 0x6b50fd00 ebx 0x6dd03c90 ecx 0x88bb0000 edx 0x012f39a0 edi 0x6dd03c30 esi 0x6dd03c30 ebp 0xbff89a88 esp 0xbff89a7c eip 0x88bb0000 0 ??? 0x88bb0000 0x0 + 2293956608 1 Pharo 0x000c5460 reportStackState + 819 2 Pharo 0x000c57e6 sigsegv + 163 3 libsystem_platform.dylib 0xa778202b _sigtramp + 43 4 ??? 0xffffffff 0x0 + 4294967295 5 libMoz2D.dylib 0x1394b9d3 _ZN12PLDHashTableD1Ev + 67 6 libMoz2D.dylib 0x13b9e492 _ZN21nsLanguageAtomService7ReleaseEv + 82 7 libMoz2D.dylib 0x138dd879 _ZN19gfxPlatformFontListD2Ev + 377 8 libMoz2D.dylib 0x13902881 _ZN22gfxMacPlatformFontListD0Ev + 17 9 libMoz2D.dylib 0x13877839 _ZN11gfxPlatform8ShutdownEv + 73 10 Pharo 0x000fb3d2 primitiveCalloutWithArgs + 1748 11 Pharo 0x00055357 executeNewMethod + 144 12 Pharo 0x00056187 ceSendsupertonumArgs + 1017 13 ??? 0x061310a3 0x0 + 101912739 14 Pharo 0x000403ab interpret + 646 15 Pharo 0x000c69d9 -[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 Smalltalk stack dump: 0xbffa09e4 M MozServices class>primShutdownPlatform 0xb45b538: a(n) MozServices class 0xbffa0a10 I FFICalloutAPI>function:module: 0x642b5a0: a(n) FFICalloutAPI 0xbffa0a38 I MozServices class(Object)>ffiCall: 0xb45b538: a(n) MozServices class 0xbffa0a5c I MozServices class>primShutdownPlatform 0xb45b538: a(n) MozServices class 0xbffa0a74 M [] in MozServices class>stop 0xb45b538: a(n) MozServices class 0xbffa0a94 M BlockClosure>ensure: 0x641e930: a(n) BlockClosure 0xbffa0ab8 I MozServices class>stop 0xb45b538: a(n) MozServices class 0xbffa0ad8 I MozServices class>shutDown: 0xb45b538: a(n) MozServices class 0xbffa0af4 M ClassSessionHandler>shutdown: 0xb7c7dc8: a(n) ClassSessionHandler 0xbffa0b14 M [] in WorkingSession>runShutdown: 0x8c5c0f8: a(n) WorkingSession 0xbffa0b38 M [] in WorkingSession>runList:do: 0x8c5c0f8: a(n) WorkingSession 0xbffa0b50 M BlockClosure>on:do: 0x641e770: a(n) BlockClosure 0xbffa0b74 M [] in WorkingSession>runList:do: 0x8c5c0f8: a(n) WorkingSession 0xbffa0b98 M Array(SequenceableCollection)>do: 0x641df40: a(n) Array 0xbffa0bbc I WorkingSession>runList:do: 0x8c5c0f8: a(n) WorkingSession 0xbffa0be4 I WorkingSession>runShutdown: 0x8c5c0f8: a(n) WorkingSession 0xbffa0c08 I WorkingSession>stop: 0x8c5c0f8: a(n) WorkingSession 0xbffa0c34 I SessionManager>snapshot:andQuit: 0x8248590: a(n) SessionManager 0xbffa0c64 I [] in SmalltalkImage>snapshot:andQuit: 0x6c0bf40: a(n) SmalltalkImage ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 5, 2017

How to get a Moose Model

by Moussa Saker

Hello everyoneÂ we are working on a Moose project andÂ we need a script to importÂ the Moose Model, right now we use:Â MooseModel root first , Â but it's not really practical, Any suggestions ? Moussa Saker LISCO Laboratory Badji Mokhtar-Annaba University, P.O. Box 12, Annaba 23000, Algeriai n

Dec. 5, 2017

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

by Stephane Ducasse

We tried | parser doc visitor | parser := XMLDOMParser new on: self xmlContents; preservesIgnorableWhitespace: false. doc := parser parseDocument. but we still have the empty nodes around. Stef On Tue, Dec 5, 2017 at 2:29 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > )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. 5, 2017

How to get rid of empty XML nodes?

by Stephane Ducasse

)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. 5, 2017

Re: [Pharo-dev] Moving from mc to tonel?

by Alistair Grant

Hi Peter, On 5 December 2017 at 11:55, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> Would you be open to a PR that incorporates Sven's changes suggested >> above? > > Certainly. One thing to keep in mind is that I had to modify > MemoryStore/MemoryHandle so it can process unicode at all, but it also > forces everything to be unicode. This is probably a good thing. The fast-import documentation says that it is strict about character encoding and only accepts UTF-8. I'll let you know when the PRs are ready. Thanks, Alistair >> I hate having to deal with string encoding, and know as little as >> possible. :-) > > Apparently me taking this approach resulted in the current situation. :-D > > Peter > > On Tue, Dec 5, 2017 at 10:27 AM, Alistair Grant <akgrant0710(a)gmail.com> > wrote: >> >> On Tue, Dec 05, 2017 at 08:56:53AM +0100, Sven Van Caekenberghe wrote: >> > >> > > On 5 Dec 2017, at 08:34, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> > > >> > > On 5 December 2017 at 03:41, Martin Dias <tinchodias(a)gmail.com> wrote: >> > >> I suspect it's related to the large number of commits in my repo. I >> > >> made >> > >> some tweaks and succeeded to create the fast-import file. But I get: >> > >> >> > >> fatal: Unsupported command: . >> > >> fast-import: dumping crash report to .git/fast_import_crash_10301 >> > >> >> > >> Do you recognize this error? >> > >> I will check my changes tweaking the git-migration tool to see if I >> > >> modified >> > >> some behavior my mistake... >> > > >> > > I had the same error just last night. >> > > >> > > In my case, it turned out to be a non-UTF8 encoded character in one of >> > > the commit messages. >> > > >> > > I tracked it down by looking at the crash report and searching for a >> > > nearby command. I've deleted the crash reports now, but I think it >> > > was the number associated with a mark command that got me near the >> > > problem character in the fast-import file. >> > > >> > > I also modified the code to halt whenever it found a non-UTF8 >> > > character. I'm sure there are better ways to do this, but: >> > > >> > > >> > > GitMigrationCommitInfo>>inlineDataFor: aString >> > > >> > > | theString | >> > > theString := aString. >> > > "Ensure the message has valid UTF-8 encoding (this will raise an >> > > error if it doesn't)" >> > > [ (ZnCharacterEncoder newForEncoding: 'utf8') decodeBytes: aString >> > > asByteArray ] >> > > on: Error >> > > do: [ :ex | self halt: 'Illegal string encoding'. >> > > theString := aString select: [ :each | each asciiValue >> > > between: 32 and: 128 ] ]. >> > > ^ 'data ' , theString size asString , String cr , (theString >> > > ifEmpty: [ '' ] ifNotEmpty: [ theString , String cr ]) >> > >> > There is also ByteArray>>#utf8Decoded (as well as >> > String>>#utf8Encoded), both using the newer ZnCharacterEncoders. So >> > you could write it shorter as: >> > >> > aString asByteArray utf8Decoded >> > >> > Instead of Error you could use the more intention revealing >> > ZnCharacterEncodingError. >> >> I agree, this was a hack to get me past the immediate issue and see if >> I could get the migration to work. >> >> >> > Apart from that, and I known you did not create this mess, encoding a >> > String into a String, although it can be done, is so wrong. You encode >> > a String (a collection of Characters, of Unicode code points) into a >> > ByteArray and you decode a ByteArray into a String. >> > >> > Sending #asByteArray to a String in almost always wrong, as is sending >> > #asString to a ByteArray. These are implicit conversions (null >> > conversions, like ZnNullEncoder) that only work for pure ASCII or >> > Latin1 (iso-8859-1), but not for the much richer set of Characters >> > that Pharo supports. So these will eventually fail, one day, in a >> > country far away. >> >> I hate having to deal with string encoding, and know as little as >> possible. :-) >> >> >> >> On Tue, Dec 05, 2017 at 08:59:34AM +0100, Peter Uhn??k wrote: >> > > In my case, it turned out to be a non-UTF8 encoded character in one of >> > > the >> > commit messages. >> > >> > I've ran into this problem in a sister project (tonel-migration), and do >> > not >> > have a proper resolution yet. I was forcing everything to be unicode, so >> > I need >> > a better way to read and write encoded strings. :< >> >> I think this is always going to be a tricky problem since the file may >> simply be corrupt, and the resolution won't always be the same. In my >> case I was happy to simply remove the offending characters. >> >> I do think it would be nice if the migration tool at least stopped and >> warned the user that the input is invalid. >> >> Would you be open to a PR that incorporates Sven's changes suggested >> above? >> >> >> >> On Tue, Dec 05, 2017 at 09:05:24AM +0100, Sven Van Caekenberghe wrote: >> > >> > Maybe ZnCharacterEncoder class>>#detectEncoding: can help, although it >> > is far from perfect. >> >> In this particular case I think it is better to try decoding with UTF8, >> since #detectEncoding: isn't completely reliable and we just want to >> know if it isn't valid UTF8. >> >> >> Cheers, >> Alistair >> >

Dec. 5, 2017

Re: [Pharo-dev] Moving from mc to tonel?

by Peter UhnÃ¡k

> Would you be open to a PR that incorporates Sven's changes suggested above? Certainly. One thing to keep in mind is that I had to modify MemoryStore/MemoryHandle so it can process unicode at all, but it also forces everything to be unicode. > I hate having to deal with string encoding, and know as little as possible. :-) Apparently me taking this approach resulted in the current situation. :-D Peter On Tue, Dec 5, 2017 at 10:27 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On Tue, Dec 05, 2017 at 08:56:53AM +0100, Sven Van Caekenberghe wrote: > > > > > On 5 Dec 2017, at 08:34, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > > > On 5 December 2017 at 03:41, Martin Dias <tinchodias(a)gmail.com> wrote: > > >> I suspect it's related to the large number of commits in my repo. I > made > > >> some tweaks and succeeded to create the fast-import file. But I get: > > >> > > >> fatal: Unsupported command: . > > >> fast-import: dumping crash report to .git/fast_import_crash_10301 > > >> > > >> Do you recognize this error? > > >> I will check my changes tweaking the git-migration tool to see if I > modified > > >> some behavior my mistake... > > > > > > I had the same error just last night. > > > > > > In my case, it turned out to be a non-UTF8 encoded character in one of > > > the commit messages. > > > > > > I tracked it down by looking at the crash report and searching for a > > > nearby command. I've deleted the crash reports now, but I think it > > > was the number associated with a mark command that got me near the > > > problem character in the fast-import file. > > > > > > I also modified the code to halt whenever it found a non-UTF8 > > > character. I'm sure there are better ways to do this, but: > > > > > > > > > GitMigrationCommitInfo>>inlineDataFor: aString > > > > > > | theString | > > > theString := aString. > > > "Ensure the message has valid UTF-8 encoding (this will raise an > > > error if it doesn't)" > > > [ (ZnCharacterEncoder newForEncoding: 'utf8') decodeBytes: aString > > > asByteArray ] > > > on: Error > > > do: [ :ex | self halt: 'Illegal string encoding'. > > > theString := aString select: [ :each | each asciiValue > > > between: 32 and: 128 ] ]. > > > ^ 'data ' , theString size asString , String cr , (theString > > > ifEmpty: [ '' ] ifNotEmpty: [ theString , String cr ]) > > > > There is also ByteArray>>#utf8Decoded (as well as > > String>>#utf8Encoded), both using the newer ZnCharacterEncoders. So > > you could write it shorter as: > > > > aString asByteArray utf8Decoded > > > > Instead of Error you could use the more intention revealing > ZnCharacterEncodingError. > > I agree, this was a hack to get me past the immediate issue and see if > I could get the migration to work. > > > > Apart from that, and I known you did not create this mess, encoding a > > String into a String, although it can be done, is so wrong. You encode > > a String (a collection of Characters, of Unicode code points) into a > > ByteArray and you decode a ByteArray into a String. > > > > Sending #asByteArray to a String in almost always wrong, as is sending > > #asString to a ByteArray. These are implicit conversions (null > > conversions, like ZnNullEncoder) that only work for pure ASCII or > > Latin1 (iso-8859-1), but not for the much richer set of Characters > > that Pharo supports. So these will eventually fail, one day, in a > > country far away. > > I hate having to deal with string encoding, and know as little as > possible. :-) > > > > On Tue, Dec 05, 2017 at 08:59:34AM +0100, Peter Uhn??k wrote: > > > In my case, it turned out to be a non-UTF8 encoded character in one of > the > > commit messages. > > > > I've ran into this problem in a sister project (tonel-migration), and do > not > > have a proper resolution yet. I was forcing everything to be unicode, so > I need > > a better way to read and write encoded strings. :< > > I think this is always going to be a tricky problem since the file may > simply be corrupt, and the resolution won't always be the same. In my > case I was happy to simply remove the offending characters. > > I do think it would be nice if the migration tool at least stopped and > warned the user that the input is invalid. > > Would you be open to a PR that incorporates Sven's changes suggested > above? > > > > On Tue, Dec 05, 2017 at 09:05:24AM +0100, Sven Van Caekenberghe wrote: > > > > Maybe ZnCharacterEncoder class>>#detectEncoding: can help, although it > > is far from perfect. > > In this particular case I think it is better to try decoding with UTF8, > since #detectEncoding: isn't completely reliable and we just want to > know if it isn't valid UTF8. > > > Cheers, > Alistair > >

Dec. 5, 2017

Re: [Pharo-dev] Moving from mc to tonel?

by Alistair Grant

On Tue, Dec 05, 2017 at 08:56:53AM +0100, Sven Van Caekenberghe wrote: > > > On 5 Dec 2017, at 08:34, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > On 5 December 2017 at 03:41, Martin Dias <tinchodias(a)gmail.com> wrote: > >> I suspect it's related to the large number of commits in my repo. I made > >> some tweaks and succeeded to create the fast-import file. But I get: > >> > >> fatal: Unsupported command: . > >> fast-import: dumping crash report to .git/fast_import_crash_10301 > >> > >> Do you recognize this error? > >> I will check my changes tweaking the git-migration tool to see if I modified > >> some behavior my mistake... > > > > I had the same error just last night. > > > > In my case, it turned out to be a non-UTF8 encoded character in one of > > the commit messages. > > > > I tracked it down by looking at the crash report and searching for a > > nearby command. I've deleted the crash reports now, but I think it > > was the number associated with a mark command that got me near the > > problem character in the fast-import file. > > > > I also modified the code to halt whenever it found a non-UTF8 > > character. I'm sure there are better ways to do this, but: > > > > > > GitMigrationCommitInfo>>inlineDataFor: aString > > > > | theString | > > theString := aString. > > "Ensure the message has valid UTF-8 encoding (this will raise an > > error if it doesn't)" > > [ (ZnCharacterEncoder newForEncoding: 'utf8') decodeBytes: aString > > asByteArray ] > > on: Error > > do: [ :ex | self halt: 'Illegal string encoding'. > > theString := aString select: [ :each | each asciiValue > > between: 32 and: 128 ] ]. > > ^ 'data ' , theString size asString , String cr , (theString > > ifEmpty: [ '' ] ifNotEmpty: [ theString , String cr ]) > > There is also ByteArray>>#utf8Decoded (as well as > String>>#utf8Encoded), both using the newer ZnCharacterEncoders. So > you could write it shorter as: > > aString asByteArray utf8Decoded > > Instead of Error you could use the more intention revealing ZnCharacterEncodingError. I agree, this was a hack to get me past the immediate issue and see if I could get the migration to work. > Apart from that, and I known you did not create this mess, encoding a > String into a String, although it can be done, is so wrong. You encode > a String (a collection of Characters, of Unicode code points) into a > ByteArray and you decode a ByteArray into a String. > > Sending #asByteArray to a String in almost always wrong, as is sending > #asString to a ByteArray. These are implicit conversions (null > conversions, like ZnNullEncoder) that only work for pure ASCII or > Latin1 (iso-8859-1), but not for the much richer set of Characters > that Pharo supports. So these will eventually fail, one day, in a > country far away. I hate having to deal with string encoding, and know as little as possible. :-) On Tue, Dec 05, 2017 at 08:59:34AM +0100, Peter Uhn??k wrote: > > In my case, it turned out to be a non-UTF8 encoded character in one of the > commit messages. > > I've ran into this problem in a sister project (tonel-migration), and do not > have a proper resolution yet. I was forcing everything to be unicode, so I need > a better way to read and write encoded strings. :< I think this is always going to be a tricky problem since the file may simply be corrupt, and the resolution won't always be the same. In my case I was happy to simply remove the offending characters. I do think it would be nice if the migration tool at least stopped and warned the user that the input is invalid. Would you be open to a PR that incorporates Sven's changes suggested above? On Tue, Dec 05, 2017 at 09:05:24AM +0100, Sven Van Caekenberghe wrote: > > Maybe ZnCharacterEncoder class>>#detectEncoding: can help, although it > is far from perfect. In this particular case I think it is better to try decoding with UTF8, since #detectEncoding: isn't completely reliable and we just want to know if it isn't valid UTF8. Cheers, Alistair

Dec. 5, 2017

Re: [Pharo-dev] using Pharo 7 from Pharo Launcher gives warning about changes file

by Cyril Ferlicot

On mar. 5 dÃ©c. 2017 at 09:20, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > Just reinstalled pharo launcher new. > Select the Pharo 7 (development version) entry, > create an image and start it. > > It always shows a warning about the changes : > > " > Pharo cannot write to the changes file named > C:\Users\nicolai\Documents\Pharo\images\Pharo 7.0 (development > version)\Pharo 7.0 (development version).changes. > > Please check that you have write permission for this file. > > You won't be able to save this image correctly until you fix this." > > > But I can save the image, and reopening gives the same message. > > I don't know if this is an Pharo 7 or a Pharo Launcher issue, but > starting a pharo 6.1 image does not give this message. > Hi! Pavel found it comes from this PR yesterday: https://github.com/pharo-project/pharo/pull/553 Now we need to find what is the problem, probably locals initialization. > nicolai > > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Dec. 5, 2017

using Pharo 7 from Pharo Launcher gives warning about changes file

by Nicolai Hess

Just reinstalled pharo launcher new. Select the Pharo 7 (development version) entry, create an image and start it. It always shows a warning about the changes : " Pharo cannot write to the changes file named C:\Users\nicolai\Documents\Pharo\images\Pharo 7.0 (development version)\Pharo 7.0 (development version).changes. Please check that you have write permission for this file. You won't be able to save this image correctly until you fix this." But I can save the image, and reopening gives the same message. I don't know if this is an Pharo 7 or a Pharo Launcher issue, but starting a pharo 6.1 image does not give this message. nicolai

Dec. 5, 2017

Re: [Pharo-dev] [Moose-dev] feenk log

by Peter UhnÃ¡k

Great work guys! Even though I don't have much time to work with Bloc yet, every time I play with it, I find it really enjoyable. :) Also +1 for draggable elements, another thing to tick of my "must have" list. :) Peter

Dec. 5, 2017

Re: [Pharo-dev] Moving from mc to tonel?

by Sven Van Caekenberghe

> On 5 Dec 2017, at 08:59, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > In my case, it turned out to be a non-UTF8 encoded character in one of the commit messages. > > I've ran into this problem in a sister project (tonel-migration), and do not have a proper resolution yet. I was forcing everything to be unicode, so I need a better way to read and write encoded strings. :< Maybe ZnCharacterEncoder class>>#detectEncoding: can help, although it is far from perfect. > On Tue, Dec 5, 2017 at 8:56 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > On 5 Dec 2017, at 08:34, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > On 5 December 2017 at 03:41, Martin Dias <tinchodias(a)gmail.com> wrote: > >> I suspect it's related to the large number of commits in my repo. I made > >> some tweaks and succeeded to create the fast-import file. But I get: > >> > >> fatal: Unsupported command: . > >> fast-import: dumping crash report to .git/fast_import_crash_10301 > >> > >> Do you recognize this error? > >> I will check my changes tweaking the git-migration tool to see if I modified > >> some behavior my mistake... > > > > I had the same error just last night. > > > > In my case, it turned out to be a non-UTF8 encoded character in one of > > the commit messages. > > > > I tracked it down by looking at the crash report and searching for a > > nearby command. I've deleted the crash reports now, but I think it > > was the number associated with a mark command that got me near the > > problem character in the fast-import file. > > > > I also modified the code to halt whenever it found a non-UTF8 > > character. I'm sure there are better ways to do this, but: > > > > > > GitMigrationCommitInfo>>inlineDataFor: aString > > > > | theString | > > theString := aString. > > "Ensure the message has valid UTF-8 encoding (this will raise an > > error if it doesn't)" > > [ (ZnCharacterEncoder newForEncoding: 'utf8') decodeBytes: aString > > asByteArray ] > > on: Error > > do: [ :ex | self halt: 'Illegal string encoding'. > > theString := aString select: [ :each | each asciiValue > > between: 32 and: 128 ] ]. > > ^ 'data ' , theString size asString , String cr , (theString > > ifEmpty: [ '' ] ifNotEmpty: [ theString , String cr ]) > > There is also ByteArray>>#utf8Decoded (as well as String>>#utf8Encoded), both using the newer ZnCharacterEncoders. So you could write it shorter as: > > aString asByteArray utf8Decoded > > Instead of Error you could use the more intention revealing ZnCharacterEncodingError. > > Apart from that, and I known you did not create this mess, encoding a String into a String, although it can be done, is so wrong. You encode a String (a collection of Characters, of Unicode code points) into a ByteArray and you decode a ByteArray into a String. > > Sending #asByteArray to a String in almost always wrong, as is sending #asString to a ByteArray. These are implicit conversions (null conversions, like ZnNullEncoder) that only work for pure ASCII or Latin1 (iso-8859-1), but not for the much richer set of Characters that Pharo supports. So these will eventually fail, one day, in a country far away. > > > Cheers, > > Alistair > > > > >

Dec. 5, 2017

Re: [Pharo-dev] Moving from mc to tonel?

by Peter UhnÃ¡k

> In my case, it turned out to be a non-UTF8 encoded character in one of the commit messages. I've ran into this problem in a sister project (tonel-migration), and do not have a proper resolution yet. I was forcing everything to be unicode, so I need a better way to read and write encoded strings. :< On Tue, Dec 5, 2017 at 8:56 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > On 5 Dec 2017, at 08:34, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > On 5 December 2017 at 03:41, Martin Dias <tinchodias(a)gmail.com> wrote: > >> I suspect it's related to the large number of commits in my repo. I made > >> some tweaks and succeeded to create the fast-import file. But I get: > >> > >> fatal: Unsupported command: . > >> fast-import: dumping crash report to .git/fast_import_crash_10301 > >> > >> Do you recognize this error? > >> I will check my changes tweaking the git-migration tool to see if I > modified > >> some behavior my mistake... > > > > I had the same error just last night. > > > > In my case, it turned out to be a non-UTF8 encoded character in one of > > the commit messages. > > > > I tracked it down by looking at the crash report and searching for a > > nearby command. I've deleted the crash reports now, but I think it > > was the number associated with a mark command that got me near the > > problem character in the fast-import file. > > > > I also modified the code to halt whenever it found a non-UTF8 > > character. I'm sure there are better ways to do this, but: > > > > > > GitMigrationCommitInfo>>inlineDataFor: aString > > > > | theString | > > theString := aString. > > "Ensure the message has valid UTF-8 encoding (this will raise an > > error if it doesn't)" > > [ (ZnCharacterEncoder newForEncoding: 'utf8') decodeBytes: aString > > asByteArray ] > > on: Error > > do: [ :ex | self halt: 'Illegal string encoding'. > > theString := aString select: [ :each | each asciiValue > > between: 32 and: 128 ] ]. > > ^ 'data ' , theString size asString , String cr , (theString > > ifEmpty: [ '' ] ifNotEmpty: [ theString , String cr ]) > > There is also ByteArray>>#utf8Decoded (as well as String>>#utf8Encoded), > both using the newer ZnCharacterEncoders. So you could write it shorter as: > > aString asByteArray utf8Decoded > > Instead of Error you could use the more intention revealing > ZnCharacterEncodingError. > > Apart from that, and I known you did not create this mess, encoding a > String into a String, although it can be done, is so wrong. You encode a > String (a collection of Characters, of Unicode code points) into a > ByteArray and you decode a ByteArray into a String. > > Sending #asByteArray to a String in almost always wrong, as is sending > #asString to a ByteArray. These are implicit conversions (null conversions, > like ZnNullEncoder) that only work for pure ASCII or Latin1 (iso-8859-1), > but not for the much richer set of Characters that Pharo supports. So these > will eventually fail, one day, in a country far away. > > > Cheers, > > Alistair > > > > >

Dec. 5, 2017

Re: [Pharo-dev] Moving from mc to tonel?

by Peter UhnÃ¡k

> I suspect it's related to the large number of commits in my repo. I made > some tweaks and succeeded to create the fast-import file. But I get: > All files in a single commit will be held temporarily in MemoryStore, so unless you have GBs of code in _single_ commit it shouldn't be a problem. There's also a possiblity that Pharo was going too fast and didn't manage to GC it in time or there's a memory leak. > > fatal: Unsupported command: . > fast-import: dumping crash report to .git/fast_import_crash_10301 > > Do you recognize this error? > Please look into the mentioned file, it should give you a context for the error (and then you can look into the import file around the same context). Peter

Dec. 5, 2017

Re: [Pharo-dev] Moving from mc to tonel?

by Sven Van Caekenberghe

> On 5 Dec 2017, at 08:34, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > On 5 December 2017 at 03:41, Martin Dias <tinchodias(a)gmail.com> wrote: >> I suspect it's related to the large number of commits in my repo. I made >> some tweaks and succeeded to create the fast-import file. But I get: >> >> fatal: Unsupported command: . >> fast-import: dumping crash report to .git/fast_import_crash_10301 >> >> Do you recognize this error? >> I will check my changes tweaking the git-migration tool to see if I modified >> some behavior my mistake... > > I had the same error just last night. > > In my case, it turned out to be a non-UTF8 encoded character in one of > the commit messages. > > I tracked it down by looking at the crash report and searching for a > nearby command. I've deleted the crash reports now, but I think it > was the number associated with a mark command that got me near the > problem character in the fast-import file. > > I also modified the code to halt whenever it found a non-UTF8 > character. I'm sure there are better ways to do this, but: > > > GitMigrationCommitInfo>>inlineDataFor: aString > > | theString | > theString := aString. > "Ensure the message has valid UTF-8 encoding (this will raise an > error if it doesn't)" > [ (ZnCharacterEncoder newForEncoding: 'utf8') decodeBytes: aString > asByteArray ] > on: Error > do: [ :ex | self halt: 'Illegal string encoding'. > theString := aString select: [ :each | each asciiValue > between: 32 and: 128 ] ]. > ^ 'data ' , theString size asString , String cr , (theString > ifEmpty: [ '' ] ifNotEmpty: [ theString , String cr ]) There is also ByteArray>>#utf8Decoded (as well as String>>#utf8Encoded), both using the newer ZnCharacterEncoders. So you could write it shorter as: aString asByteArray utf8Decoded Instead of Error you could use the more intention revealing ZnCharacterEncodingError. Apart from that, and I known you did not create this mess, encoding a String into a String, although it can be done, is so wrong. You encode a String (a collection of Characters, of Unicode code points) into a ByteArray and you decode a ByteArray into a String. Sending #asByteArray to a String in almost always wrong, as is sending #asString to a ByteArray. These are implicit conversions (null conversions, like ZnNullEncoder) that only work for pure ASCII or Latin1 (iso-8859-1), but not for the much richer set of Characters that Pharo supports. So these will eventually fail, one day, in a country far away. > Cheers, > Alistair >

Dec. 5, 2017

Re: [Pharo-dev] Moving from mc to tonel?

by Alistair Grant

On 5 December 2017 at 03:41, Martin Dias <tinchodias(a)gmail.com> wrote: > I suspect it's related to the large number of commits in my repo. I made > some tweaks and succeeded to create the fast-import file. But I get: > > fatal: Unsupported command: . > fast-import: dumping crash report to .git/fast_import_crash_10301 > > Do you recognize this error? > I will check my changes tweaking the git-migration tool to see if I modified > some behavior my mistake... I had the same error just last night. In my case, it turned out to be a non-UTF8 encoded character in one of the commit messages. I tracked it down by looking at the crash report and searching for a nearby command. I've deleted the crash reports now, but I think it was the number associated with a mark command that got me near the problem character in the fast-import file. I also modified the code to halt whenever it found a non-UTF8 character. I'm sure there are better ways to do this, but: GitMigrationCommitInfo>>inlineDataFor: aString | theString | theString := aString. "Ensure the message has valid UTF-8 encoding (this will raise an error if it doesn't)" [ (ZnCharacterEncoder newForEncoding: 'utf8') decodeBytes: aString asByteArray ] on: Error do: [ :ex | self halt: 'Illegal string encoding'. theString := aString select: [ :each | each asciiValue between: 32 and: 128 ] ]. ^ 'data ' , theString size asString , String cr , (theString ifEmpty: [ '' ] ifNotEmpty: [ theString , String cr ]) Cheers, Alistair

Dec. 5, 2017

Re: [Pharo-dev] Pharo newsletter archive

by Tudor Girba

+1 Doru > On Dec 5, 2017, at 7:54 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Yes good idea! > Tx > > On Mon, Dec 4, 2017 at 7:52 PM, Torsten Bergmann <astares(a)gmx.de> wrote: >> Hi, >> >> the newsletter archive is now available on >> >> "newsletter.pharo.org" >> >> which is more easy to remember. >> >> Thanks Marcus for setting up the redirect! >> >> Bye >> T. >> > -- www.tudorgirba.com www.feenk.com "When people care, great things can happen."

Dec. 5, 2017

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo TechTalk 21 Nov: Discord Demo

by Tudor Girba

Thanks! Doru > On Nov 23, 2017, at 8:26 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > Hi, the new version is available here: https://www.youtube.com/watch?v=y1EzOnfHUe0 > > Hopefully it helps :-) > Juraj > >> On Nov 22, 2017, at 15:45, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> Juraj Kubelka wrote >>> I will upload recording I have on my computer. It is clear. >> >> Thanks! >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >> > -- www.tudorgirba.com www.feenk.com "Value is always contextual."

Dec. 5, 2017

Re: [Pharo-dev] Pharo newsletter archive

by Stephane Ducasse

Yes good idea! Tx On Mon, Dec 4, 2017 at 7:52 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > the newsletter archive is now available on > > "newsletter.pharo.org" > > which is more easy to remember. > > Thanks Marcus for setting up the redirect! > > Bye > T. >

Dec. 5, 2017

Re: [Pharo-dev] Moving from mc to tonel?

by Martin Dias

I suspect it's related to the large number of commits in my repo. I made some tweaks and succeeded to create the fast-import file. But I get: fatal: Unsupported command: . fast-import: dumping crash report to .git/fast_import_crash_10301 Do you recognize this error? I will check my changes tweaking the git-migration tool to see if I modified some behavior my mistake... cheers, MartÃn On Fri, Dec 1, 2017 at 1:42 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > Julien, I dodn't know it but anyway my issue was just in the step > smalltalkhub -> filtree using the migration tool. > > Peter, yes it's public. This is the code I used: > > ---------------------------------------- > > migration := GitMigration on: 'MartinDias/Epicea'. > migration cacheAllVersions. > migration authors: { > 'md' -> #('Martin Dias' '<tinchodias(a)gmail.com>'). > 'MD' -> #('Martin Dias' '<tinchodias(a)gmail.com>'). > 'MartinDias' -> #('Martin Dias' '<tinchodias(a)gmail.com>'). > 'PabloTesone' -> #('Pablo Tesone' '<tesonep(a)gmail.com>'). > 'PavelKrivanek' -> #('Pavel Krivanek' '<pavel.krivanek(a)gmail.com>'). > 'DamienCassou' -> #('Damien Cassou' '<DamienCassou(a)gmail.com>'). > 'DenisKudryashov' -> #('Denis Kudryashov' '<dionisiydk(a)gmail.com>'). > 'GustavoSantos' -> #('Gustavo Santos' '<gugajansen(a)gmail.com>'). > 'ThomasHeniart' -> #('Thomas Heniart' '<heniart.thomas(a)gmail.com>'). > 'LucasGodoy' -> #('Lucas Godoy' '<godoy.lucas(a)gmail.com>'). > 'StephaneDucasse' -> #('Stephane Ducasse' '<stephane.ducasse(a)inria.fr>'). > 'VincentBlondeau' -> #('Vincent Blondeau' '<vincent.blondeau(a)inria.fr>'). > 'AlbertoBacchelli' -> #('Alberto Bacchelli' '<sbackg(a)gmail.com>'). > 'SkipLentz' -> #('Skip Lentz' '<skippetie(a)gmail.com>'). > 'TheIntegrator' -> #('The Integrator' '<integrator(a)fake.com>'). > }.l > migration > fastImportCodeToDirectory: 'src' > initialCommit: '18a30d8d' > to: './epicea-fast-import.txt' > > ---------------------- > > MartÃn > > On Thu, Nov 30, 2017 at 2:14 PM, Julien <julien.delplanque(a)inria.fr> > wrote: > >> If you use Traits and want to have Epicea loadable from GitHub on Pharo >> 6.1, it will not work. >> >> There is an issue when you try to load a Trait in Tonel format in the >> image. >> >> --- >> Julien Delplanque >> Doctorant Ã lâUniversitÃ© de Lille 1 >> http://juliendelplanque.be/phd.html >> Equipe Rmod, Inria >> BÃ¢timent B 40, avenue Halley 59650 >> <https://maps.google.com/?q=40,+avenue+Halley+59650%C2%A0Villeneuve%C2%A0d'Ascq&entry=gmail&source=g> >> Villeneuve >> <https://maps.google.com/?q=40,+avenue+Halley+59650%C2%A0Villeneuve%C2%A0d'Ascq&entry=gmail&source=g> >> d'Ascq >> <https://maps.google.com/?q=40,+avenue+Halley+59650%C2%A0Villeneuve%C2%A0d'Ascq&entry=gmail&source=g> >> NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 >> >> Le 6 nov. 2017 Ã 01:42, Martin Dias <tinchodias(a)gmail.com> a Ã©crit : >> >> Hi all, I'm considering to move Epicea (+Ombu+Hiedra) to github. I read >> that tonel is the new format and there is Peter's git-migration, which >> could be the tool to do it. >> >> Is it good idea to move now? >> Is it the right tool? >> >> Bests, >> MartÃn >> >> >> >

Dec. 5, 2017

Re: [Pharo-dev] [Vm-dev] Garbage Collection (was Re: Discussing the roadmap)

by Ben Coman

Hi Eliot, On 4 December 2017 at 23:44, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Alas a forwarding object has two fields that need to be set in separate words. > The class index in the header must be the forwarder class index, > and the first word of the object body must point to the forwarder. Good to better understand that. Just restating after condensing most of the thread, only the Main-thread would convert objects to forwarders. > Reverting obviously requires two writes too. So atomic (un)forwarding is not possible. sorry, just double-checking since I realised I erred in my example below, which may have mislead your response. IIUC(now)... while "creating" a forwarder involves writing separately to object-header and object-body. wouldn't "reverting" only involve updating an object-pointer in a slot to the real-object's new location? And that would be a single word operation on both 32bit and 64bit platforms? > >> - Currently the marking phase removes all forwarders and I would like incremental marking to maintain the same invariant (forwarders are always white). > > > > A concurrent-marking thread could essentially do the same. > > i. From shared memory load forward header Fh from object-slot > > Fheader <== object-slot > > ii. Follow forwarder to real-object, store into local temporary > > Rheader <== flattened/followed pointer > > > > iii. Atomic compare-and-swap R back into object-slot, > > object-slot <== if Fheader then Rheader whoops, corrected... i. From shared memory, concurrent marking-scan has loaded an object-pointer from object-slot. If it points to a forwarding object ... Opointer <== object-slot (as part of normal marking scan) if *Opointer isForwardingObject { Fpointer <== Opointer (redundant, just for clarity) ii. Follow that to real-object, store into local temporary Rpointer <== followed Fpointer forwarding chain to real object. iii. Atomic compare-and-swap Rpointer back into object-slot object-slot <== if still Fpointer then Rpointer When (iii.) fails * If I'm the Main-thread, I'm in the middle of handling a failed forwarder-check and can infer the GC-thread already did what I was going to do. I can be certain that... "object-slot == Rpointer" (since thats the only object-slot mutation GC-threads can do) so its fine to continue to my usual post-flattening retry * If I'm a GC-thread, either: * the Main-thread flattened the forwarder, or * the Main-thread changed which object the slot holds In either case, just re-read the slot A race scenario to consider is where the Main-thread converts an object to a forwarder simultaneous with a GC-thread flattening one of its slots. The object copy in its new location may miss that update. But in terms of the object graph that seems not a problem, since the copy without that update is still consistent. Infrequently just a little bit of work is lost. I'm contemplating other race scenarios around marking, but won't distract with them for now. cheers -ben

Dec. 5, 2017

Re: [Pharo-dev] Bloc Feedback

by Ben Coman

On 5 December 2017 at 05:19, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi Aliaksei > > Read again this sentence :) > > "BlPostAction" - a valuable that is guaranteed to be evaluated in the > beginning of every frame before anything else. > > MAy be BlPostAction should be renamed BlEarlyAction > BlPreAction > > > > On Sat, Dec 2, 2017 at 5:26 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> > wrote: > > Hi, > > > > An object that is called now "Animation" in Bloc is not necessarily > bound to > > the visual element. > > The correct name for the root class of "BlBaseAnimation" should be > > "BlPostAction" - a valuable that is guaranteed to be evaluated in the > > beginning of every frame before anything else. We have already a deferred > > action but they are only evaluated when there is enough time between > frames. > > "BlBaseAnimation" should be renamed to something line > "BlElementAnimation" > > that is guaranteed to be bound to a visual element and stops itself if > > element is no more in the scene graph by checking that explicitly before > > doing every animation step. > > > > Cheers, > > Alex > > > > On 2 December 2017 at 16:35, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > >> > >> Aliaksei Syrel wrote > >> > ... > >> > Also, what is the lifetime of an infinite animation? > >> > ... > >> > Do you have any particular use-case for animations? > >> > >> I hacked together a simplified stepping animation (may not be in the > right > >> place in the class hierarchy). Here's a pull request to discuss > >> https://github.com/pharo-graphics/Bloc/pull/37 > >> > >> > >> > >> ----- > >> Cheers, > >> Sean > >> -- > >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837. > html > >> > > > >

Dec. 4, 2017

Re: [Pharo-dev] Polymorphism between Strings and FileReference

by Stephane Ducasse

To me stringOfFileReference is a bad smell. On Fri, Dec 1, 2017 at 12:04 PM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > On Fri, Dec 1, 2017 at 11:55 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> Hi Cyril, >> >> The normal way to handle this is #asFileReference, so you can just have: >> >> aStringOrReference asFileReference readStreamDo: ... >> > > In that case, if it is a String like 'test', we will get a readStream > on the file './test' and not on the string 'test'. This is not what I > want. > > What I want is this for example: > > > > MyClass>>addComaAtTheEndOf: aStringOrFileReference > "If the argument is a String, add a coma at the end. If the > parameter is a file, add a coma at the end of its contents" > > aStringOrFileReference writeStreamDo: [ :s | s atEnd; nextPut: $, ] > > > > If I use your code, it will not add a coma at the end of the string > parameter, but at the end of the file represented by the string if it > exists. > >> Cheers, >> Alistair >> > > > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

Dec. 4, 2017

Re: [Pharo-dev] [TechTalk] Topics Wanted for 2018!

by Stephane Ducasse

I could show how to setup a pillar project. Stef On Fri, Dec 1, 2017 at 11:58 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > As you know, we are trying to have one Pharo tech-talk per month. > > The idea is to use this for > -> mini âLecturesâ > -> Demos of interesting Projects > -> Just some interesting topic to discuss with audio chat on Discord > > You can see the past topics here: > > http://pharo.org/TechTalk > > We will soon define the dates for the first half of 2018. If you want to do > a techtalk > yourself (give a presentation / Demo or moderate a discussion), feel free to > contact > me! You are able to pick a date that works best for you. > > > Marcus

Dec. 4, 2017