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

Re: [Pharo-dev] [Pharo-users] Pillar 1.1.0 released

by Johan Brichau

Hi, I just noticed that in the most recent version of Pillar, the instvar #embedded was removed from PRReference This breaks Pierâ¦ though right before this change I could make Pier3 work with Pillar just fine. The embedded var is used to specify that component references are to be embedded in the page. There are more components than Figures in Pier. I am just trying to use and work with Pier3 for Seaside book and website, so it would be great if you can consider adding the embedded variable again. thanks guys! Johan ps: email me directly, since I might miss replies via the mailinglist. > On 07 Sep 2015, at 09:51, Damien Cassou <damien.cassou(a)inria.fr> wrote: > > Cyril Ferlicot and I have polished Pillar 1.0.0 a little. Here is 1.1.0 > changelog: > > - add shebang to generated pillarPostExport.sh > - improve pillarPostExport.sh messages a little > - HTML exporter > - output a <figure> if and only if the Pillar figure has both a > caption and a label > - LaTeX exporter > - output a \begin{figure} if and only if the Pillar figure has both > a caption and a label > > Cyril migrated the list of issues and feature requests from > smalltalkhub.com to > > https://github.com/pillar-markup/pillar/issues > > Please report issues, describe feature requests and ask questions there. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill >

Sept. 13, 2015

Re: [Pharo-dev] call "compress file " from the FileList

by Marcus Denker

