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

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50300 Home: https://github.com/pharo-project/pharo-core

Sept. 3, 2015

[pharo-project/pharo-core] 770358: 50300

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 77035832f5bcfbf49f088eb2f0b20f9d865b6a29 https://github.com/pharo-project/pharo-core/commit/77035832f5bcfbf49f088eb2… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-03 (Thu, 03 Sep 2015) Changed paths: M CodeImport.package/ChunkFileFormatParser.class/definition.st A CodeImport.package/ChunkFileFormatParser.class/instance/class factory/classCommentChunkClass.st A CodeImport.package/ChunkFileFormatParser.class/instance/class factory/classOrganisationChunkClass.st A CodeImport.package/ChunkFileFormatParser.class/instance/class factory/doItChunkClass.st A CodeImport.package/ChunkFileFormatParser.class/instance/class factory/methodChunkClass.st A CodeImport.package/ChunkFileFormatParser.class/instance/class factory/styleChunkClass.st A CodeImport.package/ChunkFileFormatParser.class/instance/custom points/classSelector.st A CodeImport.package/ChunkFileFormatParser.class/instance/custom points/classSelector_.st A CodeImport.package/ChunkFileFormatParser.class/instance/custom points/classTraitSelector.st A CodeImport.package/ChunkFileFormatParser.class/instance/custom points/classTraitSelector_.st A CodeImport.package/ChunkFileFormatParser.class/instance/custom points/commentStampSelector.st A CodeImport.package/ChunkFileFormatParser.class/instance/custom points/commentStampSelector_.st A CodeImport.package/ChunkFileFormatParser.class/instance/custom points/methodsForSelector.st A CodeImport.package/ChunkFileFormatParser.class/instance/custom points/methodsForSelector_.st A CodeImport.package/ChunkFileFormatParser.class/instance/custom points/reorganizeSelector.st A CodeImport.package/ChunkFileFormatParser.class/instance/custom points/reorganizeSelector_.st A CodeImport.package/ChunkFileFormatParser.class/instance/initialization/defaultClassSelector.st A CodeImport.package/ChunkFileFormatParser.class/instance/initialization/defaultClassTraitSelector.st A CodeImport.package/ChunkFileFormatParser.class/instance/initialization/defaultCommentStampSelector.st A CodeImport.package/ChunkFileFormatParser.class/instance/initialization/defaultMethodsForSelector.st A CodeImport.package/ChunkFileFormatParser.class/instance/initialization/defaultReorganizeSelector.st M CodeImport.package/ChunkFileFormatParser.class/instance/initialization/initialize.st M CodeImport.package/ChunkFileFormatParser.class/instance/parsing/parseChunks.st M CodeImport.package/ChunkFileFormatParser.class/instance/parsing/parseClassOrganization_.st M CodeImport.package/ChunkFileFormatParser.class/instance/parsing/parseCommentDeclaration_.st M CodeImport.package/ChunkFileFormatParser.class/instance/parsing/parseMethodDeclarations_.st M CodeImport.package/ChunkFileFormatParser.class/instance/parsing/parseNextDeclaration.st R Morphic-Base.package/MenuItemMorph.class/instance/accessing/itemWithWording_.st M Morphic-Base.package/MenuMorph.class/definition.st A Morphic-Base.package/MenuMorph.class/instance/accessing/defaultTarget_.st M Morphic-Base.package/MenuMorph.class/instance/accessing/embeddable.st M Morphic-Base.package/MenuMorph.class/instance/accessing/embeddable_.st R Morphic-Base.package/MenuMorph.class/instance/accessing/itemWithWording_.st A Morphic-Base.package/MenuMorph.class/instance/construction-title/addStayUpIcons.st A Morphic-Base.package/MenuMorph.class/instance/construction-title/addStayUpItem.st A Morphic-Base.package/MenuMorph.class/instance/construction-title/addTitle_.st A Morphic-Base.package/MenuMorph.class/instance/construction-title/addTitle_icon_.st A Morphic-Base.package/MenuMorph.class/instance/construction-title/newTitleIconCalling_form_ballonText_.st R Morphic-Base.package/MenuMorph.class/instance/construction/addStayUpIcons.st R Morphic-Base.package/MenuMorph.class/instance/construction/addStayUpItem.st R Morphic-Base.package/MenuMorph.class/instance/construction/addTitle_.st R Morphic-Base.package/MenuMorph.class/instance/construction/addTitle_icon_.st R Morphic-Base.package/MenuMorph.class/instance/construction/defaultTarget_.st A Morphic-Base.package/MenuMorph.class/instance/events/pinboxClicked.st R Morphic-Base.package/MenuMorph.class/instance/initialization/defaultBounds.st R Morphic-Base.package/MenuMorph.class/instance/keyboard control/selectMoreItem_.st M NautilusRefactoring.package/NautilusRefactoring.class/instance/private-method/privateRemoveParameterMethodFor_.st M Refactoring-Core.package/RBRemoveParameterRefactoring.class/instance/transforming/getNewSelector.st A SUnit-UITesting.package/extension/MenuItemMorph/instance/itemWithWording_.st A SUnit-UITesting.package/extension/MenuMorph/instance/itemWithWording_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50299.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50300.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50299.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50300.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50300 16461 ChunkFileParser https://pharo.fogbugz.com/f/cases/16461 16459 Refactoring remove method parameter doesnt work https://pharo.fogbugz.com/f/cases/16459 16457 Minor improvements to MenuMorph https://pharo.fogbugz.com/f/cases/16457 http://files.pharo.org/image/50/50300.zip

Sept. 3, 2015

Re: [Pharo-dev] size of MCbrowser should be proportional

by Esteban Lorenzano

+1 I also submitted an issue about MCBrowser not taking into account the size of the world window (and then appearing with part of it hidden out of the visible area) > On 02 Sep 2015, at 10:07, stepharo <stepharo(a)free.fr> wrote: > > Hi guys > > now when I open MCBrowser it gets 80% of my window. > So this is good to make it larger but it should be proportional to the actual size. > > https://pharo.fogbugz.com/f/cases/16451/MCBrowser-default-size-should-propo… > Could the person that originally changed it fix it? > > Stef >

Sept. 3, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] 91327c: 50299

by Marcus Denker

this is: 16464 Smart suggestion is broken https://pharo.fogbugz.com/f/cases/16464 16458 #instead for MethodNode https://pharo.fogbugz.com/f/cases/16458 16455 Spotter dying on not understanding #canUnderstand: https://pharo.fogbugz.com/f/cases/16455 <https://pharo.fogbugz.com/f/cases/16455> > > Log Message: > ----------- > 50299 > ConfigurationOfRubric > > http://files.pharo.org/image/50/50299.zip > >

Sept. 3, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50299 Home: https://github.com/pharo-project/pharo-core

Sept. 3, 2015

[pharo-project/pharo-core] 91327c: 50299

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 91327c96398da12d50ffe960fa8c88b99315b8e3 https://github.com/pharo-project/pharo-core/commit/91327c96398da12d50ffe960… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-03 (Thu, 03 Sep 2015) Changed paths: M ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/symbolic versions/stable_.st A ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/versions/version1211_.st A ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/versions/version307_.st M GT-Spotter-EventRecorder.package/GTSpotterEventRecorder.class/instance/events/recordAccouncement_.st A GT-Spotter-EventRecorder.package/GTSpotterEventRecorder.class/instance/events/recordAnnouncement_.st M GT-Spotter-EventRecorder.package/GTSpotterEventRecorder.class/instance/initialization/linkToSpotter_.st A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - instead/testInsteadMethod.st M Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitMethodNode_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50298.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50299.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50298.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50299.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M SmartSuggestions.package/SugsNautilusContext.class/instance/refactoring/contentSelection.st M SmartSuggestions.package/SugsNautilusContext.class/instance/refactoring/flashSourceCodeArea.st M SmartSuggestions.package/SugsNautilusContext.class/instance/refactoring/formatSourceCode.st M SmartSuggestions.package/SugsNautilusContext.class/instance/refactoring/selectTheTextForTheNode.st M SmartSuggestions.package/SugsNautilusContext.class/instance/refactoring/selectionInterval.st Log Message: ----------- 50299 ConfigurationOfRubric http://files.pharo.org/image/50/50299.zip

Sept. 3, 2015

Re: [Pharo-dev] Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp

by Sven Van Caekenberghe

> On 03 Sep 2015, at 06:01, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > > On 9/2/15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> But Timestamp was already removed completely from 4.0, why re-add it, even >> deprecated ? > > Because it will be added in a compatibility layer package which is > only loaded by packages which need it. There might be other things in > the Pharo 5/4 compatibility package. But still, if external packages do load that code, they will never have to change, and the class will remain in the image forever. It is like when you load certain Squeak packages that are 'ported' with compatibility layers to Pharo: they just add again all the methods that we tried to clean up. > --HH > >> I am sure many external packages are already modified, I know I did it for >> mine. > >>> On 02 Sep 2015, at 13:19, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> >>>> On 02 Sep 2015, at 12:32, stepharo <stepharo(a)free.fr> wrote: >>>> >>>> Hi guille >>>> >>>> there is not stress. I just wanted to let you know. >>>> I was wondering if just subclassing DateAndTime would not be enough for >>>> now. >>> >>> Yes, as far as I remember Timestamp was just an empy subclass. >>> >>> We could: >>> >>> -> add it back to Deprecated50 or maybe even to a âCompatibilityâ package >>> -> Write a Quality Check rule. >>> >>>> I will go back to code with Pharo 40 >>>> >>>> stef >>>> >>>> Le 2/9/15 10:30, Guillermo Polito a Ã©crit : >>>>> If somebody can check it and fix it it would be good :). I've just >>>>> started my new job and my evenings are busy looking for an apartment or >>>>> staying in a hostel without a proper internet connection... >>>>> >>>>> If not, I think we can wait a bit. The first step should be enabling CI >>>>> jobs for pharo5. Also, I do not think the intersection between 'people >>>>> using garage opendbx' and 'people using pharo5' is that big to justify a >>>>> rush. >>>>> >>>>> Guille >>>>> >>>>> El miÃ©., 2 de sept. de 2015 a la(s) 10:12 a. m., stepharo >>>>> <stepharo(a)free.fr> escribiÃ³: >>>>> for your info... >>>>> >>>>> Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp >>>>> >>>>> Stef >>>>> >>>> >>> >> >> >> >

Sept. 3, 2015

Re: [Pharo-dev] block brace alignment (Re: feedback from J Brant)

by Sven Van Caekenberghe

