11 Apr
2013
11 Apr
'13
9:09 a.m.
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.
that you can load it and that you do not have to wait a year.
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.
This is a bad idea. Why do we have metacello for then?
If roassal uses athens then it should load it, not moose.
Stef
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev