November 2016 - Pharo-users

Re: [Pharo-users] Keeping data with an application

by Dale Henrichs

Sergio, You might take a look at the talk I gave on Voyage/Tugrik at ESUG(slides[1], video[2]). The project is in a functional, but roughed out stage --- but the main idea behind it is that with GemStone as the db serve, you are dealing with Smalltalk objects on both the client and server ... Voyage Server Blocks allow you to write code on the client that is executed against objects on the server ... STON is used for serialization/materialization ... Voyage Server Blocks let you blur the lines as to where do the objects live and where does the code execute ... Currently Tugrik uses MongoTalk as the model for Voyage-style interactions between client and server, but Voyage Server Blocks (which are not a feature of MongoTalk) may be useful on their own ... In the talk, I mention that I am looking for partners in pushing Voyage/Tugrik forward, because I think that real users with real problems are needed to drive the project forward --- I am more interested in meeting real developer needs, than building something that makes me happy:) MongoTalk was originally chosen to make it practical for folks already using Voyage/Mongo to easily kick the tires on Voyage/Tugrik, but I don't think that it is necessary to stay coupled to MongoTalk. Michal Balda is looking at something "simpler than Tugrik+MongoTalk+Voyage" and I wish that I could be in Zurich to see his presentation next week[3]:) as I want to support his efforts ... Dale [1] http://www.slideshare.net/esug/tugrik-a-new-persistence-option-for-pharo [2] https://www.youtube.com/watch?v=YwlUdRaqTwE&feature=youtu.be [3] http://forum.world.st/ANN-Zurich-Smalltalk-Meetup-Nov-8th-2016-tt4919147.ht… On 11/01/2016 08:54 AM, sergio ruiz wrote: > Hey, all.. > > One of the things that I find SUPER necessary when developing an app > is to be able to grab data from somewhere else and quickly and easily > work on it from my machine. > > For instance, when I get a bug report that smells funny, the first > thing i sometimes do is run a script that grabs the production data, > and populates my local database with that data. > > i am fleshing out a project that i would really like to use Teapot > (REST) for. i could then write several front ends in whatever > framework/language. > > I was thinking about using Voyager, but the problem is, the data is > VERY relational (see below, if interested).. objects are linked to > each other fairly tightly. I donât know if this would be the way to > handle the data, as there would be lots of duplication using mongodb > as a datastore. > > Of course, my first thought is Gemstones, but I donât know how to grab > the production data and pull it into my local development system. > > Does anyone have any thoughts on this? > > For those curious about the data design, i am setting up a REST server > for an collaborative internet radio applicationâ¦ > > - there would be a global pool of stations (just streaming urls with > metadata, really) > - each user can select from or contribute to the global pool > - users can add tags to stations (or search through the global > stations based on tags) > - users can attach comments to stations > > not complex or intimidating at all, and super easy to model in > smalltalk, but not sure about how to store data so that I can quickly > grab production data and troubleshoot if if necessary. > > Thanks! > > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.Village-Buzz.com > http://www.ThoseOptimizeGuys.com > http://www.coffee-black.com > http://www.painlessfrugality.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101

Nov. 1, 2016

Re: [Pharo-users] How does Boolean ifTrue work?

by Igor Stasenko

