- Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pharo-dev] Pharo by Example 50 released!

by Dimitris Chloupis

Both PDF and HTML version are built automagically each time we commit to the github repository so you do not need to way, just tell people to always visit to be kept up to date PDF version https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample… HTML version https://ci.inria.fr/pharo-contribution/job/UpdatedPharoByExample/lastSucces… each folder contains both pdf and html version of each chapter, enjoy :) On Sun, Jan 22, 2017 at 6:11 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Great work, can't wait for the HTML version (to link to when answering > questions). > > Thank you ! > > > On 22 Jan 2017, at 16:53, stepharong <stepharong(a)free.fr> wrote: > > > > > https://pharoweekly.wordpress.com/2017/01/22/pharo-by-example-50-released/ > > > > Super special thanks to Nicolai Hess that pushed me to do the last steps > to release. > > Thanks Nicolai your steady commits pushed me! > > > > Stef > > > > >

Jan. 23, 2017

Re: [Pharo-users] [Pharo-dev] Pharo by Example 50 released!

by Tudor Girba

Great. This is a great entry point into Pharo. Please publicize it as widely as you can. Here is the announcement tweet that you can retweet: https://twitter.com/stephaneducasse/status/823195882770284545 Cheers, Doru > On Jan 22, 2017, at 4:53 PM, stepharong <stepharong(a)free.fr> wrote: > > https://pharoweekly.wordpress.com/2017/01/22/pharo-by-example-50-released/ > > Super special thanks to Nicolai Hess that pushed me to do the last steps to release. > Thanks Nicolai your steady commits pushed me! > > Stef > -- www.tudorgirba.com www.feenk.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

Jan. 23, 2017

Re: [Pharo-users] [Pharo-dev] Pharo by Example 50 released!

by Guillermo Polito

Yeh, thanks to all who made an effort :) On Sun, Jan 22, 2017 at 5:10 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Great work, can't wait for the HTML version (to link to when answering > questions). > > Thank you ! > > > On 22 Jan 2017, at 16:53, stepharong <stepharong(a)free.fr> wrote: > > > > https://pharoweekly.wordpress.com/2017/01/22/pharo-by- > example-50-released/ > > > > Super special thanks to Nicolai Hess that pushed me to do the last steps > to release. > > Thanks Nicolai your steady commits pushed me! > > > > Stef > > > > >

Jan. 23, 2017

Re: [Pharo-users] Difficulties updating a file directory

by Ben Coman

On Mon, Jan 23, 2017 at 9:26 AM, Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com> wrote: > Hi, > > I'm having problems understanding how #chooseDirectory: works. When I run > this code: > > GrafoscopioDocumentation current localPlace: (UIManager default > chooseDirectory: 'Path to the documents Folder') > > from a playground and choose a folder in my home directory, results in > localPlace containing a FileReference to '/home/offray/Documents/Grafoscopio', > which is what I expect. But if I put a similar code here: > > """ > > GrafoscopioDocumentation >> updateDocsPlace > > self current localPlace: (UIManager default chooseDirectory: 'Path to > the documentation folder') > > """ > > and choose the same folder, I got a relative FileReference to > 'Grafoscopio', instead of the one to the full path, that doesn't point to > anything existing in my system. > > What I'm missing here? > > > Totally wild speculation (I'm not very familiar with it and I'm away where I can check) it could be that #chooseDirectory: or something it calls raises a notification that is handled by the outer UI code, which is not done when executed from Playground. Try a halt before each UIManager and check if the execution paths are different. cheers -ben

Jan. 23, 2017

Difficulties updating a file directory

by Offray Vladimir Luna CÃ¡rdenas

Hi, I'm having problems understanding how #chooseDirectory: works. When I run this code: GrafoscopioDocumentation current localPlace: (UIManager default chooseDirectory: 'Path to the documents Folder') from a playground and choose a folder in my home directory, results in localPlace containing a FileReference to '/home/offray/Documents/Grafoscopio', which is what I expect. But if I put a similar code here: """ GrafoscopioDocumentation >> updateDocsPlace self current localPlace: (UIManager default chooseDirectory: 'Path to the documentation folder') """ and choose the same folder, I got a relative FileReference to 'Grafoscopio', instead of the one to the full path, that doesn't point to anything existing in my system. What I'm missing here? Thanks, Offray

