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

Re: [Pharo-dev] chunk file format (unrecoverable changes)

by Martin Dias

On Thu, Sep 10, 2015 at 11:17 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > Now that this is fixed, should we (is it possible?) fix the changes file? > A script that replaces the "! !" by "! " in class comments should work. It's important to replace the ! mark by a space, but keep the byte positions of the strings. This is important, because the system recovers a method's source code by fetching it from the .changes (or .sources) file using the byte position where the source code was written (the sourcePointer in the trailer of the CompiledMethods). A concrete example: !OSTouchTwoFingersPinchInMoveEvent commentStamp: 'MerwanOuddane 5/11/2015 15:14' prior: 0! Two fingers are pinching in! ! <--- replace last ! by space I think this can work as a template for a script: fileStream := SourceFiles changesFileStream. fileStream resetToStart. <iterate over the fileStream and replace some !s> SourceFiles forceChangesToDisk. If somebody wants to take it... else I might do it during the weekend. Cheers, MArtin > > 2015-09-06 21:56 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > >> Do we have a documentation about the format of >> - class definitions >> - methods >> - class comments >> for the changes file ? >> >> I am asking because some entries are using two separator >> "! !" >> and some only one >> "!" >> And we have a problem with the "Recover lost changes" browser >> (https://pharo.fogbugz.com/f/cases/16498/unrecoverable-changes) >> and I am not sure if this is a bug on the code importer >> or if it is a bug on how we write changes to the changes file. >> >> >> nicolai >> >> >

Sept. 11, 2015

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

by Nicolai Hess

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

Sept. 11, 2015

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

by Nicolai Hess

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 :) > > > > >> >> 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 >> >> >

Sept. 11, 2015

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

by Nicolai Hess

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

Sept. 11, 2015

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

by Max Leske

> On 10 Sep 2015, at 19:44, Ben Coman <btc(a)openInWorld.com> wrote: > > 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]]]) Yes, exactly. > > 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

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

by Marcus Denker

> On 10 Sep 2015, at 23:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > 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. > Yes! Marcus

Sept. 11, 2015

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

by Ben Coman

On Fri, Sep 11, 2015 at 4:31 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Hi, > > is it possible to add custom context to a debugger? > (pic deleted) > 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? > I'm not sure but you might try observing the execution of SpecDebugger>>updateInspectorsFromContext: aContext. cheers -ben

Sept. 11, 2015

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

by Franck Warlouzet

I tried once to do a button which increases the text area size or reduces it depending on the source code length. But I failed to do it without opening a new window, I did not spend a lot of time on it but I do not know if there is a way to reproduce the action of the clic to resize to window. If you succeed in, I could be interested to finish this idea. Franck > To: pharo-dev(a)lists.pharo.org > From: stepharo(a)free.fr > Date: Thu, 10 Sep 2015 21:09:34 +0200 > Subject: Re: [Pharo-dev] Dynamical resizing of a Nautilus Plugin > > 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] chunk file format (unrecoverable changes)

by Nicolai Hess

Now that this is fixed, should we (is it possible?) fix the changes file? 2015-09-06 21:56 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > Do we have a documentation about the format of > - class definitions > - methods > - class comments > for the changes file ? > > I am asking because some entries are using two separator > "! !" > and some only one > "!" > And we have a problem with the "Recover lost changes" browser > (https://pharo.fogbugz.com/f/cases/16498/unrecoverable-changes) > and I am not sure if this is a bug on the code importer > or if it is a bug on how we write changes to the changes file. > > > nicolai > >

Sept. 10, 2015

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

by Eliot Miranda

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. 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… I'm sorry I didn't see your message. Did you ask on vm-dev? > 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

Sept. 10, 2015

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

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

by Thierry Goubier

Le 10/09/2015 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. :/ Morphic certainly support that. Can't help you about Nautilus, however :( Thierry > > Thanks, > Peter

Sept. 10, 2015

Dynamical resizing of a Nautilus Plugin

by Peter UhnÃ¡k

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] Disable focusing of FastTable

by stepharo

