October 2015 - Pharo-users - lists.pharo.org

Seaside on Pharo 5?

by Yuriy Tymchuk

Hi, Is there a version of Seaside that works on Pharo5? Uko

Oct. 30, 2015

Re: [Pharo-users] [ANN] Working with Pharo on the Raspberry Pi

by Tim Hendriks

What I would like is access to the GPIO pins from Pharoâ¦. It is possible from Scratch so someone (i am to stupid to do this) could maybe hack that into Pharo? Tim > On 30 Oct 2015, at 16:22, Tim Hendriks <th72(a)dds.nl> wrote: > > Pharo5 works with fine with the squeak vm in Jessie. No errorâs and much faster. Didnât test it thoroughly. > > Tim > > >> On 26 Oct 2015, at 16:41, Attila Magyar <m.magyar3(a)gmail.com> wrote: >> >> Hi Torsten, >> >> Have you tried the cogvm on the Pi? It is much faster than the stack vm. If >> I remember correctly, I used this one last time: >> http://www.mirandabanda.org/files/Cog/VM/VM.r3427/cogspurlinuxhtARM-15.33.3… >> >> Attila >> >> >> >> -- >> View this message in context: http://forum.world.st/ANN-Working-with-Pharo-on-the-Raspberry-Pi-tp4857895p… >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> > >

Oct. 30, 2015

Re: [Pharo-users] [ANN] Working with Pharo on the Raspberry Pi

by Tim Hendriks

Pharo5 works with fine with the squeak vm in Jessie. No errorâs and much faster. Didnât test it thoroughly. Tim > On 26 Oct 2015, at 16:41, Attila Magyar <m.magyar3(a)gmail.com> wrote: > > Hi Torsten, > > Have you tried the cogvm on the Pi? It is much faster than the stack vm. If > I remember correctly, I used this one last time: > http://www.mirandabanda.org/files/Cog/VM/VM.r3427/cogspurlinuxhtARM-15.33.3… > > Attila > > > > -- > View this message in context: http://forum.world.st/ANN-Working-with-Pharo-on-the-Raspberry-Pi-tp4857895p… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Oct. 30, 2015

Re: [Pharo-users] Constrained variable width of Plaground/Inspector panes

by Johan Fabry

Improve it and tweak it as much as you like, it was mainly intended as a demonstrator of how to use the Roassal spec plugin. So as long as that part remains clear, the cooler the tool the better it is :-). > On Oct 30, 2015, at 10:24, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Thanks Johan, I'll take a look. > > Maybe it will need some tweaking such as syntax highlighting and keyboard shortcuts, but this is what I was looking for. :) > > Peter ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Oct. 30, 2015

Re: [Pharo-users] Constrained variable width of Plaground/Inspector panes

by Peter UhnÃ¡k

Thanks Johan, I'll take a look. Maybe it will need some tweaking such as syntax highlighting and keyboard shortcuts, but this is what I was looking for. :) Peter On Fri, Oct 30, 2015 at 1:38 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > Peter, in the Roassal2Spec package (in the mail Roassal repository) there > is a SpecEasel class that I think does exactly what you want. > > > > > > On Oct 30, 2015, at 07:48, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > I wouldn't mind having a "special playground" just for this particular use > case. There is also Roassal Easel > <easel.png> > â > However I would like to have the code on a side rather than underneath > because code is tall, not wide. > > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University > of Chile > >

Oct. 30, 2015

Re: [Pharo-users] Constrained variable width of Plaground/Inspector panes

by Johan Fabry

Peter, in the Roassal2Spec package (in the mail Roassal repository) there is a SpecEasel class that I think does exactly what you want. > On Oct 30, 2015, at 07:48, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > I wouldn't mind having a "special playground" just for this particular use case. There is also Roassal Easel > <easel.png> > â > However I would like to have the code on a side rather than underneath because code is tall, not wide. > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Oct. 30, 2015

Re: [Pharo-users] Constrained variable width of Plaground/Inspector panes

by Alexandre Bergel

No idea, but your visualizations are gorgeous! Alexandre > On Oct 30, 2015, at 7:48 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi, > > is it possible to programatically change the width of Playground/Inspector panes? > > Currently if I want one pane bigger I have to resize both which wastes a lot of space (I need to resize twice as much). > > eg: > > <playground.png> > > I wouldn't mind having a "special playground" just for this particular use case. There is also Roassal Easel > <easel.png> > â > However I would like to have the code on a side rather than underneath because code is tall, not wide. > > Thanks, > Peter > â -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 30, 2015

Re: [Pharo-users] VM crash on Ubuntu 14.04

by Esteban Lorenzano

