November 2015 - Pharo-users

Re: [Pharo-users] Pharo for Data Visualization

by stepharo

Ronie I think that this is important that people can pick different ("compatible") driver/framework back-end. You see if Woden is only built to work on something that does not run on mac or windows then it will be limited. Stef Le 25/11/15 00:14, Ronie Salgado a Ã©crit : > > What do you mean with "modern"? > > By modern I mean a graphics card a with graphics driver that supports > at least OpenGL 4.x. That Intel HD graphics card is capable of > supporting at least OpenGL 4.2, but the Open Source Mesa driver gives > you support up until OpenGL 3.1. Unfortunately, unlike with AMD or > NVIDIA graphics cards, the open source driver is the official driver. > > Woden-Roassal requires integer arithmetic in shaders which is used to > support the selection of objects. Integer arithmetics in shaders > requires at least OpenGL 3.3, or the missing extension for which you > are receiving the error. > > It is not required by the Woden-Core api, so you should be able to try > the following in a workspace: > > WDFPSSimpleExample6 new open > > My notebook with an HD Graphics 4400 has no problems with all > "three.js" demos found here http://threejs.org/. > > Three.js or any WebGL based example is a bad test for that graphics > card. WebGL is based in OpenGL ES 2.0 which is a subset of OpenGL 2.0. > This is a very old technology for that graphics card. > > Woden will be using Vulkan in the future. According to this Phoronix > article > (http://www.phoronix.com/scan.php?page=news_item&px=LunarG-Vulkan-AMA) Valve > has already made a proper Vulkan driver for the Intel graphics cards. > We only need an official release of the Vulkan spec. > > Best regards > Ronie > > 2015-11-24 18:50 GMT-03:00 Volkert <volkert(a)komponentenwerkstatt.de > <mailto:volkert@komponentenwerkstatt.de>>: > > My notebook with an HD Graphics 4400 has no problems with all > "three.js" demos found here http://threejs.org/. > > What do you mean with "modern"? > > > > On 24.11.2015 22:25, Ronie Salgado wrote: >> You need a modern graphics card. Open source graphics drivers are >> not supported because there are very behind in their >> implementations of OpenGL. >> >> >> 2015-11-24 17:28 GMT-03:00 Volkert >> <volkert(a)komponentenwerkstatt.de >> <mailto:volkert@komponentenwerkstatt.de>>: >> >> But not on my linux box .... ubuntu 14.04 :-( >> >> >> >> >> On 24.11.2015 21:03, Alexandre Bergel wrote: >>> Woden works in Pharo 5.0 >>> I have just tried. >>> >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>>> On Nov 24, 2015, at 3:15 PM, Volkert >>>> <volkert(a)komponentenwerkstatt.de >>>> <mailto:volkert@komponentenwerkstatt.de>> wrote: >>>> >>>> Cool ... >>>> >>>> Which Pharo Version? I tried Pharo 4.0 and got this error: >>>> >>>> <edcefcdd.png> >>>> >>>> >>>> On 24.11.2015 12:50, Alexandre Bergel wrote: >>>>>> Do we have a tutorial? i found only http://woden.ronie.cl. >>>>>> >>>>>> What about mouse control and object selection. It that >>>>>> possible? >>>>> >>>>> Yes. >>>>> >>>>> To load Woden: >>>>> >>>>> Gofer new smalltalkhubUser: 'ronsaldo' project: 'Woden'; >>>>> package: 'ConfigurationOfWoden'; load. (Smalltalk at: >>>>> #ConfigurationOfWoden) loadBleedingEdge. >>>>> >>>>> Try: >>>>> =-=-=-==-=-=-==-=-=-==-=-=-= >>>>> v := RWView new. >>>>> >>>>> 1 to: 100 do: [ :i | >>>>> e := RWCube element. >>>>> e when: RWMouseButtonDown do: [ :ev | >>>>> ev element shape color: WDColor green. >>>>> ev element changed. >>>>> ]. >>>>> v add: e. >>>>> ]. >>>>> RWXZGridLayout on: v elements. >>>>> v addInteraction: RWMouseKeyControl. >>>>> v camera position: (WDVector3 x: 0.0 y: 0.0 z: 3.0). >>>>> v open >>>>> =-=-=-==-=-=-==-=-=-==-=-=-= >>>>> Use the keys A S D W and the moose to navigate. Click on >>>>> cube to make them green >>>>> >>>>> <Mail Attachment.png> >>>>> >>>>> Cheers, >>>>> Alexandre >>>>> >>>>> >>>>> >>>>>> >>>>>> BW, >>>>>> Volkert >>>>>> >>>>>> On 22.11.2015 21:10, Alexandre Bergel wrote: >>>>>>> We have also put quite some effort on Woden, a 3d engine >>>>>>> for Pharoâ¦ >>>>>>> >>>>>>> Cheers, >>>>>>> Alexandre >>>>>>> >>>>>>> >>>>>>>> On Nov 22, 2015, at 2:56 PM, Dimitris Chloupis >>>>>>>> <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> >>>>>>>> wrote: >>>>>>>> >>>>>>>> its possible via my Ephestos project, to render to >>>>>>>> video or real time but the project is still very much a >>>>>>>> WIP. Its doable but require some python knowledge and >>>>>>>> knowledge of Blender UI and API. I will be making a >>>>>>>> true Pharo API for it fairly soon but as you can >>>>>>>> imagine these things take time. >>>>>>>> >>>>>>>> On Sun, Nov 22, 2015 at 6:35 PM Volkert >>>>>>>> <volkert(a)komponentenwerkstatt.de >>>>>>>> <mailto:volkert@komponentenwerkstatt.de>> wrote: >>>>>>>> Is this possible with Pharo? >>>>>>>> >>>>>>>> http://www.asterank.com/3d/ >>>>>>>> >>>>>>>> BW, >>>>>>>> Volkert >>>>>>>> >>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> >> > >