Jan. 23, 2017

Re: [Pharo-users] DNU on materializing a fueled out exception

by Ben Coman

You needed to change the status from 'Work Needed' to 'Resolved (Fix Review Needed)', which I see Andrei has done and the monkey has run. cheers -ben On Mon, Jan 23, 2017 at 1:15 AM, Holger Freyther <holger(a)freyther.de> wrote: > > > On 28 Dec 2016, at 13:44, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > > I am not asking someone to fix what I think is important but I am still > struggling to grasp the process of getting a bugfix into Pharo5. > > > > > > But.... are you sure there will be a bugfix release of 5.0? Because I am > not sure about that. > > I have committed a slice into the Pharo5 inbox but I don't see the > monkey(?) testing the change or the slice being mentioned in the ticket. Do > I have to do anything extra? > > thanks > > holger > > Links to tickets, the slice and the individual monticello commits > > https://pharo.fogbugz.com/f/cases/19477/Fuel-out-Stack- > uses-old-debugger-API-in-Pharo-5 > http://smalltalkhub.com/#!/~Pharo/Pharo50Inbox/versions/ > SLICE-Issue-19477-Fuel-out-Stack-uses-old-debugger-API-in-Pharo-5- > HolgerHansPeterFreyther.1 > http://smalltalkhub.com/#!/~Pharo/Pharo50Inbox/versions/FuelPlatform- > HolgerHansPeterFreyther.63 > http://smalltalkhub.com/#!/~Pharo/Pharo50Inbox/versions/ > FuelTools-Debugger-HolgerHansPeterFreyther.11 >

Jan. 23, 2017

Re: [Pharo-users] DNU on materializing a fueled out exception

by Holger Freyther

> On 28 Dec 2016, at 13:44, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > I am not asking someone to fix what I think is important but I am still struggling to grasp the process of getting a bugfix into Pharo5. > > > But.... are you sure there will be a bugfix release of 5.0? Because I am not sure about that. I have committed a slice into the Pharo5 inbox but I don't see the monkey(?) testing the change or the slice being mentioned in the ticket. Do I have to do anything extra? thanks holger Links to tickets, the slice and the individual monticello commits https://pharo.fogbugz.com/f/cases/19477/Fuel-out-Stack-uses-old-debugger-AP… http://smalltalkhub.com/#!/~Pharo/Pharo50Inbox/versions/SLICE-Issue-19477-F… http://smalltalkhub.com/#!/~Pharo/Pharo50Inbox/versions/FuelPlatform-Holger… http://smalltalkhub.com/#!/~Pharo/Pharo50Inbox/versions/FuelTools-Debugger-…

Jan. 22, 2017

Re: [Pharo-users] [Pharo-dev] Pharo by Example 50 released!

by Sven Van Caekenberghe

Great work, can't wait for the HTML version (to link to when answering questions). Thank you ! > On 22 Jan 2017, at 16:53, stepharong <stepharong(a)free.fr> wrote: > > https://pharoweekly.wordpress.com/2017/01/22/pharo-by-example-50-released/ > > Super special thanks to Nicolai Hess that pushed me to do the last steps to release. > Thanks Nicolai your steady commits pushed me! > > Stef >

Jan. 22, 2017

Re: [Pharo-users] Xtreams docs (previously: Tools for easy subtext extraction from text)

by stepharong

Hi Peter > Is there a build for the PharoLimbo, or do I have to compile it myself? No and it is incomplete. I should convert the web site to a chapter. But let us see it from time to time I 'm tired to do such kind of boring job. I will send you the pdf I have

Jan. 22, 2017

Re: [Pharo-users] Tools for easy subtext extraction from text

by stepharong

Guille I think that we should also have a look at Xtreams and see if there is not a core inside. What I think that is that current stream implementation is quite terrible. Stef

Jan. 22, 2017