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

[pharo-project/pharo-core] df7367: 50100

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: df73677225de0364458ca941b2a3c48e34df276b https://github.com/pharo-project/pharo-core/commit/df73677225de0364458ca941… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-06-10 (Wed, 10 Jun 2015) Changed paths: A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyName.st A Reflectivity.package/RFNameReification.class/README.md A Reflectivity.package/RFNameReification.class/class/plugin interface/key.st A Reflectivity.package/RFNameReification.class/class/plugin interface/nodes.st A Reflectivity.package/RFNameReification.class/definition.st A Reflectivity.package/RFNameReification.class/instance/generate/genForRBVariableNode.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50099.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50100.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50099.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50100.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Shout.package/SHParserST80.class/instance/scan/-=.st M System-Support.package/SystemNavigation.class/instance/packages/allClassesInPackageNamed_.st M System-Support.package/SystemNavigation.class/instance/packages/removeAllButPackages_.st M System-Support.package/SystemNavigation.class/instance/query/allBehaviorsDo_.st M System-Support.package/SystemNavigation.class/instance/query/allClassesAndTraits.st M Tool-Base.package/extension/SystemNavigation/instance/browseClassCommentsWithString_matchCase_.st Log Message: ----------- 50100 15722 Remove unused method -= in SHParserST80 https://pharo.fogbugz.com/f/cases/15722 15725 SystemNavigation shouldnt use Smalltalk globals for self environment https://pharo.fogbugz.com/f/cases/15725 15721 Reflectivity: add #name reification for Variables https://pharo.fogbugz.com/f/cases/15721 http://files.pharo.org/image/50/50100.zip

June 10, 2015

Re: [Pharo-dev] [Pharo-users] Using GTSpotter how do I find an implementor of #accept ?

by Nicolai Hess

2015-06-10 7:39 GMT+02:00 Paul DeBruicker <pdebruic(a)gmail.com>: > when I hit shift+enter and type 'accept' I get things that are not > #accept, e.g. #accept: and AbstractAcceptor. > > If I add a space after accept it doesn't help. > > > What do I not understand? > the result list is not sorted and the result list is built by all methods having the query string as part of its selector name. Yes this can be improved and it is not difficult, for example you can add this method to GTFilterImplementor>>applyFilterWithQuery super applyFilterWithQuery. items sort: [ :a :b | (self itemFilterNameFor: a) size < (self itemFilterNameFor: b) size ] this will sort the result list by the size of the selector name. So, if there is a perfect match, it will be listed first. (BUT only in the implementors category if you "dive-in", not in the 5-elements-result-preview-list). Maybe there is a better way without sorting. (We can modify applyFilterWithQuery for the implementors filter, to put perfect matches at the begining of the list). But all this is not easy to discover. Spotter classes make some heavy use of delegation, many operations are split and delgated to subclasses (GOOD!) many classes aren't documented (BAD!) and this makes it really difficult to catch how all this is supposed to work together. nicolai > > > Thanks > > > Paul >

June 10, 2015

Re: [Pharo-dev] Testers needed! Re: Athens BitBlt bug?

by Igor Stasenko

On 9 June 2015 at 22:54, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2015-06-09 18:03 GMT+02:00 Igor Stasenko <siguctua(a)gmail.com>: > >> >> >> >> >> >> the easiest way to reproduce it would be: >> - allocate a new surface of such dimensions, that its buffer size will be >> aligned with 4k page boundary (a smallest one would be 1x1024, or 1024x1, >> since one pixel is 4 bytes) >> - try to blit this surface with bitblt >> - crash >> >> (sure it happens not always, since often there could be another memory >> page allocated for other purposes with read access granted, >> but if you continuously do that, you will inevitable face the crash) >> > > Thank you for your feedback, > but still no "luck" - no crash. > > Do you remember if this happens on windows at all or only on mac? > > Dunno. I had it on my mac. Sure it may depend on how OS/C libs allocating memory. Anyways, since we're talking about using bitmaps as fill patterns for cairo, it should be safe as long as bitblt never involved with it. Actually registering surfaces with bitblt required only if they used in operations like copying their contents to Display form require this workaround, since it involves bitblt primitive(s). For the rest of cases (and if one day, hopefully we stop using bitblt altogether), the need in this workaround can be completely eliminated. So the issue can be localized if we split implementation and make a subclass, lets say CairoMorphicCompatibleSurface, where we move all registering logic together with workarounds, and in basic class simply throw exception on attempt to use it #asForm. > > > >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- Best regards, Igor Stasenko.