Nov. 28, 2015

Re: [Pharo-users] [ANN] breakpoints and watchpoints working

by Marcus Denker

> > > Is there a way to query all breakpoints like a query of senders of #halt? you can search for the senders of #break. But as class Breakpoint has a list of all active breakpoints, we add a browseAll method there easily. > > Any reason for Whatchpoints doesn't work with expressions in the Playground? > The Playground does not yet support suggestions. This should be fixed. > Breakpoints seems to work fine (apart from some problem setting up from the menu method in Nautilus), If you find a repeatable case for that , can you add an issue on the tracker? > but a problem you could be aware is setting a break once in InputEventFetcher>>signalEvent: , and then moving the mouse, the image hangs. > Thanks, we will investigate. The âonceâ breakpoint triggers a recompile before opening the debugger. but of course the devil is in the detailsâ¦ we will check to see what exactly is happening here. Marcus

Nov. 28, 2015

Re: [Pharo-users] [ANN] breakpoints and watchpoints working

by HernÃ¡n Morales Durand

Hello, I have so many questions :) But let's start with a few. 2015-11-27 11:17 GMT-03:00 Johan Fabry <jfabry(a)dcc.uchile.cl>: > Hi all, > > Marcus, Miguel Campusano and me have been working the last few weeks on > getting breakpoints and watchpoints working for Pharo 5. Since a few days > we have functionality that works for many cases and that is easily > accessible. Itâs really cool, I urge you to try it out! > > Breakpoints: > In Nautilus in the methods list you can add a breakpoint to a method, as > well as a breakpoint that triggers once, or a breakpoint that takes a > condition. (The last is still a bit complicated. Marcus promised that he > will clean that up :-).) Also in the code pane the suggestions menu allows > you to add a breakpoint to expressions. They will be highlighted in red, > and an icon appears in the gutter. Clicking it removes the breakpoint and > also bringing up the suggestions menu allows you to remove them. > Watchpoints: > Watchpoints are a simple mechanism to log the results of specific > expressions. In the code pane the suggestions menu allows you to set a > watchpoint. The expression is highlighted in red and in the gutter a green > ball appears. Click it and you will have a simple UI that shows the last > values recorded. (Actually the watchpoint records every execution and never > throws anything away, so this can become a memory hog, be careful.) You can > remove the watchpoint from the UI and from the suggestions menu. > > In our experiments we found both very useful and powerful, try them out > and be sure to tell us if there are any problems > > First, thank you for this feature Johan, Miguel and Marcus. Is there a way to query all breakpoints like a query of senders of #halt? Any reason for Whatchpoints doesn't work with expressions in the Playground? Breakpoints seems to work fine (apart from some problem setting up from the menu method in Nautilus), but a problem you could be aware is setting a break once in InputEventFetcher>>signalEvent: , and then moving the mouse, the image hangs. Cheers HernÃ¡n > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University > of Chile > > >

Nov. 28, 2015

Re: [Pharo-users] [ANN] breakpoints and watchpoints working

by Mariano Martinez Peck

