[Pharo-project] Hallo Pharoers.. namespaces in the system level ?

Schwab,Wilhelm K bschwab at anest.ufl.edu
Mon Oct 11 11:49:23 EDT 2010


I'm certainly no expert on DST, but I will gladly help where I can.  You're starting a PhD program?  Is Stef your advisor?  That would put you in good hands.


From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Nick Papoylias [npapoylias at gmail.com]
Sent: Monday, October 11, 2010 11:43 AM
To: Pharo-project at lists.gforge.inria.fr
Subject: Re: [Pharo-project] Hallo Pharoers.. namespaces in the system level    ?

I am currently concerned with remote programming (debugger, browser, compiler e.t.c) in Pharo from one image (or environment) to another, so that this infrastructure can be used in the field of autonomous robotics to ease the development cycle.

So we should definitely exchange ideas ! Cause there surely is more than one way to go (plain sockets and API, rST, remote SystemDictionary and environment, to name a few..)

We should keep in touch !


On Mon, Oct 11, 2010 at 5:16 PM, Serge Stinckwich <serge.stinckwich at gmail.com<mailto:serge.stinckwich at gmail.com>> wrote:
2010/10/11 Nick Papoylias <npapoylias at gmail.com<mailto:npapoylias at gmail.com>>:
> Hallo to all,
> I am starting my Ph.D on 'languages and environments for autonomous
> robotics' -- and pharo will be a huge part of it.

Hi Nick,

Great to see that another guy will work in the domain of embedded
systems&autonomous robots with Smalltalk !

I already talked with Noury or Luc about that. This is really
important to share code as we are a small community, especially code
to interface with existing robotics systems like ROS, OROCOS or
Player/Stage. I will start soon to work on how to integrate Smalltalk
with ROS: http://www.ros.org/wiki/

Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam
Every DSL ends up being Smalltalk

Pharo-project mailing list
Pharo-project at lists.gforge.inria.fr<mailto:Pharo-project at lists.gforge.inria.fr>

More information about the Pharo-dev mailing list