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

Re: [Pharo-dev] Roassal 3D empty windows

by Nicolai Hess

2014-05-12 0:25 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Hi Nicolai, > > Thanks for coming back to us. Your patience is crucial for us :-) > > > Again, someone can tell me where (OS, graphic-card) Roassal 3D runs out > of the box? > > I have just taken a Moose image, loading Roassal3d using the Configuration > browser. I then manually updated the NBOpenGL by hand (I have produced a > new configuration but I do not have the right to write in the repository). > > > And even now, that I solved this issue and all(many) Roassal examples > are working, > > The R 3D IDE still only shows a black screen. And I still don't know > what this is supposed > > to be, any tutorial screenshot or video, showing what R3D IDE is? > > R3D IDE is just a small and quick experiment. Nothing fancy behind (else > we would have advertise it :-) > You can use it the following: > - Open the Roassal3D IDE > - Open a System browser and compile method methods, create classes > > You should see some cubes in the IDE. Iâve just realized that moving from > Roassal to Roassal2 has left some problems. I am working on them right nowâ¦ > > Again, thanks for keeping trying R3D. > > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > Thank you Alexandre, just one question, what system do you use (OS/Grahics). I find it strange that I am the only one with this issue on Roassal resp. NBOpenGL (I use Windows 7 with /AMD Graphics I tried a Intel graphics card as well but that one does not support multisample framebuffer)

May 12, 2014

Re: [Pharo-dev] [squeak-dev] last block arg as implicit return value?

by Nicolas Cellier

2014-05-12 20:16 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > It seems that in Pharo 3 > > [:a :b|] value: #first value: #last > > answers nil whichever compiler you use (Opal or the old one). > > > Yes, I recognize my fix with different stamps in old Compiler... No miracle, https://code.google.com/p/pharo/issues/detail?id=1614, points to it Eliot's fix is much simpler. > 2014-05-12 19:17 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > >> >> >> >> On Mon, May 12, 2014 at 10:05 AM, Nicolas Cellier < >> nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >>> I think I remember it was either the first or last parameter that was >>> returned in old implementation >>> >> >> the last. ([:a :b|] value: #first value: #last) == #last >> >> >>> >>> It's a known problem: http://bugs.squeak.org/view.php?id=5793 >>> >>> but I would have thought that this was fixed with Eliot's closure... >>> >> >> I kept the old semantics, trying to rock the boat as little as possible. >> I just checked the draft standard. The end of 3.4.4 "blocks" reads >> >> "If a block has no <block body> or no <statements> in its <block body> >> then the value of the block is undefined." >> I've found the returning the last value bizarre for a while. If others >> feel strongly we could fix it for 4.6/5.0. But I'd want agreement with >> Pharo. Marcus what does Opal do with: >> >> [:a :b|] value: #first value: #last >> >> ? >> >> Squeak & VW answer #last. >> >> >>> >>> >>> 2014-05-12 17:58 GMT+02:00 blake <dsblakewatson(a)gmail.com>: >>> >>> >> | myBlock | >>>> >> myBlock := [ : arg1 : arg2 | ]. >>>> >> myBlock value: 'hello' value: 'there' >>>> >>>> nil >>>> >>>> Because the block isn't returning a value and the last line is calling >>>> the block. >>>> >>>> >>>> >>>> >>> >>> >>> >>> >> >> >> -- >> best, >> Eliot >> > >

May 12, 2014

Re: [Pharo-dev] [squeak-dev] last block arg as implicit return value?

by ClÃ©ment Bera

It seems that in Pharo 3 [:a :b|] value: #first value: #last answers nil whichever compiler you use (Opal or the old one). 2014-05-12 19:17 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > > > > On Mon, May 12, 2014 at 10:05 AM, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > >> I think I remember it was either the first or last parameter that was >> returned in old implementation >> > > the last. ([:a :b|] value: #first value: #last) == #last > > >> >> It's a known problem: http://bugs.squeak.org/view.php?id=5793 >> >> but I would have thought that this was fixed with Eliot's closure... >> > > I kept the old semantics, trying to rock the boat as little as possible. > I just checked the draft standard. The end of 3.4.4 "blocks" reads > > "If a block has no <block body> or no <statements> in its <block body> > then the value of the block is undefined." > I've found the returning the last value bizarre for a while. If others > feel strongly we could fix it for 4.6/5.0. But I'd want agreement with > Pharo. Marcus what does Opal do with: > > [:a :b|] value: #first value: #last > > ? > > Squeak & VW answer #last. > > >> >> >> 2014-05-12 17:58 GMT+02:00 blake <dsblakewatson(a)gmail.com>: >> >> >> | myBlock | >>> >> myBlock := [ : arg1 : arg2 | ]. >>> >> myBlock value: 'hello' value: 'there' >>> >>> nil >>> >>> Because the block isn't returning a value and the last line is calling >>> the block. >>> >>> >>> >>> >> >> >> >> > > > -- > best, > Eliot >

May 12, 2014