> On 13 Sep 2015, at 00:26, Nicolai Hess <nicolaihess(a)web.de> wrote: > > There was a bug on compress file > (see issue https://pharo.fogbugz.com/f/cases/10235/StandardFileStream-compressFile-can… <https://pharo.fogbugz.com/f/cases/10235/StandardFileStream-compressFile-can…>) > > This is fixed know for Pharo 4.0, anyone knows why we can not call "compress file" > anymore in Pharo 5.0 ? > I think this could be a side effect (bug) from the new pragma based registration mechanism for registering actions in the FileList? Marcus

Sept. 13, 2015

call "compress file " from the FileList

by Nicolai Hess

There was a bug on compress file (see issue https://pharo.fogbugz.com/f/cases/10235/StandardFileStream-compressFile-can… ) This is fixed know for Pharo 4.0, anyone knows why we can not call "compress file" anymore in Pharo 5.0 ?

Sept. 12, 2015

Re: [Pharo-dev] "missing" exports on the windows vm

by Nicolai Hess

2015-05-21 20:35 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > > > 2015-05-06 0:11 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > >> We have a failing test case for NB >> NBInterpreterProxyTest>>#testStackPointer >> it fails because >> NativeBoost loadSymbol: 'stackPointerAddress' fromModule: NativeBoost >> VMModule >> returns nil >> >> This works for the linux vm! >> >> There are other methods that can be loaded, for example: >> (NativeBoost loadSymbol: 'primitiveAllObjects' fromModule: NativeBoost >> VMModule) >> -> returns an address. >> >> This stopped working for the windows pharo vm around june 2014. The >> source that >> changed is cointerp.h, the prior version had EXPORT(...) declarations >> around all >> functions in cointerp.h, the current version not. >> >> Three questions: >> >> 1. Why does this still work on linux? Does it export all functions >> declared in >> a header? >> 2. why was it changed? (I could not found the change in the code >> generator, maybe we >> exported all functions with pragma #api and now only those with pragma >> #export ? >> 3. do we need this function to be exported? Apart from this testcases, >> this method is >> called the on image startup, but the nil return does not harm. >> It seems it is not part of the main vm api (like the interpreter proxy >> functions callable from external modules) and I didn't see code thet depend >> on this. >> >> There are similiar functions for which we load the function address on >> startup: >> cStackPointerAddress and cFramePointerAddress, this seems to work, but I >> don't know if the expected result is different. >> >> In NBInterpreterProxy>>#initialize, we try to load all fourmethods: >> stackPointerAddress/framePointerAddress -> nil >> cStackPointerAddress / cFramePointerAddress -> not nil >> >> >> >> nicolai >> >> > > Anyone knows why the exports changed on windows? > Or if we need the stackPointerAddress/framePointerAddress methods? > > Maybe I'll just close the issue as won't fix. On the other hand, we now have this failing test (skipped for windows), so maybe I will remove the test. But still, I would like to know if this change was by accident or on purpose. If it was on purpose, maybe there is a way to make this test succeed on windows too? > > nicolai > >

Sept. 12, 2015

Re: [Pharo-dev] Strategies with Nautilus announcements

by stepharo

>> What we could do (maybe this is a bit overkill): >> >> - make an announcements hierarchy (NautilusPackageAnnouncement -> >> NautiulusClassAnnouncement ...) but never subscribe to this Announcemnts >> - create sub classes for every "kind" >> NautilusPackageAnnouncement subclass: NautilusPackageChangedAnnouncement >> NautilusPackageAnnouncement subclass: NautilusPackageSelectedAnnouncement >> >> NautilusClassAnnouncement subclass: NautilusClassSelectedAnnouncement >> NautilusClassAnnouncement subclass: NautilusClassChangedAnnouncement >> >> And only subscribe to this subclasses. >> That way we are using the hierarchy of Announcement classes for >> removing of duplicated code, but only >> register and announce the "leaf"-nodes >> (NautilusClassChangedAnnouncement / >> NautilusPackageChangedAnnouncement...) >> >> what do you think? > > This may do. Also another option would be to have > a NautilusSelectionAnnouncement with all 4 attributes, and then just > subclass it for a different type. Yes this solution is less verbose and has my preference. stef

Sept. 12, 2015

Re: [Pharo-dev] Strategies with Nautilus announcements

by Yuriy Tymchuk

> On 12 Sep 2015, at 17:34, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-09-09 14:32 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: > Hi, > > as NautilusMethodSelected contains also an information about protocol, class, package; > NautilusProtocolSelected contains an information about class and package; > . > . > . > > Iâve inherited NautilusClassSelected from NautilusPackageSelected and NautilusProtocolSelected from NautilusClassSelectedâ¦ to remove duplication. But as announcement subscription also includes itâs subclasses, if you subscribe to NautilusPackageSelected, you end up receiving also NautilusClassSelected, NautilusProtocolSelected and NautilusMethodSelected. > > What is a good way to resolve this (I can simply separate all the classes, but maybe there is something important from conceptual point of view)? > > I didn't know announcments are working that way, but it may make sense if you want to group announcments (register once for "WindowAnnouncement" and receiving all kind of > subannouncements (WindowClosed/WindowOpened â¦) I donât know about performance, but as far as I understand you can also subscribe to âWindowAnnouncement withAllSubclassesâ. > > What we could do (maybe this is a bit overkill): > > - make an announcements hierarchy (NautilusPackageAnnouncement -> NautiulusClassAnnouncement ...) but never subscribe to this Announcemnts > - create sub classes for every "kind" > NautilusPackageAnnouncement subclass: NautilusPackageChangedAnnouncement > NautilusPackageAnnouncement subclass: NautilusPackageSelectedAnnouncement > > NautilusClassAnnouncement subclass: NautilusClassSelectedAnnouncement > NautilusClassAnnouncement subclass: NautilusClassChangedAnnouncement > > And only subscribe to this subclasses. > That way we are using the hierarchy of Announcement classes for removing of duplicated code, but only > register and announce the "leaf"-nodes (NautilusClassChangedAnnouncement / NautilusPackageChangedAnnouncement...) > > what do you think? This may do. Also another option would be to have a NautilusSelectionAnnouncement with all 4 attributes, and then just subclass it for a different type. Uko > > > > > > > > > Uko >

Sept. 12, 2015

Re: [Pharo-dev] [Vm-dev] Re: Maintainer of FFI-Package

by Nicolai Hess

2014-09-28 22:04 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > Thank you David, > Thank you Eliot > > 2014-09-28 21:24 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > >> >> Hi Nicolai, >> >> On Sep 28, 2014, at 2:19 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >> > Who is the maintainer of the FFI-Package for >> > Squeak and/or Pharo ? >> >> I guess I'm the de facto maintainer because I'm the one who has changed >> things most recently, reimplementing the FFI plugin via the >> ThreadedFFIPlugin. >> >> >> > I especially interested in the FFI-Unix examples >> > and the state on working FFI on linux for current squeak release >> > (AFAIK it does not work with "squeak all in one" 4.5) >> >> Can you give me a reproducible case? I'd this with a Cog,Stack or >> Interpreter VM? Which specific things fail and how? >> > > Image > ----- > > /home/nicolai/Downloads/Squeak-4.5-All-in-One.app/Contents/Resources/Squeak4.5-13680.image > Squeak4.5 > latest update: #13680 > Current Change Set: Unnamed1 > Image format 6505 (32 bit) > > Virtual Machine > --------------- > > /home/nicolai/Downloads/Squeak-4.5-All-in-One.app/Contents/Linux-i686/lib/squeak/4.0-2776/squeak > Croquet Closure Cog VM [CoInterpreter VMMaker.oscog-eem.331] > Unix built on Aug 22 2013 10:35:37 Compiler: 4.1.2 20080704 (Red Hat > 4.1.2-48) > platform sources revision VM: r2776 > http://www.squeakvm.org/svn/squeak/branches/Cog Plugins: r2545 > http://squeakvm.org/svn/squeak/trunk/platforms/Cross/plugins > CoInterpreter VMMaker.oscog-eem.331 uuid: > 37d2e4b0-2f37-4e2d-8313-c63637785e59 Aug 22 2013 > StackToRegisterMappingCogit VMMaker.oscog-eem.333 uuid: > 84da9cb8-7f30-4cb7-b4fb-239a11f63b54 Aug 22 2013 > > Load > Name: FFI-Pools-eem.3 > Name: FFI-Kernel-eem.26 > Name: FFI-Tests-djm.7 > > Run FFI-Test -> 32 run, 24 passes, 0 expected failures, 0 failures, 8 > errors, 0 unexpected passes > > Load > Name: FFI-Unix-mtf.4 > > run X11Display class>>#coloredRectangles > -> Error: Could not coerse arguments > > Load newer cogvm > Virtual Machine > --------------- > > /media/Programs/squeak/Squeak-4.5-All-in-One.app/coglinux/lib/squeak/4.0-2987/squeak > Croquet Closure Cog VM [CoInterpreter VMMaker.oscog-eem.746] > Unix built on Jun 11 2014 14:59:18 Compiler: 4.1.2 20080704 (Red Hat > 4.1.2-48) > platform sources revision VM: r2987 > http://www.squeakvm.org/svn/squeak/branches/Cog Date: 2014-06-11 14:26:16 > -0700 Plugins: r2954 > http://squeakvm.org/svn/squeak/trunk/platforms/Cross/plugins > CoInterpreter VMMaker.oscog-eem.746 uuid: > cc4961d3-e629-4e28-b308-88eab314a8c9 Jun 11 2014 > StackToRegisterMappingCogit VMMaker.oscog-eem.766 uuid: > 3045c341-cfbf-494c-a7b1-fb29c26a7340 Jun 11 2014 > > Run FFI-Test -> 32 run, 32 passes, 0 expected failures, 0 failures, 0 > errors, 0 unexpected passes > > > The error in FFI-Unix is strange. The last package comment from > Name: FFI-Unix-mtf.4 > Author: mtf > is > "made the XLib examples actually work (Window is an unsigned int handle, > not a struct)" > > That the window is an int handle and not a struct explains why this > version replaces the parent class > of XDrawable from ExternalStructur to Object. But all calls with an > XDrawable still have this > object as parameter ( and not its instance var "xid"). I don't understand > how this ever > worked (or was there some kind of automatic argument conversion like: > transform an object with an instvar -> a int, if the function expects an > int handle?) > > Sure we can replace all XDrawable arguments in X11 calls from "aXDrawable" > to "aXDrawable xid". > But I only wonder, did this ever work and if Author "mtf" did the last > change, can I contact > him or is he still maintaining the FF-Unix examples? > > I would like to raise this topic again. Nothing has changed, the linux example still don't work and I can not get information about who maintains the unix-examples. >From my analysis (see above), the fix may be simple (in another discussion around that time some one else asked how to make that working, and confirmed it works with that fix). But I am confused because the latest update for the examples had the comment "made the XLib examlpes actually work". So maybe my usage or version of FFI is wrong. The last time I asked, someone said this works for him with the current stable vm, but it was actually the latest cog vm he used. But now, a year later, with the current 4.6 cog and 5.0 spur vm, some FFI unit tests still failing so maybe I am using the wrong FFI package (FFI-Kernel-EstebanLorenzano.27) ? (BTW, there is a typo in ExternalAddress class >> loadSymbol: moduleSymbol module: module <primitive: 'primitiveLoadSymbolFromModule' module: 'SqueakFFIPrims'> ^ self primitiveFail it should call ^ self primitiveFailed > > > > >> > regards >> > Nicolai >> >> Eliot (phone) > > >

Sept. 12, 2015

Re: [Pharo-dev] Strategies with Nautilus announcements

by Nicolai Hess

2015-09-09 14:32 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi, > > as NautilusMethodSelected contains also an information about protocol, > class, package; > NautilusProtocolSelected contains an information about class and package; > . > . > . > > Iâve inherited NautilusClassSelected from NautilusPackageSelected and > NautilusProtocolSelected from NautilusClassSelectedâ¦ to remove duplication. > But as announcement subscription also includes itâs subclasses, if you > subscribe to NautilusPackageSelected, you end up receiving also > NautilusClassSelected, NautilusProtocolSelected and NautilusMethodSelected. > > What is a good way to resolve this (I can simply separate all the classes, > but maybe there is something important from conceptual point of view)? > I didn't know announcments are working that way, but it may make sense if you want to group announcments (register once for "WindowAnnouncement" and receiving all kind of subannouncements (WindowClosed/WindowOpened ...) What we could do (maybe this is a bit overkill): - make an announcements hierarchy (NautilusPackageAnnouncement -> NautiulusClassAnnouncement ...) but never subscribe to this Announcemnts - create sub classes for every "kind" NautilusPackageAnnouncement subclass: NautilusPackageChangedAnnouncement NautilusPackageAnnouncement subclass: NautilusPackageSelectedAnnouncement NautilusClassAnnouncement subclass: NautilusClassSelectedAnnouncement NautilusClassAnnouncement subclass: NautilusClassChangedAnnouncement And only subscribe to this subclasses. That way we are using the hierarchy of Announcement classes for removing of duplicated code, but only register and announce the "leaf"-nodes (NautilusClassChangedAnnouncement / NautilusPackageChangedAnnouncement...) what do you think? > > Uko >

Sept. 12, 2015

Re: [Pharo-dev] http://forum.world.st down?

by Peter UhnÃ¡k

Btw since forum.world.st is just an aggregation of mailing lists, you could access the mailing list directly http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/ or use google with site: http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/ ... but the indexing seems to be quite random and there's also http://blog.gmane.org/gmane.comp.lang.smalltalk.pharo.devel but the search is also not so good... :( 2015-09-12 16:25 GMT+02:00 Dale Henrichs <dale.henrichs(a)gemtalksystems.com>: > still down:( > > On 9/11/15 12:15 PM, Dale Henrichs wrote: > >> http://downforeveryoneorjustme.com/forum.world.st >> >> >> > >

Sept. 12, 2015

Re: [Pharo-dev] [Vm-dev] Re: issue with large file path on windows

by Nicolai Hess

2015-09-10 21:31 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > > Hi Nicolai, > > I'm a bit concerned that this is creating drift with the "official" > Cog source base at http://www.squeakvm.org/svn/squeak/branches/Cog. Long > filename support for win32 was recently added by Marcel Taumel in May of > this year. Are you tracking that? How can we keep the sources harmonized? > Ok, I removed all of my code again and merged with sqWin32Directory.c and sqWin32FilePrims.c from the official cog source. I left only pharos additions for the fileattributes (posixpermissions) this should make it easier to merge which the squeak vm main branch (wrapped with pharo vm ifdefs). github branch: https://github.com/nicolaihess/pharo-vm/tree/harmonize_win_file_plugin I'll create a push request. nicolai > > On Sun, Aug 23, 2015 at 4:44 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> For those who had problems with pharo on windows and github based >> repositories, >> I built a windows vm with support for long paths: >> >> >> https://drive.google.com/file/d/0B8yEahnuIem2bmxwdzJuUXFxVGM/view?usp=shari… >> >> >> For browsing directories with large paths (FileList or Inspect), >> you may need one additional change in the image (But I am not really sure >> about that) : >> >> DiskStore>>initialize >> super initialize. >> maxFileNameLength := Smalltalk vm maxFilenameLength ifNil: [ 32767 ]. >> >> >> please test and give feedback. >> >> This wasn't as easy as I thought, and I had to make some more changes >> for the file permissions (the stat-functions don't work for files with >> long paths). >> Please test other file/folder operations. >> >> >> nicolai >> >> >> >> > > > -- > _,,,^..^,,,_ > best, Eliot > >

Sept. 12, 2015

Re: [Pharo-dev] http://forum.world.st down?

by Dale Henrichs

still down:( On 9/11/15 12:15 PM, Dale Henrichs wrote: > http://downforeveryoneorjustme.com/forum.world.st > >

Sept. 12, 2015

Re: [Pharo-dev] Annotating instance variables

by Ben Coman

On Sat, Sep 12, 2015 at 2:26 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> On 11 Sep 2015, at 20:05, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >> >> >> I saw some interesting reflection progress in Pharo 5. I wonder if there is a feature to rank instance variables. For example, from the browser I want to assign a category "important" to an instance variable, or "possibly useless", etc. for later refactorings. >> >> Is such thing "easily" possible now? There is API support from Reflectivity maybe? >> > > The infrastructure is thereâ¦ we can annotate instance variables. > > (Point slotNamed: #x) propertyAt: #note put: 'useless'. > (Point slotNamed: #x) propertyAt: #note > > One could build a user interface around that. > > Properties are not saved with monticello, though. They are like method properties. So one would > need to build something on top... > > Another idea would be to make a subclass of InstanceVariableSlot that stores the note in a property but > it is actually part of the slot definition: > > Object subclass: #Point > slots: { #x => InstanceVariableWithNote note: âthis is uselessâ. > #y } > classVariables: { } > category: 'Kernel-BasicObjects' > > As the note is part of the slot definition, it would be saved in Monticello. > > > (unrelated: I still am tempted to just use the term âinstance variableâ and get rid of the term Slot.. for the paper is was nice, but now? Especially > as we have slot like first class ClassVars and Globals that nevertheless are not slotsâ¦) Could you expand on how ClassVars and Globals are slot-like but not slots. One *tiny* consideration in favour of "slot" is that its more concise that "instance variable". Actually in post I often abbreviate to "iv" or "ivar". Also, would it be fair to say that for most programming languages variables are "dead", and it might be good to distinguish the "liveness" of slots. Further, there may be a particular class of early adopters who upon hearing the term "slot" that they don't know, will be compelled to investigate btw, can temporary variables be Slots? cheers -ben

Sept. 12, 2015

Re: [Pharo-dev] Bootstrap dependency, System-Announcements --> PragmaCollector

by Tudor Girba

When in doubt, just do small steps :). Moose dissolved this central navigation class in about 4 years. I certainly do not think that we should wait for anything. I just think that we should pick it as a target and guide the incremental improvements towards distributing the queries throughout the object model. Cheers, Doru On Sat, Sep 12, 2015 at 8:43 AM, stepharo <stepharo(a)free.fr> wrote: > > > Le 11/9/15 14:15, Ben Coman a Ã©crit : > >> On Fri, Sep 11, 2015 at 5:01 AM, Tudor Girba <tudor(a)tudorgirba.com> >> wrote: >> >>> I think SystemNavigation should essentially dissolve in the near future. >>> >> What timeline do you consider *near* ? ;) >> Should we go with my last proposal in the meantime? >> > > yes > never never stops to incrementally improve the system because something > better will happen > especially when doing this small steps is the first one in building the > better one :) > > This makes me realizes that I lost my great Calvin and Hobbes quote :) > > >> Moose used to have one of these some 10 years ago, and now all queries are >>> implemented as fluent APIs distributed throughout the model classes. >>> >> Could you clue me in on the "model" classes? >> cheers -ben >> >> On Thu, Sep 10, 2015 at 8:29 PM, stepharo <stepharo(a)free.fr> wrote: >>> >>>> Pragma should not depend on SystemNavigation. The inverse >>>> >>>> >>>> Le 10/9/15 19:44, Ben Coman a Ã©crit : >>>> >>>> On Fri, Sep 11, 2015 at 12:43 AM, Max Leske <maxleske(a)gmail.com> wrote: >>>>> >>>>>> On 10 Sep 2015, at 17:22, Ben Coman <btc(a)openInWorld.com> wrote: >>>>>>> >>>>>>> The bootstrap-dependency graph and report [1] mark dependency >>>>>>> System-Announcements --> PragmaCollector for pruning. This is due >>>>>>> to... >>>>>>> >>>>>>> SystemAnnouncer>>restoreAllNotifications >>>>>>> | collector | >>>>>>> self reset. >>>>>>> collector := PragmaCollector filter: [ :pragma | >>>>>>> pragma keyword = #systemEventRegistration ]. >>>>>>> collector reset. >>>>>>> collector do: [ :pragma | >>>>>>> pragma methodClass theNonMetaClass perform: pragma >>>>>>> selector ] >>>>>>> >>>>>>> Browsing around I came to understand that PragmaCollector is useful >>>>>>> as >>>>>>> a pragma cache, but here the collector is thrown away, so that >>>>>>> facility is not needed. A key part is "collector reset" which does... >>>>>>> self class allSystemPragmas >>>>>>> do: [:pragma | self addPragma: pragma] >>>>>>> >>>>>>> where the #addPragma: evaluates the initialize'd #filter: block. Now >>>>>>> it seems that #allSystemPragmas might fit nicely on Pragma rather >>>>>>> than >>>>>>> PragmaCollector >>>>>>> such that the following should be equivalent... >>>>>>> >>>>>>> SystemAnnouncer>>restoreAllNotifications >>>>>>> | systemPragmas | >>>>>>> self reset. >>>>>>> systemPragmas := Pragma allSystemPragmas collect: [ :pragma >>>>>>> | >>>>>>> pragma keyword = #systemEventRegistration ]. >>>>>>> systemPragmas do: [ :pragma | >>>>>>> pragma methodClass theNonMetaClass perform: pragma >>>>>>> selector >>>>>>> >>>>>>> Cool. I like that better. >>>>>> >>>>>> However #allSystemPragmas depends on SystemNavigation, so is it be >>>>>>> okay for Pragma to depend on SystemNavigation? >>>>>>> >>>>>> Spontaneously Iâd say that SystemNavigation should depend on Pragma or >>>>>> PragmaCollector for looking up pragmas, not the other way around. >>>>>> >>>>> So you mean something like... >>>>> >>>>> SystemAnnouncer>>restoreAllNotifications >>>>> self reset. >>>>> SystemNavigation allPragmasNamed: #systemEventRegistration >>>>> do: >>>>> [ :pragma | >>>>> pragma methodClass theNonMetaClass perform: pragma >>>>> selector ]. >>>>> >>>>> where... >>>>> >>>>> SystemNavigation>>allPragmasNamed: symbol do: aBlock >>>>> | systemPragmas | >>>>> systemPragmas := >>>>> self allSystemPragmas collect: [ :pragma | pragma >>>>> keyword >>>>> = symbol ]. >>>>> systemPragmas do: [ :pragma | >>>>> pragma methodClass theNonMetaClass perform: pragma >>>>> selector >>>>> >>>>> SystemNavigation>>allSystemPragmas >>>>> ^ (Array >>>>> streamContents: [:stream | >>>>> self allBehaviorsDo: [:behavior | >>>>> Pragma >>>>> withPragmasIn: behavior >>>>> do: [:pragma | stream nextPut: pragma]]]) >>>>> >>>>> cheers -ben >>>>> >>>>> >>>>> Actually, class side of Pragma has several #named:in: like methods, so >>>>>>> something like the following would be neat... >>>>>>> SystemAnnouncer>>restoreAllNotifications >>>>>>> self reset. >>>>>>> Pragma allNamed: #systemEventRegistration do: [ :pragma | >>>>>>> pragma methodClass theNonMetaClass perform: pragma >>>>>>> selector ]. >>>>>>> >>>>>> >> > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 12, 2015

Re: [Pharo-dev] Bootstrap dependency, System-Announcements --> PragmaCollector

by stepharo

Le 11/9/15 14:15, Ben Coman a Ã©crit : > On Fri, Sep 11, 2015 at 5:01 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> I think SystemNavigation should essentially dissolve in the near future. > What timeline do you consider *near* ? ;) > Should we go with my last proposal in the meantime? yes never never stops to incrementally improve the system because something better will happen especially when doing this small steps is the first one in building the better one :) This makes me realizes that I lost my great Calvin and Hobbes quote :) > >> Moose used to have one of these some 10 years ago, and now all queries are >> implemented as fluent APIs distributed throughout the model classes. > Could you clue me in on the "model" classes? > cheers -ben > >> On Thu, Sep 10, 2015 at 8:29 PM, stepharo <stepharo(a)free.fr> wrote: >>> Pragma should not depend on SystemNavigation. The inverse >>> >>> >>> Le 10/9/15 19:44, Ben Coman a Ã©crit : >>> >>>> On Fri, Sep 11, 2015 at 12:43 AM, Max Leske <maxleske(a)gmail.com> wrote: >>>>>> On 10 Sep 2015, at 17:22, Ben Coman <btc(a)openInWorld.com> wrote: >>>>>> >>>>>> The bootstrap-dependency graph and report [1] mark dependency >>>>>> System-Announcements --> PragmaCollector for pruning. This is due to... >>>>>> >>>>>> SystemAnnouncer>>restoreAllNotifications >>>>>> | collector | >>>>>> self reset. >>>>>> collector := PragmaCollector filter: [ :pragma | >>>>>> pragma keyword = #systemEventRegistration ]. >>>>>> collector reset. >>>>>> collector do: [ :pragma | >>>>>> pragma methodClass theNonMetaClass perform: pragma >>>>>> selector ] >>>>>> >>>>>> Browsing around I came to understand that PragmaCollector is useful as >>>>>> a pragma cache, but here the collector is thrown away, so that >>>>>> facility is not needed. A key part is "collector reset" which does... >>>>>> self class allSystemPragmas >>>>>> do: [:pragma | self addPragma: pragma] >>>>>> >>>>>> where the #addPragma: evaluates the initialize'd #filter: block. Now >>>>>> it seems that #allSystemPragmas might fit nicely on Pragma rather than >>>>>> PragmaCollector >>>>>> such that the following should be equivalent... >>>>>> >>>>>> SystemAnnouncer>>restoreAllNotifications >>>>>> | systemPragmas | >>>>>> self reset. >>>>>> systemPragmas := Pragma allSystemPragmas collect: [ :pragma | >>>>>> pragma keyword = #systemEventRegistration ]. >>>>>> systemPragmas do: [ :pragma | >>>>>> pragma methodClass theNonMetaClass perform: pragma >>>>>> selector >>>>>> >>>>> Cool. I like that better. >>>>> >>>>>> However #allSystemPragmas depends on SystemNavigation, so is it be >>>>>> okay for Pragma to depend on SystemNavigation? >>>>> Spontaneously Iâd say that SystemNavigation should depend on Pragma or >>>>> PragmaCollector for looking up pragmas, not the other way around. >>>> So you mean something like... >>>> >>>> SystemAnnouncer>>restoreAllNotifications >>>> self reset. >>>> SystemNavigation allPragmasNamed: #systemEventRegistration do: >>>> [ :pragma | >>>> pragma methodClass theNonMetaClass perform: pragma >>>> selector ]. >>>> >>>> where... >>>> >>>> SystemNavigation>>allPragmasNamed: symbol do: aBlock >>>> | systemPragmas | >>>> systemPragmas := >>>> self allSystemPragmas collect: [ :pragma | pragma keyword >>>> = symbol ]. >>>> systemPragmas do: [ :pragma | >>>> pragma methodClass theNonMetaClass perform: pragma >>>> selector >>>> >>>> SystemNavigation>>allSystemPragmas >>>> ^ (Array >>>> streamContents: [:stream | >>>> self allBehaviorsDo: [:behavior | >>>> Pragma >>>> withPragmasIn: behavior >>>> do: [:pragma | stream nextPut: pragma]]]) >>>> >>>> cheers -ben >>>> >>>> >>>>>> Actually, class side of Pragma has several #named:in: like methods, so >>>>>> something like the following would be neat... >>>>>> SystemAnnouncer>>restoreAllNotifications >>>>>> self reset. >>>>>> Pragma allNamed: #systemEventRegistration do: [ :pragma | >>>>>> pragma methodClass theNonMetaClass perform: pragma >>>>>> selector ]. >

Sept. 12, 2015

Re: [Pharo-dev] Annotating instance variables

by Marcus Denker

> > Properties are not saved with monticello, though. They are like method properties. So one would > need to build something on top... > > > I don't know about MC model, but maybe extending MC to support properies/annotations could be a path? > Yes, that would be a possibility. Adding things to the monticello .zip is easy (and easy to ignore later/by others). > > Another idea would be to make a subclass of InstanceVariableSlot that stores the note in a property but > it is actually part of the slot definition: > > Object subclass: #Point > slots: { #x => InstanceVariableWithNote note: âthis is uselessâ. > #y } > classVariables: { } > category: 'Kernel-BasicObjects' > > As the note is part of the slot definition, it would be saved in Monticello. > > > It could be silly question but most of the time I wish to annotate while debugging, using that option would affect my debugged objec state? No, the current class builder would migrate the objects (I think). As this does not change the shape of the instances, even that can be avoided. Marcus

Sept. 12, 2015

Re: [Pharo-dev] http://forum.world.st down?

by Dale Henrichs

Thx! On 09/11/2015 01:16 PM, Peter UhnÃ¡k wrote: > I also see it down. Btw this also happened couple of weeks ago (so I > guess it will fix itself.)) > > On Fri, Sep 11, 2015 at 9:15 PM, Dale Henrichs > <dale.henrichs(a)gemtalksystems.com > <mailto:dale.henrichs@gemtalksystems.com>> wrote: > > http://downforeveryoneorjustme.com/forum.world.st > > > >