On 1 November 2016 at 17:00, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Hey Igor is around \o/ > Hey heya! :) > BTW using size = 0 triggers a code critic telling you to use isEmpty. > > Maybe there is a rule of isEmpty ifTrue: :-) > > I think that there could be a lot of convenience methods in the base > image. They can be in an extension protocol, no issue. STON and gt have a > ton of these. In the base image. > > About beginners, well: have a look in some Zinc code and learn a truckload > of tricks. Like inject: somePath into: ... etc. > > And when puzzled, Halt now and debug or inspect it go a long way in > figuring things out. > > As long as the method is intention revealing, what is the issue? > > At the risk of some flames, Pharo isn't bound to some Smalltalk > compatibility. And that is what is cool about it. We chose another path now > we have to go our way of else. > > Building on a great foundation is nice. But that doesn't equate to > following the Smalltalk canon IMHO. > > And now 64 bits becoming real with a nice FFI and pinned objects... that > is going to bring in a lot of non smalltalk stuff for sure. > > Phil > > well, if continue on that, i think that while #ifEmpty: is perfectly fine, the #ifEmptyOrNil: are not. And indeed, in this case im also inclined to see those as pollution. Because uninitialized state can (or better to say - *must*) happen in one form - either it is nil, or empty collection, but not both. If your code having entry points that treats both of those as some kind of uninitialized state, then i would call it bad. To my opinion, it is bad practice to declare 'my method(s) can deal with any shit you can throw into it'. Personally, i prefer to clearly state what it accepting and what not, and strongly discourage any other free-form inputs, or even better - making them impossible to appear, so you don't have to put #ifEmptyOrNilOrCrazy: everywhere to make your code idioto-proof :) And the stupidity-proofing is quite simple, use converters/validators immediately on passed external data: myMethod: externalData myValidState := externalData asSanelyCheckedData. so, like that you don't have to put: myValidState ifValidState: [] everywhere :) Le 1 nov. 2016 15:14, "Igor Stasenko" <siguctua(a)gmail.com> a Ã©crit : > >> >> >> On 1 November 2016 at 11:31, jtuchel(a)objektfabrik.de < >> jtuchel(a)objektfabrik.de> wrote: >> >>> Phil, >>> >>> >>> I see your point but disagree. >>> I don't use Pharo regularly, so I cannot currently check if the >>> implementation around this emptiness check is complete. >>> >>> With complete I mean that following your logic, theere should be at >>> least implementations of >>> >>> ifEmpty: >>> ifNotEmpty: >>> ifEmpty:ifNotEmpty: >>> ifEmptyOrNil: >>> ifEmptyOrNil:otherwise: >>> >> >> why pollution? >> it just convenience method. mind you, that #isEmpty is also convenience >> method, without it you would do it like: >> >> myArray size isZero ifTrue: [] >> of wait.. #isZero also convenience method... so if you elitist then you >> have to write it like that: >> >> myArray size = 0 ifTrue: [] >> >> And that , to my opinion, adds even more pollution to the user code, >> because first, it is longer, and second >> #ifEmpty: much better clarifies the intent of author, comparing to size = >> 0 >> >> >>> I really have to check for the size of collections very often, and the >>> size of 1 is a very frequent case. So why not add: >>> >>> ifExactlyOne: >>> ifSizeIs:do: >>> ifSizeIsGreaterThan:do:otherwiseDo: >>> >>> You get the picture. I strongly believe this leads to pollution and ends >>> up in a mess. >>> We could save so much typing and make our programs so much more readable >>> if we only were a bit more creative, right? ;-) >>> A DSL is another story, though. If you write a Library that makes >>> handling Collections nicer, this is okay and the methods are good to exist >>> in its context. But they shouldn't necessarily all be part of the base >>> image. >>> >>> >>> Don't get me wrong: if you and the Pharo community agree on lots of >>> convenience methods, that is okay for me, and I find myself adding such >>> methods to VA Smalltalk from time to time. I appreciate many of them being >>> brought to VA ST in Grease. >>> >>> Sometimes, this is simply a question of taste, sometimes it saves >>> typing, sometimes it helps to improve readability of code. >>> >>> But I wouldn't go so far to tell people they should better use such a >>> method as a general advice. I would probably tell them: "look, here's a >>> method I find much more elegant, you could *also* use that to save >>> typing/increase readability". >>> >>> Just my 2 cents, and highly off topic ;-) >>> >>> Joachim >>> >>> >>> >>> >>> Am 01.11.16 um 08:43 schrieb phil(a)highoctane.be: >>> >>> Because I grew tired of the isEmpty ifTrue: [ ] all over the place. >>> And ifEmpty has the right semantics for my use cases (like assignment). >>> >>> I do not really care about portability, I am doing Pharo only. >>> >>> Phil >>> >>> On Mon, Oct 31, 2016 at 5:30 PM, jtuchel(a)objektfabrik.de < >>> jtuchel(a)objektfabrik.de> wrote: >>> >>>> Am 31.10.16 um 15:59 schrieb phil(a)highoctane.be: >>>> >>>> but you should use myCollection ifEmpty: [ ... ] >>>> >>>> >>>> interesting. Why do you think so? what if you wanted your code to be >>>> portable across Smalltalk dialects? >>>> >>>> >>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> ----------------------------------------------------------------------- >>>> Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de <jtuchel(a)objektfabrik.de> >>>> Fliederweg 1 http://www.objektfabrik.de >>>> D-71640 Ludwigsburg http://joachimtuchel.wordpress.com >>>> Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 >>>> >>>> >>>> -- >>> ----------------------------------------------------------------------- >>> Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de <jtuchel(a)objektfabrik.de> >>> Fliederweg 1 http://www.objektfabrik.de >>> D-71640 Ludwigsburg http://joachimtuchel.wordpress.com >>> Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 >>> >>> >>> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > -- Best regards, Igor Stasenko.

