I would like to start adopting Athens behind Roassal.
I believe there already is a binding. The question is what keeps us from adding Athens as
a dependency to RoassalMorphic?
Well... The way I see this is slightly different. Athens should be part of the runtime
(i.e., included in Pharo) and not use as a library. I am not sure what we will gain to
consider Athens as a separate Library.
The Roassal<-->Athens bindings works well I think. We haven't spotted any
problem. Just load Athens before loading Moose while Athens is not part of Pharo.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel
http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.