Hi Stef, Thanks for these questions. See some replies inline and we will also create threads with the larger topics to get people more engaged.
> On Jan 25, 2017, at 9:32 AM, Stephane Ducasse <[email protected]> wrote: > > Hi bloc/brick guys > > I was a great talk. I had to run because I forgot my appointment to the > doctor. > Now some points > > - first a meta point: we should check how we can get more people following > the talks. > > Now related to bloc/bricks > > - we should pay really attention to the maintenance and deployment of the > external libraries (I could ****never**** install GTK on my mac using darwin. > Sure you can experiment but I think that bloc without a widget layer is a > nice stuff but not usable. Definitely. The goal here is to get something that works without problems. GTK is an experiment only at this point to see how flexible we really are on the backend side. Moz2D is another problem that I will detail in a separate email. About Brick, see the end of the mail. > - what is the oldest machine it is working? This is an interesting question. One of the cool things about Moz2D is that it is actually another layer on top of concrete rendering backends while still being fast. The concrete rendering is flexible and decided based on the configuration of the machine depending on things like OS or hardware acceleration availability. Given that this engine is at the core of Firefox and they also have to address the problem of various hardware we are in a reasonable position. Nevertheless, it would be very cool to have people test this assumption on old machines. I think Thierry was saying that he has an old machine :). @Thierry? > What is the entrance barrier in terms of cost? Do you have another issue in mind beside the one above? > - So since you are basically two where is the roadmap? What is your > visibility in terms of % of your time on the project because at the end of > the day you should earn money. Let’s postpone this discussion for a bit longer. > - The question of the patterns used to build the widgets is important. The > question of how to validate it for real is also important. Yes, definitely. The effort did not get at that point. Bloc went through an amazing journey and it got refined multiple times by exercising it with rather crazy ideas such as effects, composition, layouts and now we think it reached a point in which the main structure is stable. I am sure we can still find smaller points to refine but the overall structure looks quite robust now. So, the next point is definitely Brick. > - Do you plan commenting/cleaning categorisation for real? I still do not get > how you can design something without writing the assumptions of the design > into class comments. > Then with such systematic lack of comments you cannot benefit from the "no > broken window effect". Now this is more if I see a comments it is either old, > bad or useless "I'm an abstract class". At least it was like that the last > time I checked. And they are certainly many many concerns that are hidden > everywhere and are undocumented. Yes. This is a focus point. Right now, there are assertions in the code for pre-conditions, there are tests and there are examples. The documentation is less advanced, but it is a focus point. For example, the new editor work is commented quite thoroughly and these comments will start to appear through the rest of the infrastructure. But, it would be very cool to have more people to start asking questions as this will help us drive documentation. > - How do you want to get people involved? To me this is totally unclear. > Especially with the previous point in mind. I mean for real not just "oh yes > we need users” I think it is hard to get people involved without providing some benefit. As you noted above, without having working widgets, there is almost no value. That is why it is critical to get to Brick, and once we will get there the feedback will come. It was really hard to get to the state of current Bloc. Glenn and Alex did a really amazing job especially if you look at how many times they iterated over the details and put up with that uncertainty. But, the results are quite incredible and now we can shift our focus to Brick. Now, Brick worked in several incarnations, the last ones being done by Glenn. And the code is there, but the blocker was text support. That is why we had all this investment in Moz2D (the only reason why we have the patching is because of the text support) and in the editor. It was not clear at all that the idea of representing a text as a plain layout of elements will work, but since a week or so we know that it does and now we can commit to it. So, the next focus is to get the editor working and then we will iterate on that. Of course, the patterns of how we compose widgets to models is important, too and this will be on focus. MVC/MVP are options, but I am also interested to see how we can get reactive programming closer to the widgets. Cheers, Doru > Stef > > > > > On Tue, Jan 24, 2017 at 5:00 PM, Esteban Lorenzano <[email protected]> > wrote: > this is going to start now :) > >> On 24 Jan 2017, at 14:03, Esteban Lorenzano <[email protected]> wrote: >> >> Hello, >> >> We will handle the techtalk as latest one: One video streaming and >> questions/discussion over our discord channel. >> So here are the links: >> >> stream: https://www.youtube.com/watch?v=fvpfr6OJ0mM >> discord: https://discord.gg/88sbn83 >> >> See you there in 3hs! >> Esteban > > -- www.tudorgirba.com www.feenk.com "No matter how many recipes we know, we still value a chef."
