For embedding morphs into text, there's a bit more than i currently did -
event handling.
Right now, morphs are used to simply render them in-place, and they even
not added as a submorphs, therefore no way to deliver any events to them
without big troubles.
The way how text layout builds (dynamically) poses certain problem on this,
since it requires adding/removing submorphs depending whether they visible
or not, as well as making sure their position are conform with text layout,
and morphic model..



On 27 August 2014 11:28, stepharo <[email protected]> wrote:

> Hi sean
>
> Thanks for this mail!!!!
>
> About bloc
> ---------
> I discussed with alain about this point at ESUG.
>     Alain would like to finish the handlers and a couple of other points,
> clean everything and release a first version.
> The problem is that alain is often doing trial and changes.
> Here is where I think you can help:
>
>     - turn some of the example for the layouts into tests
>     - start to clean/revisit some basic morphs so that we can turn them
> into bloc counterparts easily.
>            - I started to look at buttonMorph*
>            - I started to rewrite MenuMorph because it is full of old
> code. I would like to remove the direct manipulation because
>             it adds a lot of problems.
>     If you want to join let me know.
>
> About TxText
> ------------
>     - Igor added morphs in text at ESUG and he was revisiting it yesterday.
>     - we should make sure that the configuration is loading in 40
>             -now mocketry is loading in 40 so the configuration of TxText
> should be working.
>     - we should check the current use of TextMorph and friends and use
> TxText
>
> Stef
>
>
>
>
> On 27/8/14 01:48, Sean P. DeNigris wrote:
>
>> The most important items on our IU Experience agenda - Tx and Bloc - are
>> totally reliant on two (brilliant, talented...) programmers while the rest
>> of the community hopes and waits. In no way to I lack appreciation for
>> Alain
>> and Igor's efforts, but this does not seem like a robust or efficient use
>> of
>> our manpower... So, I guess what I'm really asking for both projects is -
>> how can we help?
>>
>>
>>
>> -----
>> Cheers,
>> Sean
>> --
>> View this message in context: http://forum.world.st/Pharo-
>> Development-Robustness-was-Why-Bloc-tp4774980.html
>> Sent from the Pharo Smalltalk Developers mailing list archive at
>> Nabble.com.
>>
>>
>>
>
>


-- 
Best regards,
Igor Stasenko.

Reply via email to