And what happened to the plain normal (in my mind/experience) ? self xxx ifTrue: [ self bla. self foo ]. I would say that is the most common one I've seen in the image. And it is how the old formatter worked. > On 03 Sep 2015, at 03:39, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Ben, > > have you read Kent Beck's formatting rules? I wish we would adhere to these in our formatters. And I wish he would put the formatting rules in the public domain on the web (Kent?). He actually justifies the rules he chooses; they're not just personal preferences. And IMO they produce eleant, readable Smalltalk. I have to say your block formatting below is horrible. Blocks are blocks. [ & ] are /not/ the same as { & } in C. [...] define an *object*, not merely delimit syntax. As such any good Smalltalk format will emphasize the objectness of blocks. And IMNERHO that is to make them rectangles as in > > self ifIWantedYouToWriteC ifTrue: > [self useABloodyCCompiler. > self useCCMinusPToMakeSenseOfTheDamageDoneByTheCPreProcessor] > > > On Wed, Sep 2, 2015 at 6:23 PM, Ben Coman <btc(a)openinworld.com> wrote: > On Thu, Sep 3, 2015 at 2:28 AM, stepharo <stepharo(a)free.fr> wrote: > > > > I do not really like all the formattings of kent. Because sometimes it just > > does not work. > > But this is why we ask franck (an interns to start to have a look). > > > > For example I do not like > > > > self xxx > > ifTrue: > > [ > > self bla > > self foo. > > Agreed. Unneccessary waste of a line. > > > in the current default formatter. > > and I prefer > > > > self xxx > > ifTrue: [ self bla. > > self foo > > But here the problem is that the self foo is not tab aligned because > > ifTrue: [ > > > > self xxx > > ifTrue: > > [ self bla. > > self foo > > So may be this one is a nice compromise > > Not quite there. The "self bla" is still not actually vertically aligned. > > > I think that we should change some settings. In fact in alpha things are > > there to evolve until the release :) > > I like... > self xxx > ifTrue: > [ self bla. > self foo. > ]. > > for three reasons: > * the first statement of the block is vertically aligned with the rest > * vertical alignment of paired brackets makes visual matching *simple* > * the vertical whitespace enforced by the closing bracket on its > own visually groups blocks. > > Now some people don't like the closing brace on its own because they > prefer code density. So maybe this... > > self xxx > ifTrue: > [ self bla. > self foo. ] > ifFalse: > [ self baa. > self moo. ]. > > But still I prefer... > > self xxx > ifTrue: > [ self bla. > self foo. > ] > ifFalse: > [ self baa. > self moo. > ]. > > cheers -ben > > > > > -- > _,,,^..^,,,_ > best, Eliot

Sept. 3, 2015

Re: [Pharo-dev] GitFileTree: Playing Nice with FileTree

by Thierry Goubier

Hi Sean, Le 03/09/2015 04:29, Sean P. DeNigris a Ã©crit : > If I have a filetree://path/to/canonical/local/repo repository, can I later > point a GitFileTree repo to that folder? From the MC Browser +Repository > menu, I only seem to be able to set the subfolder relative to the > #imageDirectory, not the absolute pathâ¦ Are you sure about the local path? I know I played with a few things to try to get local paths to work if used. But gitfiletree://path/to/canonical/local/repo will work. Thierry

Sept. 3, 2015

Re: [Pharo-dev] Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp

by H. Hirzel

On 9/2/15, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> On 02 Sep 2015, at 12:32, stepharo <stepharo(a)free.fr> wrote: >> >> Hi guille >> >> there is not stress. I just wanted to let you know. >> I was wondering if just subclassing DateAndTime would not be enough for >> now. > > Yes, as far as I remember Timestamp was just an empy subclass. > > We could: > > -> add it back to Deprecated50 or maybe even to a âCompatibilityâ package +1 > -> Write a Quality Check rule. > >> I will go back to code with Pharo 40 >> >> stef >> >> Le 2/9/15 10:30, Guillermo Polito a Ã©crit : >>> If somebody can check it and fix it it would be good :). I've just >>> started my new job and my evenings are busy looking for an apartment or >>> staying in a hostel without a proper internet connection... >>> >>> If not, I think we can wait a bit. The first step should be enabling CI >>> jobs for pharo5. Also, I do not think the intersection between 'people >>> using garage opendbx' and 'people using pharo5' is that big to justify a >>> rush. >>> >>> Guille >>> >>> El miÃ©., 2 de sept. de 2015 a la(s) 10:12 a. m., stepharo >>> <stepharo(a)free.fr <mailto:stepharo@free.fr>> escribiÃ³: >>> for your info... >>> >>> Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp >>> >>> Stef >>> >> > >

Sept. 3, 2015

Re: [Pharo-dev] Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp

by H. Hirzel

On 9/2/15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > But Timestamp was already removed completely from 4.0, why re-add it, even > deprecated ? Because it will be added in a compatibility layer package which is only loaded by packages which need it. There might be other things in the Pharo 5/4 compatibility package. --HH > I am sure many external packages are already modified, I know I did it for > mine. >> On 02 Sep 2015, at 13:19, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >>> On 02 Sep 2015, at 12:32, stepharo <stepharo(a)free.fr> wrote: >>> >>> Hi guille >>> >>> there is not stress. I just wanted to let you know. >>> I was wondering if just subclassing DateAndTime would not be enough for >>> now. >> >> Yes, as far as I remember Timestamp was just an empy subclass. >> >> We could: >> >> -> add it back to Deprecated50 or maybe even to a âCompatibilityâ package >> -> Write a Quality Check rule. >> >>> I will go back to code with Pharo 40 >>> >>> stef >>> >>> Le 2/9/15 10:30, Guillermo Polito a Ã©crit : >>>> If somebody can check it and fix it it would be good :). I've just >>>> started my new job and my evenings are busy looking for an apartment or >>>> staying in a hostel without a proper internet connection... >>>> >>>> If not, I think we can wait a bit. The first step should be enabling CI >>>> jobs for pharo5. Also, I do not think the intersection between 'people >>>> using garage opendbx' and 'people using pharo5' is that big to justify a >>>> rush. >>>> >>>> Guille >>>> >>>> El miÃ©., 2 de sept. de 2015 a la(s) 10:12 a. m., stepharo >>>> <stepharo(a)free.fr> escribiÃ³: >>>> for your info... >>>> >>>> Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp >>>> >>>> Stef >>>> >>> >> > > >

Sept. 3, 2015

GitFileTree: Playing Nice with FileTree

by Sean P. DeNigris

If I have a filetree://path/to/canonical/local/repo repository, can I later point a GitFileTree repo to that folder? From the MC Browser +Repository menu, I only seem to be able to set the subfolder relative to the #imageDirectory, not the absolute pathâ¦ ----- Cheers, Sean -- View this message in context: http://forum.world.st/GitFileTree-Playing-Nice-with-FileTree-tp4847786.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 3, 2015

Re: [Pharo-dev] block brace alignment (Re: feedback from J Brant)

by Eliot Miranda