you should introduce it in FTTableMorph Stef Le 10/9/15 00:06, Yuriy Tymchuk a Ã©crit : > Hi, > > is there a nice way to forbid a fast table to take focus? > > because #takesKeyboardFocus is implemented as: â^ self enabledâ. And #enabled is inherited from Morph and is always true. Do I really have to subclass the FTTableMorph just to get rid of focusing? > > Uko >

Sept. 10, 2015

Re: [Pharo-dev] FastTable non-selectable, clickable

by stepharo

yuriy Alain is probably busy but send him a mail. Le 10/9/15 12:10, Yuriy Tymchuk a Ã©crit : > Thanks, Iâll take a look on that. What would be interesting is to add a stripe like line numbers but with critic indicators. Do you know how this should work? > > Uko > >> On 10 Sep 2015, at 12:01, Stephan Eggermont <stephan(a)stack.nl> wrote: >> >> On 10-09-15 11:41, Yuriy Tymchuk wrote: >>> Ideally I want it to be embedded into rubric representation. But I donât know where to start with that. >> Add an instance variable qualitySummary to NautilusAnnotationDisplayer. >> >> add qualitySummary := self qualitySummaryMorph to noteNewOwner: aMorph >> >> in qualitySummaryMorph, return a morph that draws the summary and reacts to click by opening the QA panel. >> >> Stephan >> >> > >

Sept. 10, 2015

Re: [Pharo-dev] FastTable non-selectable, clickable

by stepharo

Stefan We know that the qualityAssistant could be better but for now we should use it and pay attention that yuriy should publish about his research and stay active around :). Stef Le 10/9/15 12:01, Stephan Eggermont a Ã©crit : > On 10-09-15 11:41, Yuriy Tymchuk wrote: >> Ideally I want it to be embedded into rubric representation. But I >> donât know where to start with that. > > Add an instance variable qualitySummary to NautilusAnnotationDisplayer. > > add qualitySummary := self qualitySummaryMorph to noteNewOwner: aMorph > > in qualitySummaryMorph, return a morph that draws the summary and > reacts to click by opening the QA panel. > > Stephan > > >

Sept. 10, 2015

Re: [Pharo-dev] Pharo on iPad Pro

by stepharo

Le 10/9/15 15:31, Stephan Eggermont a Ã©crit : > On 10-09-15 14:57, Aliaksei Syrel wrote: >> Are you Apple's advertisment agent? :D > > No that is a direct quote. I'm just happy that > Apple very slowly seems to move in the right direction. > It will probably need a lot of pressure from EU to keep > going in that direction. That makes them rather similar to Facebook, > Microsoft and Google, and earlier IBM. +1 I want a brick app in such device :) > > Stephan > > > >

Sept. 10, 2015

Re: [Pharo-dev] FogBugz (Case [Issue]16520) CI and Bugtracker - Help topic for how to contribute to Pharo basecode

by stepharo

+ 1 This is important! Stef Le 10/9/15 16:30, Alexandre Bergel a Ã©crit : > Thanks Marcus! > Apparently my two fixes are now in. This is cool! > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Sep 10, 2015, at 11:23 AM, Marcus Denker <marcus.denker(a)inria.fr >> <mailto:marcus.denker@inria.fr>> wrote: >> >> I did some workaround for now >> >> => disabled some not that useful checks >> => put the timout higher >> >> a normal run is now at around 30 min. >> >> >>> On 09 Sep 2015, at 22:05, Marcus Denker <marcus.denker(a)inria.fr >>> <mailto:marcus.denker@inria.fr>> wrote: >>> >>> It needs to be fixed but I *really* did not find any time yet. >>> >>>> On 09 Sep 2015, at 22:00, Peter UhnÃ¡k <i.uhnak(a)gmail.com >>>> <mailto:i.uhnak@gmail.com>> wrote: >>>> >>>> Maybe change the error message until it is resolved to something >>>> like "Timeout blablabla... this is CI issue, please tell the monkey >>>> to try again". >>>> So people know it's not their error and it will also tell them what >>>> to do, so they (me last week, Alex this week, someone else next >>>> week) don't need to ask again and again. >>>> >>>> Peter >>>> >>>> >>>> On Wed, Sep 9, 2015 at 9:57 PM, stepharo <stepharo(a)free.fr >>>> <mailto:stepharo@free.fr>> wrote: >>>> >>>> yes in that case why not fixing that because this is really >>>> really annoying to always get a fix rejected with a bad feedback. >>>> >>>> Stef >>>> >>>> >>>> Le 9/9/15 21:52, Marcus Denker a Ã©crit : >>>> >>>> On 09 Sep 2015, at 20:27, stepharo <stepharo(a)free.fr >>>> <mailto:stepharo@free.fr>> wrote: >>>> >>>> Not much mark it as fix to include. >>>> >>>> The last where this was done added an undeclared. Quality >>>> goes down very fast when we add changes without running the >>>> tests. >>>> >>>> Marcus >>>> >>>> >>>> >>>> >>> >> >