Nov. 1, 2016

Re: [Pharo-users] How does Boolean ifTrue work?

by Esteban A. Maringolo

2016-11-01 12:39 GMT-03:00 Joachim Tuchel <jtuchel(a)objektfabrik.de>: > I know. That's exactly the reason why I never use isEmptyOrNil > > Fun aside: how often do we need to check if some code returns nil or an empty collection. My question was aimed at exactly this: in practice ifEmptyOrNil: would probably be even more frequently needed than ifEmpty:. Otherwise, the beautiful convenience method has to be guarded by a nil test.... so we end up writing lots of methods, and not all of them seem to be universal enough to be part of the base image, imo. To start with <http://wiki.c2.com/?NullConsideredHarmful>, and then... the best way to avoid testing for nil, is to not use it at all! Wherever possible a Null Object (as in <http://wiki.c2.com/?NullObject>) is a great replacement. It is, using a domain specific UndefinedObject instead of the default nil. Regards, Esteban A. Maringolo

Nov. 1, 2016

Re: [Pharo-users] How does Boolean ifTrue work?

by phil＠highoctane.be

Hey Igor is around \o/ BTW using size = 0 triggers a code critic telling you to use isEmpty. Maybe there is a rule of isEmpty ifTrue: :-) I think that there could be a lot of convenience methods in the base image. They can be in an extension protocol, no issue. STON and gt have a ton of these. In the base image. About beginners, well: have a look in some Zinc code and learn a truckload of tricks. Like inject: somePath into: ... etc. And when puzzled, Halt now and debug or inspect it go a long way in figuring things out. As long as the method is intention revealing, what is the issue? At the risk of some flames, Pharo isn't bound to some Smalltalk compatibility. And that is what is cool about it. We chose another path now we have to go our way of else. Building on a great foundation is nice. But that doesn't equate to following the Smalltalk canon IMHO. And now 64 bits becoming real with a nice FFI and pinned objects... that is going to bring in a lot of non smalltalk stuff for sure. Phil Le 1 nov. 2016 15:14, "Igor Stasenko" <siguctua(a)gmail.com> a Ã©crit : > > > On 1 November 2016 at 11:31, jtuchel(a)objektfabrik.de < > jtuchel(a)objektfabrik.de> wrote: > >> Phil, >> >> >> I see your point but disagree. >> I don't use Pharo regularly, so I cannot currently check if the >> implementation around this emptiness check is complete. >> >> With complete I mean that following your logic, theere should be at least >> implementations of >> >> ifEmpty: >> ifNotEmpty: >> ifEmpty:ifNotEmpty: >> ifEmptyOrNil: >> ifEmptyOrNil:otherwise: >> > > why pollution? > it just convenience method. mind you, that #isEmpty is also convenience > method, without it you would do it like: > > myArray size isZero ifTrue: [] > of wait.. #isZero also convenience method... so if you elitist then you > have to write it like that: > > myArray size = 0 ifTrue: [] > > And that , to my opinion, adds even more pollution to the user code, > because first, it is longer, and second > #ifEmpty: much better clarifies the intent of author, comparing to size = 0 > > >> I really have to check for the size of collections very often, and the >> size of 1 is a very frequent case. So why not add: >> >> ifExactlyOne: >> ifSizeIs:do: >> ifSizeIsGreaterThan:do:otherwiseDo: >> >> You get the picture. I strongly believe this leads to pollution and ends >> up in a mess. >> We could save so much typing and make our programs so much more readable >> if we only were a bit more creative, right? ;-) >> A DSL is another story, though. If you write a Library that makes >> handling Collections nicer, this is okay and the methods are good to exist >> in its context. But they shouldn't necessarily all be part of the base >> image. >> >> >> Don't get me wrong: if you and the Pharo community agree on lots of >> convenience methods, that is okay for me, and I find myself adding such >> methods to VA Smalltalk from time to time. I appreciate many of them being >> brought to VA ST in Grease. >> >> Sometimes, this is simply a question of taste, sometimes it saves typing, >> sometimes it helps to improve readability of code. >> >> But I wouldn't go so far to tell people they should better use such a >> method as a general advice. I would probably tell them: "look, here's a >> method I find much more elegant, you could *also* use that to save >> typing/increase readability". >> >> Just my 2 cents, and highly off topic ;-) >> >> Joachim >> >> >> >> >> Am 01.11.16 um 08:43 schrieb phil(a)highoctane.be: >> >> Because I grew tired of the isEmpty ifTrue: [ ] all over the place. >> And ifEmpty has the right semantics for my use cases (like assignment). >> >> I do not really care about portability, I am doing Pharo only. >> >> Phil >> >> On Mon, Oct 31, 2016 at 5:30 PM, jtuchel(a)objektfabrik.de < >> jtuchel(a)objektfabrik.de> wrote: >> >>> Am 31.10.16 um 15:59 schrieb phil(a)highoctane.be: >>> >>> but you should use myCollection ifEmpty: [ ... ] >>> >>> >>> interesting. Why do you think so? what if you wanted your code to be >>> portable across Smalltalk dialects? >>> >>> >>> >>>> >>>> >>>> >>> >>> >>> -- >>> ----------------------------------------------------------------------- >>> Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de <jtuchel(a)objektfabrik.de> >>> Fliederweg 1 http://www.objektfabrik.de >>> D-71640 Ludwigsburg http://joachimtuchel.wordpress.com >>> Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 >>> >>> >>> -- >> ----------------------------------------------------------------------- >> Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de <jtuchel(a)objektfabrik.de> >> Fliederweg 1 http://www.objektfabrik.de >> D-71640 Ludwigsburg http://joachimtuchel.wordpress.com >> Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 >> >> >> > > > -- > Best regards, > Igor Stasenko. >