Hi Johan, I just gave it a try and it's super awesome (mostly the watchpoints). No need to halt + inspect anymore :) Pharo 5.0 looks sooooo cool!! On Fri, Nov 27, 2015 at 5:03 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > This is really great news. > > Thanks a lot to all of you for working together on this and for working on > it persistently for such long time (years). > > I would like to add that people should realise that the technology behind > it is really great and holds even more potential for the future. > Furthermore, these relatively simple features combine several key > foundational technologies (new compiler, AST, reflection, tools, spec, ...). > > This (and all the other impressive things everybody else is doing) is what > Pharo is all about. > > Sven > > > On 27 Nov 2015, at 15:17, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > > > Hi all, > > > > Marcus, Miguel Campusano and me have been working the last few weeks on > getting breakpoints and watchpoints working for Pharo 5. Since a few days > we have functionality that works for many cases and that is easily > accessible. Itâs really cool, I urge you to try it out! > > > > Breakpoints: > > In Nautilus in the methods list you can add a breakpoint to a method, as > well as a breakpoint that triggers once, or a breakpoint that takes a > condition. (The last is still a bit complicated. Marcus promised that he > will clean that up :-).) Also in the code pane the suggestions menu allows > you to add a breakpoint to expressions. They will be highlighted in red, > and an icon appears in the gutter. Clicking it removes the breakpoint and > also bringing up the suggestions menu allows you to remove them. > > > > Watchpoints: > > Watchpoints are a simple mechanism to log the results of specific > expressions. In the code pane the suggestions menu allows you to set a > watchpoint. The expression is highlighted in red and in the gutter a green > ball appears. Click it and you will have a simple UI that shows the last > values recorded. (Actually the watchpoint records every execution and never > throws anything away, so this can become a memory hog, be careful.) You can > remove the watchpoint from the UI and from the suggestions menu. > > > > In our experiments we found both very useful and powerful, try them out > and be sure to tell us if there are any problems > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > > > Johan Fabry - http://pleiad.cl/~jfabry > > PLEIAD and RyCh labs - Computer Science Department (DCC) - > University of Chile > > > > > > > -- Mariano http://marianopeck.wordpress.com

Nov. 27, 2015

Re: [Pharo-users] [ANN] breakpoints and watchpoints working

by Sven Van Caekenberghe

This is really great news. Thanks a lot to all of you for working together on this and for working on it persistently for such long time (years). I would like to add that people should realise that the technology behind it is really great and holds even more potential for the future. Furthermore, these relatively simple features combine several key foundational technologies (new compiler, AST, reflection, tools, spec, ...). This (and all the other impressive things everybody else is doing) is what Pharo is all about. Sven > On 27 Nov 2015, at 15:17, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > Hi all, > > Marcus, Miguel Campusano and me have been working the last few weeks on getting breakpoints and watchpoints working for Pharo 5. Since a few days we have functionality that works for many cases and that is easily accessible. Itâs really cool, I urge you to try it out! > > Breakpoints: > In Nautilus in the methods list you can add a breakpoint to a method, as well as a breakpoint that triggers once, or a breakpoint that takes a condition. (The last is still a bit complicated. Marcus promised that he will clean that up :-).) Also in the code pane the suggestions menu allows you to add a breakpoint to expressions. They will be highlighted in red, and an icon appears in the gutter. Clicking it removes the breakpoint and also bringing up the suggestions menu allows you to remove them. > > Watchpoints: > Watchpoints are a simple mechanism to log the results of specific expressions. In the code pane the suggestions menu allows you to set a watchpoint. The expression is highlighted in red and in the gutter a green ball appears. Click it and you will have a simple UI that shows the last values recorded. (Actually the watchpoint records every execution and never throws anything away, so this can become a memory hog, be careful.) You can remove the watchpoint from the UI and from the suggestions menu. > > In our experiments we found both very useful and powerful, try them out and be sure to tell us if there are any problems > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > >

Nov. 27, 2015

Re: [Pharo-users] [ANN] breakpoints and watchpoints working

by Johan Fabry

Thanks for the kind (deleted) words :-) Yes the next step for watchpoints would be better management of the values that are recorded. Visualizations would be really great, I have been thinking about that (just in the abstract) and the sky is the limit. There is nothing yet because we have not had time to work on this. Also some standard logging infrastructure in Pharo would be nice, now itâs just an ordered collection but this should be changed to a better way to do logging. > On Nov 27, 2015, at 13:39, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > Breakpoints are very convenient but I am in love with watchpoints !!!! You guys are amazing ! A million thank you :) > > As I said to Marcus I imagine some very nice graph visualization of data evolution with roassal for this :) ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Nov. 27, 2015

Re: [Pharo-users] [ANN] breakpoints and watchpoints working

by Dimitris Chloupis