Sept. 11, 2015

Re: [Pharo-dev] http://forum.world.st down?

by Peter UhnÃ¡k

I also see it down. Btw this also happened couple of weeks ago (so I guess it will fix itself.)) On Fri, Sep 11, 2015 at 9:15 PM, Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > http://downforeveryoneorjustme.com/forum.world.st > > > >

Sept. 11, 2015

Re: [Pharo-dev] Annotating instance variables

by Torsten Bergmann

Sept. 11, 2015

Re: [Pharo-dev] Annotating instance variables

by HernÃ¡n Morales Durand

Hi Marcus, Thanks for the answers. I am discovering Reflectivity, I just have a couple more questions if you don't mind: 2015-09-11 15:26 GMT-03:00 Marcus Denker <marcus.denker(a)inria.fr>: > > > On 11 Sep 2015, at 20:05, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > > > > > > I saw some interesting reflection progress in Pharo 5. I wonder if there > is a feature to rank instance variables. For example, from the browser I > want to assign a category "important" to an instance variable, or "possibly > useless", etc. for later refactorings. > > > > Is such thing "easily" possible now? There is API support from > Reflectivity maybe? > > > > The infrastructure is thereâ¦ we can annotate instance variables. > > (Point slotNamed: #x) propertyAt: #note put: 'useless'. > (Point slotNamed: #x) propertyAt: #note > > One could build a user interface around that. > > This is cool, I just hope the Nautilus plugin interface is stable by now then :) > Properties are not saved with monticello, though. They are like method > properties. So one would > need to build something on top... > > I don't know about MC model, but maybe extending MC to support properies/annotations could be a path? > Another idea would be to make a subclass of InstanceVariableSlot that > stores the note in a property but > it is actually part of the slot definition: > > Object subclass: #Point > slots: { #x => InstanceVariableWithNote note: âthis is uselessâ. > #y } > classVariables: { } > category: 'Kernel-BasicObjects' > > As the note is part of the slot definition, it would be saved in > Monticello. > > It could be silly question but most of the time I wish to annotate while debugging, using that option would affect my debugged objec state? Cheers, HernÃ¡n > (unrelated: I still am tempted to just use the term âinstance variableâ > and get rid of the term Slot.. for the paper is was nice, but now? > Especially > as we have slot like first class ClassVars and Globals that nevertheless > are not slotsâ¦) > > Marcus > > > >