Nov. 1, 2016

Keeping data with an application

by sergio ruiz

Hey, all.. One of the things that I find SUPER necessary when developing an app is to be able to grab data from somewhere else and quickly and easily work on it from my machine. For instance, when I get a bug report that smells funny, the first thing i sometimes do is run a script that grabs the production data, and populates my local database with that data. i am fleshing out a project that i would really like to use Teapot (REST) for. i could then write several front ends in whatever framework/language. I was thinking about using Voyager, but the problem is, the data is VERY relational (see below, if interested).. objects are linked to each other fairly tightly. I donât know if this would be the way to handle the data, as there would be lots of duplication using mongodb as a datastore. Of course, my first thought is Gemstones, but I donât know how to grab the production data and pull it into my local development system. Does anyone have any thoughts on this?Â For those curious about the data design, i am setting up a REST server for an collaborative internet radio applicationâ¦ - there would be a global pool of stations (just streaming urls with metadata, really) - each user can select from or contribute to the global pool - users can add tags to stations (or search through the global stations based on tags) - users can attach comments to stations not complex or intimidating at all, and super easy to model in smalltalk, but not sure about how to store data so that I can quickly grab production data and troubleshoot if if necessary. Thanks! ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Nov. 1, 2016

Re: [Pharo-users] How does Boolean ifTrue work?

by Joachim Tuchel

