Hi Stef, The log is not a replacement of the roadmap. It is only to help people see what we do live.
The roadmap and documentation are coming as well, but these are separate. Cheers, Doru > On Oct 25, 2017, at 6:45 PM, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > > Doru having a few tweets is nice but I do not think that you > communicate well around bloc. > > What I would like to get is a roadmap for Bloc V1.0. > - Here are the missing features (documentation), > - Here are where we are. > Because else it feels like Bloc will never ends. > You will argue and tell me that you experiments. But without a feature > list then > people cannot join and do not know when you get a 1.0. > > Not measuring is the best way to arrive to a point where you did not wanted. > > You see for Brick we need > Button > CheckBox > DropList > List > Table > Pane > InputField > Text > Scrollbar > Menu > And with that we can get a first Widget set. > But again without a roadmap I have some doubts. > > Stef > > > Stef > > > On Wed, Oct 25, 2017 at 6:38 PM, Stephane Ducasse > <stepharo.s...@gmail.com> wrote: >> Doru using comma for creating vectors is not really because it will >> just make the life of type inferencers more difficult. >> >> >> On Wed, Oct 25, 2017 at 5:53 PM, Tudor Girba <tu...@tudorgirba.com> wrote: >>> 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." >>> >>> >>> >>> >>> > -- www.tudorgirba.com www.feenk.com "What we can governs what we wish."