Hi Ben, have you read Kent Beck's formatting rules? I wish we would adhere to these in our formatters. And I wish he would put the formatting rules in the public domain on the web (Kent?). He actually justifies the rules he chooses; they're not just personal preferences. And IMO they produce eleant, readable Smalltalk. I have to say your block formatting below is horrible. Blocks are blocks. [ & ] are /not/ the same as { & } in C. [...] define an *object*, not merely delimit syntax. As such any good Smalltalk format will emphasize the objectness of blocks. And IMNERHO that is to make them rectangles as in self ifIWantedYouToWriteC ifTrue: [self useABloodyCCompiler. self useCCMinusPToMakeSenseOfTheDamageDoneByTheCPreProcessor] On Wed, Sep 2, 2015 at 6:23 PM, Ben Coman <btc(a)openinworld.com> wrote: > On Thu, Sep 3, 2015 at 2:28 AM, stepharo <stepharo(a)free.fr> wrote: > > > > I do not really like all the formattings of kent. Because sometimes it > just > > does not work. > > But this is why we ask franck (an interns to start to have a look). > > > > For example I do not like > > > > self xxx > > ifTrue: > > [ > > self bla > > self foo. > > Agreed. Unneccessary waste of a line. > > > in the current default formatter. > > and I prefer > > > > self xxx > > ifTrue: [ self bla. > > self foo > > But here the problem is that the self foo is not tab aligned because > > ifTrue: [ > > > > self xxx > > ifTrue: > > [ self bla. > > self foo > > So may be this one is a nice compromise > > Not quite there. The "self bla" is still not actually vertically aligned. > > > I think that we should change some settings. In fact in alpha things are > > there to evolve until the release :) > > I like... > self xxx > ifTrue: > [ self bla. > self foo. > ]. > > for three reasons: > * the first statement of the block is vertically aligned with the rest > * vertical alignment of paired brackets makes visual matching *simple* > * the vertical whitespace enforced by the closing bracket on its > own visually groups blocks. > > Now some people don't like the closing brace on its own because they > prefer code density. So maybe this... > > self xxx > ifTrue: > [ self bla. > self foo. ] > ifFalse: > [ self baa. > self moo. ]. > > But still I prefer... > > self xxx > ifTrue: > [ self bla. > self foo. > ] > ifFalse: > [ self baa. > self moo. > ]. > > cheers -ben > > -- _,,,^..^,,,_ best, Eliot

Sept. 3, 2015

block brace alignment (Re: feedback from J Brant)

by Ben Coman

On Thu, Sep 3, 2015 at 2:28 AM, stepharo <stepharo(a)free.fr> wrote: > > I do not really like all the formattings of kent. Because sometimes it just > does not work. > But this is why we ask franck (an interns to start to have a look). > > For example I do not like > > self xxx > ifTrue: > [ > self bla > self foo. Agreed. Unneccessary waste of a line. > in the current default formatter. > and I prefer > > self xxx > ifTrue: [ self bla. > self foo > But here the problem is that the self foo is not tab aligned because > ifTrue: [ > > self xxx > ifTrue: > [ self bla. > self foo > So may be this one is a nice compromise Not quite there. The "self bla" is still not actually vertically aligned. > I think that we should change some settings. In fact in alpha things are > there to evolve until the release :) I like... self xxx ifTrue: [ self bla. self foo. ]. for three reasons: * the first statement of the block is vertically aligned with the rest * vertical alignment of paired brackets makes visual matching *simple* * the vertical whitespace enforced by the closing bracket on its own visually groups blocks. Now some people don't like the closing brace on its own because they prefer code density. So maybe this... self xxx ifTrue: [ self bla. self foo. ] ifFalse: [ self baa. self moo. ]. But still I prefer... self xxx ifTrue: [ self bla. self foo. ] ifFalse: [ self baa. self moo. ]. cheers -ben

Sept. 3, 2015

Re: [Pharo-dev] feedback from J Brant

by Thierry Goubier

Le 02/09/2015 22:14, stepharo a Ã©crit : > To have fun I addressed > - > https://pharo.fogbugz.com/f/cases/16460/I-fileout-a-package-does-not-fileou… > > but it should be checked. > - https://pharo.fogbugz.com/f/cases/16461/ChunkFileParser and > introduced hooks. > > Now back to coding for real. Thanks. I think that the ability to better port Dolphin packages will help. Thierry > > Stef > > Le 2/9/15 20:28, stepharo a Ã©crit : >> Hi guys >> >> here is some feedback from John. I share it with you. >> >> >> On 02 Sep 2015, at 16:05, John Brant <brant(a)refactoryworkers.com> wrote: >> >> I've been writing some automated scripts to port SmaCC to Pharo. I >> have it where I can file in the Dolphin .pac files directly into a >> Pharo 5 image. Most things are working, but I've had to fight some >> Pharo issues. Since I wasn't sure who should be notified, I thought >> I'd complain to you :) >> >> >> :) if you would see my list of complaints about Pharo you would >> laugh a lot because it is huge and diverse. >> I put thierry on CC because he is the guy maintaining and using >> SmaCC a lot. >> So may be you can help each others. >> >> >> *) The BIConfigurableFormatter (aka RBConfigurableFormatter) sends >> #asString to nodes. First, it should format the node if it wants them >> formatted instead of relying on asString to return a formatted string. >> Second, by sending #asString, formatting has become exponential in the >> nesting level of blocks. For example, Dolphin Smalltalk runs this in 4 >> milliseconds: >> >> | stream | >> stream := WriteStream on: String new. >> stream nextPutAll: 'foo ^true and: '. >> 40 timesRepeat: [stream nextPutAll: '[true and: ']. >> stream nextPutAll: 'false'. >> 40 timesRepeat: [stream nextPut: $]]. >> (RBParser parseMethod: stream contents) formattedCode >> >> I'm guessing that Pharo wouldn't finish in a day... It takes over 4 >> seconds to format 16 nested blocks. >> >> Thanks indeed we will fix it. >> https://pharo.fogbugz.com/f/cases/16462/BIConfigurableFormatter-should-not-… >> >> >> >> *) Also on the formatter, its default doesn't appear to be compliant >> with Kent's blocks should look like blocks/rectangles/box rule. The >> way I interpret the rule is that if I draw a rectangle around >> everything in the block including the brackets, it should not include >> any text of anything outside of the block. For example, this would >> fail that test: >> >> surroundedBy: aString >> ^ self class >> streamContents: [ :s | >> s nextPutAll: aString. >> s nextPutAll: self. >> s nextPutAll: aString ] >> >> yes >> >> >> Since the block starts at the end of the #streamContents: line, a >> rectangle around all the contents in the block contains part of the >> #streamContents: selector which isn't part of the block. >> >> I do not really like all the formattings of kent. Because >> sometimes it just does not work. >> But this is why we ask franck (an interns to start to have a look). >> >> For example I do not like >> >> self xxx >> ifTrue: >> [ >> self bla >> self foo. >> >> in the current default formatter. >> and I prefer >> >> self xxx >> ifTrue: [ self bla. >> self foo >> But here the problem is that the self foo is not tab aligned >> because ifTrue: [ >> >> self xxx >> ifTrue: >> [ self bla. >> self foo >> >> So may be this one is a nice compromise >> I think that we should change some settings. In fact in alpha >> things are there to evolve until the release :) >> >> >> >> *) If I fileout a package, it doesn't fileout the metaclass extension >> methods. The RPackage>>fileOut method needs to be updated with the >> metaclassExtensionSelectors. >> >> Oops this is a bug. >> Do you mean what I mean? the extensions done by the package on >> metaclass that are not in the package. >> >> https://pharo.fogbugz.com/f/cases/16460/I-fileout-a-package-does-not-fileou… >> >> >> >> *) On windows, it appears that while the menus say Ctrl+..., they >> really mean Ctrl+... or Alt+... -- you figure it out. >> >> Yes it sucks. We are in flux with the key essentially because the >> VM often does not even gives us the correct information. >> With the new OSWindow architecture we are putting in place we will >> have all the events and not just the one the VM does not eat (like >> shift pressed) >> and we can manage all at the image level not deep into arcane and >> old C- code. >> >> >> *) It appears that Pharo is removing subString: in favor of >> substring:. The ANSI standard defines subString:. >> >> I was not aware of it. In fact ANSI is bad and totally incomplete >> (for example we studies strings and this is a mess and totally >> incomplete). >> Now we should probably add it. I will send the mail to the >> mailing-list and let people decide. >> >> >> >> >> *) The ChunkFileFormatParser>>parseNextDeclaration is hard coded to >> handle only the Pharo format: >> | substrings | >> substrings := nextChunk parseLiterals. >> (substrings includes: 'methodsFor:') >> ifTrue: [ ^self parseMethodDeclarations: substrings ]. >> (substrings includes: 'commentStamp:') >> ifTrue: [ ^self parseCommentDeclaration: substrings ]. >> (substrings includes: 'reorganize') >> ifTrue: [ ^self parseClassOrganization: substrings ]. >> Due to the hard coded nature of the types of strings accepted, I have >> to overwrite this method to be able to file in Dolphin code. In the >> other Smalltalk's, I can write an extension method or two that I use >> to file in another dialect's code. >> >> https://pharo.fogbugz.com/f/cases/16461/ChunkFileParser >> >> If you have a solution please send it. Because we are focusing on >> the bootstrap and spur the new object format plus a new FFI. Plus >> a lot more. >> So this keeps us really busy and many people left the team and we >> are restarting to teach :) >> >> I personally hate this format and the hardcoding of these strings >> and selectors everywhere so this is why the ChunkFileFormatParser >> is already >> a big step forward. >> >> >> >> I have several other things that annoy me, >> >> me too :) >> But I tried that every couple of days I fix one. >> >> >> but this is enough for now. :) >> >> Tx john :) >> >> >> >> John Brant >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> http://www.synectique.eu / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> 03 59 57 78 50 >> 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 >> >

Sept. 2, 2015

Re: [Pharo-dev] how to contribute to Moose/GToolkit

by Andrei Chis

Hi Peter, If the change affects pharo as well, create first a bug report normally, then push the change to the Moose/GToolkit and then put the issue on fixed upstream. The change will then get picked up next time we merge with Pharo. If it's an important issue feel free to bother us :) You can also update the corresponding configuration yourself and add it to the issue. I added you to the moose team. Cheers, Andrei On Wed, Sep 2, 2015 at 11:10 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > How do I fix a bug in Moose/GToolkit? > > Do I push to change to Pharo50Inbox and let you copy it from there? > Do I commit it to Moose/GToolkit directly (I would need rights)? > Do I send fileout over mailing list? > > Thanks, > Peter >

Sept. 2, 2015

how to contribute to Moose/GToolkit

by Peter UhnÃ¡k

How do I fix a bug in Moose/GToolkit? Do I push to change to Pharo50Inbox and let you copy it from there? Do I commit it to Moose/GToolkit directly (I would need rights)? Do I send fileout over mailing list? Thanks, Peter

Sept. 2, 2015

Re: [Pharo-dev] QANautilusPluggin Logic Question

by stepharo

marcus could you log that issue somewhere because I hope that we will get a new Phd working update. Stef Le 30/8/15 18:29, Marcus Denker a Ã©crit : > Hi, > > All methods (and methods of blocks) that are executing already will keep executing the wrong code. > > As only offsets change, one could do on-stack replacement of these methods, but nobody has implemented that > yet. > > It might be good to have a check that warns when changing layout of classes that are active on the stackâ¦. > >> On 30 Aug 2015, at 14:49, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> Yes, but the situation is weird, because if you look at the variable in the debugger - everything is ok. Is there a way to understand what has not mutated? >> >> Uko >> >> >>> On 30 Aug 2015, at 13:35, stepharo <stepharo(a)free.fr> wrote: >>> >>> may be code executing the check did not get mutated when the system changed shape. >>> >>> Le 30/8/15 11:00, Marcus Denker a Ã©crit : >>>>> On 30 Aug 2015, at 10:57, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>>> >>>>> So the byte symbol comes from the âpositionâ inst var of the superclass. Iâm not completely sure how it works on low level, but I guess that because you a a new variable, the others shift and it accesses the value that is actually mapped to another variable. Is it the issue of my implementation? How can I improve it? >>>>> >>>> The class builder is normally supposed to fix that transparently: You add var, all methods are recompiled and all instances are migrated. There could be bugs there. >>>> >>>>> Uko >>>>> >>>>>> On 28 Aug 2015, at 10:50, stepharo <stepharo(a)free.fr> wrote: >>>>>> >>>>>> When I add an iv to Model I get a ByteSymbol>>entity: >>>>>> >>>>>> QANautilusPluggin>>initialize >>>>>> >>>>>> changeHandler := GLMAsyncTask new >>>>>> priority: Processor activePriority - 1; >>>>>> doInBackground: [ morph entity: self currentEntity ]; >>>>>> yourself >>>>>> >>>>>> And in the debugger morph is a a Morph exactly a QANautilusPluginMorph(493092864) >>>>>> >>>>>> Yuriy do you use thread? >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>>> >>>> >>> >> > >

Sept. 2, 2015

Re: [Pharo-dev] feedback from J Brant

by stepharo

To have fun I addressed - https://pharo.fogbugz.com/f/cases/16460/I-fileout-a-package-does-not-fileou… but it should be checked. - https://pharo.fogbugz.com/f/cases/16461/ChunkFileParser and introduced hooks. Now back to coding for real. Stef Le 2/9/15 20:28, stepharo a Ã©crit : > Hi guys > > here is some feedback from John. I share it with you. > > > On 02 Sep 2015, at 16:05, John Brant <brant(a)refactoryworkers.com> wrote: > > I've been writing some automated scripts to port SmaCC to Pharo. I > have it where I can file in the Dolphin .pac files directly into a > Pharo 5 image. Most things are working, but I've had to fight some > Pharo issues. Since I wasn't sure who should be notified, I thought > I'd complain to you :) > > > :) if you would see my list of complaints about Pharo you would > laugh a lot because it is huge and diverse. > I put thierry on CC because he is the guy maintaining and using > SmaCC a lot. > So may be you can help each others. > > > *) The BIConfigurableFormatter (aka RBConfigurableFormatter) sends > #asString to nodes. First, it should format the node if it wants them > formatted instead of relying on asString to return a formatted string. > Second, by sending #asString, formatting has become exponential in the > nesting level of blocks. For example, Dolphin Smalltalk runs this in 4 > milliseconds: > > | stream | > stream := WriteStream on: String new. > stream nextPutAll: 'foo ^true and: '. > 40 timesRepeat: [stream nextPutAll: '[true and: ']. > stream nextPutAll: 'false'. > 40 timesRepeat: [stream nextPut: $]]. > (RBParser parseMethod: stream contents) formattedCode > > I'm guessing that Pharo wouldn't finish in a day... It takes over 4 > seconds to format 16 nested blocks. > > Thanks indeed we will fix it. > https://pharo.fogbugz.com/f/cases/16462/BIConfigurableFormatter-should-not-… > > > > *) Also on the formatter, its default doesn't appear to be compliant > with Kent's blocks should look like blocks/rectangles/box rule. The > way I interpret the rule is that if I draw a rectangle around > everything in the block including the brackets, it should not include > any text of anything outside of the block. For example, this would > fail that test: > > surroundedBy: aString > ^ self class > streamContents: [ :s | > s nextPutAll: aString. > s nextPutAll: self. > s nextPutAll: aString ] > > yes > > > Since the block starts at the end of the #streamContents: line, a > rectangle around all the contents in the block contains part of the > #streamContents: selector which isn't part of the block. > > I do not really like all the formattings of kent. Because > sometimes it just does not work. > But this is why we ask franck (an interns to start to have a look). > > For example I do not like > > self xxx > ifTrue: > [ > self bla > self foo. > > in the current default formatter. > and I prefer > > self xxx > ifTrue: [ self bla. > self foo > But here the problem is that the self foo is not tab aligned > because ifTrue: [ > > self xxx > ifTrue: > [ self bla. > self foo > > So may be this one is a nice compromise > I think that we should change some settings. In fact in alpha > things are there to evolve until the release :) > > > > *) If I fileout a package, it doesn't fileout the metaclass extension > methods. The RPackage>>fileOut method needs to be updated with the > metaclassExtensionSelectors. > > Oops this is a bug. > Do you mean what I mean? the extensions done by the package on > metaclass that are not in the package. > > https://pharo.fogbugz.com/f/cases/16460/I-fileout-a-package-does-not-fileou… > > > > *) On windows, it appears that while the menus say Ctrl+..., they > really mean Ctrl+... or Alt+... -- you figure it out. > > Yes it sucks. We are in flux with the key essentially because the > VM often does not even gives us the correct information. > With the new OSWindow architecture we are putting in place we will > have all the events and not just the one the VM does not eat (like > shift pressed) > and we can manage all at the image level not deep into arcane and > old C- code. > > > *) It appears that Pharo is removing subString: in favor of > substring:. The ANSI standard defines subString:. > > I was not aware of it. In fact ANSI is bad and totally incomplete > (for example we studies strings and this is a mess and totally > incomplete). > Now we should probably add it. I will send the mail to the > mailing-list and let people decide. > > > > > *) The ChunkFileFormatParser>>parseNextDeclaration is hard coded to > handle only the Pharo format: > | substrings | > substrings := nextChunk parseLiterals. > (substrings includes: 'methodsFor:') > ifTrue: [ ^self parseMethodDeclarations: substrings ]. > (substrings includes: 'commentStamp:') > ifTrue: [ ^self parseCommentDeclaration: substrings ]. > (substrings includes: 'reorganize') > ifTrue: [ ^self parseClassOrganization: substrings ]. > Due to the hard coded nature of the types of strings accepted, I have > to overwrite this method to be able to file in Dolphin code. In the > other Smalltalk's, I can write an extension method or two that I use > to file in another dialect's code. > > https://pharo.fogbugz.com/f/cases/16461/ChunkFileParser > > If you have a solution please send it. Because we are focusing on > the bootstrap and spur the new object format plus a new FFI. Plus > a lot more. > So this keeps us really busy and many people left the team and we > are restarting to teach :) > > I personally hate this format and the hardcoding of these strings > and selectors everywhere so this is why the ChunkFileFormatParser > is already > a big step forward. > > > > I have several other things that annoy me, > > me too :) > But I tried that every couple of days I fix one. > > > but this is enough for now. :) > > Tx john :) > > > > John Brant > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > http://www.synectique.eu / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > 03 59 57 78 50 > 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 >

Sept. 2, 2015

feedback from J Brant

by stepharo

Hi guys here is some feedback from John. I share it with you. On 02 Sep 2015, at 16:05, John Brant <brant(a)refactoryworkers.com> wrote: I've been writing some automated scripts to port SmaCC to Pharo. I have it where I can file in the Dolphin .pac files directly into a Pharo 5 image. Most things are working, but I've had to fight some Pharo issues. Since I wasn't sure who should be notified, I thought I'd complain to you :) :) if you would see my list of complaints about Pharo you would laugh a lot because it is huge and diverse. I put thierry on CC because he is the guy maintaining and using SmaCC a lot. So may be you can help each others. *) The BIConfigurableFormatter (aka RBConfigurableFormatter) sends #asString to nodes. First, it should format the node if it wants them formatted instead of relying on asString to return a formatted string. Second, by sending #asString, formatting has become exponential in the nesting level of blocks. For example, Dolphin Smalltalk runs this in 4 milliseconds: | stream | stream := WriteStream on: String new. stream nextPutAll: 'foo ^true and: '. 40 timesRepeat: [stream nextPutAll: '[true and: ']. stream nextPutAll: 'false'. 40 timesRepeat: [stream nextPut: $]]. (RBParser parseMethod: stream contents) formattedCode I'm guessing that Pharo wouldn't finish in a day... It takes over 4 seconds to format 16 nested blocks. Thanks indeed we will fix it. https://pharo.fogbugz.com/f/cases/16462/BIConfigurableFormatter-should-not-… *) Also on the formatter, its default doesn't appear to be compliant with Kent's blocks should look like blocks/rectangles/box rule. The way I interpret the rule is that if I draw a rectangle around everything in the block including the brackets, it should not include any text of anything outside of the block. For example, this would fail that test: surroundedBy: aString ^ self class streamContents: [ :s | s nextPutAll: aString. s nextPutAll: self. s nextPutAll: aString ] yes Since the block starts at the end of the #streamContents: line, a rectangle around all the contents in the block contains part of the #streamContents: selector which isn't part of the block. I do not really like all the formattings of kent. Because sometimes it just does not work. But this is why we ask franck (an interns to start to have a look). For example I do not like self xxx ifTrue: [ self bla self foo. in the current default formatter. and I prefer self xxx ifTrue: [ self bla. self foo But here the problem is that the self foo is not tab aligned because ifTrue: [ self xxx ifTrue: [ self bla. self foo So may be this one is a nice compromise I think that we should change some settings. In fact in alpha things are there to evolve until the release :) *) If I fileout a package, it doesn't fileout the metaclass extension methods. The RPackage>>fileOut method needs to be updated with the metaclassExtensionSelectors. Oops this is a bug. Do you mean what I mean? the extensions done by the package on metaclass that are not in the package. https://pharo.fogbugz.com/f/cases/16460/I-fileout-a-package-does-not-fileou… *) On windows, it appears that while the menus say Ctrl+..., they really mean Ctrl+... or Alt+... -- you figure it out. Yes it sucks. We are in flux with the key essentially because the VM often does not even gives us the correct information. With the new OSWindow architecture we are putting in place we will have all the events and not just the one the VM does not eat (like shift pressed) and we can manage all at the image level not deep into arcane and old C- code. *) It appears that Pharo is removing subString: in favor of substring:. The ANSI standard defines subString:. I was not aware of it. In fact ANSI is bad and totally incomplete (for example we studies strings and this is a mess and totally incomplete). Now we should probably add it. I will send the mail to the mailing-list and let people decide. *) The ChunkFileFormatParser>>parseNextDeclaration is hard coded to handle only the Pharo format: | substrings | substrings := nextChunk parseLiterals. (substrings includes: 'methodsFor:') ifTrue: [ ^self parseMethodDeclarations: substrings ]. (substrings includes: 'commentStamp:') ifTrue: [ ^self parseCommentDeclaration: substrings ]. (substrings includes: 'reorganize') ifTrue: [ ^self parseClassOrganization: substrings ]. Due to the hard coded nature of the types of strings accepted, I have to overwrite this method to be able to file in Dolphin code. In the other Smalltalk's, I can write an extension method or two that I use to file in another dialect's code. https://pharo.fogbugz.com/f/cases/16461/ChunkFileParser If you have a solution please send it. Because we are focusing on the bootstrap and spur the new object format plus a new FFI. Plus a lot more. So this keeps us really busy and many people left the team and we are restarting to teach :) I personally hate this format and the hardcoding of these strings and selectors everywhere so this is why the ChunkFileFormatParser is already a big step forward. I have several other things that annoy me, me too :) But I tried that every couple of days I fix one. but this is enough for now. :) Tx john :) John Brant -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas 03 59 57 78 50 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

Sept. 2, 2015

To Detent Or Not To Detentâ¦

by Sean P. DeNigris

Can anyone explain the purpose of sending #detentBy:atMultiplesOf:snap: in the method below? The problem is that, if you resize programatically below a factor of 0.1, you enter a black hole from which many scale attempts become effectively ignored. If the send is removed, everything works for my use case, but I don't understand its purpose and so don't know if it's a bug or feature! TransformationMorph>>#extent: newExtent self adjustAfter: [ | scaleFactor |scaleFactor := (self scale * newExtent r / self fullBounds extent r) max: 0.1. self scale: (scaleFactor detentBy: 0.1 atMultiplesOf: 1.0 snap: false)] ----- Cheers, Sean -- View this message in context: http://forum.world.st/To-Detent-Or-Not-To-Detent-tp4847682.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 2, 2015

Re: [Pharo-dev] Widget choice list

by Franck Warlouzet

Yes arrows up/down handling in fast table is not perfect. Esteban told me there is a way to have this kind of filtering direclty in the small rectangle but I did not take the time to see how. I like the search field but maybe someone prefers filtering directly in the list items area Franck > To: pharo-dev(a)lists.pharo.org > From: stephan(a)stack.nl > Date: Wed, 2 Sep 2015 16:35:39 +0200 > Subject: Re: [Pharo-dev] Widget choice list > CC: pharo-users(a)lists.pharo.org > > On 02-09-15 14:22, Franck Warlouzet wrote: > > Hi, > > > > Some of you showed interest in a widget as the one which pops up to add protocol in Nautilus, but using FastTable. We started to build such one, it allows to bind specific action on click on a item, to have icon for items, to filter items etc. Examples show how to use it. > > It is still a beginning so there is probably some strange points or improvements to do, but if it appears to be useful to replace some widgets we can enhance it. Or it can simply show you how easy it is to build a fast table with a more complex data source, which would already be a good point. > > > > You can find the code in this repo : > > > > MCHttpRepository > > location: 'http://www.smalltalkhub.com/mc/FranckW/WidgetChoiceList/main' > > user: '' > > password: '' > > > > Feel free to contact me if you have questions. > > Nice. I've fixed example4 > In the interaction between the search field and the table, you'll want > to change the focus behaviour. Starting to type should enter the text in > the search field while filtering the table and selecting the first > element that filters. Arrow up and down should move the selection of the > table. You'll also want a key combination to move up and down to the > next position where the strings start to differ again. > > I took a look at reacting to a keystroke in the text field, but there > is an announcement that is not exposed in the model. > > Stephan > > > >

Sept. 2, 2015

Re: [Pharo-dev] Widget choice list

by Stephan Eggermont

On 02-09-15 14:22, Franck Warlouzet wrote: > Hi, > > Some of you showed interest in a widget as the one which pops up to add protocol in Nautilus, but using FastTable. We started to build such one, it allows to bind specific action on click on a item, to have icon for items, to filter items etc. Examples show how to use it. > It is still a beginning so there is probably some strange points or improvements to do, but if it appears to be useful to replace some widgets we can enhance it. Or it can simply show you how easy it is to build a fast table with a more complex data source, which would already be a good point. > > You can find the code in this repo : > > MCHttpRepository > location: 'http://www.smalltalkhub.com/mc/FranckW/WidgetChoiceList/main' > user: '' > password: '' > > Feel free to contact me if you have questions. Nice. I've fixed example4 In the interaction between the search field and the table, you'll want to change the focus behaviour. Starting to type should enter the text in the search field while filtering the table and selecting the first element that filters. Arrow up and down should move the selection of the table. You'll also want a key combination to move up and down to the next position where the strings start to differ again. I took a look at reacting to a keystroke in the text field, but there is an announcement that is not exposed in the model. Stephan

Sept. 2, 2015

Re: [Pharo-dev] Pharo CI Validation Timeout

by Nicolai Hess

Low memory ? Running the rules fill up the ast cache with nearly one entry per compiled method instance. (this are thousands instances of Array/OrderedCollections/RB and OC classes) My pharo images runs from ~ 50 MB to ~ 350-400 MB after running all rules for all classes! 2015-09-02 13:42 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > I have the feeling that is is an artefact of the virtualisation somehow. > > On 02 Sep 2015, at 10:24, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > I saw also that one of the linux slaves is much much slower than the > others. Just check this: > > https://ci.inria.fr/pharo/job/30-Bootstrap/buildTimeTrend > > In one of the slaves the build takes one hour. In the other it takes 6. > > El miÃ©., 2 de sept. de 2015 a la(s) 9:11 a. m., Marcus Denker < > marcus.denker(a)inria.fr> escribiÃ³: > >> I donât think soâ¦ the job used to run in 15 minutes. But we added more >> tests, >> Rules got slowerâ¦ >> >> On 02 Sep 2015, at 08:34, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >> It is possible to see from the console output which rule or test takes a >> lot time? >> >> 2015-09-02 8:09 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: >> >>> >>> On 01 Sep 2015, at 19:15, Ben Coman <btc(a)openinworld.com> wrote: >>> >>> Do you want to try a post-load... >>> Delay delaySchedulerClass: DelayExperimentalSemaphoreScheduler >>> >>> which fixes the "super fast delay" on virtual machines reported here... >>> http://comments.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/100873 >>> >>> Its named "experimental" only since it was integrated just before >>> Pharo 4 release and did not have wide spread community testing, but >>> its complete and working. There is some further overall streamlining >>> of the DelayScheduler hierarchy I'd like to do later, but it would be >>> good to give this one a run as the default for a while to see how it >>> impacts the issue. (It would be good to get rough "CIAndRule: Timeout" >>> before and after statistics.) >>> >>> btw, is that CI error indicating it times out after one hour? Are >>> there any other timestamps present in the log that indicate if 1 hour >>> really passed? >>> >>> >>> Yes, I think soâ¦ >>> >>> https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/buildTimeTrend >>> >>> Now looking at it (no idea why it is chinese), it seems that we have some >>> slowdown recently and all runs take 40-50 minutes, a slowdown to 60 can >>> happen >>> just by having less compute power available (or running multiple things >>> in parallel). >>> >>> We should >>> >>> -> do a pass over slow tests >>> -> do a pass over slow rules >>> >>> I will put the limit higher than 60 min for now. >>> >>> Marcus >>> >>> >>> >> >> >

Sept. 2, 2015

Re: [Pharo-dev] Broken GTSpotter in #50298

by Andrei Chis

https://pharo.fogbugz.com/f/cases/16455/Spotter-dying-on-not-understanding-… On Wed, Sep 2, 2015 at 2:41 PM, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: > Thanks! > > Juraj > > On Sep 2, 2015, at 09:40, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Making an issue now. > > Cheers, > Andrei > > On Wed, Sep 2, 2015 at 2:04 PM, Juraj Kubelka <juraj.kubelka(a)gmail.com> > wrote: > >> Hi, >> >> I have fixed it yesterday. Maybe some integration is necessary to do. >> >> Cheers, >> Juraj >> >> -- >> Juraj Kubelka >> >> 2. 9. 2015 v 8:50, Peter UhnÃ¡k <i.uhnak(a)gmail.com>: >> >> > Hi, >> > >> > is Spotter working for you in latest Pharo? (#50298) >> > I downloaded fresh image and its dying on not understanding >> #canUnderstand: >> > >> > Peter >> >> > >

Sept. 2, 2015

Re: [Pharo-dev] Broken GTSpotter in #50298

by Juraj Kubelka

Thanks! Juraj > On Sep 2, 2015, at 09:40, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Making an issue now. > > Cheers, > Andrei > > On Wed, Sep 2, 2015 at 2:04 PM, Juraj Kubelka <juraj.kubelka(a)gmail.com <mailto:juraj.kubelka@gmail.com>> wrote: > Hi, > > I have fixed it yesterday. Maybe some integration is necessary to do. > > Cheers, > Juraj > > -- > Juraj Kubelka > > 2. 9. 2015 v 8:50, Peter UhnÃ¡k <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>>: > > > Hi, > > > > is Spotter working for you in latest Pharo? (#50298) > > I downloaded fresh image and its dying on not understanding #canUnderstand: > > > > Peter > >

Sept. 2, 2015

Re: [Pharo-dev] Broken GTSpotter in #50298

by Andrei Chis

Making an issue now. Cheers, Andrei On Wed, Sep 2, 2015 at 2:04 PM, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: > Hi, > > I have fixed it yesterday. Maybe some integration is necessary to do. > > Cheers, > Juraj > > -- > Juraj Kubelka > > 2. 9. 2015 v 8:50, Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > > > Hi, > > > > is Spotter working for you in latest Pharo? (#50298) > > I downloaded fresh image and its dying on not understanding > #canUnderstand: > > > > Peter > >

Sept. 2, 2015

Widget choice list

by Franck Warlouzet

Hi, Some of you showed interest in a widget as the one which pops up to add protocol in Nautilus, but using FastTable. We started to build such one, it allows to bind specific action on click on a item, to have icon for items, to filter items etc. Examples show how to use it. It is still a beginning so there is probably some strange points or improvements to do, but if it appears to be useful to replace some widgets we can enhance it. Or it can simply show you how easy it is to build a fast table with a more complex data source, which would already be a good point. You can find the code in this repo : MCHttpRepository location: 'http://www.smalltalkhub.com/mc/FranckW/WidgetChoiceList/main' user: '' password: '' Feel free to contact me if you have questions. Cheers, Franck

Sept. 2, 2015

Re: [Pharo-dev] Removing name from Object

by Peter UhnÃ¡k

> > Off the top of my head, in the worst case implementing #name on the > class-side can be fatal. > TBH using generic names (for both variables and methods) on class side is like running through a mine field. I blew up my image more than once. >From UX perspective the system should warn the user if he is trying to override some system method or variable, but that is perhaps issue of its own. Peter

Sept. 2, 2015

Re: [Pharo-dev] Broken GTSpotter in #50298

by Juraj Kubelka

Hi, I have fixed it yesterday. Maybe some integration is necessary to do. Cheers, Juraj -- Juraj Kubelka 2. 9. 2015 v 8:50, Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > Hi, > > is Spotter working for you in latest Pharo? (#50298) > I downloaded fresh image and its dying on not understanding #canUnderstand: > > Peter

Sept. 2, 2015

Re: [Pharo-dev] Removing name from Object

by Sean P. DeNigris

EstebanLM wrote > deprecate it like any other method change or removal? (And then remove it > in Pharo 6) > > +1 > thatâs the way to do it :) +1. I'm glad we're finally getting around to this :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Removing-name-from-Object-tp4847514p4847641.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 2, 2015

Re: [Pharo-dev] Removing name from Object

by Sean P. DeNigris

Hannes Hirzel wrote > Which other kinds of problems do you see with this method? > Could you elaborate a bit please why you want to remove Object>>name? Off the top of my head, in the worst case implementing #name on the class-side can be fatal. Less seriously one can get confusing result if e.g. you create a #name instVar and expect something to fail because you haven't created the getter yet, but instead it surprises you by using the unkown default implementation. At minimum, it creates confusion by using an overly generic name deep in the system. There should be as few reserved words like #class as possible, and only with very good reason, as it makes the system harder to understand. For more info, see: http://forum.world.st/name-tt3739677.html http://forum.world.st/name-selector-tt4760402.html ----- Cheers, Sean -- View this message in context: http://forum.world.st/Removing-name-from-Object-tp4847514p4847640.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 2, 2015

Re: [Pharo-dev] [Experiment] Automatic rewriting of sends to deprecated methods

by Ben Coman

On Wed, Sep 2, 2015 at 2:13 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >>>> Imagine, this is a functionality (I think) no other system has! >> >> >> Yes but we should make it pluggable. >> > Yes! > >> >> I would like something that says >> before all the tests were green and after these automatic changes >> they are also green :) > > > Exactly, that's what I implemented: you run the tests and all code covered > will be transformed automaticallly Ahh. I thought you were thinking of doing it in normally executing code. Doing it while running tests makes more sense. It only occurs on a specific user action. If you start with clean packages, all changes can be reviewed. cheers -ben

Sept. 2, 2015

Broken GTSpotter in #50298

by Peter UhnÃ¡k

Hi, is Spotter working for you in latest Pharo? (#50298) I downloaded fresh image and its dying on not understanding #canUnderstand: Peter

Sept. 2, 2015

Re: [Pharo-dev] Pharo CI Validation Timeout

by Marcus Denker

I have the feeling that is is an artefact of the virtualisation somehow. > On 02 Sep 2015, at 10:24, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > I saw also that one of the linux slaves is much much slower than the others. Just check this: > > https://ci.inria.fr/pharo/job/30-Bootstrap/buildTimeTrend <https://ci.inria.fr/pharo/job/30-Bootstrap/buildTimeTrend> > > In one of the slaves the build takes one hour. In the other it takes 6. > > El miÃ©., 2 de sept. de 2015 a la(s) 9:11 a. m., Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> escribiÃ³: > I donât think soâ¦ the job used to run in 15 minutes. But we added more tests, > Rules got slowerâ¦ > >> On 02 Sep 2015, at 08:34, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >> >> It is possible to see from the console output which rule or test takes a lot time? >> >> 2015-09-02 8:09 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>>: >> >>> On 01 Sep 2015, at 19:15, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: >>> >>> Do you want to try a post-load... >>> Delay delaySchedulerClass: DelayExperimentalSemaphoreScheduler >>> >>> which fixes the "super fast delay" on virtual machines reported here... >>> http://comments.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/100873 <http://comments.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/100873> >>> >>> Its named "experimental" only since it was integrated just before >>> Pharo 4 release and did not have wide spread community testing, but >>> its complete and working. There is some further overall streamlining >>> of the DelayScheduler hierarchy I'd like to do later, but it would be >>> good to give this one a run as the default for a while to see how it >>> impacts the issue. (It would be good to get rough "CIAndRule: Timeout" >>> before and after statistics.) >>> >>> btw, is that CI error indicating it times out after one hour? Are >>> there any other timestamps present in the log that indicate if 1 hour >>> really passed? >>> >> >> Yes, I think soâ¦ >> >> https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/buildTimeTrend <https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/buildTimeTrend> >> >> Now looking at it (no idea why it is chinese), it seems that we have some >> slowdown recently and all runs take 40-50 minutes, a slowdown to 60 can happen >> just by having less compute power available (or running multiple things in parallel). >> >> We should >> >> -> do a pass over slow tests >> -> do a pass over slow rules >> >> I will put the limit higher than 60 min for now. >> >> Marcus >> >> >> >

Sept. 2, 2015

Re: [Pharo-dev] Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp

by Sven Van Caekenberghe

But Timestamp was already removed completely from 4.0, why re-add it, even deprecated ? I am sure many external packages are already modified, I know I did it for mine. > On 02 Sep 2015, at 13:19, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 02 Sep 2015, at 12:32, stepharo <stepharo(a)free.fr> wrote: >> >> Hi guille >> >> there is not stress. I just wanted to let you know. >> I was wondering if just subclassing DateAndTime would not be enough for now. > > Yes, as far as I remember Timestamp was just an empy subclass. > > We could: > > -> add it back to Deprecated50 or maybe even to a âCompatibilityâ package > -> Write a Quality Check rule. > >> I will go back to code with Pharo 40 >> >> stef >> >> Le 2/9/15 10:30, Guillermo Polito a Ã©crit : >>> If somebody can check it and fix it it would be good :). I've just started my new job and my evenings are busy looking for an apartment or staying in a hostel without a proper internet connection... >>> >>> If not, I think we can wait a bit. The first step should be enabling CI jobs for pharo5. Also, I do not think the intersection between 'people using garage opendbx' and 'people using pharo5' is that big to justify a rush. >>> >>> Guille >>> >>> El miÃ©., 2 de sept. de 2015 a la(s) 10:12 a. m., stepharo <stepharo(a)free.fr> escribiÃ³: >>> for your info... >>> >>> Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp >>> >>> Stef >>> >> >

Sept. 2, 2015

Re: [Pharo-dev] Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp

by stepharo

Yes!!!! marcus it would be a good idea. Stef Le 2/9/15 13:19, Marcus Denker a Ã©crit : > >> On 02 Sep 2015, at 12:32, stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>> wrote: >> >> Hi guille >> >> there is not stress. I just wanted to let you know. >> I was wondering if just subclassing DateAndTime would not be enough >> for now. > > Yes, as far as I remember Timestamp was just an empy subclass. > > We could: > > -> add it back to Deprecated50 or maybe even to a âCompatibilityâ package > -> Write a Quality Check rule. > >> I will go back to code with Pharo 40 >> >> stef >> >> Le 2/9/15 10:30, Guillermo Polito a Ã©crit : >>> If somebody can check it and fix it it would be good :). I've just >>> started my new job and my evenings are busy looking for an apartment >>> or staying in a hostel without a proper internet connection... >>> >>> If not, I think we can wait a bit. The first step should be enabling >>> CI jobs for pharo5. Also, I do not think the intersection between >>> 'people using garage opendbx' and 'people using pharo5' is that big >>> to justify a rush. >>> >>> Guille >>> >>> El miÃ©., 2 de sept. de 2015 a la(s) 10:12 a. m., stepharo >>> <stepharo(a)free.fr <mailto:stepharo@free.fr>> escribiÃ³: >>> >>> for your info... >>> >>> Garage-OpenDBX does not load on Pharo 50 because it uses >>> Timestamp >>> >>> Stef >>> >> >

Sept. 2, 2015

Re: [Pharo-dev] Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp

by Marcus Denker

> On 02 Sep 2015, at 12:32, stepharo <stepharo(a)free.fr> wrote: > > Hi guille > > there is not stress. I just wanted to let you know. > I was wondering if just subclassing DateAndTime would not be enough for now. Yes, as far as I remember Timestamp was just an empy subclass. We could: -> add it back to Deprecated50 or maybe even to a âCompatibilityâ package -> Write a Quality Check rule. > I will go back to code with Pharo 40 > > stef > > Le 2/9/15 10:30, Guillermo Polito a Ã©crit : >> If somebody can check it and fix it it would be good :). I've just started my new job and my evenings are busy looking for an apartment or staying in a hostel without a proper internet connection... >> >> If not, I think we can wait a bit. The first step should be enabling CI jobs for pharo5. Also, I do not think the intersection between 'people using garage opendbx' and 'people using pharo5' is that big to justify a rush. >> >> Guille >> >> El miÃ©., 2 de sept. de 2015 a la(s) 10:12 a. m., stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> escribiÃ³: >> for your info... >> >> Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp >> >> Stef >> >

Sept. 2, 2015

Re: [Pharo-dev] widgetDo: vs ifWidget:

by Peter UhnÃ¡k

In that case I rest my case and I will stick with #widgetDo: :) Not even the naming. I would say. lot of code in spec should be rewritten. > The holder should be most of the time directly exposed to reduce the API. I know; it is moving, albeit slowly. Thanks, Peter

Sept. 2, 2015

Re: [Pharo-dev] Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp

by stepharo

Hi guille there is not stress. I just wanted to let you know. I was wondering if just subclassing DateAndTime would not be enough for now. I will go back to code with Pharo 40 stef Le 2/9/15 10:30, Guillermo Polito a Ã©crit : > If somebody can check it and fix it it would be good :). I've just > started my new job and my evenings are busy looking for an apartment > or staying in a hostel without a proper internet connection... > > If not, I think we can wait a bit. The first step should be enabling > CI jobs for pharo5. Also, I do not think the intersection between > 'people using garage opendbx' and 'people using pharo5' is that big to > justify a rush. > > Guille > > El miÃ©., 2 de sept. de 2015 a la(s) 10:12 a. m., stepharo > <stepharo(a)free.fr <mailto:stepharo@free.fr>> escribiÃ³: > > for your info... > > Garage-OpenDBX does not load on Pharo 50 because it uses > Timestamp > > Stef >

Sept. 2, 2015

Re: [Pharo-dev] widgetDo: vs ifWidget:

by stepharo

Le 2/9/15 10:56, Peter UhnÃ¡k a Ã©crit : > Hi, > > in Spec Adapter there's method > > widgetDo: aBlock > ^ self widget ifNotNil: aBlock > > > my question however is: > does the naming make sense? > > #*Do: is generally associated with iterating over collections. Widget > is always a single entity. > On the other hand we have #ifNil: #ifTrue: #ifFalse: > > There is also #ifNotNilDo:, however that is superseded by #ifNotNil: > > So from this perspective, wouldn't it make more sense to have this? > ifWidget: aBlock > ^ self widget ifNotNil: aBlock I prefer widgetDo: because this if logic is not really good and the user should not be exposed > > What do you think? > > Thanks, > Peter

Sept. 2, 2015

Re: [Pharo-dev] widgetDo: vs ifWidget:

by stepharo

Le 2/9/15 10:56, Peter UhnÃ¡k a Ã©crit : > Hi, > > in Spec Adapter there's method > > widgetDo: aBlock > ^ self widget ifNotNil: aBlock > > > my question however is: > does the naming make sense? Not even the naming. I would say. lot of code in spec should be rewritten. The holder should be most of the time directly exposed to reduce the API. > > #*Do: is generally associated with iterating over collections. Widget > is always a single entity. > On the other hand we have #ifNil: #ifTrue: #ifFalse: > > There is also #ifNotNilDo:, however that is superseded by #ifNotNil: > > So from this perspective, wouldn't it make more sense to have this? > ifWidget: aBlock > ^ self widget ifNotNil: aBlock > > What do you think? > > Thanks, > Peter

Sept. 2, 2015

Re: [Pharo-dev] widgetDo: vs ifWidget:

by Aliaksei Syrel

The same naming blablaDo: is heavily used in Bloc and therefore in Brick. I personally like blablaDo: more, because it hides check logic from user and doesn't force to think about if-elses. It's all about "if" word. You know, when reader sees "if" a complexity of an app instantly rises (in the head). But let's discuss :) I agree that it can be associated with iteration and is not the best idea... Cheers, Alex On Wed, Sep 2, 2015 at 10:56 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Hi, > > in Spec Adapter there's method > > widgetDo: aBlock > ^ self widget ifNotNil: aBlock > > > my question however is: > does the naming make sense? > > #*Do: is generally associated with iterating over collections. Widget is > always a single entity. > On the other hand we have #ifNil: #ifTrue: #ifFalse: > > There is also #ifNotNilDo:, however that is superseded by #ifNotNil: > > So from this perspective, wouldn't it make more sense to have this? > ifWidget: aBlock > ^ self widget ifNotNil: aBlock > > What do you think? > > Thanks, > Peter >

Sept. 2, 2015

Rubric #mouseDown, #mouseUp and #click

by Stephan Eggermont

We have a few morphs where #on:#mouseDown send: aMessage to: aTarget is used where I'd expected that to be on #click. Mostly in Rubric and the Nautilus annotations If a morph is supposed to behave as a button, the action should happen on the #mouseUp, but only if the mouse pointer hasn't moved away from the morph. That is what #click does. And ExpanderTitleMorph GrowlMorph JobProgressMorph react on #mouseUp instead of #click Stephan

Sept. 2, 2015

widgetDo: vs ifWidget:

by Peter UhnÃ¡k

Hi, in Spec Adapter there's method widgetDo: aBlock ^ self widget ifNotNil: aBlock my question however is: does the naming make sense? #*Do: is generally associated with iterating over collections. Widget is always a single entity. On the other hand we have #ifNil: #ifTrue: #ifFalse: There is also #ifNotNilDo:, however that is superseded by #ifNotNil: So from this perspective, wouldn't it make more sense to have this? ifWidget: aBlock ^ self widget ifNotNil: aBlock What do you think? Thanks, Peter

Sept. 2, 2015

Re: [Pharo-dev] Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp

by Guillermo Polito

If somebody can check it and fix it it would be good :). I've just started my new job and my evenings are busy looking for an apartment or staying in a hostel without a proper internet connection... If not, I think we can wait a bit. The first step should be enabling CI jobs for pharo5. Also, I do not think the intersection between 'people using garage opendbx' and 'people using pharo5' is that big to justify a rush. Guille El miÃ©., 2 de sept. de 2015 a la(s) 10:12 a. m., stepharo <stepharo(a)free.fr> escribiÃ³: > for your info... > > Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp > > Stef > >