Sept. 10, 2015

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

by stepharo

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

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

by stepharo

Hi ben I agree with you. I had the impression that many pragmaCollector methods would make sense in Pragma class level. Please continue your analysis. We should drastically clean SystemNavigation. - It should work on environment - remove all the browse behavior. Stef Le 10/9/15 17:22, Ben Coman a Ã©crit : > 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 > > However #allSystemPragmas depends on SystemNavigation, so is it be > okay for Pragma to depend on SystemNavigation? > > 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 ]. > > cheers -ben > > [1] https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… > >

Sept. 10, 2015

improvements of RB are cool!!!!

by stepharo

today I spend a couple of hours refactoring some hiearchies and I had many push them and others... and this was a really experience: - do you want to remove the methods in the other subclasses? oh yes please. We should continue to improve pharo because it is becoming better and better. Stef

Sept. 10, 2015

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

by Ben Coman

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

Re: [Pharo-dev] String concatenation using comma ","

by Max Leske

> On 10 Sep 2015, at 18:38, Chris Muller <asqueaker(a)gmail.com> wrote: > > I generally agree about implicit type-conversions, but I don't really > think this one is all that implicit. String concatentation returns a > String, no exceptions. > > By not having this for Strings actually led to Andreas getting bitten, > which is why it was added to Squeak. The "bite" comes when your > program encounters an error, and in your error-handler you wrote a > descriptive message, 'It didn''t work because the value is ', > someOtherString. Except someOtherString is nil. Now your > error-handler itself has an error, blowing up and leading you on a > wild goose chase because of a trivial message-concatentation problem > instead of the real problem. > > Can you describe an example where you feel this one could potentially > bite you by its "implicitnessâ? Thatâs a mean question :) I canât think of an example that is directly related but consider this method: doSomethingWith: someObject self printThisOntoAWebPage: âmy literal â, someObject The intention here is to print something out and âsomeObjectâ is supposed to have a certain format. Letâs say that âsomeObjectâ is a Date object and I want it to be printed as dd.mm.yyyy. The implicit conversion would yield âmy literal 10 September 2015â instead of the expected âmy literal 10.09.2015â. With an exception I would have seen that I need to format that object first, with implicit conversion I might overlook the mistake. Yes, itâs quite the construct I built here but in my experience the truth isnât that far away from it. Cheers, Max > > On Thu, Sep 10, 2015 at 9:34 AM, Max Leske <maxleske(a)gmail.com> wrote: >> Iâm with Sven on this. Just because JavaScript implementations (and others) choose to perform implicit type conversion doesnât mean itâs a good thing. It might make it easier for newcomers to write a hello world program but it will bite you when youâre trying to do actual work. >> >>> On 10 Sep 2015, at 16:16, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> No, this is not a good idea (silent conversions). It is one of the original differences between Pharo and Squeak. Try searching the MLs, I am sure it is all still there. >>> >>> You can also concatenate exceptions to create an exception set, I am sure there are other examples. >>> >>>> On 10 Sep 2015, at 16:12, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: >>>> >>>> Hi >>>> >>>> I'm just curious why "," doesn't convert object to string during concatenation? >>>> >>>> For example I expect >>>> 'answer is ', 42 >>>> to return 'answer is 42' instead of 'SmallInteger are not indexable'. >>>> >>>> Of course you could say that >>>> 'answer is ', 42 asString >>>> does the job... but still why not to put asString in concatenation method >>>> >>>> Cheers, >>>> Alex >>>> >>> >>> >> >> >