Am 01.11.2016 um 12:21 schrieb Esteban Lorenzano: > >> On 1 Nov 2016, at 11:39, jtuchel(a)objektfabrik.de >> <mailto:jtuchel@objektfabrik.de> wrote: >> >> are they also implemented in UndefinedObject? > > no, because empty != nil I know. That's exactly the reason why I never use isEmptyOrNil ð Fun aside: how often do we need to check if some code returns nil or an empty collection. My question was aimed at exactly this: in practice ifEmptyOrNil: would probably be even more frequently needed than ifEmpty:. Otherwise, the beautiful convenience method has to be guarded by a nil test.... so we end up writing lots of methods, and not all of them seem to be universal enough to be part of the base image, imo. Joachim > > Esteban >

Nov. 1, 2016

Re: [Pharo-users] How does Boolean ifTrue work?

by Igor Stasenko

On 1 November 2016 at 11:31, jtuchel(a)objektfabrik.de < jtuchel(a)objektfabrik.de> wrote: > Phil, > > > I see your point but disagree. > I don't use Pharo regularly, so I cannot currently check if the > implementation around this emptiness check is complete. > > With complete I mean that following your logic, theere should be at least > implementations of > > ifEmpty: > ifNotEmpty: > ifEmpty:ifNotEmpty: > ifEmptyOrNil: > ifEmptyOrNil:otherwise: > why pollution? it just convenience method. mind you, that #isEmpty is also convenience method, without it you would do it like: myArray size isZero ifTrue: [] of wait.. #isZero also convenience method... so if you elitist then you have to write it like that: myArray size = 0 ifTrue: [] And that , to my opinion, adds even more pollution to the user code, because first, it is longer, and second #ifEmpty: much better clarifies the intent of author, comparing to size = 0 > I really have to check for the size of collections very often, and the > size of 1 is a very frequent case. So why not add: > > ifExactlyOne: > ifSizeIs:do: > ifSizeIsGreaterThan:do:otherwiseDo: > > You get the picture. I strongly believe this leads to pollution and ends > up in a mess. > We could save so much typing and make our programs so much more readable > if we only were a bit more creative, right? ;-) > A DSL is another story, though. If you write a Library that makes handling > Collections nicer, this is okay and the methods are good to exist in its > context. But they shouldn't necessarily all be part of the base image. > > > Don't get me wrong: if you and the Pharo community agree on lots of > convenience methods, that is okay for me, and I find myself adding such > methods to VA Smalltalk from time to time. I appreciate many of them being > brought to VA ST in Grease. > > Sometimes, this is simply a question of taste, sometimes it saves typing, > sometimes it helps to improve readability of code. > > But I wouldn't go so far to tell people they should better use such a > method as a general advice. I would probably tell them: "look, here's a > method I find much more elegant, you could *also* use that to save > typing/increase readability". > > Just my 2 cents, and highly off topic ;-) > > Joachim > > > > > Am 01.11.16 um 08:43 schrieb phil(a)highoctane.be: > > Because I grew tired of the isEmpty ifTrue: [ ] all over the place. > And ifEmpty has the right semantics for my use cases (like assignment). > > I do not really care about portability, I am doing Pharo only. > > Phil > > On Mon, Oct 31, 2016 at 5:30 PM, jtuchel(a)objektfabrik.de < > jtuchel(a)objektfabrik.de> wrote: > >> Am 31.10.16 um 15:59 schrieb phil(a)highoctane.be: >> >> but you should use myCollection ifEmpty: [ ... ] >> >> >> interesting. Why do you think so? what if you wanted your code to be >> portable across Smalltalk dialects? >> >> >> >>> >>> >>> >> >> >> -- >> ----------------------------------------------------------------------- >> Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de <jtuchel(a)objektfabrik.de> >> Fliederweg 1 http://www.objektfabrik.de >> D-71640 Ludwigsburg http://joachimtuchel.wordpress.com >> Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 >> >> >> -- > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de <jtuchel(a)objektfabrik.de> > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > > > -- Best regards, Igor Stasenko.

Nov. 1, 2016

Re: [Pharo-users] [ANN] Pharo By Example 5.0

by Dimitris Chloupis

