- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ENH]: Zinc - Streaming Download Progress

by Sven Van Caekenberghe

Hi Sean, Yeah, that would be nice. But do you agree that the only solution is to use a dynamic variable ? Because signalling code has to known whether there is someone catching the notifications, right ? The #signalProgress option in ZnClient was just the first step, the interface. The real, interesting signalling has to happen in ZnUtils class>>#streamFrom:to:size: If you agree that the dynamic variable is the way to go, I can quite easily implement it. Sven On 12 Jul 2012, at 17:58, Sean P. DeNigris wrote: > It would be /really/ nice if Zinc sent notifications of streaming download > progress to log listeners and HTTPProgress handlers. > > The following method showed nice progress notifications via both routes > until the file started to download, which is the bulk of the time spent... > > downloadLatestVmMakerImage > > | client | > client := ZnClient new. > client signalProgress: true. > client log addListener: self. > > [client > url: > 'https://ci.lille.inria.fr/pharo/job/Cog%20Git%20Tracker/lastSuccessfulBuild…'; > downloadTo: '/Volumes/Fast/Squeak/Cog/vmmaker-image.zip'.] > on: HTTPProgress > do: [ :ex | > Transcript show: ex asString; cr. > ex resume ] > > -- > View this message in context: http://forum.world.st/ENH-Zinc-Streaming-Download-Progress-tp4639686.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

July 12, 2012

[Pharo-project] [ENH]: Zinc - Streaming Download Progress

by Sean P. DeNigris

It would be /really/ nice if Zinc sent notifications of streaming download progress to log listeners and HTTPProgress handlers. The following method showed nice progress notifications via both routes until the file started to download, which is the bulk of the time spent... downloadLatestVmMakerImage | client | client := ZnClient new. client signalProgress: true. client log addListener: self. [client url: 'https://ci.lille.inria.fr/pharo/job/Cog%20Git%20Tracker/lastSuccessfulBuild…'; downloadTo: '/Volumes/Fast/Squeak/Cog/vmmaker-image.zip'.] on: HTTPProgress do: [ :ex | Transcript show: ex asString; cr. ex resume ] -- View this message in context: http://forum.world.st/ENH-Zinc-Streaming-Download-Progress-tp4639686.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 12, 2012

Re: [Pharo-project] PBE2 - PDFs

by phil＠highoctane.be

Spec Drafts>Zinc,... 2012/7/12 Damien Cassou <damien.cassou(a)gmail.com> > Hi Phil, > > On Thu, Jul 12, 2012 at 12:49 PM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > > There are quite a number of tex files in the repo that have no PDF > > rendition. > > > for example? > > > > As I have been working a bit on sound, I think I could also contribute > > something to a chapter on that subject. > > If you see an already existing chapter you could contribute to or want > to create a new one, go ahead. Please tell us what you are doing on > "Squeak By Example" <sbe(a)iam.unibe.ch>. > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > -- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges Belgium

July 12, 2012

[Pharo-project] Monticello preferences not working in 1.4

by phil＠highoctane.be

