For me there is nothing that sucks more than having to type code to create a GUI in year 2014....�� This a strong reason why I miss my days coding in Delphi so much.��

at least halos try to compensate for that partly.I love halos please dont remove them, good thing they suck for you, they rock for me. The fact that I can close a problematic morph that refuses to exit, by bringing its halo and clicking x , is enough reason to keep them around for me.��

I love the idea of halos the idea that you can hack any gui with simple actions, with no code invloved, ��and resynthesised it is definetly something I find immensely useful though the implementation of halos is far from ideal.��

On Tue, Oct 21, 2014 at 9:18 AM, stepharo <stepharo@free.fr> wrote:

Note that halo implementation sucks!
In Bloc alain clean it and he is able to plug halos and package them cleanly.

In addition in Bloc he took the decision not to implement for now the direct creation of certain widget because
this kind of feature leads to spaghetti dependencies.

Stef

On 20/10/14 20:35, Sean P. DeNigris wrote:

Ralph Boland wrote

I am not in the habit of using halos, not really sure what they are for.
But your description implies they are quite useful.
What does�� "bring up halos on and inspect a button to see how to duplicate
its action" mean?�� Could you please describe in step by step detail.

Hi Ralph! I think the best way to understand why Morphic is revolutionary is
to read the papers of its creators (e.g.
http://web.media.mit.edu/~jmaloney/papers/DirectnessAndLivenessInMorphic.pdf).
I also wrote http://stackoverflow.com/a/4410189/424245 which should give a
taste and also answers your question more directly. HTH.

-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Spec-Understandability-tp4778370p4785597.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.