Sept. 10, 2015

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

by Max Leske

> 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. > > 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 ]. > > cheers -ben > > [1] https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… >

Sept. 10, 2015

Re: [Pharo-dev] String concatenation using comma ","

by Chris Muller

I generally agree about implicit type-conversions, but I don't really think this one is all that implicit. String concatentation returns a String, no exceptions. By not having this for Strings actually led to Andreas getting bitten, which is why it was added to Squeak. The "bite" comes when your program encounters an error, and in your error-handler you wrote a descriptive message, 'It didn''t work because the value is ', someOtherString. Except someOtherString is nil. Now your error-handler itself has an error, blowing up and leading you on a wild goose chase because of a trivial message-concatentation problem instead of the real problem. Can you describe an example where you feel this one could potentially bite you by its "implicitness"? On Thu, Sep 10, 2015 at 9:34 AM, Max Leske <maxleske(a)gmail.com> wrote: > Iâm with Sven on this. Just because JavaScript implementations (and others) choose to perform implicit type conversion doesnât mean itâs a good thing. It might make it easier for newcomers to write a hello world program but it will bite you when youâre trying to do actual work. > >> On 10 Sep 2015, at 16:16, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> No, this is not a good idea (silent conversions). It is one of the original differences between Pharo and Squeak. Try searching the MLs, I am sure it is all still there. >> >> You can also concatenate exceptions to create an exception set, I am sure there are other examples. >> >>> On 10 Sep 2015, at 16:12, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: >>> >>> Hi >>> >>> I'm just curious why "," doesn't convert object to string during concatenation? >>> >>> For example I expect >>> 'answer is ', 42 >>> to return 'answer is 42' instead of 'SmallInteger are not indexable'. >>> >>> Of course you could say that >>> 'answer is ', 42 asString >>> does the job... but still why not to put asString in concatenation method >>> >>> Cheers, >>> Alex >>> >> >> > >

Sept. 10, 2015

Re: [Pharo-dev] String concatenation using comma ","

by Esteban A. Maringolo

Esteban A. Maringolo 2015-09-10 11:34 GMT-03:00 Max Leske <maxleske(a)gmail.com>: > > Iâm with Sven on this. Just because JavaScript implementations (and others) choose to perform implicit type conversion doesnât mean itâs a good thing. It might make it easier for newcomers to write a hello world program but it will bite you when youâre trying to do actual work. > +1 To this. In the long term having explicit conversions is what I found more valuable. Regards!

Sept. 10, 2015

Bootstrap dependency, System-Announcements --> PragmaCollector

by Ben Coman

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 However #allSystemPragmas depends on SystemNavigation, so is it be okay for Pragma to depend on SystemNavigation? 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 ]. cheers -ben [1] https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM…

Sept. 10, 2015

Re: [Pharo-dev] String concatenation using comma ","

by phil＠highoctane.be

I came to realize the value of that too. Phil On Thu, Sep 10, 2015 at 4:34 PM, Max Leske <maxleske(a)gmail.com> wrote: > Iâm with Sven on this. Just because JavaScript implementations (and > others) choose to perform implicit type conversion doesnât mean itâs a good > thing. It might make it easier for newcomers to write a hello world program > but it will bite you when youâre trying to do actual work. > > > On 10 Sep 2015, at 16:16, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > No, this is not a good idea (silent conversions). It is one of the > original differences between Pharo and Squeak. Try searching the MLs, I am > sure it is all still there. > > > > You can also concatenate exceptions to create an exception set, I am > sure there are other examples. > > > >> On 10 Sep 2015, at 16:12, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > >> > >> Hi > >> > >> I'm just curious why "," doesn't convert object to string during > concatenation? > >> > >> For example I expect > >> 'answer is ', 42 > >> to return 'answer is 42' instead of 'SmallInteger are not indexable'. > >> > >> Of course you could say that > >> 'answer is ', 42 asString > >> does the job... but still why not to put asString in concatenation > method > >> > >> Cheers, > >> Alex > >> > > > > > > >

