December 2017 - Pharo-users

Re: [Pharo-users] FLSerialization>>analysisStep too slow?

by Andreas Brodbeck

Am 13.12.17 um 12:06 schrieb Eno: > Thanks Mariano. > > There is no such method: FLSerializer>>setDebug and FLDebugSerialization > class in my 6.1 image. Debugging support needs to be loaded extra with "FuelDebug", like this: (ConfigurationOfFuel project stableVersion) load: #(default FuelDebug). Cheers, Andreas -- Andreas Brodbeck www.mindclue.ch

Dec. 17, 2017

Re: [Pharo-users] Pharo Launcher name

by Alexandre Bergel

+1 EnvoyÃ© de mon iPhone > Le 17 dÃ©c. 2017 Ã 15:01, Mariano Martinez Peck <marianopeck(a)gmail.com> a Ã©crit : > > I also find having it called Pharo quite disturbing. PharoLauncher should be much better. Something that also disturbing is to see the same icon as all my pharo images / VMs. It would be much better if aside from having a different name, it could have a different icon. > > Cheers, > >> On Sun, Dec 17, 2017 at 2:55 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> I agree with you and we should rename it PharoLauncher. >> >> Stef >> >> On Sun, Dec 17, 2017 at 12:32 AM, Glenn Hoetker <ghoetker(a)me.com> wrote: >> > I love the Pharo Launcher. But, I find it confusing to have an application >> > called âPharo.appâ. Nothing in that name suggests it is a launcher. It is >> > also very confusing to have an application called âPharo.appâ next to one >> > called âPharo6.1.appâ when they are very different things (at least from a >> > users perspective). >> > >> > Has changing the name of the Pharo Launcher to âPharo Launcherâ ever been >> > considered? >> > >> > Just a thought. Most of all, thanks for the wonderful tool. >> > >> > Glenn >> > > > > -- > Mariano > http://marianopeck.wordpress.com

Dec. 17, 2017

Re: [Pharo-users] Athens error

by Hilaire

Strangely when this morph menu is asked, the same error shows up, see screenshot. May be something else is wrong in the image, in the next days I will try to build differently the image application Le 17/12/2017 Ã 18:29, Igor Stasenko a Ã©critÂ : > i think it will help more if you reveal the full stack trace with > actual exception.. IIRC you can do it by clicking on errorneous morph > and in its menu pick the stack trace. > -- Dr. Geo http://drgeo.eu

Dec. 17, 2017

Re: [Pharo-users] Pharo things analog reads ?

by Denis Kudriashov

Hi Steven 2017-12-17 12:40 GMT+01:00 Steven Costiou <steven.costiou(a)kloum.io>: > Hi, > > For what i know, raspberry pi boards cannot read analog sensors (which are > the most interesting imo), except by connecting to some kind of bridges or > to Arduino boards. > > In the PharoTHings code i see that there are Arduino classes, and also it > is based on wiringpi and wiringpi provides support for i2c which is needed > to connect to an Arduino and perform analog reads. > > I'm exploring the wiringpi doc to see if there is an example for that, but > in the meantime, would someone already have an example of analog reads with > PharoThings, with working code (even simple) ? > It is in my todo. I need to build example with temperature sensor. I will continue work on it next year. Now feel free to contribute to the project. About Arduino: it is not finished. Problem that I use Mac but serial port is not working there (it is required for Firmata) > > > Steven. >

Dec. 17, 2017

Re: [Pharo-users] FLSerialization>>analysisStep too slow?

by Stephane Ducasse

Did you read the chapter on Metacello in deep into Pharo? in essence you create a class where you express dependencies to other projects and packages. Have a look at the configuration of Soup for example Object subclass: #ConfigurationOfSoup instanceVariableNames: 'project' classVariableNames: 'LastVersionLoad' package: 'ConfigurationOfSoup' ConfigurationOfSoup >> baseline19: spec <version: '1.9-baseline'> spec for: #'common' do: [ spec blessing: #'baseline'. spec repository: 'http://www.smalltalkhub.com/mc/PharoExtras/Soup/main'. spec project: 'XMLParser' with: [ spec className: #ConfigurationOfXMLParser; versionString: #'stable'; repository: 'http://www.smalltalkhub.com/mc/PharoExtras/XMLParser/main' ]. spec package: 'Soup-Core' with: [ spec requires: #('XMLParser' ). ]; package: 'Soup-Zinc' with: [ spec requires: #('Soup-Core' ). ]; package: 'Soup-XPath' with: [ spec requires: #('Soup-Core' ). ]; package: 'Soup-Help' with: [ spec requires: #('Soup-Core' ). ]; package: 'Soup-Tests-Core' with: [ spec requires: #('Soup-Core' ). ]; package: #'Soup-Tools' with: [ spec requires: #('Soup-Core' 'Soup-Zinc' 'Soup-XPath' 'Soup-Help' ). ]. ]. On Sun, Dec 17, 2017 at 6:53 AM, Eno <tgkuo1(a)gmail.com> wrote: > Sure, it's a great news that the leader could give me a hand. > > I came from Dolphin, not acquainted with pharo configuration, though I knew > a lot that it could automize the loading and update. > > It depended upon Magritte3, Sandstone, and my packages. > > The store directory need to be changed in other's new image, currently, I > set it fixed inside the method, MacOSResolver>>store, > WindowsResolver>>store. > > On new installed image while running up via wordmenu, a new db file need to > be created from the tool icon. > > > Thanks. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Dec. 17, 2017

