On 31 Jul 2015, at 12:35, Nicolai Hess <nicolaihess@web.de> wrote:



2015-07-31 12:26 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com>:
Hi,

the idea is to replace all old text classes usage, then remove them (and Rubric will became the unique text editor in Pharo)
so��� I *think* (not sure about it), the duplication of classes is in this case on purpose, and a temporal thing.

But the duplication makes it *really* difficult to clean  up Rubric from the old TextEditor API.



Yes, we need to wait 

1) replace all users of the old 
2) remove old
3) clean up

The reason for the duplication is that after 1) you can just delete the old editor related code, as all needed parts
are in the new package already.

(At least this is how I understand it)

Marcus