Re: [Pharo-dev] [squeak-dev] last block arg as implicit return value?

by Chris Muller

> just checked the draft standard. The end of 3.4.4 "blocks" reads > > "If a block has no <block body> or no <statements> in its <block body> then > the value of the block is undefined." Heh, which is somewhat ambiguous coming from the same book that introduces us to UndefinedObject...

May 12, 2014

Re: [Pharo-dev] [squeak-dev] last block arg as implicit return value?

by Eliot Miranda

On Mon, May 12, 2014 at 10:05 AM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > I think I remember it was either the first or last parameter that was > returned in old implementation > the last. ([:a :b|] value: #first value: #last) == #last > > It's a known problem: http://bugs.squeak.org/view.php?id=5793 > > but I would have thought that this was fixed with Eliot's closure... > I kept the old semantics, trying to rock the boat as little as possible. I just checked the draft standard. The end of 3.4.4 "blocks" reads "If a block has no <block body> or no <statements> in its <block body> then the value of the block is undefined." I've found the returning the last value bizarre for a while. If others feel strongly we could fix it for 4.6/5.0. But I'd want agreement with Pharo. Marcus what does Opal do with: [:a :b|] value: #first value: #last ? Squeak & VW answer #last. > > > 2014-05-12 17:58 GMT+02:00 blake <dsblakewatson(a)gmail.com>: > > >> | myBlock | >> >> myBlock := [ : arg1 : arg2 | ]. >> >> myBlock value: 'hello' value: 'there' >> >> nil >> >> Because the block isn't returning a value and the last line is calling >> the block. >> >> >> >> > > > > -- best, Eliot

May 12, 2014

Re: [Pharo-dev] Pillar - bold quote marks versus OSX TextEdit

by Yuriy Tymchuk

Another question is: are quotes the appropriate syntax? :) uko On 12 May 2014, at 18:10, Ben Coman <btc(a)openinworld.com> wrote: > > Just a note it might be good to add to Pillar documentation [1] which says... you can make something ""bold"" like that. But I was having trouble getting this to work since the quote marks would just appear in the generated PDF. I found the answer by copy pasting the quote mark from [1] into the Mixed input field of [2] and pressing convert tells me this is UTF-16 code 22. If I type the quote mark " directly into that field, then I get the same result. However if I type the quote mark " into TextMate, then copy that character into [2], it tells me its UTF-16 201C!!! what-the! > > So I found out how to disable Smart Quotes at [3]. > > [1] github.com/pillar-markup/pillar-documentation > [2] rishida.net/tools/conversion > [3] devin.la/blog/disable-smart-quotes-osx-mavericks > > cheers -ben >

May 12, 2014

Pillar - bold quote marks versus OSX TextEdit

by Ben Coman

Just a note it might be good to add to Pillar documentation [1] which says... you can make something ""bold"" like that. But I was having trouble getting this to work since the quote marks would just appear in the generated PDF. I found the answer by copy pasting the quote mark from [1] into the Mixed input field of [2] and pressing convert tells me this is UTF-16 code 22. If I type the quote mark " directly into that field, then I get the same result. However if I type the quote mark " into TextMate, then copy that character into [2], it tells me its UTF-16 201C!!! what-the! So I found out how to disable Smart Quotes at [3]. [1] github.com/pillar-markup/pillar-documentation [2] rishida.net/tools/conversion [3] devin.la/blog/disable-smart-quotes-osx-mavericks cheers -ben

May 12, 2014

Re: [Pharo-dev] Improving Pharo By Example

by kilon alios

