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

Re: [Pharo-dev] Condense changes

by Sven Van Caekenberghe

On 18 Apr 2014, at 13:28, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 18.04.2014 um 13:19 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > >> >> On 18 Apr 2014, at 12:23, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> Smalltalk condenseChanges >> >> That is old, please read https://pharo.fogbugz.com/f/cases/12729/Smalltalk-condenseChanges-raises-Zn… >> > Ok, thanks, the search didnât bring up that issue. But if the PharoChangesCondenser is integrated in the image why is it not used when Smalltalk condenseChanges is invoked? Another case of âlet us load that stuff but donât make it publicâ? Because it does not (yet) work on Windows. The new code is way better (faster, easier to understand).

April 18, 2014

Re: [Pharo-dev] Condense changes

by Norbert Hartl

Am 18.04.2014 um 13:19 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > On 18 Apr 2014, at 12:23, Norbert Hartl <norbert(a)hartl.name> wrote: > >> Smalltalk condenseChanges > > That is old, please read https://pharo.fogbugz.com/f/cases/12729/Smalltalk-condenseChanges-raises-Zn… > Ok, thanks, the search didnât bring up that issue. But if the PharoChangesCondenser is integrated in the image why is it not used when Smalltalk condenseChanges is invoked? Another case of âlet us load that stuff but donât make it publicâ? Norbert

April 18, 2014

Re: [Pharo-dev] Condense changes

by Sven Van Caekenberghe

On 18 Apr 2014, at 12:23, Norbert Hartl <norbert(a)hartl.name> wrote: > Smalltalk condenseChanges That is old, please read https://pharo.fogbugz.com/f/cases/12729/Smalltalk-condenseChanges-raises-Zn…

April 18, 2014

Re: [Pharo-dev] Condense changes

by Norbert Hartl

Am 18.04.2014 um 12:20 schrieb Norbert Hartl <norbert(a)hartl.name>: > > Am 18.04.2014 um 11:45 schrieb Marcus Denker <marcus.denker(a)inria.fr>: > >> >> On 17 Apr 2014, at 21:13, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: >> >>> hi all, >>> >>> In a fresh image #30826, I tried: >>> >>> Smalltalk image condenseChanges -> ZnInvalidUTF8 error >>> >>> https://pharo.fogbugz.com/default.asp?12729& >>> describes that but it is closed. >>> >>> I tried the new version: >>> >>> PharoChangesCondenser condense. -> parse error >>> >> Works fine for me. No error. > Well, I did Smalltalk condenseChanges Norbert > I investigated that yesterday while playing with shrinking of an image and Iâve found the culprit. > > https://pharo.fogbugz.com/default.asp?13207 > > Norbert > >> >> >>> Do we open a new bug? >>> >>> Is there another way that I missed? >>> >>> Do you agree that we should remove condenseChanges from SmalltalkImage? >>> >> In Pharo4â¦ >> >> Marcus

April 18, 2014

Re: [Pharo-dev] Condense changes

by Norbert Hartl

Am 18.04.2014 um 11:45 schrieb Marcus Denker <marcus.denker(a)inria.fr>: > > On 17 Apr 2014, at 21:13, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > >> hi all, >> >> In a fresh image #30826, I tried: >> >> Smalltalk image condenseChanges -> ZnInvalidUTF8 error >> >> https://pharo.fogbugz.com/default.asp?12729& >> describes that but it is closed. >> >> I tried the new version: >> >> PharoChangesCondenser condense. -> parse error >> > Works fine for me. No error. I investigated that yesterday while playing with shrinking of an image and Iâve found the culprit. https://pharo.fogbugz.com/default.asp?13207 Norbert > > >> Do we open a new bug? >> >> Is there another way that I missed? >> >> Do you agree that we should remove condenseChanges from SmalltalkImage? >> > In Pharo4â¦ > > Marcus >

April 18, 2014

Re: [Pharo-dev] Condense changes

by Marcus Denker

On 17 Apr 2014, at 21:13, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > hi all, > > In a fresh image #30826, I tried: > > Smalltalk image condenseChanges -> ZnInvalidUTF8 error > > https://pharo.fogbugz.com/default.asp?12729& > describes that but it is closed. > > I tried the new version: > > PharoChangesCondenser condense. -> parse error > Works fine for me. No error. > Do we open a new bug? > > Is there another way that I missed? > > Do you agree that we should remove condenseChanges from SmalltalkImage? > In Pharo4â¦ Marcus

April 18, 2014

EyeMorph inspector issue

by phil＠highoctane.be

I wanted to look at a form and did aForm asMorph explore. Then selected the Morph view in the drop down and then, MNU. Issue is here: https://pharo.fogbugz.com/default.asp?13208 What to do? I've crappily patched but someone educated should look at this since this is a cool feature of Pharo3. Phil

April 18, 2014

R: [ANN] FontAwesome for Seaside

by Lorenzo Schiavina