I wanted to switch the default package-cache location to somewhere else. So, I changed the prefs setting to the location where I moved all of the packages. But... this opening Monticello afterwards still lists the original location (in fact the first place where I ran the one click (that I moved somewhere else). See screenshot. What to do? Phil[image: Images intÃ©grÃ©es 1]

July 12, 2012

[Pharo-project] Weird error with halos on a SystemWindow

by phil＠highoctane.be

self world answers nil and then cannot do the displayWorld. Weird for a halomorph. What's wrong here? It is annoying since I was using the halo "red" menu to work with a morph interactively. Ideas? Pharo 1.4 here. doMenu: evt with: menuHandle "Ask hand to invoke the halo menu for my inner target." | menu | self obtainHaloForEvent: evt andRemoveAllHandlesBut: nil. self world displayWorld. menu := innerTarget buildHandleMenu: evt hand. innerTarget addTitleForHaloMenu: menu. menu popUpEvent: evt in: self world.

July 12, 2012

Re: [Pharo-project] FileSystem. Possible FSReference rename

by Denis Kudriashov

2012/7/12 Sean P. DeNigris <sean(a)clipperadams.com> > > Denis Kudriashov wrote > > > > I think FSLocator and FSReference are same objects: > > FSReference = fileSystem + path > > FSLocator = "some origin object" + path. > > > > I think "some origin object" can be implemented as special > > FSRelativeFileSystem. And fileLocator became fileReference. > > > > Now in "FSLocator vmDirectory" "some origin object" is symbol. And > > FileLocator>>resolve method perform some complex stuff through FSResolver > > hierarchy logic. > > > > What is purpose of FSResolver hierarchy? > > What is purpose of #resolve: and #resolve methods? Why so many classes > (in > > FileSystem) implement it: FSLocator, FSReferece, FSPath, FSFileSystem, > > FSResolver? > > From Issue 6333: FileSystem refactoring > "- cleaned up FileLocator / FileReference hierarchy > - use FileLocators wherever possible" > > Cami, what do you think about Denis's point? > > Sean > > Hello, Good you found this thread. I have no time to see deeper what happens with current FS state. But I think my questions not influence current design changes. So, I am very interesting what you thing about all of that?

July 12, 2012

Re: [Pharo-project] FileSystem. Possible FSReference rename

by Camillo Bruni

Hi sean / denis, see my comments below... On 2012-07-12, at 14:10, Sean P. DeNigris wrote: > Denis Kudriashov wrote >> >> I think FSLocator and FSReference are same objects: >> FSReference = fileSystem + path >> FSLocator = "some origin object" + path. indeed they are way to similar ;), I doubted myself a couple of times already whether they are really needed or not :) and I do not particularly like the implementation :/ >> I think "some origin object" can be implemented as special >> FSRelativeFileSystem. And fileLocator became fileReference. Indeed a relative filesystem is something I need (or better a relative store..) This is specially nice if you want to start stacking filesystems into each other. I will explicitly need that for the new internal Pharo2.0 fileystem... >> Now in "FSLocator vmDirectory" "some origin object" is symbol. And >> FileLocator>>resolve method perform some complex stuff through FSResolver >> hierarchy logic. >> >> What is purpose of FSResolver hierarchy? You need at least on per Platform (resolving home / preferences / documents...) That will leave you with already 3 different implementations. But actually it might make sense to put these methods (as extensions?) on the specific stores! >> What is purpose of #resolve: and #resolve methods? Why so many classes (in >> FileSystem) implement it: FSLocator, FSReferece, FSPath, FSFileSystem, >> FSResolver? I will think about it a bit more. I don't have real refactoring plans for FileSystem anymore, so if someone comes up with a nice solution I am glad to adapt it and put it in 2.0 :) best cami

July 12, 2012

[Pharo-project] [update 2.0] #20205

by Marcus Denker

20205 ----- Issue 6349: unload Package TrueType http://code.google.com/p/pharo/issues/detail?id=6349 Issue 6345: failing test Tests.Release.ReleaseTest.testUndeclared http://code.google.com/p/pharo/issues/detail?id=6345 Issue 6342: doesNotUnderstand: Finder UI>>guessTypeByName: http://code.google.com/p/pharo/issues/detail?id=6342 -- Marcus Denker -- http://marcusdenker.de

July 12, 2012

Re: [Pharo-project] FileSystem. Possible FSReference rename

by Sean P. DeNigris

Denis Kudriashov wrote > > I think FSLocator and FSReference are same objects: > FSReference = fileSystem + path > FSLocator = "some origin object" + path. > > I think "some origin object" can be implemented as special > FSRelativeFileSystem. And fileLocator became fileReference. > > Now in "FSLocator vmDirectory" "some origin object" is symbol. And > FileLocator>>resolve method perform some complex stuff through FSResolver > hierarchy logic. > > What is purpose of FSResolver hierarchy? > What is purpose of #resolve: and #resolve methods? Why so many classes (in > FileSystem) implement it: FSLocator, FSReferece, FSPath, FSFileSystem, > FSResolver? >From Issue 6333: FileSystem refactoring "- cleaned up FileLocator / FileReference hierarchy - use FileLocators wherever possible" Cami, what do you think about Denis's point? Sean -- View this message in context: http://forum.world.st/FileSystem-Possible-FSReference-rename-tp3317375p4639… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 12, 2012

Re: [Pharo-project] PBE2 - PDFs

by Damien Cassou

Hi Phil, On Thu, Jul 12, 2012 at 12:49 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > There are quite a number of tex files in the repo that have no PDF > rendition. for example? > As I have been working a bit on sound, I think I could also contribute > something to a chapter on that subject. If you see an already existing chapter you could contribute to or want to create a new one, go ahead. Please tell us what you are doing on "Squeak By Example" <sbe(a)iam.unibe.ch>. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 12, 2012