Sept. 11, 2015

Re: [Pharo-dev] [Vm-dev] Re: [squeak-dev] Criteria For Plugin Compatibility

by David T. Lewis

Eliot, I agree. Indeed, even with an interpreter VM it has long been the case that a plugin compiled as 64 bit will not work on a VM compiled for 64 bit and vice versa. With the number of variations of 32/64, Spur/V3, and so forth, I don't think that this is a problem worth worrying about. Better to just be a aware that plugins are not readily interchangeable in those cases. Dave > Hi Chris, > > On Fri, Sep 11, 2015 at 9:01 AM, Chris Cunnington <brasspen(a)gmail.com> > wrote: > >> I had the idea that a plugin from one VM could be dragged into another >> VM's directory and that it could be used just by starting up the image. >> I've done a little experimenting and it seems more of an idea of a >> reality. >> The functionality is there, but VM developers over the years have not >> seen >> this as a priority. Typically plugins and their VMs are compiled >> together. >> Or a person adds one by recompiling a VM compilation rig they already >> have. >> > > The problems I see with this are > > a) a plugin compiled for Spur may not work with V3 or vice verse. The > issue is the header size of an object. Some plugins, but not all, use > this > define, and the header sizes between Spur and V3 are incompatible. > > b) 32-bit plugins won't work with 64-bit VMs, and 64-bit plugins won't > work > with 32-bit VMs. Period. > > Now there are platform-level packaging technologies, such as fat binaries > on Mac OS X, that allow one to construct plugins that contain more than > one > binary. But this is a lot of work to build and maintain. > > So personally I wouldn't put much effort into this level of drag-and-drop > compatibility. Instead I'd put energy into good error messages so that > when plugins don't work the user can find out why, and that when the wrong > kind of plugin is used the VM doesn't just stumble along, maybe producing > incorrect results, but instead puts the plugin out with a comprehensible > complaint. > > Does this make sense? I know its a downer, but what you propose is, IMO, > not affordable given our resources. > > > And I must say, *this is a VM-DEV discussion, not a general purpose Squeak > discussion*, yes? > > As I had a rig for the Interpreter VM I decided to compile a plugin and > see >> if I could drag it around to other VM directories for use. Most times it >> didn't work. >> >> I compiled a TheUniversalAnswer plugin which returns 42. I moved it from >> a >> 4.14.1-3430 VM to a 4.14.1-3414 VM. I could get it to work if I did not >> use >> the squeak.sh start script. That is, I dragged so.vm-sound-null, >> so.TheUniversalAnswer and so.vm-display-X11 into the same directory as >> the >> VM binary. That worked. >> >> The only way to see the external plugins is with #listLoadedModules. >> But, >> irritatingly, modules are loaded as needed, so once you have proof of >> using >> the primitive from the plugin, yea, it will appear as a result of that >> Smalltalk listLoadedModules message. So, it's not that useful. >> >> I dragged so.TheUniversalAnswer around to other VMs such as 4.0.3-2202 >> and >> 4.13.10-3268 without success. And the unload selectors #forgetModule: >> and >> unloadModule:, which both use primitive 571 don't appear to work on my >> Ubuntu 15.04. >> >> So, I don't know if a community of plugins passed around is in the >> offing. >> What I have learned is that many of the answers are in >> sqUnixExternalPrims.c. The issues are really where does the VM look for >> primitives and what does it do when it finds one. It appears to me, >> after >> reading both the non-Cog and Cog versions of that file, that this an >> interesting area poorly documented that VM developers alter in haste to >> get >> on to something else. >> >> It's pretty important stuff, though. Do you start the VM with the binary >> on the path? Do you use squeak.sh? Where is the VM looking for stuff. >> Where >> will FFI look for stuff. And so on. >> >> Chris >> >> >> >> > > > -- > _,,,^..^,,,_ > best, Eliot >

