I personally think Denis has raised an important remark. Fuel responsibility here should stop at supporting post materialization actions. So...I do agree that this code is ONE particular usage of Fuel and such code should likely be packaged with the tool and not with Fuel .
On Mon, Dec 19, 2016 at 2:41 PM, Tudor Girba <tu...@tudorgirba.com> wrote: > Hi, > > > On Dec 19, 2016, at 6:34 PM, Denis Kudriashov <dionisi...@gmail.com> > wrote: > > > > Hi. > > > > 2016-12-19 18:08 GMT+01:00 Max Leske <maxle...@gmail.com>: > > I suppose that functionality should be resolved via FuelPlatform. > Something like > > > > FLPlatform current > > openDebuggerOn: Processor activeProcess > > context: materialization root > > label: 'External stack' > > > > Is it really nice way to do it? I mean why we force system to open > debugger when serialised context is loaded? > > IMHO it is responsibility of tool to decide what to do with object. It > should be good extension for file browser or inspector. Tool will detect > that it work with context and will allow to debug it. > > > > Post materialisation action is nice feature but for me it is overused > here. > > Looking from far away (I did not check the code) I kind of agree with this > point of view. If we make it the responsibility of the tool, the design > becomes a bit more object-centric. To me it looks like the Platform tries > to know more things that are not about Fuel. > > Cheers, > Doru > > -- > www.tudorgirba.com > www.feenk.com > > "The coherence of a trip is given by the clearness of the goal." > > > > > > > -- Mariano http://marianopeck.wordpress.com