Re: [Pharo-users] FLSerialization>>analysisStep too slow?

by Stephane Ducasse

On Sun, Dec 17, 2017 at 6:47 AM, Eno <tgkuo1(a)gmail.com> wrote: > Well, it is just my intent to place related playgrounds, doc, help, and > classes/methods, mophic, tool browser etc into domain object dbs of > topics/playgrounds trees while exploring the image and studing/writing > packages. can you explain how it is working (not the implementation) but the idea. Because you have living objects so why putting them in a dbs? > > It's just a convenient help and an working enviornment I made specifically > by my interest, not meant to replace the current IDE, Sure > using the tricks that > the morphic browser would somehow integrate inside to glamour browser. > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Dec. 17, 2017

Re: [Pharo-users] Pharo Launcher name

by Mariano Martinez Peck

I also find having it called Pharo quite disturbing. PharoLauncher should be much better. Something that also disturbing is to see the same icon as all my pharo images / VMs. It would be much better if aside from having a different name, it could have a different icon. Cheers, On Sun, Dec 17, 2017 at 2:55 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > I agree with you and we should rename it PharoLauncher. > > Stef > > On Sun, Dec 17, 2017 at 12:32 AM, Glenn Hoetker <ghoetker(a)me.com> wrote: > > I love the Pharo Launcher. But, I find it confusing to have an > application > > called âPharo.appâ. Nothing in that name suggests it is a launcher. It > is > > also very confusing to have an application called âPharo.appâ next to one > > called âPharo6.1.appâ when they are very different things (at least from > a > > users perspective). > > > > Has changing the name of the Pharo Launcher to âPharo Launcherâ ever been > > considered? > > > > Just a thought. Most of all, thanks for the wonderful tool. > > > > Glenn > > -- Mariano http://marianopeck.wordpress.com

Dec. 17, 2017

Re: [Pharo-users] Pharo Launcher name

by Stephane Ducasse

I agree with you and we should rename it PharoLauncher. Stef On Sun, Dec 17, 2017 at 12:32 AM, Glenn Hoetker <ghoetker(a)me.com> wrote: > I love the Pharo Launcher. But, I find it confusing to have an application > called âPharo.appâ. Nothing in that name suggests it is a launcher. It is > also very confusing to have an application called âPharo.appâ next to one > called âPharo6.1.appâ when they are very different things (at least from a > users perspective). > > Has changing the name of the Pharo Launcher to âPharo Launcherâ ever been > considered? > > Just a thought. Most of all, thanks for the wonderful tool. > > Glenn

Dec. 17, 2017

Re: [Pharo-users] Athens error

by Igor Stasenko

i think it will help more if you reveal the full stack trace with actual exception.. IIRC you can do it by clicking on errorneous morph and in its menu pick the stack trace. On 16 December 2017 at 23:29, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi, > > With DrGeo built on image Pharo7.0-64bit-e41f921 Athens error shows up on > the canvas (screenshot). > > The drgeo dev. environment based on the older Pharo7.0-64bit-f82fc36 image > does not have this error with the same VM. > > The DrGeo build removes some pharo package but it is unlikely to produce > such error, or so? > > -- > Dr. Geo > http://drgeo.eu > > -- Best regards, Igor Stasenko.

Dec. 17, 2017

Pharo things analog reads ?

by Steven Costiou

Hi, For what i know, raspberry pi boards cannot read analog sensors (which are the most interesting imo), except by connecting to some kind of bridges or to Arduino boards. In the PharoTHings code i see that there are Arduino classes, and also it is based on wiringpi and wiringpi provides support for i2c which is needed to connect to an Arduino and perform analog reads. I'm exploring the wiringpi doc to see if there is an example for that, but in the meantime, would someone already have an example of analog reads with PharoThings, with working code (even simple) ? Steven.

Dec. 17, 2017