Re: [Gzz] Encapsulating enfilade/string matching in CellTexter?

[Tuomas Lukka]

> Hm. Would it work to simply use different characters for each special span,
> so that you could recognize which one was which? With the 6000-odd
> Java-accessible 'custom' characters in Unicode, there might be enough room 
> for that...
> dunno.

Uhhmmm, no. YUCK.

> > Also, the problem with using setText() is that you don't really know
> > where the text came from; you should only use setText if you're setting
> > it from scratch.
> 
> I don't agree. What setText() implies is that you can't give xanalogical
> addresses for the text-- for example, when a user has pasted plain text into 
> the
> cell. In these cases, I believe the matching to be appropriate.

No, the opposite: you have no idea from where the user pasted the words
so matching them and claiming that these are the words that mr. X wrote
on 27.4.2004 is not right.

The point is that the content may come from a different cell, a different
application, anything. Making a Xanalogical transclusion where you're
not sure there is one is not right.

With ExtEdit you're pretty sure you know that the user *started* with
the content and edited it so it's reasonably ok to say that it has
something of the same...

        Tuomas