Re: [cdt-dev] [DSF] FinalLaunchSequence extensibility

[Mikhail Khodjaiants <mikhailkhod@xxxxxxxxxxxxxx>]

I like this option. In addition I would suggest:
   - move the current step classes from FinalLaunchSequence into a utility class
   - add an abstract super class for FinalLaunchSequence with abstract
getSteps() method

On Wed, Jul 7, 2010 at 12:00 PM, Pawel Piech <pawel.piech@xxxxxxxxxxxxx> wrote:
> Another option would be to add a a Step.getID() method which would return an
> optional identifier for the step (Step is an abstract class so this would be
> a backward compatible change). The deriving class could override
> Sequence.getSteps() and insert its own steps into the sequence in front of
> or after a step with a known ID.  getSteps() is called many times, but it's
> assumed to be static, so the deriving class can safely call the super-class
> once and then cache the modified array.
>
> Cheers,
> Pawel
>