One of the problem is that the Morphic replacement will probably be
less than Morphic was (or was intended to be) :(
you mean less messy
Surely.
I think that you did not look at Bloc because we have already a lot
there and much nicer.
You'll probably tell me that for the kind of work
Hi Alain
thierry did not look at Bloc :)
We see it :)
Stef
Le 24/3/15 16:13, Alain Plantec via Pharo-dev a écrit :
Le 25/3/15 06:29, Ben Coman a écrit :
One of the things that drew me to do the Delay refactoring, is simply
that I could. That is, I was amazed that I could dig so deep so
easily, see a path to improvement and effect change at a fundamental
level. Excepting complexities with the CI due to
2015-03-24 15:16 GMT+01:00 Esteban Lorenzano esteba...@gmail.com:
On 24 Mar 2015, at 14:29, kilon alios kilon.al...@gmail.com wrote:
There is a big diffirence between Morphic and the other. Morphic is a full
solution and mature one as well. The others , with the exception of Bloc ,
try to
---BeginMessage---
Hello Esteban,
Most probably is because you are doing double work: you draw with Athens, but
you convert it to a Form to display it (and a Form is a Morph using
DisplayPlugin).
I can ensure you that if you use Athens directly with SDL2 (an example I can
share with you
---BeginMessage---
Hello Thierry,
Le 24 mars 2015 à 15:24, Thierry Goubier thierry.goub...@gmail.com a écrit :
One of the problem is that the Morphic replacement will probably be less than
Morphic was (or was intended to be) :(
why do you think so ?
Cheers
Alain
You'll probably tell
On 24 Mar 2015, at 14:29, kilon alios kilon.al...@gmail.com wrote:
There is a big diffirence between Morphic and the other. Morphic is a full
solution and mature one as well. The others , with the exception of Bloc ,
try to wrap things up or offering better solution to some areas.
The
There is a big diffirence between Morphic and the other. Morphic is a full
solution and mature one as well. The others , with the exception of Bloc ,
try to wrap things up or offering better solution to some areas.
The one thing I don't understand is why improving Morphic or even
redesigning it
And well… I think Nicolai is right in a point (not the fault of Brick, btw):
current status is far from ideal:
- we have Morphic, and it’s upcoming replace, Brick (but Brick is not in the
image, so the pain there is less)
- we have Spec to support our tooling.
- we have Glamour to support…
On 24 Mar 2015, at 14:23, Thierry Goubier thierry.goub...@gmail.com wrote:
Hi Esteban,
2015-03-24 13:56 GMT+01:00 Esteban Lorenzano esteba...@gmail.com
mailto:esteba...@gmail.com:
And well… I think Nicolai is right in a point (not the fault of Brick, btw):
current status is far from
Hi Esteban,
2015-03-24 13:56 GMT+01:00 Esteban Lorenzano esteba...@gmail.com:
And well... I think Nicolai is right in a point (not the fault of Brick,
btw): current status is far from ideal:
- we have Morphic, and it's upcoming replace, Brick (but Brick is not in
the image, so the pain
Yes, we do not have the replacement now, but we have never had so much
investment and will around the UI as we have now. We do not know at this
point what is the better way, we do not know the exact roadmap because it is
more than just a matter of implementation. But, I know that the kinds
Tudor , I am only amazed how much you guys accomplish with so limited
resources. I may not agree with some of the choices but I am very happy
with the progress Pharo is making and glad I stick around.
If the community is not ready for a roadmap , so be it. You will be ready
when you will be
I have to confess I did not understand this obsession of implementing
everything in Pharo when I joined coming from python. But now I find this
obsession too infectious to resist :)
That's why its impossible to convert people via HN and Reddit. Like skydiving
(I imagine), it seems like a
Hi Kilon,
The situation is like this. For quite a while we did not have enough
expertise in this community to build serious UI frameworks that can work.
In the meantime we learnt a lot. GT is not just a couple of windows. It's
an experiment of building something that does not exist anywhere else,
] Which one to use? [WAS: Re: GLMBrick whats next?]
Hello Thierry,
Le 24 mars 2015 à 15:24, Thierry Goubier thierry.goub...@gmail.com a
écrit :
One of the problem is that the Morphic replacement will probably be less
than Morphic was (or was intended to be) :(
why do you think so ?
Because
Hi,
2015-03-24 15:27 GMT+01:00 Tudor Girba tu...@tudorgirba.com:
Hi,
I think I do not understand this point. Why do you say that the future
solution will be less than Morphic?
Because we're driving it with uses which are less than Morphic requirements
were.
Because you don't need Morphic
---BeginMessage---
Le 24 mars 2015 à 15:56, Thierry Goubier thierry.goub...@gmail.com a écrit :
2015-03-24 15:39 GMT+01:00 Denis Kudriashov dionisi...@gmail.com
mailto:dionisi...@gmail.com:
2015-03-24 17:36 GMT+03:00 Thierry Goubier thierry.goub...@gmail.com
Hi,
On Tue, Mar 24, 2015 at 3:24 PM, Thierry Goubier thierry.goub...@gmail.com
wrote:
2015-03-24 15:16 GMT+01:00 Esteban Lorenzano esteba...@gmail.com:
On 24 Mar 2015, at 14:29, kilon alios kilon.al...@gmail.com wrote:
There is a big diffirence between Morphic and the other. Morphic is a
2015-03-24 15:39 GMT+01:00 Denis Kudriashov dionisi...@gmail.com:
2015-03-24 17:36 GMT+03:00 Thierry Goubier thierry.goub...@gmail.com:
IMHO, Rubrics, just from it's layout approach, is already a step backward.
What you mean by this? What's wrong with Rubric layouting?
Padding -
2015-03-24 16:43 GMT+01:00 Aliaksei Syrel alex.sy...@gmail.com:
The same in Brick:
GLMButtonBrick new
marginLeft: 10;
text: 'Parse';
vAlign: #center;
hSpaceFill;
openInBrickWindow
Yes, I agree - using composition for margin/padding/aligning is much more
simple, readable,
---BeginMessage---
Hello all,
I think you should consider what is mature and what is in the image now.
now we have Spec with Morphic, Morphic without Spec as an alternative, GT Tool
framework (with Brick), Glamour.
Regarding text editing we have Rubric.
My fault, someone (sorry I don’t
] Which one to use? [WAS: Re: GLMBrick whats next?]
Le 24 mars 2015 à 15:56, Thierry Goubier thierry.goub...@gmail.com a
écrit :
2015-03-24 15:39 GMT+01:00 Denis Kudriashov dionisi...@gmail.com:
2015-03-24 17:36 GMT+03:00 Thierry Goubier thierry.goub...@gmail.com:
IMHO, Rubrics, just from
2015-03-24 17:36 GMT+03:00 Thierry Goubier thierry.goub...@gmail.com:
IMHO, Rubrics, just from it's layout approach, is already a step backward.
What you mean by this? What's wrong with Rubric layouting?
On Mar 24, 2015, at 10:29, kilon alios kilon.al...@gmail.com wrote:
[Spec] does not support custom made GUIs which is what I want
That’s simply not true. Spec supports the embedding of whatever Morph you want
inside your GUI. So you can easily mix and match your custom components with
all
pharo-dev@lists.pharo.org
Cc:
Date: Tue, 24 Mar 2015 16:02:56 +0100
Subject: Re: [Pharo-dev] Which one to use? [WAS: Re: GLMBrick whats next?]
Le 24 mars 2015 à 15:56, Thierry Goubier thierry.goub...@gmail.com a
écrit :
2015-03-24 15:39 GMT+01:00 Denis Kudriashov dionisi...@gmail.com
On Wed, Mar 25, 2015 at 6:08 AM, Sean P. DeNigris s...@clipperadams.com
wrote:
I have to confess I did not understand this obsession of implementing
everything in Pharo when I joined coming from python. But now I find this
obsession too infectious to resist :)
That's why its impossible to
if you read my mail, you will notice that I said BOTH are on the table (and
we are actually moving oon both):
- Bloc is the redesign
- In the mean time we WORK and ENCOURAGE others to work on improve it.
Last time I asked about Bloc , I was told not to use it and instead stick
with Spec or
---BeginMessage---
I don’t get it sorry.
Padding by ten pixels to the left:
| leftMargin aParserButton |
leftMargin := Morph new
width: 10;
hResizing: #shrinkWrap;
vResizing: #spaceFill.
aParserButton :=
29 matches
Mail list logo