Sept. 2, 2015

Re: [Pharo-dev] Removing name from Object

by Esteban Lorenzano

but if we deprecate, that means we need to remove it from the system. deprecated is for external users, not for Pharo it self. Esteban ps: We *can not* remove #name from the system just like that. It is too widely use, we need to give users time to adapt. Doing otherwise is not professional and expect a lot of people yelling (and with reason, in this case). > On 02 Sep 2015, at 10:21, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > The problem is if (like in the past) name is extensively used by some library we depend upon (like... let's say morphic), a deprecation that raises an exception may turn the system unusable. It's not that it is not doable, but we should do it gently and with love. > > El miÃ©., 2 de sept. de 2015 a la(s) 9:30 a. m., Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> escribiÃ³: >> On 02 Sep 2015, at 09:25, Peter UhnÃ¡k <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>> wrote: >> >> On Wed, Sep 2, 2015 at 8:40 AM, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >> How can we find out, which external projects depend on this? >> >> Is #name in any way special? Why not just deprecate it like any other method change or removal? (And then remove it in Pharo 6) > > +1 > thatâs the way to do it :) > >> >> Peter >

Sept. 2, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50298 Home: https://github.com/pharo-project/pharo-core

Sept. 2, 2015

[pharo-project/pharo-core] a72653: 50298

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: a72653a6f7361fa944b2b40348467587d0f098bd https://github.com/pharo-project/pharo-core/commit/a72653a6f7361fa944b2b403… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-02 (Wed, 02 Sep 2015) Changed paths: A Balloon-Tests.package/PointArrayTest.class/README.md A Balloon-Tests.package/PointArrayTest.class/definition.st A Balloon-Tests.package/PointArrayTest.class/instance/running/setUp.st A Balloon-Tests.package/PointArrayTest.class/instance/testing/testAt.st A Balloon-Tests.package/PointArrayTest.class/instance/testing/testAtPut.st A Balloon-Tests.package/PointArrayTest.class/instance/testing/testAtPutFloat.st A Balloon-Tests.package/PointArrayTest.class/instance/testing/testAtPutFraction.st A Balloon-Tests.package/PointArrayTest.class/instance/testing/testAtPutInt4.st A Balloon-Tests.package/PointArrayTest.class/instance/testing/testAtPutLargeInteger.st A Balloon-Tests.package/PointArrayTest.class/instance/testing/testBounds.st A Balloon-Tests.package/PointArrayTest.class/instance/testing/testDefaultElement.st A Balloon-Tests.package/PointArrayTest.class/instance/testing/testSize.st A Balloon-Tests.package/ShortIntegerArrayTest.class/README.md A Balloon-Tests.package/ShortIntegerArrayTest.class/definition.st A Balloon-Tests.package/ShortIntegerArrayTest.class/instance/running/setUp.st A Balloon-Tests.package/ShortIntegerArrayTest.class/instance/testing/testAt.st A Balloon-Tests.package/ShortIntegerArrayTest.class/instance/testing/testAtPut.st A Balloon-Tests.package/ShortIntegerArrayTest.class/instance/testing/testSetUp.st A Balloon-Tests.package/ShortIntegerArrayTest.class/instance/testing/testSwapBytePairs.st A Balloon-Tests.package/ShortIntegerArrayTest.class/instance/testing/testWriteBigEndianOn.st A Balloon-Tests.package/ShortIntegerArrayTest.class/instance/testing/testWriteLittleEndianOn.st R BalloonTests.package/PointArrayTest.class/README.md R BalloonTests.package/PointArrayTest.class/definition.st R BalloonTests.package/PointArrayTest.class/instance/running/setUp.st R BalloonTests.package/PointArrayTest.class/instance/testing/testAt.st R BalloonTests.package/PointArrayTest.class/instance/testing/testAtPut.st R BalloonTests.package/PointArrayTest.class/instance/testing/testAtPutFloat.st R BalloonTests.package/PointArrayTest.class/instance/testing/testAtPutFraction.st R BalloonTests.package/PointArrayTest.class/instance/testing/testAtPutInt4.st R BalloonTests.package/PointArrayTest.class/instance/testing/testAtPutLargeInteger.st R BalloonTests.package/PointArrayTest.class/instance/testing/testBounds.st R BalloonTests.package/PointArrayTest.class/instance/testing/testDefaultElement.st R BalloonTests.package/PointArrayTest.class/instance/testing/testSize.st R BalloonTests.package/ShortIntegerArrayTest.class/README.md R BalloonTests.package/ShortIntegerArrayTest.class/definition.st R BalloonTests.package/ShortIntegerArrayTest.class/instance/running/setUp.st R BalloonTests.package/ShortIntegerArrayTest.class/instance/testing/testAt.st R BalloonTests.package/ShortIntegerArrayTest.class/instance/testing/testAtPut.st R BalloonTests.package/ShortIntegerArrayTest.class/instance/testing/testSetUp.st R BalloonTests.package/ShortIntegerArrayTest.class/instance/testing/testSwapBytePairs.st R BalloonTests.package/ShortIntegerArrayTest.class/instance/testing/testWriteBigEndianOn.st R BalloonTests.package/ShortIntegerArrayTest.class/instance/testing/testWriteLittleEndianOn.st M Collections-Abstract.package/ManifestCollectionsAbstract.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st R Jobs.package/ManifestJobs.class/class/meta-data - dependency analyser/ignoredDependencies.st R Jobs.package/ManifestJobs.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st M Kernel.package/ManifestKernel.class/class/meta-data - dependency analyser/ignoredDependencies.st M Kernel.package/ManifestKernel.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st A Network-Tests.package/Base64MimeConverterTest.class/README.md A Network-Tests.package/Base64MimeConverterTest.class/definition.st A Network-Tests.package/Base64MimeConverterTest.class/instance/setup/setUp.st A Network-Tests.package/Base64MimeConverterTest.class/instance/tests/testBase64Encoded.st A Network-Tests.package/Base64MimeConverterTest.class/instance/tests/testDecodeMimeHeader.st A Network-Tests.package/Base64MimeConverterTest.class/instance/tests/testMimeEncodeDecode.st A Network-Tests.package/Base64MimeConverterTest.class/instance/tests/testOnByteArray.st A Network-Tests.package/HTTPEncodingTest.class/README.md A Network-Tests.package/HTTPEncodingTest.class/definition.st A Network-Tests.package/HTTPEncodingTest.class/instance/tests/testEncodeForHTTP.st A Network-Tests.package/MailAddressParserTest.class/README.md A Network-Tests.package/MailAddressParserTest.class/definition.st A Network-Tests.package/MailAddressParserTest.class/instance/tests/testAddressesIn.st A Network-Tests.package/MailMessageTest.class/README.md A Network-Tests.package/MailMessageTest.class/definition.st A Network-Tests.package/MailMessageTest.class/instance/tests/testCreateFromString.st A Network-Tests.package/MailMessageTest.class/instance/tests/testMultiPartAlternative.st A Network-Tests.package/MailMessageTest.class/instance/tests/testMultiPartMixed.st A Network-Tests.package/MailMessageTest.class/instance/tests/testRecipientList.st A Network-Tests.package/MailMessageTest.class/instance/tests/testSimpleCreate.st A Network-Tests.package/MockSocketStream.class/README.md A Network-Tests.package/MockSocketStream.class/class/instance creation/on_.st A Network-Tests.package/MockSocketStream.class/definition.st A Network-Tests.package/MockSocketStream.class/instance/accessing/atEnd_.st A Network-Tests.package/MockSocketStream.class/instance/accessing/inStream.st A Network-Tests.package/MockSocketStream.class/instance/accessing/outStream.st A Network-Tests.package/MockSocketStream.class/instance/initialization/initialize.st A Network-Tests.package/MockSocketStream.class/instance/stream in/nextLine.st A Network-Tests.package/MockSocketStream.class/instance/stream in/nextLineCrLf.st A Network-Tests.package/MockSocketStream.class/instance/stream in/resetInStream.st A Network-Tests.package/MockSocketStream.class/instance/stream in/upToAll_.st A Network-Tests.package/MockSocketStream.class/instance/stream out/resetOutStream.st A Network-Tests.package/MockSocketStream.class/instance/stream out/sendCommand_.st A Network-Tests.package/MockSocketStream.class/instance/testing/atEnd.st A Network-Tests.package/NetNameResolverTest.class/README.md A Network-Tests.package/NetNameResolverTest.class/definition.st A Network-Tests.package/NetNameResolverTest.class/instance/accessing/localHostAddressIsLoopBackAddress.st A Network-Tests.package/NetNameResolverTest.class/instance/accessing/localHostNameIsLoopBackName.st A Network-Tests.package/NetNameResolverTest.class/instance/testing/testLocalHostAddress.st A Network-Tests.package/NetNameResolverTest.class/instance/testing/testLocalHostName.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/README.md A Network-Tests.package/QuotedPrintableMimeConverterTest.class/definition.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/accesing/decode_.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/accesing/encode_.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/running/setUp.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeCRLF.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeCustomNewline.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeDecodedStrings.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeSimpleStrings.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeSoftLinebreak.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeSoftLinebreakCR.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeSoftLinebreakCRLF.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeSoftLinebreakLF.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeCR.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeCRLF.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeEncodedStrings.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeLF.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeLongLine.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeSimpleStrings.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeSoftLinebreak.st A Network-Tests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testLongLine.st A Network-Tests.package/SMTPClientTest.class/README.md A Network-Tests.package/SMTPClientTest.class/definition.st A Network-Tests.package/SMTPClientTest.class/instance/running/setUp.st A Network-Tests.package/SMTPClientTest.class/instance/testing/testMailFrom.st A Network-Tests.package/SocketStreamTest.class/README.md A Network-Tests.package/SocketStreamTest.class/definition.st A Network-Tests.package/SocketStreamTest.class/instance/setup/setUp.st A Network-Tests.package/SocketStreamTest.class/instance/setup/tearDown.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testNextIntoClose.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testNextIntoCloseNonSignaling.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testUpTo.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testUpToAfterCloseNonSignaling.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testUpToAfterCloseSignaling.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testUpToAll.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testUpToAllAfterCloseNonSignaling.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testUpToAllAfterCloseSignaling.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testUpToAllLimit.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testUpToAllTimeout.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testUpToEndClose.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testUpToEndCloseNonSignaling.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testUpToMax.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testUpToSmallInteger.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testUpToTimeout.st A Network-Tests.package/SocketStreamTest.class/instance/stream protocol/testUpToWithByteArray.st A Network-Tests.package/SocketTest.class/README.md A Network-Tests.package/SocketTest.class/definition.st A Network-Tests.package/SocketTest.class/instance/setup/listenerAddress.st A Network-Tests.package/SocketTest.class/instance/setup/listenerPort.st A Network-Tests.package/SocketTest.class/instance/setup/setUp.st A Network-Tests.package/SocketTest.class/instance/setup/tearDown.st A Network-Tests.package/SocketTest.class/instance/tests/testClientConnect.st A Network-Tests.package/SocketTest.class/instance/tests/testDataReceive.st A Network-Tests.package/SocketTest.class/instance/tests/testDataSending.st A Network-Tests.package/SocketTest.class/instance/tests/testLocalAddress.st A Network-Tests.package/SocketTest.class/instance/tests/testLocalPort.st A Network-Tests.package/SocketTest.class/instance/tests/testRemoteAddress.st A Network-Tests.package/SocketTest.class/instance/tests/testRemotePort.st A Network-Tests.package/SocketTest.class/instance/tests/testServerAccept.st A Network-Tests.package/SocketTest.class/instance/tests/testUDPBroadcastError.st A Network-Tests.package/TCPSocketEchoTest.class/README.md A Network-Tests.package/TCPSocketEchoTest.class/definition.st A Network-Tests.package/TCPSocketEchoTest.class/instance/accessing/localhost.st A Network-Tests.package/TCPSocketEchoTest.class/instance/accessing/port.st A Network-Tests.package/TCPSocketEchoTest.class/instance/private/withTCPEchoServer_.st A Network-Tests.package/TCPSocketEchoTest.class/instance/testing/clientSend_.st A Network-Tests.package/TCPSocketEchoTest.class/instance/testing/runServer.st A Network-Tests.package/TCPSocketEchoTest.class/instance/testing/testEcho.st A Network-Tests.package/UDPSocketEchoTest.class/README.md A Network-Tests.package/UDPSocketEchoTest.class/definition.st A Network-Tests.package/UDPSocketEchoTest.class/instance/accessing/localhost.st A Network-Tests.package/UDPSocketEchoTest.class/instance/accessing/port.st A Network-Tests.package/UDPSocketEchoTest.class/instance/private/receiveUDPDataFrom_.st A Network-Tests.package/UDPSocketEchoTest.class/instance/private/withUDPEchoServer_.st A Network-Tests.package/UDPSocketEchoTest.class/instance/testing/clientSend_.st A Network-Tests.package/UDPSocketEchoTest.class/instance/testing/runServer.st A Network-Tests.package/UDPSocketEchoTest.class/instance/testing/testEcho.st A Network-Tests.package/UUIDPrimitivesTest.class/README.md A Network-Tests.package/UUIDPrimitivesTest.class/definition.st A Network-Tests.package/UUIDPrimitivesTest.class/instance/tests/testComparison.st A Network-Tests.package/UUIDPrimitivesTest.class/instance/tests/testCreation.st A Network-Tests.package/UUIDPrimitivesTest.class/instance/tests/testCreationEquality.st A Network-Tests.package/UUIDPrimitivesTest.class/instance/tests/testCreationFromString.st A Network-Tests.package/UUIDPrimitivesTest.class/instance/tests/testCreationFromString36NotNil.st A Network-Tests.package/UUIDPrimitivesTest.class/instance/tests/testCreationFromString36With0.st A Network-Tests.package/UUIDPrimitivesTest.class/instance/tests/testCreationFromString36WithNillUUID.st A Network-Tests.package/UUIDPrimitivesTest.class/instance/tests/testCreationFromStringNotNil.st A Network-Tests.package/UUIDPrimitivesTest.class/instance/tests/testCreationNil.st A Network-Tests.package/UUIDPrimitivesTest.class/instance/tests/testCreationNodeBased.st A Network-Tests.package/UUIDPrimitivesTest.class/instance/tests/testDuplicationsKinda.st A Network-Tests.package/UUIDPrimitivesTest.class/instance/tests/testOrder.st A Network-Tests.package/UUIDPrimitivesTest.class/instance/tests/testUniqueness.st A Network-Tests.package/UUIDTest.class/README.md A Network-Tests.package/UUIDTest.class/definition.st A Network-Tests.package/UUIDTest.class/instance/testing/testComparison.st R NetworkTests.package/Base64MimeConverterTest.class/README.md R NetworkTests.package/Base64MimeConverterTest.class/definition.st R NetworkTests.package/Base64MimeConverterTest.class/instance/setup/setUp.st R NetworkTests.package/Base64MimeConverterTest.class/instance/tests/testBase64Encoded.st R NetworkTests.package/Base64MimeConverterTest.class/instance/tests/testDecodeMimeHeader.st R NetworkTests.package/Base64MimeConverterTest.class/instance/tests/testMimeEncodeDecode.st R NetworkTests.package/Base64MimeConverterTest.class/instance/tests/testOnByteArray.st R NetworkTests.package/HTTPEncodingTest.class/README.md R NetworkTests.package/HTTPEncodingTest.class/definition.st R NetworkTests.package/HTTPEncodingTest.class/instance/tests/testEncodeForHTTP.st R NetworkTests.package/MailAddressParserTest.class/README.md R NetworkTests.package/MailAddressParserTest.class/definition.st R NetworkTests.package/MailAddressParserTest.class/instance/tests/testAddressesIn.st R NetworkTests.package/MailMessageTest.class/README.md R NetworkTests.package/MailMessageTest.class/definition.st R NetworkTests.package/MailMessageTest.class/instance/tests/testCreateFromString.st R NetworkTests.package/MailMessageTest.class/instance/tests/testMultiPartAlternative.st R NetworkTests.package/MailMessageTest.class/instance/tests/testMultiPartMixed.st R NetworkTests.package/MailMessageTest.class/instance/tests/testRecipientList.st R NetworkTests.package/MailMessageTest.class/instance/tests/testSimpleCreate.st R NetworkTests.package/MockSocketStream.class/README.md R NetworkTests.package/MockSocketStream.class/class/instance creation/on_.st R NetworkTests.package/MockSocketStream.class/definition.st R NetworkTests.package/MockSocketStream.class/instance/accessing/atEnd_.st R NetworkTests.package/MockSocketStream.class/instance/accessing/inStream.st R NetworkTests.package/MockSocketStream.class/instance/accessing/outStream.st R NetworkTests.package/MockSocketStream.class/instance/initialization/initialize.st R NetworkTests.package/MockSocketStream.class/instance/stream in/nextLine.st R NetworkTests.package/MockSocketStream.class/instance/stream in/nextLineCrLf.st R NetworkTests.package/MockSocketStream.class/instance/stream in/resetInStream.st R NetworkTests.package/MockSocketStream.class/instance/stream in/upToAll_.st R NetworkTests.package/MockSocketStream.class/instance/stream out/resetOutStream.st R NetworkTests.package/MockSocketStream.class/instance/stream out/sendCommand_.st R NetworkTests.package/MockSocketStream.class/instance/testing/atEnd.st R NetworkTests.package/NetNameResolverTest.class/README.md R NetworkTests.package/NetNameResolverTest.class/definition.st R NetworkTests.package/NetNameResolverTest.class/instance/accessing/localHostAddressIsLoopBackAddress.st R NetworkTests.package/NetNameResolverTest.class/instance/accessing/localHostNameIsLoopBackName.st R NetworkTests.package/NetNameResolverTest.class/instance/testing/testLocalHostAddress.st R NetworkTests.package/NetNameResolverTest.class/instance/testing/testLocalHostName.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/README.md R NetworkTests.package/QuotedPrintableMimeConverterTest.class/definition.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/accesing/decode_.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/accesing/encode_.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/running/setUp.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeCRLF.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeCustomNewline.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeDecodedStrings.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeSimpleStrings.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeSoftLinebreak.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeSoftLinebreakCR.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeSoftLinebreakCRLF.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeSoftLinebreakLF.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeCR.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeCRLF.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeEncodedStrings.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeLF.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeLongLine.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeSimpleStrings.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeSoftLinebreak.st R NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testLongLine.st R NetworkTests.package/SMTPClientTest.class/README.md R NetworkTests.package/SMTPClientTest.class/definition.st R NetworkTests.package/SMTPClientTest.class/instance/running/setUp.st R NetworkTests.package/SMTPClientTest.class/instance/testing/testMailFrom.st R NetworkTests.package/SocketStreamTest.class/README.md R NetworkTests.package/SocketStreamTest.class/definition.st R NetworkTests.package/SocketStreamTest.class/instance/setup/setUp.st R NetworkTests.package/SocketStreamTest.class/instance/setup/tearDown.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testNextIntoClose.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testNextIntoCloseNonSignaling.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testUpTo.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testUpToAfterCloseNonSignaling.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testUpToAfterCloseSignaling.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testUpToAll.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testUpToAllAfterCloseNonSignaling.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testUpToAllAfterCloseSignaling.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testUpToAllLimit.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testUpToAllTimeout.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testUpToEndClose.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testUpToEndCloseNonSignaling.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testUpToMax.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testUpToSmallInteger.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testUpToTimeout.st R NetworkTests.package/SocketStreamTest.class/instance/stream protocol/testUpToWithByteArray.st R NetworkTests.package/SocketTest.class/README.md R NetworkTests.package/SocketTest.class/definition.st R NetworkTests.package/SocketTest.class/instance/setup/listenerAddress.st R NetworkTests.package/SocketTest.class/instance/setup/listenerPort.st R NetworkTests.package/SocketTest.class/instance/setup/setUp.st R NetworkTests.package/SocketTest.class/instance/setup/tearDown.st R NetworkTests.package/SocketTest.class/instance/tests/testClientConnect.st R NetworkTests.package/SocketTest.class/instance/tests/testDataReceive.st R NetworkTests.package/SocketTest.class/instance/tests/testDataSending.st R NetworkTests.package/SocketTest.class/instance/tests/testLocalAddress.st R NetworkTests.package/SocketTest.class/instance/tests/testLocalPort.st R NetworkTests.package/SocketTest.class/instance/tests/testRemoteAddress.st R NetworkTests.package/SocketTest.class/instance/tests/testRemotePort.st R NetworkTests.package/SocketTest.class/instance/tests/testServerAccept.st R NetworkTests.package/SocketTest.class/instance/tests/testUDPBroadcastError.st R NetworkTests.package/TCPSocketEchoTest.class/README.md R NetworkTests.package/TCPSocketEchoTest.class/definition.st R NetworkTests.package/TCPSocketEchoTest.class/instance/accessing/localhost.st R NetworkTests.package/TCPSocketEchoTest.class/instance/accessing/port.st R NetworkTests.package/TCPSocketEchoTest.class/instance/private/withTCPEchoServer_.st R NetworkTests.package/TCPSocketEchoTest.class/instance/testing/clientSend_.st R NetworkTests.package/TCPSocketEchoTest.class/instance/testing/runServer.st R NetworkTests.package/TCPSocketEchoTest.class/instance/testing/testEcho.st R NetworkTests.package/UDPSocketEchoTest.class/README.md R NetworkTests.package/UDPSocketEchoTest.class/definition.st R NetworkTests.package/UDPSocketEchoTest.class/instance/accessing/localhost.st R NetworkTests.package/UDPSocketEchoTest.class/instance/accessing/port.st R NetworkTests.package/UDPSocketEchoTest.class/instance/private/receiveUDPDataFrom_.st R NetworkTests.package/UDPSocketEchoTest.class/instance/private/withUDPEchoServer_.st R NetworkTests.package/UDPSocketEchoTest.class/instance/testing/clientSend_.st R NetworkTests.package/UDPSocketEchoTest.class/instance/testing/runServer.st R NetworkTests.package/UDPSocketEchoTest.class/instance/testing/testEcho.st R NetworkTests.package/UUIDPrimitivesTest.class/README.md R NetworkTests.package/UUIDPrimitivesTest.class/definition.st R NetworkTests.package/UUIDPrimitivesTest.class/instance/tests/testComparison.st R NetworkTests.package/UUIDPrimitivesTest.class/instance/tests/testCreation.st R NetworkTests.package/UUIDPrimitivesTest.class/instance/tests/testCreationEquality.st R NetworkTests.package/UUIDPrimitivesTest.class/instance/tests/testCreationFromString.st R NetworkTests.package/UUIDPrimitivesTest.class/instance/tests/testCreationFromString36NotNil.st R NetworkTests.package/UUIDPrimitivesTest.class/instance/tests/testCreationFromString36With0.st R NetworkTests.package/UUIDPrimitivesTest.class/instance/tests/testCreationFromString36WithNillUUID.st R NetworkTests.package/UUIDPrimitivesTest.class/instance/tests/testCreationFromStringNotNil.st R NetworkTests.package/UUIDPrimitivesTest.class/instance/tests/testCreationNil.st R NetworkTests.package/UUIDPrimitivesTest.class/instance/tests/testCreationNodeBased.st R NetworkTests.package/UUIDPrimitivesTest.class/instance/tests/testDuplicationsKinda.st R NetworkTests.package/UUIDPrimitivesTest.class/instance/tests/testOrder.st R NetworkTests.package/UUIDPrimitivesTest.class/instance/tests/testUniqueness.st R NetworkTests.package/UUIDTest.class/README.md R NetworkTests.package/UUIDTest.class/definition.st R NetworkTests.package/UUIDTest.class/instance/testing/testComparison.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50297.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50298.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50297.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50298.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/TabManagerModel.class/instance/api/removeTab_.st M Spec-Core.package/TabManagerModel.class/instance/initialization/initialize.st A Spec-Core.package/TabManagerModel.class/instance/private/basicRemoveTab_.st A Spec-MorphicAdapters.package/MorphicTabManagerAdapter.class/instance/factory/buildTab_.st M Spec-MorphicAdapters.package/MorphicTabManagerAdapter.class/instance/spec protocol/addTab_.st A Spec-MorphicAdapters.package/MorphicTabManagerAdapter.class/instance/spec protocol/removeTab_.st M Spec-MorphicAdapters.package/MorphicTabManagerAdapter.class/instance/widget API/getTabs.st A Spec-MorphicAdapters.package/MorphicTabManagerAdapter.class/instance/widget API/tabDeleted_.st M Spec-Tests.package/TabModelTest.class/README.md M Spec-Tests.package/TabModelTest.class/definition.st A Spec-Tests.package/TabModelTest.class/instance/instance creation/redMorphTab.st A Spec-Tests.package/TabModelTest.class/instance/running/setUp.st A Spec-Tests.package/TabModelTest.class/instance/running/tearDown.st A Spec-Tests.package/TabModelTest.class/instance/tests/testAddTabOpened.st A Spec-Tests.package/TabModelTest.class/instance/tests/testAddTabUnopened.st M Spec-Tests.package/TabModelTest.class/instance/tests/testChangeLabel.st M Spec-Tests.package/TabModelTest.class/instance/tests/testInitialSelectedTab.st A Spec-Tests.package/TabModelTest.class/instance/tests/testRemoveTab.st A Spec-Tests.package/TabModelTest.class/instance/tests/testRemoveTabFromManager.st A Spec-Tests.package/TabModelTest.class/instance/tests/testRemoveTabFromManager2.st A Spec-Tests.package/TabModelTest.class/instance/tests/testRemoveTabFromMorphic.st A Spec-Tests.package/TabModelTest.class/instance/utility/morphicTabsFor_.st R Spec-Tests.package/TabModelTest.class/instance/utility/redMorphTab.st M System-FileRegistry.package/ManifestSystemFileRegistry.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st M UIManager.package/ManifestUIManager.class/class/meta-data - dependency analyser/ignoredDependencies.st Log Message: ----------- 50298 14426 BalloonTests package should be Balloon-Tests https://pharo.fogbugz.com/f/cases/14426 14437 NetworkTests package should be Network-Tests https://pharo.fogbugz.com/f/cases/14437 16449 update bootstrap dependencies v2 https://pharo.fogbugz.com/f/cases/16449 11461 TabModel not really removed tabs https://pharo.fogbugz.com/f/cases/11461 http://files.pharo.org/image/50/50298.zip

Sept. 2, 2015

Re: [Pharo-dev] Removing name from Object

by Sven Van Caekenberghe

> On 02 Sep 2015, at 10:21, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > The problem is if (like in the past) name is extensively used by some library we depend upon (like... let's say morphic), a deprecation that raises an exception may turn the system unusable. It's not that it is not doable, but we should do it gently and with love. You mean (Object>>#name) removeFromSystem ;-) > El miÃ©., 2 de sept. de 2015 a la(s) 9:30 a. m., Esteban Lorenzano <estebanlm(a)gmail.com> escribiÃ³: >> On 02 Sep 2015, at 09:25, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >> On Wed, Sep 2, 2015 at 8:40 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: >> How can we find out, which external projects depend on this? >> >> Is #name in any way special? Why not just deprecate it like any other method change or removal? (And then remove it in Pharo 6) > > +1 > thatâs the way to do it :) > >> >> Peter >

Sept. 2, 2015