flex-dev mailing list archives

> I.e. just more convenient 'Send Commands To Flex Debugger' action? I'm
> afraid this will be a feature for 2 people in the world: you and me.
> Most of developers do not care about underlying tools.
I'm pretty sure that in some scenarios, for worker that generate first impredictable results
and then for some, later the code path fails, the user if he has 10+ workers, won't want to
go through all workers instances but will want to filter them as soon as he has met the failling
impredictable situation, this couldn't be easily or even not at all solved by unit tests,
the reason why being able to debug at this level could be important, ok, it seems an edge
case, but this case will be met I'm sure in complicated applications.
It is not a feature for me to play with FDB through IntelliJ, the goal with this feature is
to find an easy way to debug at worker instance level.
Given this feature exists already and could be more user friendly and not hiden by default
made me thought it was easy to implement / integrate in the Debug/Console view, if not, I
will use the trick you gave me if I met this kind of scenario but what about other people
they don't know the trick ?
Do I make sense ?
Frédéric THOMAS
> Date: Thu, 29 May 2014 18:23:54 +0400
> From: alexander.doroshko@jetbrains.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
>
> I.e. just more convenient 'Send Commands To Flex Debugger' action? I'm
> afraid this will be a feature for 2 people in the world: you and me.
> Most of developers do not care about underlying tools.
>
> On 29.05.2014 17:46, Frédéric THOMAS wrote:
> > Not sure how much extra work it would cost to add this feature as default in the
form of a command line input at the botton of the debug/console view and the output in the
main part of the console view but it would be a "very nice to have" to interact directly with
FDB and give us the possibility to play at worker instance level.
> >
> > Frédéric THOMAS
>