Excuse the language but I think its justified THIS IS FUCKING AMAZING !!!! Breakpoints are very convenient but I am in love with watchpoints !!!! You guys are amazing ! A million thank you :) As I said to Marcus I imagine some very nice graph visualization of data evolution with roassal for this :) On Fri, Nov 27, 2015 at 4:18 PM Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > Hi all, > > Marcus, Miguel Campusano and me have been working the last few weeks on > getting breakpoints and watchpoints working for Pharo 5. Since a few days > we have functionality that works for many cases and that is easily > accessible. Itâs really cool, I urge you to try it out! > > Breakpoints: > In Nautilus in the methods list you can add a breakpoint to a method, as > well as a breakpoint that triggers once, or a breakpoint that takes a > condition. (The last is still a bit complicated. Marcus promised that he > will clean that up :-).) Also in the code pane the suggestions menu allows > you to add a breakpoint to expressions. They will be highlighted in red, > and an icon appears in the gutter. Clicking it removes the breakpoint and > also bringing up the suggestions menu allows you to remove them. > > Watchpoints: > Watchpoints are a simple mechanism to log the results of specific > expressions. In the code pane the suggestions menu allows you to set a > watchpoint. The expression is highlighted in red and in the gutter a green > ball appears. Click it and you will have a simple UI that shows the last > values recorded. (Actually the watchpoint records every execution and never > throws anything away, so this can become a memory hog, be careful.) You can > remove the watchpoint from the UI and from the suggestions menu. > > In our experiments we found both very useful and powerful, try them out > and be sure to tell us if there are any problems > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University > of Chile > > >

Nov. 27, 2015

[ANN] breakpoints and watchpoints working

by Johan Fabry

Hi all, Marcus, Miguel Campusano and me have been working the last few weeks on getting breakpoints and watchpoints working for Pharo 5. Since a few days we have functionality that works for many cases and that is easily accessible. Itâs really cool, I urge you to try it out! Breakpoints: In Nautilus in the methods list you can add a breakpoint to a method, as well as a breakpoint that triggers once, or a breakpoint that takes a condition. (The last is still a bit complicated. Marcus promised that he will clean that up :-).) Also in the code pane the suggestions menu allows you to add a breakpoint to expressions. They will be highlighted in red, and an icon appears in the gutter. Clicking it removes the breakpoint and also bringing up the suggestions menu allows you to remove them. Watchpoints: Watchpoints are a simple mechanism to log the results of specific expressions. In the code pane the suggestions menu allows you to set a watchpoint. The expression is highlighted in red and in the gutter a green ball appears. Click it and you will have a simple UI that shows the last values recorded. (Actually the watchpoint records every execution and never throws anything away, so this can become a memory hog, be careful.) You can remove the watchpoint from the UI and from the suggestions menu. In our experiments we found both very useful and powerful, try them out and be sure to tell us if there are any problems ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Nov. 27, 2015

Re: [Pharo-users] Analyzing Tweets

by Alexandre Bergel

I do not know. I told them to register, but I have no idea if they actually did. Alexandre > On Nov 27, 2015, at 12:13 AM, Arturo Zambrano <arturo.zambrano(a)gmail.com> wrote: > > Looks nice, very similar to what Agustin presented in Smalltalks a few days ago. We will post more info soon. > > > So there are at least 3 known projects working in Pharo + Roassal > > Are the authors in this list? Great work! > It would be great to share the experience > > On Thu, Nov 26, 2015 at 5:12 PM, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net> wrote: > Never mind. I found it[1]. It was on the see more of the you tube video (I advice to make it more visible on the page of the project): > > [1] https://github.com/ser515asu/AgileTweetViz-Technocrats > [2] https://sites.google.com/a/asu.edu/project-geeko/ > > Cheers, > > Offray > > > On 26/11/15 15:07, Offray Vladimir Luna CÃ¡rdenas wrote: > Really nice and helpful... I don't see any public repo for the tool on . There is any? > > Cheers, > > Offray > > On 26/11/15 13:44, Alexandre Bergel wrote: > Hi! > > Some students from Arizona State University are analyzing some tweets. This is pretty cool. Here are some short video and url full of pictures: > > https://sites.google.com/a/asu.edu/project-geeko/ > https://drive.google.com/file/d/0BxQoWoSofKvaTkN5bk9hN0NyQ28/view > https://www.youtube.com/watch?v=cnuc_crnWB0&feature=youtu.be > > Impressive! > > Cheers, > Alexandre > > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 27, 2015

Python's argparse like CommandlineHandler?

by Julien Delplanque

Hello, Is there a way to specify: - The "type" of command line arguments. - The default value if none is given. - That an argument is obligatory or optional? A bit like argparse does in Python, if you know it. Julien

Nov. 27, 2015