not to say about efficiency. I've been doing some cpu cycle tests. Rendering a 1600@1200 gradient to world canvas (repeat each 50ms): ~90% cpu consumption Same test, but sending it direct to window canvas using bridge: ~40% cpu consumption so... we are in the good path :) Esteban On Apr 16, 2013, at 8:28 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 16 April 2013 19:09, kilon <thekilon@yahoo.co.uk> wrote:
And you guys then say that pharo is not macos first citizen
ha
ha
and
ha
I am a macos user , I love my imac and macos, but my vote goes to cross platform.
Still another great library that is more than welcomed, definitely cant do any harm ;)
By saying that we don't need Cairo on MacOS i meant following:
Athens designed to support multiple backends. It is out of question, that better to use most suitable backend, available on current platform.
But apart of it stays ObjC bridge. Which would allow us to speak with ObjC-runtime (and Mac VM using it) directly.
-- View this message in context: http://forum.world.st/Fwd-do-you-know-what-is-this-tp4681962p4681975.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Best regards, Igor Stasenko.