Sept. 10, 2015

Re: [Pharo-dev] String concatenation using comma ","

by Max Leske

Iâm with Sven on this. Just because JavaScript implementations (and others) choose to perform implicit type conversion doesnât mean itâs a good thing. It might make it easier for newcomers to write a hello world program but it will bite you when youâre trying to do actual work. > On 10 Sep 2015, at 16:16, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > No, this is not a good idea (silent conversions). It is one of the original differences between Pharo and Squeak. Try searching the MLs, I am sure it is all still there. > > You can also concatenate exceptions to create an exception set, I am sure there are other examples. > >> On 10 Sep 2015, at 16:12, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: >> >> Hi >> >> I'm just curious why "," doesn't convert object to string during concatenation? >> >> For example I expect >> 'answer is ', 42 >> to return 'answer is 42' instead of 'SmallInteger are not indexable'. >> >> Of course you could say that >> 'answer is ', 42 asString >> does the job... but still why not to put asString in concatenation method >> >> Cheers, >> Alex >> > >

Sept. 10, 2015

Re: [Pharo-dev] FogBugz (Case [Issue]16520) CI and Bugtracker - Help topic for how to contribute to Pharo basecode

by Alexandre Bergel

Thanks Marcus! Apparently my two fixes are now in. This is cool! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Sep 10, 2015, at 11:23 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > I did some workaround for now > > => disabled some not that useful checks > => put the timout higher > > a normal run is now at around 30 min. > > >> On 09 Sep 2015, at 22:05, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> It needs to be fixed but I *really* did not find any time yet. >> >>> On 09 Sep 2015, at 22:00, Peter UhnÃ¡k <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>> wrote: >>> >>> Maybe change the error message until it is resolved to something like "Timeout blablabla... this is CI issue, please tell the monkey to try again". >>> So people know it's not their error and it will also tell them what to do, so they (me last week, Alex this week, someone else next week) don't need to ask again and again. >>> >>> Peter >>> >>> >>> On Wed, Sep 9, 2015 at 9:57 PM, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: >>> yes in that case why not fixing that because this is really really annoying to always get a fix rejected with a bad feedback. >>> >>> Stef >>> >>> >>> Le 9/9/15 21:52, Marcus Denker a Ã©crit : >>> >>> On 09 Sep 2015, at 20:27, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: >>> >>> Not much mark it as fix to include. >>> The last where this was done added an undeclared. Quality goes down very fast when we add changes without running the tests. >>> >>> Marcus >>> >>> >>> >>> >> >

Sept. 10, 2015

Re: [Pharo-dev] Image and bootstrap dependencies

by Ben Coman

Very cool. A couple of minor improvements: * The double-clicked "target" node is also hidden, so its label does not show. * When double-clicking a second node "B", it resets to show all links, rather than showing only the links for "B". Perhaps reset only when the "target" node is double-clicked again, or the background in double-clicked. cheers -ben On Thu, Sep 10, 2015 at 9:50 PM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > I updated the graph. > There is now: > > dependencies to remove in red > if you double-click on a node, you only see links where the node is > involved. > > > > Le 10 sept. 2015 Ã 13:30, Ben Coman a Ã©crit : > > On Thu, Sep 10, 2015 at 3:54 PM, Christophe Demarey > <Christophe.Demarey(a)inria.fr> wrote: > > Hi Ben, > > > Le 9 sept. 2015 Ã 16:03, Ben Coman a Ã©crit : > > > The interactive graph is cool. Some suggestions: > > * Mark nodes of dependencies you want to prune in red. > > > > yes, I will add it ASAP > > > * Allow nodes to be pinned > > * http://bl.ocks.org/GerHobbelt/3637711 > > > > very good idea. > > TBH, I justa wanted to have a first visualization usable very fast. The > > current result can be improved a lot. > > > no problem. release early, release often is a good practice. > cheers -ben > >

Sept. 10, 2015

Re: [Pharo-dev] FogBugz (Case [Issue]16520) CI and Bugtracker - Help topic for how to contribute to Pharo basecode