ok people I think I made pillar angry :D I dont why, maybe I said something I should not have said, maybe I pushed her too much , maybe I smell too bad but since yesterday she compiles but refuses to cooperate with me. In detail each time I try to use pillar syntax lets say "!! Finding classes" instead of seeing the syntax and compile to something like "1.2 Finding classes" it compiles it as it is "!! Finding classes" , it does the same thing with other pillar syntax too. I tried to redownload the repo , and reinstall pier and recompile from scratch again it does the same things. You can replicate this by cloning the UpdatedPharoByExample github repo and just go to PharoTour.pier and add "!! Something something" and compile. The problem is evident in both the pdfs and hmtl outputs. Please help me make pillar friendly again, tell her I apologize and I lover her very much :) On Sat, May 10, 2014 at 7:09 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > Thanks Damien and Yuriy > > > On Sat, May 10, 2014 at 6:51 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com>wrote: > >> >> On 10 May 2014, at 17:01, kilon alios <kilon.alios(a)gmail.com> wrote: >> >> I found a bug in Pillar syntax >> >> when I type 3 + 4 , it seems like it takes + as part of the pillar >> syntax and uses latex syntax and when it tries to generate the pdf it fails >> so I am forced now to type it as raw text like this : {{{3+4}}} >> >> >> Itâs not a bug, itâs a feature :). Iâd suggest you to use something like >> ==inline code== for wrapping of ââitalicâ'. >> >> >> also I would like the ability to have a dark background for text like we >> do with smalltalk syntax . >> >> >> I donât really understand what you need. If you need to style the result, >> it should be done outside of pillar. >> >> >> >> Pharo Tour chapters proceeds well, I compile to both latex html and pdf , >> I see no problems so far with my text, I copy my text directly from the >> latex files of the original PBE in github. >> >> >> I also improved the Readme. >> >> >> On Thu, May 8, 2014 at 9:16 AM, stepharo <stepharo(a)free.fr> wrote: >> >>> >>> >>> I also added Chapter 1 - Quick Tour in Pharo. Just the first part , >>> the chapter is of course still a WIP. >>> >>> I am not so sure what you mean about automated tests, are they for the >>> example code ? >>> >>> >>> >>> if you see in the tex when we have example we also have a tag that >>> indicates that the code can be extracted >>> and run. I do not remember but oscar did a script and we where able to >>> automatically verify that all the simple examples were correctly working >>> with a version of Pharo. >>> >>> Now in Pillar we should introduce the notion of tag to support at the >>> word level. >>> - index >>> - comment >>> - citation >>> >>> >>> >>> I am all for automation. >>> >>> >>> On Mon, May 5, 2014 at 11:08 PM, stepharo <stepharo(a)free.fr> wrote: >>> >>>> This is really cool that people want to update the Pharo by Example >>>> book. >>>> This is a really an important task and it will have a real impact. >>>> You can also reduce the number of screenshots or point related to the >>>> interaction. >>>> >>>> What would be good is to make the automated tests working again because >>>> we could spot >>>> if we got some regressions. >>>> >>>> Stef >>>> >>>> >>>> How I can help improve Pharo by Example , add chapters and update >>>>> current ones for Pharo 3 ? >>>>> >>>>> What is the process ? >>>>> >>>> >>>> >>>> >>> >>> >> >> >

May 12, 2014

Re: [Pharo-dev] Github & Pharo.org

by kilon alios

Hey Esteban , I see you link my video tutorials. I recommend instead to link to my video playlist called "Pharo Video Tutorial" which can be found here -> https://www.youtube.com/watch?v=Ol5ivaEATLQ&list=PLqbtQ7OkSta0ULYAd7Qdxof85… In this playlist I have uploaded, I am uploading and will upload video tutorials only for the basics of Pharo (similar to Pharo By Example) and then I will create other playlists for important libraries , spec, morphic etc. On Mon, May 12, 2014 at 3:18 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > I added it at download page: http://pharo.org/download > now we have to improve all that infrastructure :) > > Esteban > > On 03 May 2014, at 19:06, phil(a)highoctane.be wrote: > > Am I blind or am I having a hard time spotting our stuff on GitHub from > Pharo.org as well as some other properties that help us be visible? > > Meaning: > > https://github.com/orgs/pharo-project/ > > https://github.com/SquareBracketAssociates > > are very important places and aren't mentioned much. > > As are: https://github.com/tide-framework if someone wants to use Marina > so use the Pharo power... > > Maybe can we add these and > > http://en.wikipedia.org/wiki/Pharo > > as well (as we bothered updating the page...) > > Also, in http://pharo.org/get-involved we sent people directly to the > Fogbugz thing. > > We should mention this Penelope monkey as well: http://bugs.pharo.org/ > > Also, in documentation, people are doing webapps, so we need to add > "Dynamic Web Development with Seaside" to http://pharo.org/documentation > > http://book.seaside.st/book > > And, we also must also add this gorgeous > > http://spec.st/ > > and Sebastian's Mapless supernice site as well. > > > I do not have access to the CMS, so please some kind soul, do it :-) [or > tell me how] > > Phil > > >

May 12, 2014

Re: [Pharo-dev] Github & Pharo.org

by Esteban Lorenzano

I added it at download page: http://pharo.org/download now we have to improve all that infrastructure :) Esteban On 03 May 2014, at 19:06, phil(a)highoctane.be wrote: > Am I blind or am I having a hard time spotting our stuff on GitHub from Pharo.org as well as some other properties that help us be visible? > > Meaning: > > https://github.com/orgs/pharo-project/ > > https://github.com/SquareBracketAssociates > > are very important places and aren't mentioned much. > > As are: https://github.com/tide-framework if someone wants to use Marina so use the Pharo power... > > Maybe can we add these and > > http://en.wikipedia.org/wiki/Pharo > > as well (as we bothered updating the page...) > > Also, in http://pharo.org/get-involved we sent people directly to the Fogbugz thing. > > We should mention this Penelope monkey as well: http://bugs.pharo.org/ > > Also, in documentation, people are doing webapps, so we need to add "Dynamic Web Development with Seaside" to http://pharo.org/documentation > > http://book.seaside.st/book > > And, we also must also add this gorgeous > > http://spec.st/ > > and Sebastian's Mapless supernice site as well. > > > I do not have access to the CMS, so please some kind soul, do it :-) [or tell me how] > > Phil

May 12, 2014