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

Re: [Pharo-project] [ANN] iPad Dr. Geo 12.10

by Hilaire Fernandes

Peter, I really need to know what were your expectations during this frustration time, so I will have a very clear indication about what and how I should improve. You can email me privately at hilaire AT drgeo.eu Thanks Hilaire Le 16/09/2012 21:23, Peter Hugosson-Miller a Ã©crit : > Hehe, AFAIK, "frustration time" isn't a proper phrase, it's just > something I made up to try and describe the time it takes from starting > up a new program I've never seen before, until it makes me frustrated. > In the best of cases that never happens, and I must say that it's highly > personal, and depends largely on my expectations at the time. > > In this case, I had already decided to buy the app, not knowing if I > would have a use for it, just because I like to do things to help the > Smalltalk community in any way that I can. In the back of my mind I also > hoped it might be something I could use with my kids, to show them a bit > about geometry, maths in general, and maybe even Smalltalk. I was not > expecting a beautiful, polished finish, nor much in the way of > documentation, but I'd hoped that, given a few minutes of time, there > would be enough clues to be found by clicking and prodding around, to be > able to make it do something cool. > > Sadly, during the time I had available during that first look, I didn't > manage to make anything happen at all, and I felt frustrated. I fear > that someone with higher expectations might have become cross at that > point, and that's why I wanted to suggest a tutorial button. Now I know > that I just need to go and watch those demo videos before I try next > time :-) >

Sept. 17, 2012

Re: [Pharo-project] [ANN] iPad Dr. Geo 12.10

by Hilaire Fernandes

Dmitry Golubovsky (Android) and Esteban Lorenzano (iPad) proved to be very reliable people to work with, they also have a good sense of human relationship. Thanks you guys. Now I hope, to see more Android and iPad Smalltalk Pharo applications. It will really consolidate our ecosystem. Thanks Hilaire Le 17/09/2012 03:16, Chris Muller a Ã©crit : > Hilaire, I completely admire your dedication. Making great software > is a long road. Congratulations.

Sept. 17, 2012

Re: [Pharo-project] Zinc Progress

by Sven Van Caekenberghe

On 16 Sep 2012, at 23:14, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> the culprit IMO is ZnClient>>#executeWithRetriesRemaining: which does a >>> on: Exception do:[ ... retry ]. so that means on an HTTPProgress you >>> initiate a retry? (and wait for retryDelay), AUCH! :D >> >> Yeah, that is probably it, and that is horrible, terrible. .. ;-) >> In #executeWithTimeout a special #exceptionSetForIfFail is used to avoid that, if I remember correctly. >> Tomorrow, I'll have another look, with a fresh head. > > cool ;) I assume a simple Exception => Error will do :P Well, no ;-) I think it would be better to only do a retry on NetworkErrors and ZnParseErrors. On the other hand, the ifFail functionality should trigger on any Error. We'll see. Thanks again for the help, you made Pharo faster by removing my explicit Delays ;-) Sven Sven Van Caekenberghe uploaded a new version of Zinc-HTTP to project Zinc HTTP Components: http://www.squeaksource.com/ZincHTTPComponents/Zinc-HTTP-SvenVanCaekenbergh… ==================== Summary ==================== Name: Zinc-HTTP-SvenVanCaekenberghe.301 Author: SvenVanCaekenberghe Time: 17 September 2012, 10:10:49 am UUID: 85632c09-a6c4-40e9-b29b-1c5e86d07ead Ancestors: Zinc-HTTP-SvenVanCaekenberghe.300 Fixed a bug where HTTPProgress notifications would trigger a retry. Thanks Camillo Bruni for finding this problem and suggesting a solution. Now, retries are only triggered by (NetworkError, ZnParseError), while the #ifFailBlock will be trigger on any Error. Furthermore, #noteRetrying: and noteIgnoringExceptionOnReusedConnection: will report on the actual exception. The default #ifFailBlock is now [ :exception | exception pass ] for some cleaner code. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Sept. 17, 2012

Re: [Pharo-project] [ANN] iPad Dr. Geo 12.10

by Chris Muller

