Here's a wild idea (yeah, a usual disclaimer, it could've been proposed
by somebody else): use runsArray kind of deal, just like Text with
attributes. That's when real flexibility just starts!

And maybe unify Text and the StreamSequence into a single clean
framework.

bolot


On Thu, 2 Sep 1999, Andres Valloud wrote:

> Hi.
> 
> What things should this object support? Consider that lots of features
> will mean lots of index and position management overhead...
> 
> 1. On the fly removeAt: and add:readFrom:to: without losing position.
> 2. On the fly resizing of stream segments sequenced.
> 3. Support for nextPut:, enlarging the last stream sequenced when
> appropriate.
> 4. Reverse next.
> 5. Access by substream.
> 6. Any other?
> 7. A better name?
> 
> Andres.
> 
> PS: note that the method removeAt: has a little bug in the last
> changeset, it should include the line
> 
> size _ nil.
> 
> somewhere.
> 
> 
>