June 9, 2015

Re: [Pharo-dev] Testers needed! Re: Athens BitBlt bug?

by Nicolai Hess

2015-06-09 18:03 GMT+02:00 Igor Stasenko <siguctua(a)gmail.com>: > > > > > > the easiest way to reproduce it would be: > - allocate a new surface of such dimensions, that its buffer size will be > aligned with 4k page boundary (a smallest one would be 1x1024, or 1024x1, > since one pixel is 4 bytes) > - try to blit this surface with bitblt > - crash > > (sure it happens not always, since often there could be another memory > page allocated for other purposes with read access granted, > but if you continuously do that, you will inevitable face the crash) > Thank you for your feedback, but still no "luck" - no crash. Do you remember if this happens on windows at all or only on mac? > > -- > Best regards, > Igor Stasenko. >

June 9, 2015

Re: [Pharo-dev] Cannot browse class side methods :)

by Nicolai Hess

2015-06-09 20:23 GMT+02:00 stepharo <stepharo(a)free.fr>: > reverting ... reintroduces the old behavior and bug but we can browse > class methods. > If you revert this change, you can add the following change replace self selectedClass = class ifTrue: [ self selectedClass: nil ]. with self selectedClass theNonMetaClass = class ifTrue: [ self selectedClass: nil ]. in AbstractNautilusUI>>#classRemoved: this should solve the bug "15708 Deleting a class with nautilus raises an error" > > selectedClassWithoutChangingSelection: aClass > > self resetCategoriesList. > self okToChangeSourceAndComment > ifFalse: [ ^ self ]. > aClass > ifNil: [ self unselectClass ] > ifNotNil: [ > acceptor := ClassOrMethodDefinitionAcceptor model: self. > self classWidget selectClass: aClass. > ((self selectedPackageIncludes: aClass theNonMetaClass) or: [ > model showHierarchy ]) > ifTrue: [ > self model > package: self selectedPackage > class: aClass theNonMetaClass > category: nil > method: nil ] > ifFalse: [ self selectedClass: aClass withSelection: (self > parentOfClass: aClass theNonMetaClass) ]. > self updateOnClassSelection ]. > > => > > selectedClassWithoutChangingSelection: aClass > > self resetCategoriesList. > self okToChangeSourceAndComment > ifFalse: [ ^ self ]. > aClass > ifNil: [ self unselectClass ] > ifNotNil: [ > acceptor := ClassOrMethodDefinitionAcceptor model: self. > self classWidget selectClass: aClass. > ((self selectedPackageIncludes: aClass theNonMetaClass) or: [ > model showHierarchy ]) > ifTrue: [ > self model > package: self selectedPackage > class: aClass > category: nil > method: nil ] > ifFalse: [ self selectedClass: aClass withSelection: (self > parentOfClass: aClass) ]. > self updateOnClassSelection ]. > >

June 9, 2015

Re: [Pharo-dev] Roassal Camp Smalltalk

by Yuriy Tymchuk

