September 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Android Dr. Geo 12.10 release

by Hilaire Fernandes

I've just released version 12.10 for Android http://play.google.com/store/apps/details?id=eu.drgeo.android Dr. Geo is an interactive geometry software written with Pharo Smalltalk. It comes with a lot of changes: https://launchpad.net/drgeo/+milestone/12.10 Thanks Hilaire

Sept. 6, 2012

Re: [Pharo-project] Fwd: Working with Pharo 1.4/2.0 â¦

by Chris Cunningham

On Thu, Sep 6, 2012 at 8:30 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Below is a blog post and my reply... If anyone has anything to add, here's > the link... > https://schrievkrom.wordpress.com/2012/09/06/working-with-pharo-1-42-0/ ... >> * creating accessor methods for instance attributes is not speedy and >> takes too much clicks >> >> * then I looked for a setting framework and I was really surprised to see, >> how difficult it was â or at least the documentation I read about it. >> After working with the setting framework of VASmalltalk I would prefer the >> simple approach than a perhaps even more powerful approach. >> ... > * accessor creation â will you describe what steps you took (e.g. manual > creation, context menu (there are two possiblities here), etc)? If you > illustrate your ideal behavior, I will create an issue and push to include > it in Nautilusâ¦ I haven't worked with the framework in VA, and personally, don't like frameworks to create accessor methods. However, just yesterday, I really wished that the debugger had a button when enountering an unknown method called 'create accessor' or something similar - if the method looks like an accessor method for a variable that doesn't have one, offer up the option of letting the runner (coder) just create the simplest flavor right there in the debugger. It would show up right next to the Create button at the same time. My favorite method of coding, in any case... -Chris

Sept. 6, 2012

Re: [Pharo-project] [ANN] - statsd client

by Francois Stephany

Thanks Paul, This was somewhere on my "todo/wish list" :) On 06/09/12 07:45, Paul DeBruicker wrote: > Hi - > > I wanted to graph timing and event tallies that happen in my app without > doing much log processing so I made a statsd client and put it here: > > http://ss3.gemstone.com/ss/Statsd.html > > It sends UDP datagrams to the statsd daemon. I tested it in Squeak > trunk & Pharo-1.4 (it should work in older versions) and expect to port > it to Gemstone sometime soon. It has no dependencies so could be useful > for more than just Seaside stuff. > > thanks > > Paul > > > > statsd: https://github.com/etsy/statsd > statsd is: "A network daemon that runs on the Node.js platform and > listens for statistics, like counters and timers, sent over UDP and > sends aggregates to one or more pluggable backend services (e.g., > Graphite)". > > graphite: http://graphite.wikidot.com/ > Graphite is: "Graphite is a highly scalable real-time graphing system. > As a user, you write an application that collects numeric time-series > data that you are interested in graphing, and send it to Graphite's > processing backend, carbon, which stores the data in Graphite's > specialized database. The data can then be visualized through graphite's > web interfaces." > > > > > -- http://tulipemoutarde.be CA: +1 778 558 3225 BE: +32 65 709 131

Sept. 6, 2012

[Pharo-project] MemoryMonitor not in from Pharo?

by Alexandre Bergel

Hi! Some times ago MemoryMonitor was in Pharo. Apparently it has been removed. Any idea why? http://www.squeaksource.com/MemoryMonitor.html Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 6, 2012

[Pharo-project] Fwd: Working with Pharo 1.4/2.0 â¦

by Sean P. DeNigris

Below is a blog post and my reply... If anyone has anything to add, here's the link... https://schrievkrom.wordpress.com/2012/09/06/working-with-pharo-1-42-0/ > As I mentioned in my previous posting I at last have found now some time > to do actually some âseriousâ work with Pharo. > > Here are some thoughts â just to write down my first impressions: > > Pharo 1.4 > > I do most of the stuff with Pharo 1.4 for now and here some points in the > developer GUI: > > * multiple selection in the browser does not work â this was pretty boring > > * creating accessor methods for instance attributes is not speedy and > takes too much clicks > > * then I looked for a setting framework and I was really surprised to see, > how difficult it was â or at least the documentation I read about it. > After working with the setting framework of VASmalltalk I would prefer the > simple approach than a perhaps even more powerful approach. > > Pharo 2.0 and Nautilus > > I also had a look at Pharo 2.0 â and I have MANY,MANY problems with its > new browser: âNautilusâ. The reason for my problems is the way they create > the GUI: the buttons do not show the actual state of the GUI, but they > show what will happen, when the button is pressed !!! > > This is a radical approach changing the whole GUI and make it very > difficult to understand. Perhaps this is due to the fact, that they have > no suitable GUI elements (like two state buttons) for supporting this GUI > interaction. > > The visual appearance is in my view always in a conflict state. > > Then I look at buttons here in my home and most of these buttons are > on/off buttons. The possible values of these buttons are know prior to the > user â this is different to the buttons of Nautilus, where you perhaps do > not know the other state ( Groups Packages ). > > The on/off switch of my computer is a reverse-state button, but there is a > LED light, showing the actual state of the computer and the user know how > to use the button. > > The on/off switch of my power-subsystem in my computer has also a two > state button â but it shows the actual state (1 for on, 0 for off). > Thanks for the great feedback! This is gold for the Pharo dev community. I encourage you to bring this feedback to the dev list, or â even better â create issues, or (best option) take on a few so we can integrate them!! A few comments/questions: * multiple selection in 1.4 â consider the browser in 1.4 to be legacy. Nautilus will be the future browser in Pharo, and it will have multiple selection * accessor creation â will you describe what steps you took (e.g. manual creation, context menu (there are two possiblities here), etc)? If you illustrate your ideal behavior, I will create an issue and push to include it in Nautilusâ¦ * Settings â I find this one *really* interesting. Will you highlight the key differences to VA? Maybe we can improve the framework in Pharo, or at minimum create a UI that makes things simpler and more straightforward for you Re Nautilus: it is not production-ready, which is why it was not included in Pharo 1.4, but it is under heavy development by a great developer, Benjamin VanRyseghem. He is very open to this type of feedback. Specifically, I couldnât agree more about the buttons!!! After months of using Nautilus, I /still/ have no idea whether Iâm on the class or instance side. -- View this message in context: http://forum.world.st/Fwd-Working-with-Pharo-1-4-2-0-tp4646428.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 6, 2012

