2015-07-31 12:55 GMT+02:00 Esteban Lorenzano <[email protected]>: > > On 31 Jul 2015, at 12:35, Nicolai Hess <[email protected]> wrote: > > > > 2015-07-31 12:26 GMT+02:00 Esteban Lorenzano <[email protected]>: > >> 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. > > > why? can’t you just ignore the old ones? I do not understand :( >
For example, in the current effort to replace PluggableTextMorph with Rubric, how do you make sure to use *only* rubrics API and methods and not the others copied from the old Text API? *Every* change we make for, for example styling or keyboard handling, has to be done for *both*. > > Esteban > > > > > >
