[Moose-dev] Re: About roassal design points for scalability if it will use athens for real

Because if there is only one coordinate system, then zooming in and out accumulate floating point errors. I am pretty sure Cairo has a translation mechanism under the wood. Because we live by having Roassal and all our tools cross-platform. Focusing only on Pharo means that we cannot pay engineering work anymore.

We are excited by the perspective to use Athens more. We can now fully rendering using Athens, without having disrupted our ability to be cross-platform. We plan to use Athens more, but we cannot "go faster than the music". As fas as I have seen, Athens is usable since last month,

when Igor advertised his tutorial. During that month we made Roassal perfectly work on Athens. So yes, we will use Athens more, but we cannot do more than what we are doing right now. I agree this is not optimal. This part of Roassal went through some period of try and adjust if I remember correctly. Having a solution based on matrixes is indeed much better. This is what the hierarchy looks like: <Screen Shot 2013-05-06 at 2.21.49 PM.png> This hierarchy is rather stable since nobody asked for more extremity shapes. Theses classes are very short and easy to understand. Probably code can be refactored out since they contain duplication. We will work on that on some point.

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