Really nice! Lorenzo -----Messaggio originale----- Da: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] Per conto di Torsten Bergmann Inviato: giovedÃ¬ 17 aprile 2014 10:27 A: seaside(a)lists.squeakfoundation.org; seaside-dev(a)lists.squeakfoundation.org; Pharo Development List; pharo-users(a)lists.pharo.org; pharo-business(a)lists.pharo.org Oggetto: [Pharo-dev] [ANN] FontAwesome for Seaside Hi, FontAwesome is (as you may know) an iconic font designed for the user with Twitter Bootstrap. I now created a "FontAwesome for Seaside" project - which is a small Seaside wrapper for the FontAwesome project (using the latest version 4.0.3). This is intended as an addition to the already available "Bootstrap for Seaside" [2] project that I wrote and both should allow you to give your Smalltalk based web application a nice stylish look. The project is located on STHub, see [1] where you will also find the documentation. A live demo can be found on http://pharo.pharocloud.com/fontawesome. To try yourself load it from the Pharo config browser or read the docu to see what is required. Thx T. [1] http://smalltalkhub.com/#!/~TorstenBergmann/FontAwesome [2] http://smalltalkhub.com/#!/~TorstenBergmann/Bootstrap

April 18, 2014

Phexample: Image Destroying Bug

by Sean P. DeNigris

Gofer it url: 'http://ss3.gemtalksystems.com/ss/MetaRepoForPharo20'; configurationOf: 'Phexample'; loadStable. "In 2.0, evaluating the following line brings up a debugger (the expected behavior). In 3.0, it never returns, creating an more and more debugger processes until the image becomes unresponsive." true should beFalse. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Phexample-Image-Destroying-Bug-tp4755253.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 18, 2014

Re: [Pharo-dev] Closure vs BlockClosure

by Bernardo Ezequiel Contreras

the historical anecdote could be nice as part of the class documentation. On Thu, Apr 17, 2014 at 8:59 PM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > Thanks Eliot for the historical anecdote > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Apr 17, 2014, at 1:54 PM, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > > > Hi Alexandre, > > > > > > On Thu, Apr 17, 2014 at 8:21 AM, Alexandre Bergel < > alexandre.bergel(a)me.com> wrote: > > Because what we call a block is actually a closure. Smalltalk-80 > invented blocks, which were not closures at that time. Over the time we > found out that Blocks are not really useful, but instead the humanity > largely prefer closure. > > > > I don't think this is right. Yesterday ClÃ©ment and I had lunch with Dan > Ingalls and we talked about the origin of blocks. At first blocks were not > even real objects; instead they were just a syntactic construct for delayed > evaluation. Over time the original Smalltalk team found they needed more > and more useful features, and they wanted everything to be objects so they > introduced both the syntax for blocks and the class BlockContext, but they > didn't look at other languages and so they didn't implement blocks as > closures. > > > > So I think its more accurate to say > > Over time Smalltalkers found blocks were /really/ useful. Later on > they found out that they could implement blocks as closures, with the > result that they were even more useful and much cleaner, leading to a more > efficient virtual machine. > > > > But ok, this is not a pressing thing. Was just a tough. > > > > If it ain't broke don't fix it. The name BlockClosure isn't incorrect. > These are blocks implemented as closures. The name MethodContext /is/ > broken. These /aren't/ just MethodContexts any more, they are both > BlockContexts and MethodContexts, so collapsing ContextPart and > MethodContext together into just Context, and deleting the now unused > BlockContext does make sense. > > > > [snip] > > > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > On Apr 17, 2014, at 11:45 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > wrote: > > > > > Itâs like saying that we have to run Pharo on JVM because everyone is > doing that. In 80s block was invented. Why should we rename it because of > some other languages? > > > > > > Uko > > > > > > On 17 Apr 2014, at 16:35, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > > > > >> Wellâ¦ the whole community of programming language call a closure a > closure. Calling a block what is actually a closure may not be a > well-marketed move in my opinion. > > >> > > >> Alexandre > > >> -- > > >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > >> Alexandre Bergel http://www.bergel.eu > > >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >> > > >> > > >> > > >> On Apr 17, 2014, at 10:29 AM, Sebastian Sastre < > sebastian(a)flowingconcept.com> wrote: > > >> > > >>> On Apr 17, 2014, at 10:08 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > wrote: > > >>> > > >>>> I would rather rename is to Block, as everyone is calling it a > âblockâ. > > >>> > > >>> That might be actually a good idea > > >>> > > >>> sebastian > > >>> > > >>> o/ > > >>> > > >>> PS: thinking in that line there is also âContextâ as, conceptually, > what these blocks of code want to do is to keep the evaluation in a > specific context. But to ease know-how transference and type less Iâd > rather go with the most popular name, as you suggested: âBlock' > > >>> > > >>> > > >> > > >> > > > > > > > > > > > > > > > > > > -- > > best, > > Eliot > > > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

April 18, 2014