- Pharo-users - lists.pharo.org

Re: [Pharo-users] What can we look forward to in 2017?

by Ben Coman

On Wed, Dec 14, 2016 at 5:15 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > On Tue, Dec 13, 2016 at 6:15 PM horrido <horrido.hobbies(a)gmail.com> wrote: > >> Fellow Pharoers: What is the most exciting development in 2017 to look >> forward to? I'm asking for things to put into the end-of-year post in my >> "Make Smalltalk Great Again!" campaign. Thanks. >> > > I would not call it "most exciting development" for anyone but is > definitely for me > > Generally the plans for my project Ephestos for 2017 are > > 1) To create an Unreal API for Pharo > 2) To create a Blender API for Pharo > 3) To create a Supercollider API for Pharo > > Unreal is the most powerful game/graphics engine. > Blender is the most powerful 3d editor. > Supercollider is the most powerful live coding music and audio synthesis > platform. > > I have developed the foundation for all three , the only thing remaining > know is to wrap their APIs for Pharo. > > So by end of 2017 Pharo will have received a massive boost to its 2d and > 3d graphics capabilities and > music and audio synthesis capabilities. > I like your ambition and you seem to be having great fun, so good luck. cheers -ben > > Supercollider part is not a high priority goal as the other two, but I > think I can squeeze it through. > > Low priority goals and less exciting for me are > > 1) improvements to Nireas expanding its customisability, recreating the > GUI , improving the blue theme and offer multiple other themes too > 2) a tool that unifies workspace, system browser and inspector under one > roof. I have not tested yet grafoscopio in detail, so it may form the basis > for this tool > 3) further contributions to Pharo By Example and possibly other books > >

Dec. 14, 2016

Re: [Pharo-users] What can we look forward to in 2017?

by Dimitris Chloupis

On Tue, Dec 13, 2016 at 6:15 PM horrido <horrido.hobbies(a)gmail.com> wrote: > Fellow Pharoers: What is the most exciting development in 2017 to look > forward to? I'm asking for things to put into the end-of-year post in my > "Make Smalltalk Great Again!" campaign. Thanks. > I would not call it "most exciting development" for anyone but is definitely for me Generally the plans for my project Ephestos for 2017 are 1) To create an Unreal API for Pharo 2) To create a Blender API for Pharo 3) To create a Supercollider API for Pharo Unreal is the most powerful game/graphics engine. Blender is the most powerful 3d editor. Supercollider is the most powerful live coding music and audio synthesis platform. I have developed the foundation for all three , the only thing remaining know is to wrap their APIs for Pharo. So by end of 2017 Pharo will have received a massive boost to its 2d and 3d graphics capabilities and music and audio synthesis capabilities. Supercollider part is not a high priority goal as the other two, but I think I can squeeze it through. Low priority goals and less exciting for me are 1) improvements to Nireas expanding its customisability, recreating the GUI , improving the blue theme and offer multiple other themes too 2) a tool that unifies workspace, system browser and inspector under one roof. I have not tested yet grafoscopio in detail, so it may form the basis for this tool 3) further contributions to Pharo By Example and possibly other books

Dec. 14, 2016

Re: [Pharo-users] accessing local/instance variables with metalinks

by Yuriy Tymchuk