you can type p (void)printCallStack() then you will have the active stack when crash happened. Is often a lot more useful than the trace of the vm. Esteban > On 29 Oct 2015, at 19:03, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > > OK, back with access to the Ubuntu machine, I reproduced the crash when running under gdb (reproducing it is never an issue, finding the minimal case is the issue). See below for gdb output. But my vm has no debug information compiled, so it is not really useful. Can I download a vm with debug info compiled from somewhere? I would prefer to avoid having to download the sources and compile et cetera â¦ > > Once I have such a VM I will make some time to further investigate, and report results. > > Program received signal SIGSEGV, Segmentation fault. > 0xb8c2bc31 in ?? () > (gdb) bt > #0 0xb8c2bc31 in ?? () > #1 0x080fc9f2 in primitiveNativeCall () > #2 0xb4fba770 in ?? () > #3 0xb503b05e in ?? () > #4 0xb503afcb in ?? () > #5 0xb5011abd in ?? () > #6 0xb4fba5c0 in ?? () > (gdb) > >> On Oct 27, 2015, at 19:09, Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>> wrote: >> >> >> >> 2015-10-26 15:03 GMT+01:00 Johan Fabry <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>>: >> Hi Nicolai, >> >> thanks for following up on this. >> >> I am in the process of determining what causes the crash. I fear that to reproduce the problem you will need to have ROS installed, I have not yet been able to reproduce it without ROS running. I do not want to inflict the installation of ROS on you without being 100% sure. >> >> I am using Roassal because this is for Live Robot Programming (http://pleiad.cl/LRP <http://pleiad.cl/LRP>) which uses a dynamic visualization of the running code. To reproduce the bug (until now) I need to develop code in LRP when using ROS, and then it happens randomly. I realize that this is too much to ask for an outsider to reproduce the bug (I did not expect anybody to download and install PhaROS to try to reproduce, thanks for that!!). >> >> Can you inform me how I can get you more useful debug info to you? I will keep trying to find minimal steps to reproduce in the mean time. >> >> No, the best we can hope for is a crash when it is running from debugger, you can start the vm with a debugger or >> attach the debugger to a running process. If we are lucky, the debugger will show a stacktrace. >> >> >>> On Oct 24, 2015, at 19:45, Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>> wrote: >>> >>> Can you provide the image file. >>> What exactly runs in the image (does it depend on ROS or >>> does it crash even without it). For what do you >>> use Roassal in this environment. >>> Can you reproduce the crash with a clean image (and maybe loading >>> some package - without all of the ROS-stuff? >>> (I just followed the installation guide for PhaROS, but I have no idea >>> how to go from here to do anything to reproduce the crash). >>> >>> >>> >>> 2015-10-24 21:32 GMT+02:00 Johan Fabry <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>>: >>> >>> Ben, thanks for replying but since no VM guys are following up on this, apparently, it does not make much sense for me to go this way. >>> >>> Guys, am I to assume there is not help for me on this topic? >>> >>> > On Oct 23, 2015, at 11:03, Ben Coman <btc(a)openInWorld.com <mailto:btc@openInWorld.com>> wrote: >>> > >>> > On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote: >>> >> Hi all, >>> >> >>> >> I am having some unpleasant experiences on Ubuntu 14.04 (experimenting with Live Robot Programming on PhaROS). The VM crashes after a random amount of time (< 25 minutes), with no clear sequence of steps on how to reproduce the crash. I am using Pharo 4 (Pharo 40622 as installed by PhaROS) + Roassal which required an install of libcairo2:i386 . VM version details below. >>> >> >>> >> There is no printout on stdout, and the debug.log does not contain recent entries (timestamp is always some minutes before the actual crash happens). >>> >> >>> >> Is this a known problem? If so, how can I fix it, and if not how can I provide more debugging info? >>> >> >>> >> Thanks in advance! >>> > >>> > I'm not much help since I haven't done these myself, but just some >>> > ideas (maybe someone can add more details) >>> > * compile and run a debug vm >>> > * trace all function calls, http://tinyurl.com/gdb-trace-all <http://tinyurl.com/gdb-trace-all> >>> > >>> >>> >>> >>> ---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- >>> >>> Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> >>> PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile >>> >>> >>> >> >> >> >> ---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- >> >> Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> >> PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > > > > ---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- > > Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile >

Oct. 30, 2015

Re: [Pharo-users] TestAsserter>>assertCollection:hasSameElements:

by jtuchel＠objektfabrik.de

Peter, > Adding the feedback generation into makes the API even more > complicated, because you'd have to ar least pass a String as a fourth > parameter. > So we'd end up with: > > > assertExecuting: aBlock with: listOfArguments resultsIn: > expectedResult otherwise: failureString. ... and if you - like me - wonder if this would be any better than the current #assert:description: and some additional bindWith:'s for reusable nicer error texts, we may finally agree that we can as well leave SUnit as it is ... and bite the bullet of writing a bit more code for better feedback. > > In this form, I am sure nobody would use it. Or just for very special > and important tests. So all that I can come up with for now is > insufficient, unfortunately. Sure, there can be variants that provide > some standard parameters for most of the arguments, but the base > problem remains that the API is clumsy. So my whole point boils down to: please don't add too much cruft to SUnit just to get better feedback. Joachim

Oct. 30, 2015

Constrained variable width of Plaground/Inspector panes

by Peter UhnÃ¡k

Hi, is it possible to programatically change the width of Playground/Inspector panes? Currently if I want one pane bigger I have to resize both which wastes a lot of space (I need to resize twice as much). eg: I wouldn't mind having a "special playground" just for this particular use case. There is also Roassal Easel â However I would like to have the code on a side rather than underneath because code is tall, not wide. Thanks, Peter â

Oct. 30, 2015