Sept. 11, 2015

http://forum.world.st down?

by Dale Henrichs

http://downforeveryoneorjustme.com/forum.world.st

Sept. 11, 2015

Re: [Pharo-dev] Catalog does not update to include MessageFlowBrowser

by Torsten Bergmann

Hi Esteban, Unfortunately it is now completely broken, the JSON is not returned anymore: http://catalog.pharo.org/catalog/json gives MessageNotUnderstood: receiver of "repositoryUrl" is nil Can you have a look again? Thanks! Regards Torsten > Gesendet: Freitag, 11. September 2015 um 19:03 Uhr > Von: "Esteban Lorenzano" <estebanlm(a)gmail.com> > An: "Torsten Bergmann" <astares(a)gmx.de> > Cc: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: Catalog does not update to include MessageFlowBrowser > > > > On 11 Sep 2015, at 16:38, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > > >> On 11 Sep 2015, at 16:29, Torsten Bergmann <astares(a)gmx.de> wrote: > >> > >> Hi, > >> > >> ConfigurationOfMessageFlowBrowser is in http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo50 > >> for a week now but still not included in http://catalog.pharo.org > >> > >> According to the description there is a daily catalog job - but so far no results. It is not > >> included although the config includes the necessary catalog methods. > >> > >> - Is MetaRepoForPharo50 already recognized? > >> - Is it possible to "manually" trigger the catalog generation in case a new project is done? > >> > >> Anyone able to look into this? > > > > Iâll check the logs. > > fixed. > something went wrong when updating FFI (my fault :P) and then everything stop working. Of course there is a log who tells me that something went wrong, but I forget to check them :D > > cheers, > > > > > Esteban > > > >> > >> Thx > >> T. > > > >

Sept. 11, 2015

Re: [Pharo-dev] [Vm-dev] Re: issue with large file path on windows

by Eliot Miranda

Hi Nicolai, On Fri, Sep 11, 2015 at 12:48 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-09-11 9:44 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > >> >> >> 2015-09-11 9:43 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: >> >>> >>> >>> 2015-09-10 23:07 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >>> >>>> >>>> Hi Nicolai, >>>> >>>> On Thu, Sep 10, 2015 at 1:17 PM, Nicolai Hess <nicolaihess(a)web.de> >>>> wrote: >>>> >>>>> >>>>> >>>>> >>>>> 2015-09-10 21:31 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >>>>> >>>>>> >>>>>> Hi Nicolai, >>>>>> >>>>>> I'm a bit concerned that this is creating drift with the >>>>>> "official" Cog source base at >>>>>> http://www.squeakvm.org/svn/squeak/branches/Cog. Long filename >>>>>> support for win32 was recently added by Marcel Taumel in May of this year. >>>>>> Are you tracking that? How can we keep the sources harmonized? >>>>>> >>>>> >>>>> Yes, I know, and I already asked on the ML if we can take that change >>>>> or >>>>> if it is not possible because we have already other changes (pharos >>>>> file plugin >>>>> provides addition attributes (the file permissions)). >>>>> >>>> >>>> Esteban and I just harmonized this. I'm (almost correctly) generating >>>> the plugin source such that one can define either PharoVM or not to chose >>>> between the different versions. I say "almost" because I'm currently >>>> spitting out >>>> >>>> #define PharoVM 0 >>>> ... >>>> #if PharoVM >>>> >>>> instead of >>>> >>>> #if !defined(PharoVM) >>>> # define PharoVM 0 >>>> #endif >>>> ... >>>> #if PharoVM >>>> >>>> but I'll fix it v soon. >>>> >>> >>> OK, I'll try to copy marcels solution >>> >>> >>>> >>>> But I got no response, so I tried to adopt Marcels change. >>>>> >>>>> And I only found the change for sqWin32FilePrims.c, but missed the >>>>> other change >>>>> that is necessary in sqWin32Directory.c (and asked on the ML). In the >>>>> meantime Marcel added this but I could not find >>>>> the changed source, only an updated vm. >>>>> Is this change already comitted? >>>>> >>>> >>>> Yes, see >>>> http://www.squeakvm.org/svn/squeak/branches/Cog/platforms/win32/vm/sqWin32D… >>>> >>> >>> Ah, good. Now (I must be blind, but) I can not see the other change, >>> shouldn't there >>> be a "plugins" folder in Cog/platforms/win32/? >>> Where are the changes to sqWin32FilePrims.c now? >>> >> >> Ok, found it. It is in the trunk branch :) >> > > > No, wait, now I am confused. The change to sqWin32FilePrims.c is only in > the trunk branch and the change to sqWin32Directory.c is > only in the Cog branch. What branch includes the solution for both > (sqWin32Directory.c and sqWin32FilePrims.c) and should be > used for a merge into pharos vm repository? > There are two "externals" in the Cog branch: X platforms/win32/plugins X platforms/Cross/plugins So http://www.squeakvm.org/svn/squeak/branches/Cog is the Cog repository, but http://www.squeakvm.org/svn/squeak/branches/Cog/platforms/win32/plugins is in fact http://squeakvm.org/svn/squeak/trunk/platforms/win32/plugins and http://www.squeakvm.org/svn/squeak/branches/Cog/platforms/Cross/plugins is in fact http://squeakvm.org/svn/squeak/trunk/platforms/Cross/plugins OK? > > >> >> >> >>> >>> >>> >>> >>>> >>>> I'm sorry I didn't see your message. Did you ask on vm-dev? >>>> >>> >>> I am not sure, maybe I only send it in the squeak-dev list >>> >>> >>>> >>>> >>>> >>>>> I would love if someone else got this working. >>>>> >>>> >>>> :-) I hear you :-) >>>> >>>> >>>> >>>>> >>>>> nicolai >>>>> >>>>> >>>>> >>>>>> >>>>>> On Sun, Aug 23, 2015 at 4:44 AM, Nicolai Hess <nicolaihess(a)web.de> >>>>>> wrote: >>>>>> >>>>>>> For those who had problems with pharo on windows and github based >>>>>>> repositories, >>>>>>> I built a windows vm with support for long paths: >>>>>>> >>>>>>> >>>>>>> https://drive.google.com/file/d/0B8yEahnuIem2bmxwdzJuUXFxVGM/view?usp=shari… >>>>>>> >>>>>>> >>>>>>> For browsing directories with large paths (FileList or Inspect), >>>>>>> you may need one additional change in the image (But I am not really >>>>>>> sure about that) : >>>>>>> >>>>>>> DiskStore>>initialize >>>>>>> super initialize. >>>>>>> maxFileNameLength := Smalltalk vm maxFilenameLength ifNil: [ >>>>>>> 32767 ]. >>>>>>> >>>>>>> >>>>>>> please test and give feedback. >>>>>>> >>>>>>> This wasn't as easy as I thought, and I had to make some more changes >>>>>>> for the file permissions (the stat-functions don't work for files >>>>>>> with long paths). >>>>>>> Please test other file/folder operations. >>>>>>> >>>>>>> >>>>>>> nicolai >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> _,,,^..^,,,_ >>>>>> best, Eliot >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> _,,,^..^,,,_ >>>> best, Eliot >>>> >>>> >>> >> > > -- _,,,^..^,,,_ best, Eliot

Sept. 11, 2015

Re: [Pharo-dev] [squeak-dev] Criteria For Plugin Compatibility

by Eliot Miranda

Hi Chris, On Fri, Sep 11, 2015 at 9:01 AM, Chris Cunnington <brasspen(a)gmail.com> wrote: > I had the idea that a plugin from one VM could be dragged into another > VM's directory and that it could be used just by starting up the image. > I've done a little experimenting and it seems more of an idea of a reality. > The functionality is there, but VM developers over the years have not seen > this as a priority. Typically plugins and their VMs are compiled together. > Or a person adds one by recompiling a VM compilation rig they already have. > The problems I see with this are a) a plugin compiled for Spur may not work with V3 or vice verse. The issue is the header size of an object. Some plugins, but not all, use this define, and the header sizes between Spur and V3 are incompatible. b) 32-bit plugins won't work with 64-bit VMs, and 64-bit plugins won't work with 32-bit VMs. Period. Now there are platform-level packaging technologies, such as fat binaries on Mac OS X, that allow one to construct plugins that contain more than one binary. But this is a lot of work to build and maintain. So personally I wouldn't put much effort into this level of drag-and-drop compatibility. Instead I'd put energy into good error messages so that when plugins don't work the user can find out why, and that when the wrong kind of plugin is used the VM doesn't just stumble along, maybe producing incorrect results, but instead puts the plugin out with a comprehensible complaint. Does this make sense? I know its a downer, but what you propose is, IMO, not affordable given our resources. And I must say, *this is a VM-DEV discussion, not a general purpose Squeak discussion*, yes? As I had a rig for the Interpreter VM I decided to compile a plugin and see > if I could drag it around to other VM directories for use. Most times it > didn't work. > > I compiled a TheUniversalAnswer plugin which returns 42. I moved it from a > 4.14.1-3430 VM to a 4.14.1-3414 VM. I could get it to work if I did not use > the squeak.sh start script. That is, I dragged so.vm-sound-null, > so.TheUniversalAnswer and so.vm-display-X11 into the same directory as the > VM binary. That worked. > > The only way to see the external plugins is with #listLoadedModules. But, > irritatingly, modules are loaded as needed, so once you have proof of using > the primitive from the plugin, yea, it will appear as a result of that > Smalltalk listLoadedModules message. So, it's not that useful. > > I dragged so.TheUniversalAnswer around to other VMs such as 4.0.3-2202 and > 4.13.10-3268 without success. And the unload selectors #forgetModule: and > unloadModule:, which both use primitive 571 don't appear to work on my > Ubuntu 15.04. > > So, I don't know if a community of plugins passed around is in the offing. > What I have learned is that many of the answers are in > sqUnixExternalPrims.c. The issues are really where does the VM look for > primitives and what does it do when it finds one. It appears to me, after > reading both the non-Cog and Cog versions of that file, that this an > interesting area poorly documented that VM developers alter in haste to get > on to something else. > > It's pretty important stuff, though. Do you start the VM with the binary > on the path? Do you use squeak.sh? Where is the VM looking for stuff. Where > will FFI look for stuff. And so on. > > Chris > > > > -- _,,,^..^,,,_ best, Eliot