> On 08 Jun 2015, at 18:22, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> Well at least for me it is certainly not clear what release policy is Roassal following; i.e. if I see a minor version change what to expect, if any BC breaks were introduced, etc. Of course this is extra effort for the person doing it, so it should be taken with care. But there are certainly things to be discussed about this. > > Hi Peter, > > Indeed, we have not been good at producing a descent version numbering schema. > My position was always this one: the last version should always fit your need. However, some product favored stability when Roassal is used in a commercial setting. > We will be more careful when updating the configuration with a proper version number. Versioning is in fact a complex thing. Thatâs why I suggest to have a brainstorming session during the camp. Uko > > Cheers, > Alexandre > > >> >> On Fri, Jun 5, 2015 at 7:31 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> Oh, then itâs my bad. Last time Iâve checked it seemed that it wasnât updated for a long time. Maybe I was wrong. >> >> Uko >> >> >> >>> On 05 Jun 2015, at 18:08, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>> >>> There sure are, look at ConfigurationOfRoassal2>>version*: >>> >>> and in my baseline I have something like >>> >>> ~~~~~~~~~~~ >>> spec >>> project: 'Roassal2' with: [ >>> spec >>> className: #ConfigurationOfRoassal2; >>> versionString: '1.52'; >>> repository: 'http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/' ]; >>> ~~~~~~~~~~~ >>> >>> Peter >>> >>> On Fri, Jun 5, 2015 at 4:37 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>> But are there numbered version to refer to? >>> >>> Uko >>> >>>> On 05 Jun 2015, at 16:34, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>> >>>> >>>> >>>> On Fri, Jun 5, 2015 at 3:29 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>> Iâm interested in participating. Personally Iâd like to talk more about design decisions behind roassal ecosystem, release strategy and so on. Usually when I work with Roassal I have this issue that things are breaking because of rapid changes, or because of the differences between different parts of roassal. Maybe someone is also concerned about this, so we can discuss and maybe improve somethingâ¦ >>>> >>>> Yes I am also interested in this, right now I am actually using quite old version (month+) because I didn't have time to keep up. :) (Arguably 90% of my problems were from infamous composite shapes. :)) >>>> >>>> Peter >>>> >>>> Uko >>>> >>>>> On 04 Jun 2015, at 19:55, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>>> >>>>> Dear Colleagues and Friends, >>>>> >>>>> We are happy to announce we will organize a CampSmalltalk about the Roassal visualization engine, on _Sunday 12 July_. >>>>> >>>>> As far as we have seen, the interests are multiple. Here is a list of topics we will happy to work on: >>>>> - Port of Roassal on VisualWorks >>>>> - Using Roassal on Gemstone >>>>> - HTML/JavaScript export >>>>> - Improving Grapher, our charting library >>>>> >>>>> If you wish to participate, get in touch with us. Since we will probably have a sponsoring of the event, it would be nice to know how many will attend to ease the logistic and the pizza ordering :-) >>>>> >>>>> Cheers, >>>>> Alexandre >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

June 9, 2015

Re: [Pharo-dev] Comments in STON

by Sven Van Caekenberghe

Where exactly can I find what you changed ? I don't see any commit of you on github ... > On 09 Jun 2015, at 20:10, stepharo <stepharo(a)free.fr> wrote: > > > > Le 9/6/15 20:06, stepharo a Ã©crit : >> I will update the STON chapter :) > > Done :) > >> >> >> Le 8/6/15 23:39, Sven Van Caekenberghe a Ã©crit : >>> I would do it like this: use a wrapping stream to skip comments. >>> >>> === >>> Name: STON-Core-SvenVanCaekenberghe.59 >>> Author: SvenVanCaekenberghe >>> Time: 8 June 2015, 11:34:32.886167 pm >>> UUID: 7ab942b5-9d1a-44c3-9d58-da29feb72380 >>> Ancestors: STON-Core-SvenVanCaekenberghe.58 >>> >>> Add experimental STONCStyleCommentsSkipStream and tests >>> === >>> Name: STON-Tests-SvenVanCaekenberghe.54 >>> Author: SvenVanCaekenberghe >>> Time: 8 June 2015, 11:34:52.918771 pm >>> UUID: 3dcb2c9c-6efe-4d62-bf36-3bbe91f09d08 >>> Ancestors: STON-Tests-SvenVanCaekenberghe.53 >>> >>> Add experimental STONCStyleCommentsSkipStream and tests >>> === >>> >>> Then you can do as follows: >>> >>> STON fromStream: (STONCStyleCommentsSkipStream on: 'Point[/* this is X*/ 1, /* this is Y*/ 2] // Nice huh ?' readStream). >>> >>> => 1@2 >>> >>> STON fromStream: (STONCStyleCommentsSkipStream on: '// Here is how you create a point: >>> Point[ >>> // this is X >>> 1, >>> // this is Y >>> 2 ] >>> // Nice huh ?' readStream). >>> >>> => 1@2 >>> >>> This helper class would be useable in other contexts too (like NeoJSON). >>> >>> The advantage is that it does not change the STON (or JSON) syntax itself, it just add some functionality for those who want it. >>> >>> What do you think ? >>> >>> Sven >>> >>> PS: this probably needs some more testing >>> >>>> On 08 Jun 2015, at 17:16, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>>> On 08 Jun 2015, at 17:03, Damien Cassou <damien.cassou(a)inria.fr> wrote: >>>>> >>>>> >>>>> Sven Van Caekenberghe <sven(a)stfx.eu> writes: >>>>> >>>>>> I am not so sure we should add that. >>>>>> >>>>>> The JSON spec explicitly does not allow comments because of fear of abuse (that the comments would be used to add semantic meaning outside the spec). >>>>> >>>>> really? That's surprising. Comments in configuration files are very >>>>> important. Even more when the configuration files are templates for new >>>>> users. >>>> I know some people are using STON in ways that I did not originally anticipate, that is of course cool, but writing configuration files was not the original goal. STON is a version of JSON that is closer to our object model. >>>> >>>> Like I said, I will think about it. >>>> >>>>> -- >>>>> Damien Cassou >>>>> http://damiencassou.seasidehosting.st >>>>> >>>>> "Success is the ability to go from one failure to another without >>>>> losing enthusiasm." --Winston Churchill >>> >>> >> >> >> > >

June 9, 2015

Re: [Pharo-dev] Does anybody ever used compareToClipboard: ?

by Eliot Miranda

On Tue, Jun 9, 2015 at 11:15 AM, stepharo <stepharo(a)free.fr> wrote: > Does anybody ever used compareToClipboard: ? > Because we are thinking to remove it. > Yes, I use it enough that I would miss it. For example, run two different (de)compilations, list the output and compare the two using compareToClipboard. Occasionally it is useful to do a quick comparison of two texts, and the easiest way to do that us to use compareToClipboard. -- best, Eliot

June 9, 2015

Re: [Pharo-dev] Cannot browse class side methods :)

