Thanks Torsten. This is a great write up.
I think there is real opportunity here, someone is introduced to one
thing new (a Pi), they are receptive to being introduced to a second
new thing (Pharo) at the same time. And often it will be an
individual decision that doesn't need to compete with corporate
doctrine to use Java or Microsoft - but once they are exposed, usage
may drift back into their corporate work.
Maybe the next book could be: Pi/BeagleBone + Pharo + PharROS +
Phratch + some accessories + a bit of electronics design.
btw, a small grammar correction...
> Now we want that the Pi starts this command
Now we want the Pi to start this command
cheers -ben
On Mon, Oct 26, 2015 at 4:47 AM, Torsten Bergmann <astares(a)gmx.de> wrote:
> I wrote a small article on Medium on how to setup the Pi
> with a touch screen and Pharo:
>
> https://medium.com/@astares/pharo-pi-9eef257b6a21#.gw72pe7uy
>
> Hope one or the other might be interested.
>
> Have fun
> T.
>
>> > we need to write a script to delete all the wrong methods.
>>
>
> I inspected the failing lint rule and executed on the dictionary:
>
> self keys do: [:classSymbol |
> (self at: classSymbol) do: [:selector |
> classSymbol asClass removeSelector: selector.
> ]]
>
> resulting slice is committed:
> https://pharo.fogbugz.com/f/cases/16254/
>
Marcus we should NOT use asClass in the system.
It is a bad concept because the environment is not explicit.
It is a plague and we will fight it when we will want a real "remote"
environment.
Stef