By the way, we need to add a rubric highlighting to the classes somehow :). Uko > On 12 Dec 2016, at 13:36, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hello, > > Not yet. It should be easy to add if we find a good API for itâ¦ > > I will work on it this week (I have blocked some time for RF related hacking). > > e.g I think we have to extend the syntax for reifications to use classes. > > something like: > > arguments: {RFTempReification named: #trachelCanvas}; > > The current symbols then would be the same as using > > RFReification named: #object > > But subclasses can be used directly and parametrized. > > Marcus > >> On 5 Dec 2016, at 20:42, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >> >> Hi, >> >> what is the best way to access variables from within a metalink? >> >> for example I have a message send `surface clear` and I want to change it to `surface clear: trachelCanvas color`. >> >> I can use #instVarNamed: >> >> ``` >> MetaLink new >> metaObject: [ :object | >> (object instVarNamed: #surface) clear: (object instVarNamed: #trachelCanvas) color. >> ]; >> selector: #value:; >> arguments: #(object); >> control: #instead. >> ``` >> >> but the above isn't exactly nice, plus it wouldn't work with temporary variables. >> >> Thanks, >> Peter >> > >

Dec. 14, 2016

Re: [Pharo-users] What can we look forward to in 2017?

by Stephane Ducasse

+1 On Tue, Dec 13, 2016 at 6:41 PM, Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com> wrote: > Hi, > > As an alternative to "most exciting developments for next year" I would > propose "Mapping the place that Smalltalk/Pharo has for you". For example, > if someone is interested in data driven storytelling, interactive > documentation, reproducible research, and/or data activism, I would think > that Grafoscopio[1] is a project to put into the radar. It's also a > showcase of both, other Pharo technologies (Roassal, GT-Tools, STON, > NeoJSON, WebBrowser, etc.) and, also, how Pharo ecosystem and community can > empower learners. > > [1] http://mutabit.com/grafoscopio/index.en.html > > Of course others have their own bets about their own projects and why > they're important and for who. > > So my approach would be to prepare kind of a short interview, with some > questions that Pharo users/developers could answer to tell the story of > their territory explorations on the map that Smalltalk/Pharo has for you. > > Cheers, > > Offray > > > > On 13/12/16 11:00, horrido wrote: > >> Fellow Pharoers: What is the most exciting development in 2017 to look >> forward to? I'm asking for things to put into the end-of-year post in my >> "Make Smalltalk Great Again!" campaign. Thanks. >> >> >> >> -- >> View this message in context: http://forum.world.st/What-can >> -we-look-forward-to-in-2017-tp4926791.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> >> > >

Dec. 14, 2016

Re: [Pharo-users] What can we look forward to in 2017?

by Ben Coman

On Wed, Dec 14, 2016 at 8:11 AM, horrido <horrido.hobbies(a)gmail.com> wrote: > Wow! These *are* exciting. Thanks! > > > Ben Coman wrote > > Pharo 6 release due April 2017. > > - 64-bit!!! > Actually to be specific, this is the 64-bit JIT'ed Cog VM, as distinct from the old 64-bit Interpreter VM [1] circa 2010 that I've seen people on discussion boards confuse. [1] http://www.squeakvm.org/squeak64/ cheers -ben > > - Sista - adaptive method inlining at the bytecode level > > > > https://clementbera.wordpress.com/2014/01/09/the-sista- > chronicles-i-an-introduction-to-adaptive-recompilation/ > > http://www.mirandabanda.org/cogblog/on-line-papers-and-presentations/ > > > > Pharo 7 > > - Iceberg UI interface to git > > > > http://www.esug.org/wiki/pier/Conferences/2016/Tuesday/1100-1130-Iceberg > > - Pharo workflow moving to git. > > > > http://forum.world.st/Notes-about-Pharo-6-release-and-new- > process-for-Pharo-7-td4920100.html > > > > > > cheers -ben > > > > > > -- > View this message in context: http://forum.world.st/What- > can-we-look-forward-to-in-2017-tp4926791p4926841.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Dec. 14, 2016

Re: [Pharo-users] What can we look forward to in 2017?

by horrido

Wow! These *are* exciting. Thanks! Ben Coman wrote > Pharo 6 release due April 2017. > - 64-bit!!! > - Sista - adaptive method inlining at the bytecode level > > https://clementbera.wordpress.com/2014/01/09/the-sista-chronicles-i-an-intr… > http://www.mirandabanda.org/cogblog/on-line-papers-and-presentations/ > > Pharo 7 > - Iceberg UI interface to git > > http://www.esug.org/wiki/pier/Conferences/2016/Tuesday/1100-1130-Iceberg > - Pharo workflow moving to git. > > http://forum.world.st/Notes-about-Pharo-6-release-and-new-process-for-Pharo… > > > cheers -ben -- View this message in context: http://forum.world.st/What-can-we-look-forward-to-in-2017-tp4926791p4926841… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Dec. 14, 2016

Re: [Pharo-users] Hash collision

by Andres Valloud

Oh, ok... then the failure code isn't doing what was intended :). On 12/13/16 15:16 , Martin McClure wrote: > On 12/13/2016 08:39 AM, Andres Valloud wrote: >> I would have expected the floats to be a byte object of size 8. Why is >> this conversion needed? Is somehow the primitive thinking the float has >> size 2? Or is the primitive hashing 32 bits at a time? The prim used >> to be a C version of the byte oriented 1644525 multiplicative hash, did >> this change? > > The float is not a byte object of size 8, it's a word object of size 2. > > When you feed it to #hashBytes:startingWith: the primitive fails. (I > didn't look at why -- maybe because it isn't a byte object?) > > The alternative Smalltalk code treats it like it was a byte object, even > though it's not. So it iterates through the two words, multiplying each > by 1664525, then keeping only the low-order 28 bits of the result. But > since each word is a full 32 bits, the high-order four bits of each > word, which include the sign bit, can never affect the hash. > > Regards, > > -Martin >

Dec. 14, 2016

Re: [Pharo-users] Hash collision

by Martin McClure

On 12/13/2016 08:39 AM, Andres Valloud wrote: > I would have expected the floats to be a byte object of size 8. Why is > this conversion needed? Is somehow the primitive thinking the float has > size 2? Or is the primitive hashing 32 bits at a time? The prim used > to be a C version of the byte oriented 1644525 multiplicative hash, did > this change? The float is not a byte object of size 8, it's a word object of size 2. When you feed it to #hashBytes:startingWith: the primitive fails. (I didn't look at why -- maybe because it isn't a byte object?) The alternative Smalltalk code treats it like it was a byte object, even though it's not. So it iterates through the two words, multiplying each by 1664525, then keeping only the low-order 28 bits of the result. But since each word is a full 32 bits, the high-order four bits of each word, which include the sign bit, can never affect the hash. Regards, -Martin

Dec. 14, 2016

Re: [Pharo-users] [Pharo-dev] The Iceberg TechTalk recording

by Dimitris Chloupis

you can add an annotation for the first 10 minutes that links directly to the time the techtalk actually starts you can also link to the precise time like this https://youtu.be/AuZAFfWS34w?t=598 you can get this link by pushing the playback cursor to the time you want to link and then right click and choose Copy URL at current time On Tue, Dec 13, 2016 at 11:57 PM Nicolas Passerini <npasserini(a)gmail.com> wrote: > Maybe we could try to edit the video? Is it possible? > > 2016-12-13 21:20 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > Ah, but you need to skip until minute 10 :P > > Esteban > > > On 13 Dec 2016, at 21:19, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > Hi, > > > > for those who couldnât join us, this is the recording: > > > > https://www.youtube.com/watch?v=AuZAFfWS34w > > > > I think it was a great talk :) > > > > cheers, > > Esteban > > >

Dec. 14, 2016

Re: [Pharo-users] The Iceberg TechTalk recording

by Nicolas Passerini

Maybe we could try to edit the video? Is it possible? 2016-12-13 21:20 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Ah, but you need to skip until minute 10 :P > > Esteban > > > On 13 Dec 2016, at 21:19, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > Hi, > > > > for those who couldnât join us, this is the recording: > > > > https://www.youtube.com/watch?v=AuZAFfWS34w > > > > I think it was a great talk :) > > > > cheers, > > Esteban > >

Dec. 13, 2016