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

Re: [Pharo-dev] [Pharo-users] Adding custom context to a debugger

by Tudor Girba

What do you mean by custom context? In GTDebugger you should be able to customize anything you want. Doru On Thu, Sep 10, 2015 at 11:00 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > And also for GTDebugger, although that has most likely very different > internals. > > > â > > On Thu, Sep 10, 2015 at 10:31 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> Hi, >> >> is it possible to add custom context to a debugger? >> >> >> â >> I would like to add a reference to the highlighted area. >> >> I am assuming that since SpecDebugger doesn't provide plugin support I >> would have to modify the source code? >> >> Thanks, >> Peter >> > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 10, 2015

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

by Tudor Girba

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> 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. 10, 2015

Re: [Pharo-dev] Adding custom context to a debugger

by Peter UhnÃ¡k

And also for GTDebugger, although that has most likely very different internals. â On Thu, Sep 10, 2015 at 10:31 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Hi, > > is it possible to add custom context to a debugger? > > > â > I would like to add a reference to the highlighted area. > > I am assuming that since SpecDebugger doesn't provide plugin support I > would have to modify the source code? > > Thanks, > Peter >

Sept. 10, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 10, 2015

[pharo-project/pharo-core] 235654: 50318

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 235654f721ea98534fb69ba6f532dae458fe738a https://github.com/pharo-project/pharo-core/commit/235654f721ea98534fb69ba6… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-10 (Thu, 10 Sep 2015) Changed paths: M PragmaCollector.package/PragmaCollector.class/definition.st M PragmaCollector.package/PragmaCollector.class/instance/system changes/noMoreAnnounceWhile_.st M Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - after/testAfterBlockSequence.st M Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - after/testAfterSequence.st M Reflectivity.package/RFASTTranslator.class/instance/reflectivity/emitMetaLinkAfter_.st M Reflectivity.package/RFASTTranslatorForEffect.class/instance/visitor-double dispatching/visitSequenceNode_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50317.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50318.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50317.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50318.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Sources.package/SourceFileArray.class/instance/public - string writing/writeSource_preamble_onSuccess_onFail_.st M System-Sources.package/extension/CompiledMethod/instance/putSource_withPreamble_.st Log Message: ----------- 50318 16545 Improve #after on sequence node https://pharo.fogbugz.com/f/cases/16545 16498 unrecoverable changes https://pharo.fogbugz.com/f/cases/16498 16548 Undeclared ivar in PragmaCollector https://pharo.fogbugz.com/f/cases/16548 http://files.pharo.org/image/50/50318.zip

Sept. 10, 2015

Adding custom context to a debugger

by Peter UhnÃ¡k

Hi, is it possible to add custom context to a debugger? â I would like to add a reference to the highlighted area. I am assuming that since SpecDebugger doesn't provide plugin support I would have to modify the source code? Thanks, Peter

Sept. 10, 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? > 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)). 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? I would love if someone else got this working. 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. 10, 2015

Re: [Pharo-dev] Dynamical resizing of a Nautilus Plugin

by Peter UhnÃ¡k

hmm... it's not pretty but this seems to work... for anyone that might be also interested (maybe Yuriy and QA?): ~~~~~~~~~~~~~~~ MyPluginMorph>>changeHeight: aNumber self submorphAfter layoutFrame topOffset: aNumber + self padding. self layoutFrame bottomOffset: aNumber. self layoutChanged ~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~ MyPluginMorph>>padding "Padding set between plugins in AbstractNautilusUI>>addAll: (middleHeight := middle height + 4)." ^ 4 ~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~ MyPluginMorph>>height "If the morph is not attached yet return negated padding to hide the plugin by default." ^ owner ifNil: [ self padding negated ] ifNotNil: [ super height ] ~~~~~~~~~~~~~~~ Peter On Thu, Sep 10, 2015 at 9:09 PM, stepharo <stepharo(a)free.fr> wrote: > probably but we should play wiht the internal of nautilus. > > Le 10/9/15 20:59, Peter UhnÃ¡k a Ã©crit : > > Hi, >> >> is it possible to dynamically resize (or add/remove) plugin in nautilus? >> >> It seems that plugins are added during build >> (AbstractNautilusUI>>addAll:), >> however is it possible to do at morphic level? >> >> Because if I resize the morph of the plugin the parent will have empty >> space; so probably I would have to move all the morphs underneath it, but I >> am not knowledgeable enough of Morphic. >> >> Since I can freely resize by hand the code pane area I think it should be >> possible, but I am lost. :/ >> >> Thanks, >> Peter >> > > >

Sept. 10, 2015

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

by Eliot Miranda

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? 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. 10, 2015

Re: [Pharo-dev] Dynamical resizing of a Nautilus Plugin

by stepharo

probably but we should play wiht the internal of nautilus. Le 10/9/15 20:59, Peter UhnÃ¡k a Ã©crit : > Hi, > > is it possible to dynamically resize (or add/remove) plugin in nautilus? > > It seems that plugins are added during build > (AbstractNautilusUI>>addAll:), > however is it possible to do at morphic level? > > Because if I resize the morph of the plugin the parent will have empty > space; so probably I would have to move all the morphs underneath it, > but I am not knowledgeable enough of Morphic. > > Since I can freely resize by hand the code pane area I think it should > be possible, but I am lost. :/ > > Thanks, > Peter

Sept. 10, 2015