On 21/10/14 14:20, kilon alios wrote:
I may have but then halos have been abandoned in pharo at least functionality wise ,
Why are you saying that. You can get halos on any morph, just halos do not show up when you do not want them.
I have not seen any improvement to them from when I started using Squeak 2 years ago and if I remember there were once a time you had to enable them in pharo settings.
Did you ever look at the code of Halos? Halos are not defined per Morph but in a global tables. So we started to clean them.
Also both a gui builder for squeak and another for pharo have been abandonware . So it looks pharo is not doing well on GUI front especially when it has to compete with gui designers in visual basic, visual studio, QT, GTK and many more. Do you think that spec is nothing in terms of dev. Give me 1/1000 of the ressources put on one of this project and we will have a real UIBuilder.
Stef
On Tue, Oct 21, 2014 at 2:01 PM, Ben Coman <btc@openinworld.com <mailto:btc@openinworld.com>> wrote:
kilon alios wrote:
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.
I think you misread it. The key word is the "implementation" sucks. It seems Bloc is cleaning the implementation, not removing the functionality.
-ben
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 <mailto:stepharo@free.fr> <mailto:stepharo@free.fr <mailto: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... <http://web.media.mit.edu/%7E__jmaloney/papers/__DirectnessAndLivenessInMorph...>
<http://web.media.mit.edu/~jmaloney/papers/DirectnessAndLivenessInMorphic.pdf <http://web.media.mit.edu/%7Ejmaloney/papers/DirectnessAndLivenessInMorphic.pdf>>). I also wrote http://stackoverflow.com/a/__4410189/424245 <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
<http://forum.world.st/Spec-Understandability-tp4778370p4785597.html> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.