Sept. 11, 2015

Re: [Pharo-dev] Annotating instance variables

by Marcus Denker

> On 11 Sep 2015, at 20:05, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > > I saw some interesting reflection progress in Pharo 5. I wonder if there is a feature to rank instance variables. For example, from the browser I want to assign a category "important" to an instance variable, or "possibly useless", etc. for later refactorings. > > Is such thing "easily" possible now? There is API support from Reflectivity maybe? > The infrastructure is thereâ¦ we can annotate instance variables. (Point slotNamed: #x) propertyAt: #note put: 'useless'. (Point slotNamed: #x) propertyAt: #note One could build a user interface around that. Properties are not saved with monticello, though. They are like method properties. So one would need to build something on top... Another idea would be to make a subclass of InstanceVariableSlot that stores the note in a property but it is actually part of the slot definition: Object subclass: #Point slots: { #x => InstanceVariableWithNote note: âthis is uselessâ. #y } classVariables: { } category: 'Kernel-BasicObjects' As the note is part of the slot definition, it would be saved in Monticello. (unrelated: I still am tempted to just use the term âinstance variableâ and get rid of the term Slot.. for the paper is was nice, but now? Especially as we have slot like first class ClassVars and Globals that nevertheless are not slotsâ¦) Marcus

Sept. 11, 2015

Re: [Pharo-dev] Running a test method in Nautilus

by Alexandre Bergel

Thanks! That would be fantastic. Alexandre > On Sep 11, 2015, at 2:40 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 11 Sep 2015, at 16:37, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: >> >> I do experience the same thing with Guille today. >> Before, Nautilus ran twice the method for a failed test: one to get the status of the test and another one for the debugger. >> Maybe in Nautilus cleanup, it was removed. >> > Yes, I removed that double runnning.. this was not a good idea. Now it is much simpler. > > And yes, it is better to directly open the debugger when running single tests explicitly. > > I will fix it. > > Marcus > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 11, 2015

Re: [Pharo-dev] Running a test method in Nautilus

by Alexandre Bergel

Excellent! Thanks ! Works! Alexandre > On Sep 11, 2015, at 2:43 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> However, this indicates many closed issues. How can I filter out the close issues? >> > Yes, it is annoying that the default for the search is to search closed issues. > > You can, though, filter the search results. Press â+Refine Furtherâ, there are many things, amount them âOpen or Closedâ. Select Open. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 11, 2015

Annotating instance variables

by HernÃ¡n Morales Durand

I saw some interesting reflection progress in Pharo 5. I wonder if there is a feature to rank instance variables. For example, from the browser I want to assign a category "important" to an instance variable, or "possibly useless", etc. for later refactorings. Is such thing "easily" possible now? There is API support from Reflectivity maybe? Cheers HernÃ¡n

Sept. 11, 2015

Re: [Pharo-dev] [Reflectivity] Progress with Reifications

by Marcus Denker

> On 11 Sep 2015, at 17:42, Craig Latta <craig(a)netjam.org> wrote: > > > "Reificated" is not a word. The word that means what you want is > "reified". > > Yes, I saw that just after pressing âSendââ¦ should have send a correction. Marcus

Sept. 11, 2015

Re: [Pharo-dev] [Reflectivity] Progress with Reifications

by Marcus Denker

> On 11 Sep 2015, at 17:28, Gustavo Santos <gugajansen(a)gmail.com> wrote: > > Hello Marcus, > > I wanted to modify some event creation in Epicea and I just used this mechanism. > It's pretty cool! > Very good that is was helpful! If you find any problems, let me knowâ¦ there will be many cases where things are not yet working as they should. But it seems to get more stable with each that we fix. Marcus

Sept. 11, 2015

Re: [Pharo-dev] Running a test method in Nautilus

by Marcus Denker

the left hand side of the method name. If the test fail, it does not open a debugger. I need to run it a second time. This is a rather odd behavior. > Am I the only one to experience this? > > Side question: > I try to check on the bug tracker if there is something about that, but I was not able to find it. I entered in the search input field the tree keywords: test button nautilus > The result is https://pharo.fogbugz.com/f/search/?sSearchFor=test+button+nautilus > However, this indicates many closed issues. How can I filter out the close issues? > Yes, it is annoying that the default for the search is to search closed issues. You can, though, filter the search results. Press â+Refine Furtherâ, there are many things, amount them âOpen or Closedâ. Select Open. Marcus

Sept. 11, 2015

Re: [Pharo-dev] Running a test method in Nautilus

by Marcus Denker

> On 11 Sep 2015, at 16:37, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > I do experience the same thing with Guille today. > Before, Nautilus ran twice the method for a failed test: one to get the status of the test and another one for the debugger. > Maybe in Nautilus cleanup, it was removed. > Yes, I removed that double runnning.. this was not a good idea. Now it is much simpler. And yes, it is better to directly open the debugger when running single tests explicitly. I will fix it. Marcus

Sept. 11, 2015

Re: [Pharo-dev] Catalog does not update to include MessageFlowBrowser

by Esteban Lorenzano

> On 11 Sep 2015, at 16:38, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 11 Sep 2015, at 16:29, Torsten Bergmann <astares(a)gmx.de> wrote: >> >> Hi, >> >> ConfigurationOfMessageFlowBrowser is in http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo50 >> for a week now but still not included in http://catalog.pharo.org >> >> According to the description there is a daily catalog job - but so far no results. It is not >> included although the config includes the necessary catalog methods. >> >> - Is MetaRepoForPharo50 already recognized? >> - Is it possible to "manually" trigger the catalog generation in case a new project is done? >> >> Anyone able to look into this? > > Iâll check the logs. fixed. something went wrong when updating FFI (my fault :P) and then everything stop working. Of course there is a log who tells me that something went wrong, but I forget to check them :D cheers, > > Esteban > >> >> Thx >> T. >

Sept. 11, 2015

Re: [Pharo-dev] [Reflectivity] Progress with Reifications

by Craig Latta

"Reificated" is not a word. The word that means what you want is "reified". -C -- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

Sept. 11, 2015

Re: [Pharo-dev] [Reflectivity] Progress with Reifications

by Gustavo Santos

Hello Marcus, I wanted to modify some event creation in Epicea and I just used this mechanism. It's pretty cool! Cheers, On Thu, Jun 18, 2015 at 2:36 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > in Pharo5 #120 we have lots of progress with Reflectivity regarding to > âreificated valuesâ. > > 1) more reificated value are working. > > #arguments - an array of the arguments of a message send or method > #receiver - receiver of a message (or method executed) > #context for Methods > #sender for method and message > > This means we have now all the info needed to e.g. pass all date needed to > do a message send on the meta level. > (receiver, args, selector), or a variable store (#name, #newValue). > > 2) Reifications as arguments to conditions. When the block used as a > condition has arguments, the name > is matched to the possible reifications and if valid this value is passed > as an argument. Very useful e.g. for > object specific links: > > link := MetaLink new > condition: [: object | object == <the object I am > intersted in>]; > metaObject: <someObject>; > selector: <some selector> > > This link would only be active for this one object. > > 3) Reifications as meta object > ------------- > > Every valid reified value can be the metaobject of the link. e.g. you can > now define a link where the meta is the node where the Link is installed: > > link := MetaLink new > metaObject: #node; > selector: #tagHasBeenExecuted. > > Or the #receiver: > > link := MetaLink new > metaObject: #receiver; > selector: #perform:withArguments:; > arguments: #(selector arguments). > > TODO > > -> #slot, #global. #variable reifications > -> #after needs to wrap in ensure: > -> primitives > -> more tests > -> optimize link preambles: when reifying both #arguments and #receiver, > merge the preamble into one for performance. > > -- Gustavo Santos

Sept. 11, 2015

Re: [Pharo-dev] Catalog does not update to include MessageFlowBrowser

by Esteban Lorenzano

> On 11 Sep 2015, at 16:29, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > ConfigurationOfMessageFlowBrowser is in http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo50 > for a week now but still not included in http://catalog.pharo.org > > According to the description there is a daily catalog job - but so far no results. It is not > included although the config includes the necessary catalog methods. > > - Is MetaRepoForPharo50 already recognized? > - Is it possible to "manually" trigger the catalog generation in case a new project is done? > > Anyone able to look into this? Iâll check the logs. Esteban > > Thx > T.

Sept. 11, 2015

Re: [Pharo-dev] Running a test method in Nautilus

by Christophe Demarey

I do experience the same thing with Guille today. Before, Nautilus ran twice the method for a failed test: one to get the status of the test and another one for the debugger. Maybe in Nautilus cleanup, it was removed. Le 11 sept. 2015 Ã 16:34, Peter UhnÃ¡k a Ã©crit : > If the test fail, it does not open a debugger. > > This happens when I click on the button next to the _class_, however I've never experienced such problem with the button next to a _method_. > > Peter > > On Fri, Sep 11, 2015 at 4:21 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > I can run a test method by pressing the button located on the left hand side of the method name. If the test fail, it does not open a debugger. I need to run it a second time. This is a rather odd behavior. > Am I the only one to experience this? > > Side question: > I try to check on the bug tracker if there is something about that, but I was not able to find it. I entered in the search input field the tree keywords: test button nautilus > The result is https://pharo.fogbugz.com/f/search/?sSearchFor=test+button+nautilus > However, this indicates many closed issues. How can I filter out the close issues? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Sept. 11, 2015

Re: [Pharo-dev] [Moose-dev] Pillar 2.0.0: Introduction of PetitPillar

by Ferlicot D. Cyril

Le 11/09/2015 15:49, Alexandre Bergel a Ã©crit : > Hi Cyril, > > I use Pillar for AgileVisualization. One problem I have is that the book contains many code snippets. How can I run all the code snippet in order to spot error? Is there an easy way for that? > > Alexandre > > > You mean you you use a lot of scripts with a "eval=true" parameter ? If you want an easy way to debug code into scripts you can remove the "--headless" parameter of the "pharo" script will you test your chapter. During the export if you have an exception the image will open a debugger with the context of the script. -- Cheers Cyril

Sept. 11, 2015

Re: [Pharo-dev] Running a test method in Nautilus

by Peter UhnÃ¡k

> > If the test fail, it does not open a debugger. This happens when I click on the button next to the _class_, however I've never experienced such problem with the button next to a _method_. Peter On Fri, Sep 11, 2015 at 4:21 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > I can run a test method by pressing the button located on the left hand > side of the method name. If the test fail, it does not open a debugger. I > need to run it a second time. This is a rather odd behavior. > Am I the only one to experience this? > > Side question: > I try to check on the bug tracker if there is something about that, but I > was not able to find it. I entered in the search input field the tree > keywords: test button nautilus > The result is > https://pharo.fogbugz.com/f/search/?sSearchFor=test+button+nautilus > However, this indicates many closed issues. How can I filter out the close > issues? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Sept. 11, 2015

Catalog does not update to include MessageFlowBrowser

by Torsten Bergmann

Hi, ConfigurationOfMessageFlowBrowser is in http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo50 for a week now but still not included in http://catalog.pharo.org According to the description there is a daily catalog job - but so far no results. It is not included although the config includes the necessary catalog methods. - Is MetaRepoForPharo50 already recognized? - Is it possible to "manually" trigger the catalog generation in case a new project is done? Anyone able to look into this? Thx T.

Sept. 11, 2015

Running a test method in Nautilus

by Alexandre Bergel

Hi! I can run a test method by pressing the button located on the left hand side of the method name. If the test fail, it does not open a debugger. I need to run it a second time. This is a rather odd behavior. Am I the only one to experience this? Side question: I try to check on the bug tracker if there is something about that, but I was not able to find it. I entered in the search input field the tree keywords: test button nautilus The result is https://pharo.fogbugz.com/f/search/?sSearchFor=test+button+nautilus However, this indicates many closed issues. How can I filter out the close issues? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 11, 2015

Re: [Pharo-dev] [Moose-dev] Pillar 2.0.0: Introduction of PetitPillar

by Peter UhnÃ¡k

On Fri, Sep 11, 2015 at 3:49 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi Cyril, > > I use Pillar for AgileVisualization. One problem I have is that the book > contains many code snippets. How can I run all the code snippet in order to > spot error? Is there an easy way for that? > > Alexandre This probably doesn't apply since you have your scripts directly in the pillar files... but for the Layout chapter scripts I've used this (It goes through all "Layout/figures/*.st" files, compiles them and executes them.) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |root scripts| root := '/home/peter/prog/agilevisualization/book-skeleton' asFileReference. scripts := (root / 'Layout' / 'figures') children select: [ :each | each name endsWith: '.st' ]. scripts do: [ :each | Transcript logCr: each name. nil class compiler source: each contents; evaluate ]. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Peter

Sept. 11, 2015

Re: [Pharo-dev] [Moose-dev] Pillar 2.0.0: Introduction of PetitPillar

by Alexandre Bergel

Hi Cyril, I use Pillar for AgileVisualization. One problem I have is that the book contains many code snippets. How can I run all the code snippet in order to spot error? Is there an easy way for that? Alexandre > On Sep 11, 2015, at 9:06 AM, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> wrote: > > Hi everyone! > Yes, a new version of Pillar, again! > > With this version we removed the old parser of Pillar to introduce > PetitPillar base on PetitParser. > This parser is slower than the previous one but we will be able to > improve his speed. > We will also be able to improve Pillar at the parser level, which was > impossible before. So we will be able to remove some hacks and improve > the experience of the users. > If you are good in parser and you want to contribute to his improvement, > feel free to help, we have a lot of tests to help. This is my first > parser so I am sure it have a lot of rooms for improvement. > > -- > Cheers > Cyril > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 11, 2015

Re: [Pharo-dev] Bootstrap dependency, System-Announcements --> PragmaCollector

by Ben Coman

On Fri, Sep 11, 2015 at 5:01 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I think SystemNavigation should essentially dissolve in the near future. What timeline do you consider *near* ? ;) Should we go with my last proposal in the meantime? > Moose used to have one of these some 10 years ago, and now all queries are > implemented as fluent APIs distributed throughout the model classes. Could you clue me in on the "model" classes? cheers -ben > On Thu, Sep 10, 2015 at 8:29 PM, stepharo <stepharo(a)free.fr> wrote: >> >> Pragma should not depend on SystemNavigation. The inverse >> >> >> Le 10/9/15 19:44, Ben Coman a Ã©crit : >> >>> On Fri, Sep 11, 2015 at 12:43 AM, Max Leske <maxleske(a)gmail.com> wrote: >>>>> >>>>> On 10 Sep 2015, at 17:22, Ben Coman <btc(a)openInWorld.com> wrote: >>>>> >>>>> The bootstrap-dependency graph and report [1] mark dependency >>>>> System-Announcements --> PragmaCollector for pruning. This is due to... >>>>> >>>>> SystemAnnouncer>>restoreAllNotifications >>>>> | collector | >>>>> self reset. >>>>> collector := PragmaCollector filter: [ :pragma | >>>>> pragma keyword = #systemEventRegistration ]. >>>>> collector reset. >>>>> collector do: [ :pragma | >>>>> pragma methodClass theNonMetaClass perform: pragma >>>>> selector ] >>>>> >>>>> Browsing around I came to understand that PragmaCollector is useful as >>>>> a pragma cache, but here the collector is thrown away, so that >>>>> facility is not needed. A key part is "collector reset" which does... >>>>> self class allSystemPragmas >>>>> do: [:pragma | self addPragma: pragma] >>>>> >>>>> where the #addPragma: evaluates the initialize'd #filter: block. Now >>>>> it seems that #allSystemPragmas might fit nicely on Pragma rather than >>>>> PragmaCollector >>>>> such that the following should be equivalent... >>>>> >>>>> SystemAnnouncer>>restoreAllNotifications >>>>> | systemPragmas | >>>>> self reset. >>>>> systemPragmas := Pragma allSystemPragmas collect: [ :pragma | >>>>> pragma keyword = #systemEventRegistration ]. >>>>> systemPragmas do: [ :pragma | >>>>> pragma methodClass theNonMetaClass perform: pragma >>>>> selector >>>>> >>>> Cool. I like that better. >>>> >>>>> However #allSystemPragmas depends on SystemNavigation, so is it be >>>>> okay for Pragma to depend on SystemNavigation? >>>> >>>> Spontaneously Iâd say that SystemNavigation should depend on Pragma or >>>> PragmaCollector for looking up pragmas, not the other way around. >>> >>> So you mean something like... >>> >>> SystemAnnouncer>>restoreAllNotifications >>> self reset. >>> SystemNavigation allPragmasNamed: #systemEventRegistration do: >>> [ :pragma | >>> pragma methodClass theNonMetaClass perform: pragma >>> selector ]. >>> >>> where... >>> >>> SystemNavigation>>allPragmasNamed: symbol do: aBlock >>> | systemPragmas | >>> systemPragmas := >>> self allSystemPragmas collect: [ :pragma | pragma keyword >>> = symbol ]. >>> systemPragmas do: [ :pragma | >>> pragma methodClass theNonMetaClass perform: pragma >>> selector >>> >>> SystemNavigation>>allSystemPragmas >>> ^ (Array >>> streamContents: [:stream | >>> self allBehaviorsDo: [:behavior | >>> Pragma >>> withPragmasIn: behavior >>> do: [:pragma | stream nextPut: pragma]]]) >>> >>> cheers -ben >>> >>> >>>>> Actually, class side of Pragma has several #named:in: like methods, so >>>>> something like the following would be neat... >>>>> SystemAnnouncer>>restoreAllNotifications >>>>> self reset. >>>>> Pragma allNamed: #systemEventRegistration do: [ :pragma | >>>>> pragma methodClass theNonMetaClass perform: pragma >>>>> selector ].

Sept. 11, 2015

Pillar 2.0.0: Introduction of PetitPillar

by Ferlicot D. Cyril

Hi everyone! Yes, a new version of Pillar, again! With this version we removed the old parser of Pillar to introduce PetitPillar base on PetitParser. This parser is slower than the previous one but we will be able to improve his speed. We will also be able to improve Pillar at the parser level, which was impossible before. So we will be able to remove some hacks and improve the experience of the users. If you are good in parser and you want to contribute to his improvement, feel free to help, we have a lot of tests to help. This is my first parser so I am sure it have a lot of rooms for improvement. -- Cheers Cyril

Sept. 11, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 11, 2015

[pharo-project/pharo-core] 127a47: 50320

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 127a47eee1c4b21d93a52699da70b0ab2343f23e https://github.com/pharo-project/pharo-core/commit/127a47eee1c4b21d93a52699… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-11 (Fri, 11 Sep 2015) Changed paths: M ConfigurationOfVersionner.package/ConfigurationOfVersionner.class/instance/symbolic versions/stable_.st A ConfigurationOfVersionner.package/ConfigurationOfVersionner.class/instance/versions/version2134_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50319.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50320.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50319.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50320.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Versionner-Core-Commands.package/VSBrowseVersionCommand.class/instance/execute/execute.st M Versionner-Core-Commands.package/VSSaveProjectCommand.class/instance/execute/execute.st M Versionner-Core-DependenciesModel.package/MCModel2MTModelVisitor.class/instance/visiting/visitMCVersion_.st M Versionner-Core-DependenciesModel.package/MTProject.class/definition.st A Versionner-Core-DependenciesModel.package/MTProject.class/instance/accessing/announcer.st M Versionner-Core-DependenciesModel.package/VersionnerToolBox.class/instance/spec creation/projectSpecFromRequiredProject_.st M Versionner-Core-Model.package/MBConfigurationRoot.class/definition.st A Versionner-Core-Model.package/MBConfigurationRoot.class/instance/accessing/announcer.st A Versionner-Core-Model.package/MBConfigurationRoot.class/instance/initialize-release/initialize.st M Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/instance/accessing/title.st A Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/instance/accessing/toolName.st A Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/instance/api/aboutText.st A Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/instance/api/aboutTitle.st M Versionner-Tests-Core-Commands.package/VSReleaseDevelopmentVersionCommandTest.class/instance/expected results/expectedTestResolveSymbolicVersionInResult.st Log Message: ----------- 50320 16546 Integrate Versionner https://pharo.fogbugz.com/f/cases/16546 http://files.pharo.org/image/50/50320.zip

Sept. 11, 2015

Re: [Pharo-dev] Bootstrap dependency, System-Announcements --> PragmaCollector

by stepharo

yes but we are focusing on bootstrap and we cannot do deep first :) Doing a pass on systemnavigation will help. And having the dependencies in the right order would help too. Le 10/9/15 23:01, Tudor Girba a Ã©crit : > I think SystemNavigation should essentially dissolve in the near > future. Moose used to have one of these some 10 years ago, and now all > queries are implemented as fluent APIs distributed throughout the > model classes. I would want the Pharo code model should move in the > same direction. > > Doru > > On Thu, Sep 10, 2015 at 8:29 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Pragma should not depend on SystemNavigation. The inverse > > > Le 10/9/15 19:44, Ben Coman a Ã©crit : > > On Fri, Sep 11, 2015 at 12:43 AM, Max Leske > <maxleske(a)gmail.com <mailto:maxleske@gmail.com>> wrote: > > On 10 Sep 2015, at 17:22, Ben Coman > <btc(a)openInWorld.com> wrote: > > The bootstrap-dependency graph and report [1] mark > dependency > System-Announcements --> PragmaCollector for pruning. > This is due to... > > SystemAnnouncer>>restoreAllNotifications > | collector | > self reset. > collector := PragmaCollector filter: [ :pragma | > pragma keyword = #systemEventRegistration ]. > collector reset. > collector do: [ :pragma | > pragma methodClass theNonMetaClass > perform: pragma selector ] > > Browsing around I came to understand that > PragmaCollector is useful as > a pragma cache, but here the collector is thrown away, > so that > facility is not needed. A key part is "collector > reset" which does... > self class allSystemPragmas > do: [:pragma | self addPragma: pragma] > > where the #addPragma: evaluates the initialize'd > #filter: block. Now > it seems that #allSystemPragmas might fit nicely on > Pragma rather than > PragmaCollector > such that the following should be equivalent... > > SystemAnnouncer>>restoreAllNotifications > | systemPragmas | > self reset. > systemPragmas := Pragma allSystemPragmas > collect: [ :pragma | > pragma keyword = #systemEventRegistration ]. > systemPragmas do: [ :pragma | > pragma methodClass theNonMetaClass > perform: pragma selector > > Cool. I like that better. > > However #allSystemPragmas depends on SystemNavigation, > so is it be > okay for Pragma to depend on SystemNavigation? > > Spontaneously Iâd say that SystemNavigation should depend > on Pragma or PragmaCollector for looking up pragmas, not > the other way around. > > So you mean something like... > > SystemAnnouncer>>restoreAllNotifications > self reset. > SystemNavigation allPragmasNamed: > #systemEventRegistration do: > [ :pragma | > pragma methodClass theNonMetaClass perform: > pragma selector ]. > > where... > > SystemNavigation>>allPragmasNamed: symbol do: aBlock > | systemPragmas | > systemPragmas := > self allSystemPragmas collect: [ :pragma | > pragma keyword > = symbol ]. > systemPragmas do: [ :pragma | > pragma methodClass theNonMetaClass perform: > pragma selector > > SystemNavigation>>allSystemPragmas > ^ (Array > streamContents: [:stream | > self allBehaviorsDo: [:behavior | > Pragma > withPragmasIn: behavior > do: [:pragma | stream nextPut: pragma]]]) > > cheers -ben > > > Actually, class side of Pragma has several #named:in: > like methods, so > something like the following would be neat... > SystemAnnouncer>>restoreAllNotifications > self reset. > Pragma allNamed: #systemEventRegistration do: > [ :pragma | > pragma methodClass theNonMetaClass > perform: pragma selector ]. > > > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

Sept. 11, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 11, 2015

[pharo-project/pharo-core] 60d9f9: 50319

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 60d9f9a757251d663c2083e4779a8f62f477576d https://github.com/pharo-project/pharo-core/commit/60d9f9a757251d663c2083e4… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-11 (Fri, 11 Sep 2015) Changed paths: M ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/symbolic versions/stable_.st A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version1185_.st A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version1186_.st A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version1214Moose51_.st M Rubric.package/RubAbstractTextArea.class/instance/initialize/plugFindReplace.st M Rubric.package/RubCursor.class/instance/submorphs-accessing/noteNewOwner_.st M Rubric.package/RubFindReplaceService.class/instance/accessing/textArea_.st M Rubric.package/RubFindReplaceService.class/instance/user-interface/newDialog.st M Rubric.package/RubFloatingEditorBuilder.class/instance/accessing/withEditedContentsDo_.st M Rubric.package/RubFloatingEditorBuilder.class/instance/private/buildEditor.st M Rubric.package/RubGhostTextDisplayer.class/instance/submorphs-accessing/noteNewOwner_.st M Rubric.package/RubHighlightSegmentMorph.class/instance/event handling/registerTextArea.st M Rubric.package/RubPluggableTextMorphExample.class/instance/view creation/open.st M Rubric.package/RubPrimarySelectionMorph.class/instance/event handling/registerTextArea.st M Rubric.package/RubScrolledTextMorph.class/instance/accessing/model_.st A Rubric.package/RubScrolledTextMorph.class/instance/event handling/whenLostFocus_.st R Rubric.package/RubScrolledTextMorph.class/instance/event handling/whenLostForcus_.st M Rubric.package/RubScrolledTextMorph.class/instance/initialize-release/initialize.st M Rubric.package/RubShoutStylerDecorator.class/instance/accessing/next_.st M Rubric.package/RubTextAreaExamples.class/class/examples/textFieldWithCRAction.st M Rubric.package/RubTextFieldMorph.class/instance/initialize-release/initialize.st M Rubric.package/RubTextSegmentMorph.class/instance/event handling/registerTextArea.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50318.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50319.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50318.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50319.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50319 16503 Remove senders of subscribe:send:to: in Rubric https://pharo.fogbugz.com/f/cases/16503 http://files.pharo.org/image/50/50319.zip

Sept. 11, 2015