already answered: you are just scared :) 1) NB does not need to be used in 2.0... is just there, as any other package... it just will not work in iOS, but the image will be ok 2) Athens will replace old graphics infrastructure, but not in 2.0 and certainly, that should not be a problem for use it in iOS in the future (since athens is a framework that uses cairo, but can use other backends, like the old balllon3d) Esteban On Feb 19, 2013, at 3:08 PM, "phil@highoctane.be" <phil@highoctane.be> wrote:
There is a potential problem for me with 2.0:
It includes NativeBoost/Athens....
As I am targeting iOS running on a StackVM, am I stuck to 1.4? Is there anything to do to ensure that Pharo 2.0 is not a dead end for such developments?
Maybe this is just me scaring myself... There is value in an all software Pharo stack. Which is why I went that way in the first place.
Phil