I took a look at GLMBrick and I am wondering what is the intent:
- a temporary solution until this functions/behavior are included in Morphic
- a layer on top of morphic without the intent to do this in Morphic any
time.
- a temporary solution until this functions/behaviors are implemented with
bl
Le 31/12/14 11:58, Nicolai Hess a écrit :
I took a look at GLMBrick and I am wondering what is the intent:
- a temporary solution until this functions/behavior are included in
Morphic
would be nice.
- a layer on top of morphic without the intent to do this in Morphic
any time.
- a tempor
Hi,
Brick was born out of necessity. It is a thin layer on top of basic Morphic
that is supposed to coexist with Morphic but not be bound by various
problems Morphic has (such as the layout). Alex Syrel built it primarily
for performance reasons and it was critical to make GTSpotter work. In the
m
Of course, I meant to say that Brick is the incremental solution, not Bloc
:)
Doru
On Wed, Dec 31, 2014 at 2:08 PM, Tudor Girba wrote:
> Hi,
>
> Brick was born out of necessity. It is a thin layer on top of basic
> Morphic that is supposed to coexist with Morphic but not be bound by
> various p
Bloc has a big future, for sure! I hope it will move Pharo to a very new
level! As Doru said, Brick was born out of necessity. More exactly because
of text resizing in Inspector. By default, if one wants to clip/resize text
in tabs she uses clippingBounds. And clippingBounds is called during...
wha
Thank you for this explanation
2014-12-31 23:47 GMT+01:00 Aliaksei Syrel :
> Bloc has a big future, for sure! I hope it will move Pharo to a very new
> level! As Doru said, Brick was born out of necessity. More exactly because
> of text resizing in Inspector. By default, if one wants to clip/resi
2015-01-06 10:55 GMT+01:00 Nicolai Hess :
> Thank you for this explanation
>
> 2014-12-31 23:47 GMT+01:00 Aliaksei Syrel :
>
>> Bloc has a big future, for sure! I hope it will move Pharo to a very new
>> level! As Doru said, Brick was born out of necessity. More exactly because
>> of text resizing
Hi,
Sorry if my reply will be too long, but I tried to summarise our experience
with Morphic/Brick and give some useful feedback or even provide ideas. Who
wants will read :)
Brick is not a thin layer anymore.
It depends on what you mean under 'a thin layer' ;) Anyway, Brick was born
out of need
Thanks for this reply, Alex.
Doru
On Mon, Mar 23, 2015 at 8:54 PM, Aliaksei Syrel
wrote:
> Hi,
>
> Sorry if my reply will be too long, but I tried to summarise our
> experience with Morphic/Brick and give some useful feedback or even provide
> ideas. Who wants will read :)
>
> Brick is not a th
--- Begin Message ---
thanks a lot for these explanations.
yep! very promising :)
I would love to see all these improvements implemented in Bloc.
> Le 23 mars 2015 à 20:54, Aliaksei Syrel a écrit :
>
> What we really want to have in Bloc is an easy way to detect that user
> clicked outside of
Hi Aliaksei,
this is a good and interesting read, especially the feedback on making
it fast (solution to some performance problems in Morphic).
However, I have the feeling that the css inspired layout syntax is a
step backward on what is/was Morphic (which is using other morphs to
constrain
2015-03-23 20:54 GMT+01:00 Aliaksei Syrel :
> Hi,
>
> Sorry if my reply will be too long, but I tried to summarise our
> experience with Morphic/Brick and give some useful feedback or even provide
> ideas. Who wants will read :)
>
Hi,
thank you, this is a really great source of information, and i
Hi Nicolai,
I am surprised by your conclusion that the current Brick implementation
disqualifies it from being part of the Core :)
Let's recap.
Brick was created to support GT. We wanted GT in the image, hence Brick is
in the image as part of Glamour. In the meantime, Brick has grown and it's
no
> On 24 Mar 2015, at 12:37, Tudor Girba wrote:
>
> Hi Nicolai,
>
> I am surprised by your conclusion that the current Brick implementation
> disqualifies it from being part of the Core :)
it was not that what disqualifies it. It is the “we will not announce it” part
:)
I mean: if it is not a
2015-03-24 12:37 GMT+01:00 Tudor Girba :
> Hi Nicolai,
>
> I am surprised by your conclusion that the current Brick implementation
> disqualifies it from being part of the Core :)
>
not the implementation, the uncertainty of its purpose - a GT private
implementation / a public framework.
>
>
>
Hi,
I think I might have misunderstood your mail :).
Tthe intention behind Brick is not to be a separate framework but an
internal tool for GT. At least not now, and at least not before we
investigate how we get to the end goal of having a vectorial canvas (hence
Bloc). Is this satisfying?
Cheer
Tudor Girba-2 wrote
> Concretely, on March 31 and April 1 (no joke :)), we have a session in
> Bern
> where Alain Plantec will join us to look into how to approach this problem
> concretely.
Given that, now I /really/ feel it would be beneficial to have the talks
recorded because otherwise you inc
There is only one talk about Bloc. The rest is like a sprint.
Doru
On Tue, Mar 24, 2015 at 2:41 PM, Sean P. DeNigris
wrote:
> Tudor Girba-2 wrote
> > Concretely, on March 31 and April 1 (no joke :)), we have a session in
> > Bern
> > where Alain Plantec will join us to look into how to approach
--- Begin Message ---
Hello Sean,
As I’ve already said, I’m currently working on a documentation on Bloc.
I’ve stopped adding new things into it (well only examples and bug fixes)
It is far from being finished and polished
https://github.com/SquareBracketAssociates/PharoInProgress/tree/master/Bl
2015-03-24 13:54 GMT+01:00 Tudor Girba :
> Hi,
>
> I think I might have misunderstood your mail :).
>
> Tthe intention behind Brick is not to be a separate framework but an
> internal tool for GT. At least not now, and at least not before we
> investigate how we get to the end goal of having a vec
All in all, you should see Brick as a pragmatic intermediary step
towards removing Morph. I agree that it can be better (what cannot
be), but I disagree we should discard GT because of it.
I did not say "discard GT" . Brick is in the image, but I don't want
to have it in the
co
21 matches
Mail list logo