by Marcus Denker

I did some workaround for now => disabled some not that useful checks => put the timout higher a normal run is now at around 30 min. > On 09 Sep 2015, at 22:05, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > It needs to be fixed but I *really* did not find any time yet. > >> On 09 Sep 2015, at 22:00, Peter UhnÃ¡k <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>> wrote: >> >> Maybe change the error message until it is resolved to something like "Timeout blablabla... this is CI issue, please tell the monkey to try again". >> So people know it's not their error and it will also tell them what to do, so they (me last week, Alex this week, someone else next week) don't need to ask again and again. >> >> Peter >> >> >> On Wed, Sep 9, 2015 at 9:57 PM, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: >> yes in that case why not fixing that because this is really really annoying to always get a fix rejected with a bad feedback. >> >> Stef >> >> >> Le 9/9/15 21:52, Marcus Denker a Ã©crit : >> >> On 09 Sep 2015, at 20:27, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: >> >> Not much mark it as fix to include. >> The last where this was done added an undeclared. Quality goes down very fast when we add changes without running the tests. >> >> Marcus >> >> >> >> >

Sept. 10, 2015

Re: [Pharo-dev] String concatenation using comma ","

by Sven Van Caekenberghe

No, this is not a good idea (silent conversions). It is one of the original differences between Pharo and Squeak. Try searching the MLs, I am sure it is all still there. You can also concatenate exceptions to create an exception set, I am sure there are other examples. > On 10 Sep 2015, at 16:12, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > Hi > > I'm just curious why "," doesn't convert object to string during concatenation? > > For example I expect > 'answer is ', 42 > to return 'answer is 42' instead of 'SmallInteger are not indexable'. > > Of course you could say that > 'answer is ', 42 asString > does the job... but still why not to put asString in concatenation method > > Cheers, > Alex >

Sept. 10, 2015

Re: [Pharo-dev] Pharo on iPad Pro

by phil＠highoctane.be

Still, this is better than having your app die on your own device coz some damn dev cert expired. Phil On Thu, Sep 10, 2015 at 3:57 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > wait, wait, I knew there was a catch :D > > This refers to creating your own app with XCODE and installing it to your > OWN iOS device. App store still remains the easy way of distributing apps > and I doubt that will accept Pharo as it is . > > On Thu, Sep 10, 2015 at 3:52 PM Stephan Eggermont <stephan(a)stack.nl> > wrote: > >> On 10-09-15 14:26, Dimitris Chloupis wrote: >> > It would have to be a closed version, since Apple does not allow for >> apps >> > that can load third party code. Or did this change ? >> >> It changed. >> >> https://developer.apple.com/xcode/ >> >> Now everyone can get their app on their Apple device. >> Xcode 7 and Swift now make it easier for everyone to build apps and run >> them directly on their Apple devices. Simply sign in with your Apple ID, >> and turn your idea into an app that you can touch on your iPad, iPhone, >> or Apple Watch. Download Xcode 7 beta and try it yourself today. Program >> membership is not required. >> >> Stephan >> >> >>

Sept. 10, 2015

String concatenation using comma ","

by Aliaksei Syrel

Hi I'm just curious why "," doesn't convert object to string during concatenation? For example I expect > 'answer is ', 42 to return 'answer is 42' instead of 'SmallInteger are not indexable'. Of course you could say that > 'answer is ', 42 asString does the job... but still why not to put asString in concatenation method Cheers, Alex

Sept. 10, 2015

Re: [Pharo-dev] Image and bootstrap dependencies

by Craig Latta

> I updated the graph. There is now: > > * dependencies to remove in red > * if you double-click on a node, you only see links where the node > is involved. Very nice! -C -- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

Sept. 10, 2015

Re: [Pharo-dev] Pharo on iPad Pro

by Dimitris Chloupis