Re: [Pharo-project] [squeak-dev] [ANN] - statsd client

by Sven Van Caekenberghe

Cool ! Any actual pictures of your app/stats ? On 06 Sep 2012, at 16:45, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Hi - > > I wanted to graph timing and event tallies that happen in my app without doing much log processing so I made a statsd client and put it here: > > http://ss3.gemstone.com/ss/Statsd.html > > It sends UDP datagrams to the statsd daemon. I tested it in Squeak trunk & Pharo-1.4 (it should work in older versions) and expect to port it to Gemstone sometime soon. It has no dependencies so could be useful for more than just Seaside stuff. > > thanks > > Paul > > > statsd: https://github.com/etsy/statsd > statsd is: "A network daemon that runs on the Node.js platform and listens for statistics, like counters and timers, sent over UDP and sends aggregates to one or more pluggable backend services (e.g., Graphite)". > > graphite: http://graphite.wikidot.com/ > Graphite is: "Graphite is a highly scalable real-time graphing system. As a user, you write an application that collects numeric time-series data that you are interested in graphing, and send it to Graphite's processing backend, carbon, which stores the data in Graphite's specialized database. The data can then be visualized through graphite's web interfaces."

Sept. 6, 2012

[Pharo-project] [ANN] - statsd client

by Paul DeBruicker

Hi - I wanted to graph timing and event tallies that happen in my app without doing much log processing so I made a statsd client and put it here: http://ss3.gemstone.com/ss/Statsd.html It sends UDP datagrams to the statsd daemon. I tested it in Squeak trunk & Pharo-1.4 (it should work in older versions) and expect to port it to Gemstone sometime soon. It has no dependencies so could be useful for more than just Seaside stuff. thanks Paul statsd: https://github.com/etsy/statsd statsd is: "A network daemon that runs on the Node.js platform and listens for statistics, like counters and timers, sent over UDP and sends aggregates to one or more pluggable backend services (e.g., Graphite)". graphite: http://graphite.wikidot.com/ Graphite is: "Graphite is a highly scalable real-time graphing system. As a user, you write an application that collects numeric time-series data that you are interested in graphing, and send it to Graphite's processing backend, carbon, which stores the data in Graphite's specialized database. The data can then be visualized through graphite's web interfaces."

Sept. 6, 2012

Re: [Pharo-project] Process browser: next generation

by Goubier Thierry

Le 06/09/2012 16:31, phil(a)highoctane.be a Ã©crit : > Main UI process and a haltOnce would indeed be great instead of the > current kata. I'd be a lot safer if I could "trace" the main UI process instead of blocking it. Maybe block it, kill it (keep the stack) and restart a new one immediately (in a safe UI context with say just the debugger open) so that I can explore the current state and eventually let it proceed. -- Remote debug from another Pharo image ? Thierry > 2012/9/6 Goubier Thierry <thierry.goubier(a)cea.fr > <mailto:thierry.goubier@cea.fr>> > > Le 06/09/2012 16:16, Sean P. DeNigris a Ã©crit : > > > Alexandre Bergel-7 wrote > > > Ok, this is indeed the first thing you want > > On Sep 5, 2012, at 7:51 PM, phil@ wrote: > > An ability to jump to the process code right away. > > > > Yes, that would be super cool! > > > Isn't that the case in the current process browser ? > > Or do you mean something like forcing a breakpoint in a currently > running process ? > > ( It would be cool to breakpoint like that the main UI process... :)). > > Thierry > > > > > -- > View this message in context: > http://forum.world.st/Process-__browser-next-generation-__tp4646267p4646408… > <http://forum.world.st/Process-browser-next-generation-tp4646267p4646408.html> > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 6, 2012

Re: [Pharo-project] Process browser: next generation

by Sean P. DeNigris

Goubier Thierry wrote > > Well, it would make up, in some cases, for the fact the "emergency" > interrupt key doesn't work (in 1.3, 1.4 and 2.0 all versions under Linux). > Except that you wouldn't be able to open the browser, no? IIRC Igor had some ideas about more robust interrupt behavior... ah, yes, here it is... Issue 4608: [ENH]: More robust user interrupt http://code.google.com/p/pharo/issues/detail?id=4608 Cheers, Sean -- View this message in context: http://forum.world.st/Process-browser-next-generation-tp4646267p4646416.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 6, 2012

Re: [Pharo-project] Process browser: next generation

by Goubier Thierry

Le 06/09/2012 16:29, Sean P. DeNigris a Ã©crit : > > Goubier Thierry wrote >> >> Or do you mean something like forcing a breakpoint in a currently >> running process ? >> > > Yes, exactly :) Well, it would make up, in some cases, for the fact the "emergency" interrupt key doesn't work (in 1.3, 1.4 and 2.0 all versions under Linux). Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 6, 2012