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

Re: [Pharo-dev] Threaded #anySatisfy:

by stepharo

We got some problems with the cache logic recently. To the point we would like to add a UUID to the file name. It needs a real look. Stef > * I'm don't think it's used, but this might be a candidate: > cacheAllFileNamesDuring: aBlock > cacheFileNames == true ifTrue: [ ^ aBlock value ]. > allFileNames := nil. > cacheFileNames := true. > <-- If this is a suspension point, if terminated, the file names would > be static from the next call to allFileNames until the next time > cacheAllFiles... is used --> > ^ aBlock ensure: [ > allFileNames := nil. > cacheFileNames := false] > > If the need is guarding against arbitrary termination, not just errors > in the block itself, I think it would have to be: > > ^[allFileNames := nil. > cacheFileNames := true. > aBlock value ] ensure: > [allFileNames := nil. > cacheFileNames := false] > > > Of the actually called methods from includesVersionNamed:, I stopped > checking after stumbling into, and spending too much time wondering > why the code did what it did: > > MCFileBasedRepository >> #readableFileNames > | all cached new emptyFilenamelength | > "<hyphenated-package-name>.<dotted.branch.tag>-<initials>.<count>.mcz" > emptyFilenamelength := 'P-i.c.mcz' size. > all := self allFileNames."from repository" > all := all reject: [ :each | each size < emptyFilenamelength]. > "first stupid way to filter first level broken files. Ideally we should > remove any files not following the naming pattern: > PackageName-author.number[(branch)].mcz" > cached := self cachedFileNames."in memory" > new := all difference: cached. > ^ (cached asArray, new) > select: [:ea | self canReadFileNamed: ea] > > Removing cached entries from all entries, then iterating on the > remaining + cached? > That's an aweful lot of nonsense for the clearly essential capability > to say you are able to read files that have recently been deleted from > the file system...

Sept. 25, 2014

Re: [Pharo-dev] Monticello commit hook

by Franco Musi

Hi Thierry, for now I want only to execute code for the ones done via the Monticello Browser, but it will be good to look at the other options if I happen to need them sometime in the future. 2014-09-25 16:03 GMT-03:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > Le 25/09/2014 20:54, Eliot Miranda a Ã©crit : > >> Hi All, >> >> I was about to respond to Franco;s question by suggesting he start a >> commit, to open up the commit dialog, and then use halos to explore the >> window, from where he'd find what he was looking for and learn a >> strategy he could use for the long-term to explore this wonderfully >> reflective and open system we call Smalltalk. But on opening a Pahro >> 3.0 image to make sure that halos were available I couldn't find them >> So what's a person to do if they want to explore the system from the >> UI? It used to be that one could quickly look behind the curtain and >> find riches there. Why has this avenue been cut off? Is there an >> alternative? >> > > Hi Eliot, > > what you do in Pharo is to get the control UI menu, with Ctrl+Shift+Mouse > Right Click. > > On Thu, Sep 25, 2014 at 11:14 AM, Franco Musi <fmusi33(a)gmail.com >> <mailto:fmusi33@gmail.com>> wrote: >> >> Hey guys, I'm new here with Pharo and Monticello and I want to >> extend the commit's functionality. Can you lead me to which classes >> or methods do I have to start looking for making Monticello execute >> some code of mine whenever it does a commit? >> > > What you are asking depends on what you want to do. Do you want all > commits to be trapped, or just some on a certain repository, or just the > ones done via a save in the Monticello Browser? > > The last one would be the easy one, but it isn't the only one. > > Thierry > >

Sept. 25, 2014

Re: [Pharo-dev] Threaded #anySatisfy:

by stepharo

IMHO, the better option would be the version using a shared queue, but putting it in a non-core package, say, Collections - Parallell. Anyone else think it'd be a useful addition? Cheers, Henry Yes! Now it would be nice to be able to get more information about methods (with Spur object format probably) to know if a method is performing side effect or not. Stef

Sept. 25, 2014

Re: [Pharo-dev] new VMs promoted ad stable

by Torsten Bergmann

