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

[Pharo4] removing Breakpoints (old implementation)

by Marcus Denker

Hi, We will remove the old BreakPoint implementationâ¦ later we get new ones based on MetaLinks. https://pharo.fogbugz.com/f/cases/13621/remove-old-BreakPoints-for-now Marcus

July 21, 2014

Re: [Pharo-dev] 503 on pharo-contribution CI

by Marcus Denker

On 21 Jul 2014, at 12:46, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > pharo-contribution disappear again. > retartedâ¦ very strange. > On Fri, Jul 18, 2014 at 10:12 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> On 18 Jul 2014, at 10:04, Max Leske <maxleske(a)gmail.com> wrote: >> >>> Iâm getting a 503 when trying to access pharo-contribution CI. It was working until half an hour ago. Could someone take a look please? >>> >>> Cheers, >>> Max >> >> I have restarting it... > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ >

July 21, 2014

Re: [Pharo-dev] 503 on pharo-contribution CI

by Serge Stinckwich

pharo-contribution disappear again. On Fri, Jul 18, 2014 at 10:12 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 18 Jul 2014, at 10:04, Max Leske <maxleske(a)gmail.com> wrote: > >> Iâm getting a 503 when trying to access pharo-contribution CI. It was working until half an hour ago. Could someone take a look please? >> >> Cheers, >> Max > > I have restarting it... -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

July 21, 2014

Re: [Pharo-dev] [Pharo4] MetaLinks on Slots

by Norbert Hartl

