December 2016 - Pharo-users

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

by Marcus Denker

Ah, yes. And context menusâ¦ > On 14 Dec 2016, at 10:46, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Ah, looks like I didnât read the topic correctlyâ¦ Iâd like to have styling for the class template, because it is a bit complicated to highlight variables. > > Uko > >> On 14 Dec 2016, at 12:44, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> There is a MetalinkIconStyler already. >> >> But I think that it is better to have stylers for the users of metalinks, e.g. there is a special >> styler for breakpoints. >> >> I see the general styler more as a debug tool (it is off by default). >> >> Marcus >>> On 14 Dec 2016, at 05:10, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>> >>> 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] accessing local/instance variables with metalinks

by Yuriy Tymchuk

Ah, looks like I didnât read the topic correctlyâ¦ Iâd like to have styling for the class template, because it is a bit complicated to highlight variables. Uko > On 14 Dec 2016, at 12:44, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > There is a MetalinkIconStyler already. > > But I think that it is better to have stylers for the users of metalinks, e.g. there is a special > styler for breakpoints. > > I see the general styler more as a debug tool (it is off by default). > > Marcus >> On 14 Dec 2016, at 05:10, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> 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 Dimitris Chloupis

Thank you Ben , but just to clarify those APIs will be partial and depend on the needs of a game I develop. Obviously it's unrealistic to wrap the entire Blender or Unreal API in a single year. Each one contains over ten thousands methods. Probably in a year I can do one hundred methods each maybe more again depending on the needs of the game. But I am looking into automatic wrapping like Igor did for NBOpenGL using header files so I won't need to do this manually which is both time consuming and boring. Documentation is also the same story, I won't be porting it to Pharo, again because I don't need to. That means the user will need to understand both APIs and know both Python and c++. So my "ambition" is far smaller than it may seem. In the end I am just one guy with limited time like most of you. On Wed, 14 Dec 2016 at 12:46, Ben Coman <btc(a)openinworld.com> wrote: > 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] accessing local/instance variables with metalinks

by Marcus Denker

There is a MetalinkIconStyler already. But I think that it is better to have stylers for the users of metalinks, e.g. there is a special styler for breakpoints. I see the general styler more as a debug tool (it is off by default). Marcus > On 14 Dec 2016, at 05:10, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > 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 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