Hi Esteban, But the Windows VM still has this bug, see here http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2014-September/1… and here https://pharo.fogbugz.com/f/cases/13995/Recent-Windows-VM-does-not-reopen-f… cheers, T. > Gesendet: Donnerstag, 25. September 2014 um 17:53 Uhr > Von: "Esteban Lorenzano" <estebanlm(a)gmail.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: [Pharo-dev] new VMs promoted ad stable > > Hi, > > I promoted latest VMs to stable. > Not many changes, but at least infamous SmallInteger bug should not be there anymore. > > cheers, > Esteban >

Sept. 25, 2014

Re: [Pharo-dev] [pharo-project/pharo-core] 8cce4c: 40254

by stepharo

Basically the idea is that we get a API to manage all the windowing and event information. We will be to clean the VM event handling code. Right now it works normally. Soon we will have a SDL plugin as a back end. And it should be using Ronie UFFI Stef >> 14071 OSWindow integration part1 > Can we get a short status update? What can be done on which platforms? > Thanks :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/pharo-project-pharo-core-8cce4c-40254-tp4780221p47802… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Sept. 25, 2014

Re: [Pharo-dev] Windows VM does not reopen fullscreen images

by stepharo

If one person does a pull request it will help. Stef On 25/9/14 10:03, Torsten Bergmann wrote: > See > > https://pharo.fogbugz.com/f/cases/13995/Recent-Windows-VM-does-not-reopen-f… > > If I understand correctly it is already fixed in eliots vmmaker source. When will the next > sync happen? Any Pharo-VM Maintainer that is able to care? > > Thx > T. > >

Sept. 25, 2014

Re: [Pharo-dev] [pharo-project/pharo-core] 18c33b: 30858

by stepharo

+ 1 :) On 24/9/14 23:52, Sean P. DeNigris wrote: > GitHub wrote >> 14034 add to Pharo3: substrings: >> https://pharo.fogbugz.com/f/cases/14034 > I've had subStringXyz -> substringXyz in the back of my mind for quite a > while, but kept putting it off after the pain of the first one we changed. > If we're committed to making them consistent, maybe we should do them all > for this release and be done with it... > > allRangesOfSubString: > findNextSubString:inTextMorph: > subStrings: > testSubStrings > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/pharo-project-pharo-core-18c33b-30858-tp4779985p47800… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Sept. 25, 2014

Re: [Pharo-dev] Nautilus roadmap / icons

by stepharo

On 24/9/14 18:14, phil(a)highoctane.be wrote: > > In > https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/Cleaning… > > I see that you want to remove history, text/bytecode icons > > Why ? > > I am using those. > I propose that. I would prefer that people use the plugins that they want and that the default is lighter. Simplifying - the history to me is really limited. - for the buttons one button is to switch mode other button (the I) with the same symbolic feel are queries (ugly) - I do not see why we need button to switch more for something that really few people use (it could be a menu) or at least a checkbox and not a button. > Phil >

Sept. 25, 2014

Re: [Pharo-dev] Monticello commit hook

by stepharo

On 24/9/14 02:03, fmusi wrote: > Hey guys, I'm new here with Pharo and Monticello welcome > and I want to extend the > commit's functionality. Can you tell us what you want to achieve? > Can you lead me to which classes or methods do I > have to start looking for making Monticello execute some code of mine > whenever it does a commit? look at snapshot method > > Thanks in advance. > > > > -- > View this message in context: http://forum.world.st/Monticello-commit-hook-tp4779799.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Sept. 25, 2014

Re: [Pharo-dev] Code critics problem

by stepharo

On 23/9/14 19:39, phil(a)highoctane.be wrote: > Hello, > > I tried to run Code Critics on some packages and I got a stacktrace. > > I fueled it out: > > https://www.dropbox.com/s/m4plmq5lilyvixl/Debugger-Stack-UndefinedObject-20… > > Ideas why? Without looking at it. No. Are you on 4.0? > > Are code critics working in the first place? Yes there were working. > > TIA > Phil

Sept. 25, 2014