Hi, Our team is working on a couple of projects that are relevant for the core of Pharo, namely GT and Bloc/Brick. At ESUG we were asked by several people, and Stef in particular, to make the progress on these projects more transparent. To this end, we will start two streams of signals: - fine grained info bits on out Twitter account (several times a week): https://twitter.com/feenkcom - a less often but regular (probably every 2 weeks) activity log message sent to this mailing list
Please let us know if you see an issue with this. In the meantime, let’s start. Bloc: - Over the past couple of weeks Alex worked on transformations and measurements in the core system. It turns out that there was room for quite a number of performance optimizations and for making the system more debuggable. - At the low level, this involved adding matrix and vector support. https://twitter.com/feenkcom/status/923123870537863168 https://twitter.com/feenkcom/status/916300180848349185 - At a higher level, it implies keeping track of measurements https://twitter.com/AliakseiSyrel/status/915203525931622400 - And of transformations: https://twitter.com/feenkcom/status/919603739656417281 https://twitter.com/feenkcom/status/917116164484096001 - The BlScalableElement is now working properly GT Examples: - The current repository with unary-based examples is at: https://github.com/feenkcom/gtoolkit-examples - We now have a runner in the inspector that allows us to both see the source code and run and play with the resulting object: https://twitter.com/feenkcom/status/923210686204989442 - Andrei made the “after” behavior to work with unary examples. Cheers, The feenk team -- www.tudorgirba.com www.feenk.com "Being happy is a matter of choice."