wait, wait, I knew there was a catch :D This refers to creating your own app with XCODE and installing it to your OWN iOS device. App store still remains the easy way of distributing apps and I doubt that will accept Pharo as it is . On Thu, Sep 10, 2015 at 3:52 PM Stephan Eggermont <stephan(a)stack.nl> wrote: > On 10-09-15 14:26, Dimitris Chloupis wrote: > > It would have to be a closed version, since Apple does not allow for apps > > that can load third party code. Or did this change ? > > It changed. > > https://developer.apple.com/xcode/ > > Now everyone can get their app on their Apple device. > Xcode 7 and Swift now make it easier for everyone to build apps and run > them directly on their Apple devices. Simply sign in with your Apple ID, > and turn your idea into an app that you can touch on your iPad, iPhone, > or Apple Watch. Download Xcode 7 beta and try it yourself today. Program > membership is not required. > > Stephan > > >

Sept. 10, 2015

Re: [Pharo-dev] Pharo on iPad Pro

by Craig Latta

They still won't approve apps that install new code at runtime, though. So any IDE that used Monticello, for example, would have to be distributed ad-hoc rather than through the Apple Store. Please let me know if that's changed; I would be a lot more interested in iOS if it did. -C -- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

Sept. 10, 2015

Re: [Pharo-dev] Image and bootstrap dependencies

by Christophe Demarey

I updated the graph. There is now: dependencies to remove in red if you double-click on a node, you only see links where the node is involved. Le 10 sept. 2015 Ã 13:30, Ben Coman a Ã©crit : > On Thu, Sep 10, 2015 at 3:54 PM, Christophe Demarey > <Christophe.Demarey(a)inria.fr> wrote: >> Hi Ben, >> >> Le 9 sept. 2015 Ã 16:03, Ben Coman a Ã©crit : >> >> The interactive graph is cool. Some suggestions: >> * Mark nodes of dependencies you want to prune in red. >> >> >> yes, I will add it ASAP >> >> * Allow nodes to be pinned >> * http://bl.ocks.org/GerHobbelt/3637711 >> >> >> very good idea. >> TBH, I justa wanted to have a first visualization usable very fast. The >> current result can be improved a lot. > > no problem. release early, release often is a good practice. > cheers -ben >

Sept. 10, 2015

Re: [Pharo-dev] Pharo on iPad Pro

by phil＠highoctane.be

Time to dust off Xcode :-) Pharo 5.0 on iPad would be cool. Phil On Thu, Sep 10, 2015 at 3:46 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > WOW thats quite a change of direction !!! > Thanks for bringing this to my attention :) Suddenly I am way more > optimistic :) > > On Thu, Sep 10, 2015 at 3:52 PM Stephan Eggermont <stephan(a)stack.nl> > wrote: > >> On 10-09-15 14:26, Dimitris Chloupis wrote: >> > It would have to be a closed version, since Apple does not allow for >> apps >> > that can load third party code. Or did this change ? >> >> It changed. >> >> https://developer.apple.com/xcode/ >> >> Now everyone can get their app on their Apple device. >> Xcode 7 and Swift now make it easier for everyone to build apps and run >> them directly on their Apple devices. Simply sign in with your Apple ID, >> and turn your idea into an app that you can touch on your iPad, iPhone, >> or Apple Watch. Download Xcode 7 beta and try it yourself today. Program >> membership is not required. >> >> Stephan >> >> >>

Sept. 10, 2015

Re: [Pharo-dev] Pharo on iPad Pro

by Dimitris Chloupis

WOW thats quite a change of direction !!! Thanks for bringing this to my attention :) Suddenly I am way more optimistic :) On Thu, Sep 10, 2015 at 3:52 PM Stephan Eggermont <stephan(a)stack.nl> wrote: > On 10-09-15 14:26, Dimitris Chloupis wrote: > > It would have to be a closed version, since Apple does not allow for apps > > that can load third party code. Or did this change ? > > It changed. > > https://developer.apple.com/xcode/ > > Now everyone can get their app on their Apple device. > Xcode 7 and Swift now make it easier for everyone to build apps and run > them directly on their Apple devices. Simply sign in with your Apple ID, > and turn your idea into an app that you can touch on your iPad, iPhone, > or Apple Watch. Download Xcode 7 beta and try it yourself today. Program > membership is not required. > > Stephan > > >

Sept. 10, 2015