I can just repeat myself. This is such a big impact and a huge step forward. Bravo! Sadly there is other work to do. Norbert Am 21.07.2014 um 11:28 schrieb Marcus Denker <marcus.denker(a)inria.fr>: > Hello, > > One of the questions with having meta objects for variables (Slots and Globals) is: For what is is good? > > Here is one exampleâ¦ in early stage but working. > > Imagine you want to âhook intoâ instance variable access. It can be done with e.g. bytecode manipulation, or > on the AST level. But that is far from nice. > > With the new first class variables, there is now a fun way to do it: MetaLinks. > > Make a class TT with an instance var âtâ and add an accessor. > > Now we can define a MetaLink: it describes a call to a meta object that we wan to do before, after or instead > of what our variable normally does. (default is #before): > > | link | > link := MetaLink new > metaObject: Halt; > selector: #now. > > This link says: âdo a Halt now before where I will get installedâ. > > To install the link, just get the Slot meta object and set it using #link: > > (TT slotNamed: #t) link: link. > > This sets the link by replacing the Slot with a LinkWrapper Slot, and then recompiles all using methods. > > Thus evaluating: > > TT new t > > will get you a #halt. > > Lots of things are not yet implemented (multiple links, uninstall, arguments,â¦) > but it starts to show how simple one can do quite powerful things. > > Marcus > > >

July 21, 2014

Re: [Pharo-dev] [Pharo4] MetaLinks on Slots

by Clara Allende

Super cool, and then we have to integrate with the metaLink based breakpoints (almost there), and we can start a party :D 2014-07-21 11:33 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Man, this is exciting! > > A strong reason to already switch to Pharo 4 :) > > Doru > > > On Mon, Jul 21, 2014 at 11:28 AM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> Hello, >> >> One of the questions with having meta objects for variables (Slots and >> Globals) is: For what is is good? >> >> Here is one exampleâ¦ in early stage but working. >> >> Imagine you want to âhook intoâ instance variable access. It can be done >> with e.g. bytecode manipulation, or >> on the AST level. But that is far from nice. >> >> With the new first class variables, there is now a fun way to do it: >> MetaLinks. >> >> Make a class TT with an instance var âtâ and add an accessor. >> >> Now we can define a MetaLink: it describes a call to a meta object that >> we wan to do before, after or instead >> of what our variable normally does. (default is #before): >> >> | link | >> link := MetaLink new >> metaObject: Halt; >> selector: #now. >> >> This link says: âdo a Halt now before where I will get installedâ. >> >> To install the link, just get the Slot meta object and set it using #link: >> >> (TT slotNamed: #t) link: link. >> >> This sets the link by replacing the Slot with a LinkWrapper Slot, and >> then recompiles all using methods. >> >> Thus evaluating: >> >> TT new t >> >> will get you a #halt. >> >> Lots of things are not yet implemented (multiple links, uninstall, >> arguments,â¦) >> but it starts to show how simple one can do quite powerful things. >> >> Marcus >> >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

July 21, 2014

Re: [Pharo-dev] [Pharo4] MetaLinks on Slots

by Tudor Girba

Man, this is exciting! A strong reason to already switch to Pharo 4 :) Doru On Mon, Jul 21, 2014 at 11:28 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hello, > > One of the questions with having meta objects for variables (Slots and > Globals) is: For what is is good? > > Here is one exampleâ¦ in early stage but working. > > Imagine you want to âhook intoâ instance variable access. It can be done > with e.g. bytecode manipulation, or > on the AST level. But that is far from nice. > > With the new first class variables, there is now a fun way to do it: > MetaLinks. > > Make a class TT with an instance var âtâ and add an accessor. > > Now we can define a MetaLink: it describes a call to a meta object that we > wan to do before, after or instead > of what our variable normally does. (default is #before): > > | link | > link := MetaLink new > metaObject: Halt; > selector: #now. > > This link says: âdo a Halt now before where I will get installedâ. > > To install the link, just get the Slot meta object and set it using #link: > > (TT slotNamed: #t) link: link. > > This sets the link by replacing the Slot with a LinkWrapper Slot, and then > recompiles all using methods. > > Thus evaluating: > > TT new t > > will get you a #halt. > > Lots of things are not yet implemented (multiple links, uninstall, > arguments,â¦) > but it starts to show how simple one can do quite powerful things. > > Marcus > > > > -- www.tudorgirba.com "Every thing has its own flow"

July 21, 2014

[Pharo4] MetaLinks on Slots

by Marcus Denker

Hello, One of the questions with having meta objects for variables (Slots and Globals) is: For what is is good? Here is one exampleâ¦ in early stage but working. Imagine you want to âhook intoâ instance variable access. It can be done with e.g. bytecode manipulation, or on the AST level. But that is far from nice. With the new first class variables, there is now a fun way to do it: MetaLinks. Make a class TT with an instance var âtâ and add an accessor. Now we can define a MetaLink: it describes a call to a meta object that we wan to do before, after or instead of what our variable normally does. (default is #before): | link | link := MetaLink new metaObject: Halt; selector: #now. This link says: âdo a Halt now before where I will get installedâ. To install the link, just get the Slot meta object and set it using #link: (TT slotNamed: #t) link: link. This sets the link by replacing the Slot with a LinkWrapper Slot, and then recompiles all using methods. Thus evaluating: TT new t will get you a #halt. Lots of things are not yet implemented (multiple links, uninstall, arguments,â¦) but it starts to show how simple one can do quite powerful things. Marcus

July 21, 2014

Re: [Pharo-dev] [ANN] Ephestos - Using and Coding Blender from inside Pharo

by kilon alios

According to this http://stackoverflow.com/questions/9903670/measure-local-sockets-speed The speed for a modern computer should be around 200 mbs/sec , you can easily choke Pharo with this amount of data.I seriously doubt that Pharo can process 200mbs in 1 second. So it looks like you will worry about Pharo a lot sooner than you will worry about Ephestos. Also Ephestos because it allows you to execute any kind of python code, you have the option to let the data sit inside blender and fetch it whenever you want them or just the precise data that interests you. Afterall Blender is much faster than Pharo with dealing with 3d data and Pharo has light years of distance to cover before it competes in that area. By the way MORSE looks like it uses sockets already from what I read in the documentation section for communicating with matlab and other applications. I read also in the second link you sent "The last line configure the robotâs components on socket, for more information about services and datastreams, go to Middleware configuration <http://www.openrobots.org/morse/doc/latest/user/builder.html#middleware-con…> " so if is fast enough for Blender I don't see why it won't be fast enough for Ephestos. Ephestos afterall is Blender and is Python. Its great that binding for Pharo already exist , I am sure you can find a way to make everything work together , including Ephestos. Afterall the biggest problem always is knowledge , " how I do this" , technology already provides huge amount of solution but you have to know how to use the tools. Ephestos wont teach you pharo, it wont teach you python and certainly wont teach you blender. My thinking about sockets is that they present two big advantages over wrapping code and FFIs a) Much easier to use. See how simple Ephestos is . b) No maintenance needed at all. The library changes ? no problemo, unlike a wrapper or a FFI no API needs to be defined at Pharo side, that ensures that the latest of the library ported is supported with no extra work. c) The socket bridge may have no scope, it could run as Ephestos does any kind of code and any kind of library out of the box. You sacrifice some performance but that a small price to pay over the advantages. On Mon, Jul 21, 2014 at 11:02 AM, Serge Stinckwich < serge.stinckwich(a)gmail.com> wrote: > On Mon, Jul 21, 2014 at 9:48 AM, kilon alios <kilon.alios(a)gmail.com> > wrote: > > Well in theory it should work. > > > > I am saying "in theory" because I have not tried MORSE. > > > > What is Ephestos ? Basically its a python application that creates a > > streamsocket server that listens byte data, then it takes the byte > messages > > it converts them to strings and it executes them using exec() built-in > > python function. The end. See what I did here , I did not mention > Blender at > > all. Actually Ephestos is implemented as Blender addon. So it gives you > both > > access to Bpy and python libraries. A Blender addon is basically a python > > application + access to BPY + extra stuff to make it easy to select and > > enable in the Blender GUI. > > > > Now from what I see at first glance MORSE uses BPY and BGE. BGE , the > > blender game engine is a separate app essentially with its own API. So I > > need to wrap Ephestos for BGE but it will still be the same thing with > added > > more code to be called by BGE. It should be fairly easy to do and I will > do > > it. > > > > I don't know if there are other implementation details about MORSE but I > > don't think there will be a problem to make it work with Ephestos. > > > > Of course Ephestos has still got some big limitations a) does not receive > > data from Blender b) does not support of multiline python code. I don't > know > > about b) it may work already if you add newlines in your python strings > and > > whitespaces but I will have to test this and of course improve it to > make it > > easier to use. Both of these features will be added since they are high > > priority goals. > > Thank you for your explanations Kilon. I understand better how it works > now. > Yes receiving data like perception data from robots is quite important > for MORSE. > One problem I envision, is that the data could be huge and some > performance issues could appear I guess > if you have to translate data structures from Python to Pharo. > > BTW, Noury and Luc developed a ROS binding for Pharo. > ROS is a robotic middleware that could be used to do communication with > MORSE. > > Regards, > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > >

July 21, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40108 Home: https://github.com/pharo-project/pharo-core

July 21, 2014

[pharo-project/pharo-core] 44c32e: 40108

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 44c32e5d088f2a45edc349ae4054c56b49d382d4 https://github.com/pharo-project/pharo-core/commit/44c32e5d088f2a45edc349ae… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-07-21 (Mon, 21 Jul 2014) Changed paths: A Morphic-Core.package/MorphicCoreUIManager.class/README.md A Morphic-Core.package/MorphicCoreUIManager.class/definition.st A Morphic-Core.package/MorphicCoreUIManager.class/instance/ui process/resumeUIProcess_.st A Morphic-Core.package/MorphicCoreUIManager.class/instance/ui process/spawnNewProcess.st A Morphic-Core.package/MorphicCoreUIManager.class/instance/ui process/terminateUIProcess.st A Morphic-Core.package/MorphicCoreUIManager.class/instance/ui process/uiProcess.st A Morphic-Core.package/MorphicCoreUIManager.class/instance/ui requests/checkForNewDisplaySize.st A Morphic-Core.package/MorphicCoreUIManager.class/instance/ui requests/currentWorld.st A Morphic-Core.package/MorphicCoreUIManager.class/instance/ui requests/newDisplayDepthNoRestore_.st A Morphic-Core.package/MorphicCoreUIManager.class/instance/ui requests/restoreDisplayAfter_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script108.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40108.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Settings-Tools.package/DebugSystemSettings.class/class/settings/debugSettingsOn_.st A Slot.package/LayoutAbstractScope.class/instance/enumerating/indexOf_.st A Slot.package/LayoutAbstractScope.class/instance/enumerating/indexOf_ifAbsent_.st M Slot.package/LinkWrapper.class/README.md A Slot.package/LinkWrapper.class/instance/forwarded/=.st A Slot.package/LinkWrapper.class/instance/forwarded/hash.st A Slot.package/LinkWrapper.class/instance/forwarded/index.st A Slot.package/LinkWrapper.class/instance/forwarded/index_.st A Slot.package/LinkWrapper.class/instance/forwarded/isSpecial.st A Slot.package/LinkWrapper.class/instance/forwarded/isVisible.st A Slot.package/LinkWrapper.class/instance/forwarded/name.st A Slot.package/LinkWrapper.class/instance/forwarded/name_.st A Slot.package/LinkWrapper.class/instance/forwarded/parentScopeFor_.st A Slot.package/LinkWrapper.class/instance/forwarded/size.st M Slot.package/Slot.class/instance/meta-object-protocol/link_.st R Tool-Explorer.package/ObjectExplorer.class/class/as yet unclassified/about.st Log Message: ----------- 40108 13620 LinkWrapper Slot: first working version https://pharo.fogbugz.com/f/cases/13620 13611 add MorphicCoreUIManager https://pharo.fogbugz.com/f/cases/13611 13619 Small cleanup related to Explorer https://pharo.fogbugz.com/f/cases/13619 http://files.pharo.org/image/40/40108.zip

July 21, 2014