Hilaire, I completely admire your dedication. Making great software is a long road. Congratulations. On Sun, Sep 16, 2012 at 3:30 AM, Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> wrote: > Dr. Geo (aka Dr. Geometry) 12.10 for iPad is available on AppStore. It > comes in two versions: gratis and paid. > http://itunes.apple.com/us/app/dr.-geometry/id559858173?l=fr&ls=1&mt=8 > > Compare to the desktop versions, it is almost feature complete: only the > script and programmed figure can not be created or edited with this > version. However, sketches including scripts are interpreted and > rendered correctly on the tablet. > > *Feedbacks* and *rating* are welcome and greatly appreciated! > > Thanks! > > http://drgeo.eu > > >

Sept. 17, 2012

Re: [Pharo-project] Zinc Progress

by Camillo Bruni

>> the culprit IMO is ZnClient>>#executeWithRetriesRemaining: which does a >> on: Exception do:[ ... retry ]. so that means on an HTTPProgress you >> initiate a retry? (and wait for retryDelay), AUCH! :D > > Yeah, that is probably it, and that is horrible, terrible. .. ;-) > In #executeWithTimeout a special #exceptionSetForIfFail is used to avoid that, if I remember correctly. > Tomorrow, I'll have another look, with a fresh head. cool ;) I assume a simple Exception => Error will do :P

Sept. 16, 2012

Re: [Pharo-project] Smalltalkhub news

by Camillo Bruni

On 2012-09-16, at 22:50, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 16 Sep 2012, at 21:56, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >>> I am especially interested in the last point. Has it something to do with (using) Zn ? >> >> yes, we basically did a HEAD request and returned false on 404, however >> Zn does 3 or so retries, and thus makes everything slow :). I don't know what >> the side-effects are, but we reduce the retryCount to 0, to get low response times. >> >> I thought that upon a valid 404 response there is no retry needed? (but I guess >> I miss something here :P) > > The reason ZnClient keeps on retrying on 404 is because you probably had #enforceHttpSuccess true as part of #systemPolicy and only 2xx response are considered a success. ah right, that will do it! > But this is an interesting use case: basically 404 is a valid response here. I'll have to think about that so more. well now I know, so I'm fine by manually changing it :P

Sept. 16, 2012

Re: [Pharo-project] Zinc Progress

by Sven Van Caekenberghe

On 16 Sep 2012, at 21:59, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> I assume that the overhead only occurs for small files... >>> >>> ZnClient new >>> signalProgress: true; >>> systemPolicy; >>> beOneShot; >>> url: 'http://smalltalkhub.com/mc/estebanlm/Voyage/main?format=raw'; >>> get. >>> >>> with progress 2.5secs without, 57ms.. :/ well might be that the server >>> responds with an incomplete header or so... >> >> another remark with signalProgress the time to run highly varies, 250ms - 2500ms. >> whereas without progress notification it stays <140ms > > the culprit IMO is ZnClient>>#executeWithRetriesRemaining: which does a > on: Exception do:[ ... retry ]. so that means on an HTTPProgress you > initiate a retry? (and wait for retryDelay), AUCH! :D Yeah, that is probably it, and that is horrible, terrible. .. ;-) In #executeWithTimeout a special #exceptionSetForIfFail is used to avoid that, if I remember correctly. Tomorrow, I'll have another look, with a fresh head. Thx again! -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Sept. 16, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 352 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 16, 2012

Re: [Pharo-project] Smalltalkhub news

by Sven Van Caekenberghe

On 16 Sep 2012, at 21:56, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> I am especially interested in the last point. Has it something to do with (using) Zn ? > > yes, we basically did a HEAD request and returned false on 404, however > Zn does 3 or so retries, and thus makes everything slow :). I don't know what > the side-effects are, but we reduce the retryCount to 0, to get low response times. > > I thought that upon a valid 404 response there is no retry needed? (but I guess > I miss something here :P) The reason ZnClient keeps on retrying on 404 is because you probably had #enforceHttpSuccess true as part of #systemPolicy and only 2xx response are considered a success. But this is an interesting use case: basically 404 is a valid response here. I'll have to think about that so more. Thanks for pushing this and letting me know. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Sept. 16, 2012

[Pharo-project] [update 2.0] #20289

by StÃ©phane Ducasse

20289 ----- - Issue 6626: [Nautilus] removing groups is not working properly. Thanks Benjamin Van Ryseghem. http://code.google.com/p/pharo/issues/detail?id=6626 - Issue 5103: Better Gofer error messages. Thanks Sean De Nigris and Camillo Bruni. http://code.google.com/p/pharo/issues/detail?id=5103 - Issue 6673: Remove squeakmap from MC repositories. http://code.google.com/p/pharo/issues/detail?id=6673

Sept. 16, 2012