No I don't unless it was part of the commits then is in git history and everyone who has cloned the repo has it. On Tue, 1 Nov 2016 at 15:51, stepharo <stepharo(a)free.fr> wrote: > I would like to know if you have this file on your HD. > > Else I will remove the reference to it. > > Le 30/10/16 Ã 22:41, Dimitris Chloupis a Ã©crit : > > are you asking me a question or request ? > > On Sun, Oct 30, 2016 at 11:39 PM stepharo <stepharo(a)free.fr> wrote: > > I'm looking for the > > figures/workspaceInspector.png > > Because I pulled and I cannot latex anymore. > > I'm working on the web site: http://books.pharo.org to get > > all the book pdfs in a well defined place (and all the rest). > > all the pointer to git hub > > all the pointer to the jenkins server. > > Stef > > Le 29/10/16 Ã 20:45, Dimitris Chloupis a Ã©crit : > > I forgot to add that the final render of the book cover can be found here > > > https://gitlab.com/Kilon/pbe5-cover/raw/master/Pharo%20demo/renders/render-… > > have fun :) > > On Sat, Oct 29, 2016 at 9:38 PM Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > As promised I released PBE5.0 just now, which basically puts a tag to our > github repository to mark the beginning of version 5 and also provided a > release in a fork of separate downloads for the book and the repository > itself which anything that is required to build the book. > > If you want just to read , downloading the pdf is enough. You can get the > release from here > > > https://github.com/SquareBracketAssociates/UpdatedPharoByExample/releases/t… > > Unfortunately I was not able to port the Reflection chapter , it needs a > ton of work , probably a complete rewrite but since its a late chapter and > we already have achieved a 80% updating I think it was the right time now > that pharo 7 is starting developing . > > Still till PBE6.0 we have a long way to go but I think we can get there > far easier than we got from PBE1.4 to PBE5.0. > > The rest of the details are in the link. > > Salute to fellow Guardians of the Light :) > > > >

Nov. 1, 2016

Re: [Pharo-users] [ANN] Pharo By Example 5.0

by stepharo

I would like to know if you have this file on your HD. Else I will remove the reference to it. Le 30/10/16 Ã 22:41, Dimitris Chloupis a Ã©crit : > are you asking me a question or request ? > > On Sun, Oct 30, 2016 at 11:39 PM stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > I'm looking for the > > figures/workspaceInspector.png > > Because I pulled and I cannot latex anymore. > > I'm working on the web site: http://books.pharo.org to get > > all the book pdfs in a well defined place (and all the rest). > > all the pointer to git hub > > all the pointer to the jenkins server. > > Stef > > > Le 29/10/16 Ã 20:45, Dimitris Chloupis a Ã©crit : >> I forgot to add that the final render of the book cover can be >> found here >> >> https://gitlab.com/Kilon/pbe5-cover/raw/master/Pharo%20demo/renders/render-… >> >> have fun :) >> >> On Sat, Oct 29, 2016 at 9:38 PM Dimitris Chloupis >> <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: >> >> As promised I released PBE5.0 just now, which basically puts >> a tag to our github repository to mark the beginning of >> version 5 and also provided a release in a fork of separate >> downloads for the book and the repository itself which >> anything that is required to build the book. >> >> If you want just to read , downloading the pdf is enough. You >> can get the release from here >> >> https://github.com/SquareBracketAssociates/UpdatedPharoByExample/releases/t… >> >> Unfortunately I was not able to port the Reflection chapter , >> it needs a ton of work , probably a complete rewrite but >> since its a late chapter and we already have achieved a 80% >> updating I think it was the right time now that pharo 7 is >> starting developing . >> >> Still till PBE6.0 we have a long way to go but I think we can >> get there far easier than we got from PBE1.4 to PBE5.0. >> >> The rest of the details are in the link. >> >> Salute to fellow Guardians of the Light :) >> >

Nov. 1, 2016

Re: [Pharo-users] Image freezes on Linux if it was previously saved on Windows

by Sean Glazier

did you get a fix for this? I am seeing this in pharo 5 image and I have not seen a fix yet -- View this message in context: http://forum.world.st/Image-freezes-on-Linux-if-it-was-previously-saved-on-… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 1, 2016