>
> You are very very right. We indeed do not want to introduce all these classes.
>
> Your email made me think about something: rewriting Roassal from scratch, but
> putting the core notions brought by Athens at the center of Roassal.
May be you should a controlled experience to see but indeed
> What do you mean? Athens is in Pharo 3.0 by default. We are no longer loading
> it manually. You can safely invest all your energy in Athens :).
:-)
I will
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~
Hi,
On Mon, Nov 18, 2013 at 9:44 PM, Alexandre Bergel
wrote:
> Hi Stef,
>
> Your email made me think a lot.
>
> > But in roassal you do not have the concept of a polylines?
>
> Actually no, but it is likely that we should. A general way to defines
> polygons is the way to go.
>
> > I do not get
Hi Stef,
Your email made me think a lot.
> But in roassal you do not have the concept of a polylines?
Actually no, but it is likely that we should. A general way to defines polygons
is the way to go.
> I do not get why you want to pollute Roassal with SVG names.
> If you introduce the notion
