Just a point. We should definitely not throw away TxText :).

My message was that we should stop investing in the TextMorph. I suggested Rubric because it is available now and can be integrated with visible improvements over what exists.

But, TxText should be the future. Perhaps we can already commit to it for Pharo 4.0 and then we make it a goal for the whole community to get it finished. I would be supportive for such a decision.

Doru


On Wed, Jul 23, 2014 at 11:46 AM, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi,

Not yet :(. It's the first thing after releasing the current implementation of GT and Moose.

Doru


On Wed, Jul 23, 2014 at 11:22 AM, stepharo <stepharo@free.fr> wrote:

On 22/7/14 14:43, Tudor Girba wrote:
First of all: Excellent job!

About the editor: I would indeed suggest adopting Rubric as a solution for now (until the new Text widget comes around). We use it extensively in GT and I can attest that it is better than PluggableTextMorph.

doru did you loaded TxText?
and TxViewContainer example2

Doru


On Tue, Jul 22, 2014 at 2:05 PM, Marcus Denker <marcus.denker@inria.fr> wrote:

On 22 Jul 2014, at 13:57, stepharo <stepharo@free.fr> wrote:


On 22/7/14 10:41, Clara Allende wrote:
Hi guys!��
Finally the metaLink-based breakpoints are "ready". I have made some explanations on my��blog, but basically now you have the option "break here" in SmartSuggestions menu.
So it's still experimental, and even though I have some tests, it would be nice if you can test it, because I can't cover all possible use cases :)��
And any feedback is most appreciated!��

Specially, since eventually we will have several kinds of breakpoints, I would like to ask in which way would you like to choose them (a pop menu? a sublist?)

Thanks in advance!

PS: The script for downloading the code is in the blog post :P
PS2: After talking with Anne and Baptiste, things that are not there yet but I want to have:��
* a highlight on the method/messageSend where the breakpoint is inserted
* expose persistent breakpoints (it is there but the default is to halt once)
* line breakpoints (not sure when, for now the breakpoints are AST based)
* integration with TextEditor, once it is done ;)

Can you grab igor and sit with him to get this point?
Another idea would be to use the editor in Moose (Rubrik?).
Better a solution now than to wait forever for perfection���

Marcus




--

"Every thing has its own flow"




--

"Every thing has its own flow"



--
www.tudorgirba.com

"Every thing has its own flow"