by stepharo

reverting ... reintroduces the old behavior and bug but we can browse class methods. selectedClassWithoutChangingSelection: aClass self resetCategoriesList. self okToChangeSourceAndComment ifFalse: [ ^ self ]. aClass ifNil: [ self unselectClass ] ifNotNil: [ acceptor := ClassOrMethodDefinitionAcceptor model: self. self classWidget selectClass: aClass. ((self selectedPackageIncludes: aClass theNonMetaClass) or: [ model showHierarchy ]) ifTrue: [ self model package: self selectedPackage class: aClass theNonMetaClass category: nil method: nil ] ifFalse: [ self selectedClass: aClass withSelection: (self parentOfClass: aClass theNonMetaClass) ]. self updateOnClassSelection ]. => selectedClassWithoutChangingSelection: aClass self resetCategoriesList. self okToChangeSourceAndComment ifFalse: [ ^ self ]. aClass ifNil: [ self unselectClass ] ifNotNil: [ acceptor := ClassOrMethodDefinitionAcceptor model: self. self classWidget selectClass: aClass. ((self selectedPackageIncludes: aClass theNonMetaClass) or: [ model showHierarchy ]) ifTrue: [ self model package: self selectedPackage class: aClass category: nil method: nil ] ifFalse: [ self selectedClass: aClass withSelection: (self parentOfClass: aClass) ]. self updateOnClassSelection ].

June 9, 2015

Cannot browse class side methods :)

by stepharo

Hi guys I think that one recent fix breaks the fact that we may want to see class method I suspect 15708 Deleting a class with nautilus raises an error https://pharo.fogbugz.com/f/cases/15708 Stef

June 9, 2015