I propose some modifications to the Transcript as a (singleton) class, and revert to the use of TranscriptModel.
See the latest post on 3948: Transcript and ThreadedTranscript needs to be merged. Fernando On Wed, Apr 6, 2011 at 10:39 PM, Igor Stasenko <[email protected]> wrote: > On 6 April 2011 20:24, <[email protected]> wrote: >> Em 06/04/2011 09:07, Igor Stasenko <[email protected]> escreveu: >>> > On 6 April 2011 13:54, Fernando Olivero <[email protected]> >> wrote: >> >>> > Hi Stef, i will as an initial step take Igor's suggestion and make >>> > Transcript a global wich points to an instance of TranscriptModel >>> > ( the new name i propose for the current class taken from CUIS). >>> > I still believe that composition is better then inheritance for >>> > handling different behaviors of the Transcript, so i argue against >>> > making it a subclass of WriteStream and making it polymorphic with >>> > a write stream instead. >>> > >>> That's totally not my concern. As long as thing which sits there >>> responds to writestream protocol , i don't care about rest. >>> >> >> Would it make sense then to lift the methods from {write}stream and >> put then in a Trait so the composition is made through reuse of code? >> >> My 0.0199999.... > > hehe.. yes, but if to follow this road every time you need to do small > improvement, > then at some day you will discover that you rewriting whole system > from scratch :) > >> >> -- >> Cesar Rabak > > > -- > Best regards, > Igor Stasenko AKA sig. > >
