Works perfectly now, thanks for the fix!
On 30.05.2014 15:07, Frédéric THOMAS wrote:
@Alexander
Fixed: https://issues.apache.org/jira/browse/FLEX-34346 (the compiled FDB
attached)
In a mxml file, when a inline item renderer is defined, a file id is added to
the file list of the SWF linking t
ood enough for you.
Frédéric THOMAS
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: [FDB] Integration
> Date: Thu, 29 May 2014 17:11:13 +0100
>
> I just merged the FDBWorkers branch onto the Develop branch, DO NOT DELETE
> the FDBWorkers branch, i
.doros...@jetbrains.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
>
> On 29.05.2014 19:08, Frédéric THOMAS wrote:
> > The lasted FDB: https://issues.apache.org/jira/browse/FLEX-34342 (Break and
> > Clear command should accept paths)
> Works great!
> How
the trick ?
Do I make sense ?
Frédéric THOMAS
Date: Thu, 29 May 2014 18:23:54 +0400
From: alexander.doros...@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 fo
On 29.05.2014 19:08, Frédéric THOMAS wrote:
The lasted FDB: https://issues.apache.org/jira/browse/FLEX-34342 (Break and
Clear command should accept paths)
Works great!
However I was lucky to catch one tricky regression.
If MXML file contains inline item renderer(s) then this mxml file has
more
The lasted FDB: https://issues.apache.org/jira/browse/FLEX-34342 (Break and
Clear command should accept paths)
Frédéric THOMAS
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: [FDB] Integration
> Date: Thu, 29 May 2014 16:02:43 +0100
>
> > I.e.
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.doros...@jetbrains.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
>
> I.e. just more convenient 'Send Commands To Fle
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
ive us the possibility to play at
worker instance level.
Frédéric THOMAS
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: [FDB] Integration
> Date: Thu, 29 May 2014 14:28:34 +0100
>
> Just tried it, not user friendly :-) but very nice feature to achieve my
Just tried it, not user friendly :-) but very nice feature to achieve my goal,
thanks for the trick.
Frédéric THOMAS
> Date: Thu, 29 May 2014 17:08:31 +0400
> From: alexander.doros...@jetbrains.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
>
> There's a
ommands to pass
directly to FDB ?
Frédéric THOMAS
Date: Thu, 29 May 2014 16:51:58 +0400
From: alexander.doros...@jetbrains.com
To: dev@flex.apache.org
Subject: Re: [FDB] Integration
On 29.05.2014 16:29, Frédéric THOMAS wrote:
IDE will not set/remove breakpoints per worker, only for all wor
; To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
>
> On 29.05.2014 16:29, Frédéric THOMAS wrote:
> >> IDE will not set/remove breakpoints per worker, only for all workers,
> >> this seems to be what users expect.
> > Really ? look at the Java breakpoint window, it a
On 29.05.2014 16:29, Frédéric THOMAS wrote:
IDE will not set/remove breakpoints per worker, only for all workers,
this seems to be what users expect.
Really ? look at the Java breakpoint window, it allows to set a BP for all
threads and also for a particular thread if I'm not wrong, why not for
ion, then
> 1.5 weeks of business trip to Google I/O in San Francisco.
Thanks for the info.
Frédéric THOMAS
> Date: Thu, 29 May 2014 16:20:59 +0400
> From: alexander.doros...@jetbrains.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
>
> Thanks for additional expla
Thanks for additional explanations!
IDE will not set/remove breakpoints per worker, only for all workers,
this seems to be what users expect.
Yep, there can be some headache if the same or different breakpoints are
hit in different workers, I hope I'll sort it out at IDE side.
I plan to work on
Ok great, just to be sure you not take me wrong and understand the concept,
please follow this commented FDB session:
Apache fdb (Flash Player Debugger) [build development]
Copyright 2013 The Apache Software Foundation. All rights reserved.
(fdb) run
Waiting for Player to connect
Player connected
On 29.05.2014 11:50, Frédéric THOMAS wrote:
AIR users will still have to use the DebuggableWorker class as base
class for their workers and the main app as well though.
I'm not sure we can convince all developers to rewrite their workers,
but I hope no fatal error happens if fdb fails to suspend
om
> To: dev@flex.apache.org
> Subject: RE: [FDB] Integration
> Date: Thu, 29 May 2014 08:50:12 +0100
>
> > > AIR users will still have to use the DebuggableWorker class as base
> > > class for their workers and the main app as well though.
> > I'm not sur
Just forgot to mention that in case of ambiguous partial file name
passed to the break / clear command, FDB doesn't do anything but print
an ambiguous files warning.
Frédéric THOMAS
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: [FDB] Integration
&
do:
break mx\core\DebuggableWorker.as:56
or
break mx/core/DebuggableWorker.as:56
> > I just wonder, is it easily doable to modify the Breakpoint UI like
> > what is done for Java and adding a combobox to access threads on top
> > of the Frame list ?
> Shouldn't be ex
On 28.05.2014 16:06, Frédéric THOMAS wrote:
AIR users will still have to use the DebuggableWorker class as base
class for their workers and the main app as well though.
I'm not sure we can convince all developers to rewrite their workers,
but I hope no fatal error happens if fdb fails to suspen
te: Tue, 27 May 2014 18:26:06 +0400
> From: alexander.doros...@jetbrains.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
>
> Sounds awesome!
> Trying to support original buggy fdb from closed-source Adobe AIR SDK
> was a real headache for me. Now I start thinking
depuis un mobile Samsung.
Message d'origine De : Alexander Doroshko
Date :27/05/2014 15:26
(GMT+00:00) A : dev@flex.apache.org Objet : Re: [FDB]
Integration
Sounds awesome!
Trying to support original buggy fdb from closed-source Adobe AIR SDK
was a real headache for me
Sounds awesome!
Trying to support original buggy fdb from closed-source Adobe AIR SDK
was a real headache for me. Now I start thinking about including your
fdb into IntelliJ IDEA installation or just asking IDE users to use
debugger from upcoming Apache Flex SDK.
I'll play with your fdb today/t
DebuggableWorker.as:56 (Worker 0)
(fdb) delete 3
(fdb) info break
Num Type Disp Enb AddressWhat
(fdb) quit
The program is running. Exit anyway? (y or n) y
Process finished with exit code 0
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: [FDB]
ought to let you do
without to change the active worker.
Frédéric THOMAS
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
> Date: Sun, 25 May 2014 04:01:05 +
>
> Awesome!
>
> On 5/24/14 6:12 AM, "Frédéric THOMAS" wrote:
>
uch as
>I progress.
>
>Frédéric THOMAS
>
>[1] https://issues.apache.org/jira/browse/FLEX-34332
>[2]https://issues.apache.org/jira/browse/FLEX-34333
>
>
>> From: webdoubl...@hotmail.com
>> To: dev@flex
2
[2]https://issues.apache.org/jira/browse/FLEX-34333
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: [FDB] Integration
> Date: Fri, 23 May 2014 13:46:03 +0100
>
> Hi guys,
>
> Just to tell yo
ic THOMAS
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: [FDB] Integration
> Date: Sat, 3 May 2014 19:15:23 +0100
>
> Resolved another issue [1], so, the last FDB is there.
>
> Frédéric THOMAS
>
> [1] https://issues.apache.org/jira/
Resolved another issue [1], so, the last FDB is there.
Frédéric THOMAS
[1] https://issues.apache.org/jira/browse/FLEX-34297
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: [FDB] Integration
> Date: Sat, 3 May 2014 16:49:30 +0100
>
> Hi,
>
> I j
rom: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: [FDB] Integration
> Date: Thu, 1 May 2014 14:43:51 +0100
>
> Oups, thanks, done !!
>
> Frédéric THOMAS
>
> > From: aha...@adobe.com
> > To: dev@flex.apache.org
> > Subject: Re: [FDB] I
Oups, thanks, done !!
Frédéric THOMAS
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
> Date: Thu, 1 May 2014 13:35:35 +
>
> Hi Fred, the DebuggableWorker class code looks fine. The file should
> probably have an Apache Header inste
s,
>>better
>> >that than what I thought :P
>> >
>> >Also, it's going to work for Flex projects but not for pure AS3
>>projects
>> >if I put that base class in the existing libs, should we create an
>>other
>> >lib that pure AS3 pro
minutes.
Thanks for your help !
Frédéric THOMAS
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
> Date: Wed, 30 Apr 2014 20:38:50 +
>
> I think core.swc is supposed to contain stuff you can use in AS3 projects
> w/o pulling in all of the
project could reference ? how do you see it could be
>better ?
>
>Is it a good solution for IDEs ?
>
>Frédéric THOMAS
>
>> From: webdoubl...@hotmail.com
>> To: dev@flex.apache.org
>> Subject: RE: [FDB] Integration
>> Date: Wed, 30 Apr 2014 20:17:29 +0100
>>
in the existing libs, should we create an other lib that
pure AS3 project could reference ? how do you see it could be better ?
Is it a good solution for IDEs ?
Frédéric THOMAS
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: [FDB] Integration
> Date: Wed, 30 Apr
It is not even that, even if I stop in the main thread, switch to the worker
and try to stop it, it doesn't want, digging into
Frédéric THOMAS
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: [FDB] Integration
> Date: Wed, 30 Apr 2014 19:47:33 +010
message sent to a worker:
simpleRequestResponseMessageIsolate(DMessage.OutStopDebug,
DMessage.InBreakAtExt, every, isolateId);
Frédéric THOMAS
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
> Date: Wed, 30 Apr 2014 17:02:01 +
>
> Looks right.
in order to have a place to break.
> var i:int = 0;
>}
>}
>}
>
>
>Frédéric THOMAS
>
>> From: aha...@adobe.com
>> To: dev@flex.apache.org
>> Subject: Re: [FDB] Integration
>> Date: Wed, 30 Apr 2014 16:18:04 +
>>
>>
break.
var i:int = 0;
}
}
}
Frédéric THOMAS
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
> Date: Wed, 30 Apr 2014 16:18:04 +
>
>
>
> On 4/30/14 8:49 AM, "Frédéric THOMAS" wrote:
>
> >Coul
On 4/30/14 8:49 AM, "Frédéric THOMAS" wrote:
>Could be a solution, you meant like the idleTimer in SystemManager ?
Actually, I was referring to debugTickler in Application.as (both mx and
spark).
-Alex
Could be a solution, you meant like the idleTimer in SystemManager ?
Frédéric THOMAS
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
> Date: Wed, 30 Apr 2014 15:28:26 +
>
>
>
> On 4/30/14 8:15 AM, "Alexander Doroshko"
&
: Wed, 30 Apr 2014 19:24:58 +0400
> From: alexander.doros...@jetbrains.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
>
> On 30.04.2014 19:20, Frédéric THOMAS wrote:
> >
> >> You are right, suspending all running workers that contain the file,
> >
On 4/30/14 8:15 AM, "Alexander Doroshko"
wrote:
>On 30.04.2014 17:30, Frédéric THOMAS wrote:
>>> Why to put some BP in on the suspended ones ?
>> I meant : Why to put some BP only in the suspended ones ?
>You are right, suspending all running workers that contain the file,
>setting breakpoint t
On 30.04.2014 19:20, Frédéric THOMAS wrote:
You are right, suspending all running workers that contain the file,
setting breakpoint there (and probably resuming?) seems to be the best.
Sure resuming it if I halted it.
Unfortunately some workers may fail to suspend if they are doing
nothing.
Apr 2014 19:15:32 +0400
> From: alexander.doros...@jetbrains.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
>
> On 30.04.2014 17:30, Frédéric THOMAS wrote:
> >> Why to put some BP in on the suspended ones ?
> > I meant : Why to put some BP only in the
P.S. I have some extra days off this week and will be able to continue
discussion only on Monday.
ml BP fix on it.
That's what I played with.
Alexander
> Frédéric THOMAS
>
>> From: webdoubl...@hotmail.com
>> To: dev@flex.apache.org
>> Subject: RE: [FDB] Integration
>> Date: Wed, 30 Apr 2014 14:21:45 +0100
>>
>>>> I created 2 tickets [1] f
m
> To: dev@flex.apache.org
> Subject: RE: [FDB] Integration
> Date: Wed, 30 Apr 2014 14:21:45 +0100
>
> > > I created 2 tickets [1] for the merge, [2] for the fix, I
> attached it the fixed FDB. Main thread with the target file is not
> paused
> > Switching wor
oint again for each existing worker that didn't contain the
> file before.
Yep, was my goal too.
Frédéric THOMAS
> Date: Wed, 30 Apr 2014 15:37:38 +0400
> From: alexander.doros...@jetbrains.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
>
> On 30.04
On 30.04.2014 14:14, Frédéric THOMAS wrote:
I created 2 tickets [1] for the merge, [2] for the fix, I attached it the fixed
FDB. Main thread with the target file is not paused
Switching workers when VM is paused after new worker creation seems to
work now, that' great!
Setting a breakpoint to t
he.org
> Subject: Re: [FDB] Integration
> Date: Wed, 30 Apr 2014 03:16:46 +
>
>
>
> On 4/29/14 3:30 PM, "Frédéric THOMAS" wrote:
>
>
> >So, is there any objection to have one version in the SDK and one in
> >Falcon ?
> I'm ok with that.
>
> -Alex
>
>
>
On 4/29/14 3:30 PM, "Frédéric THOMAS" wrote:
>So, is there any objection to have one version in the SDK and one in
>Falcon ?
I'm ok with that.
-Alex
e any objection to have one version in the SDK and one in Falcon ?
Frédéric THOMAS
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
> Date: Tue, 29 Apr 2014 21:35:03 +
>
> Yes, definitely. If you can get FDB with workers to not need Falcon
al breakpoints as desired, and then type 'continue'.
(fdb) continue
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: [FDB] Integration
> Date: Tue, 29 Apr 2014 20:32:08 +0100
>
> > Trying to open any file
> > triggers event at worker si
7;t think that a good idea.
>
>Instead, can we have 2 versions ? one using the current ASC classes and
>shipped with the current SDK, the other one in Falcon ?
>
>Frédéric THOMAS
>
>> From: aha...@adobe.com
>> To: dev@flex.apache.org
>> Subject: Re: [FDB] Integration
>
g that out !
Frédéric THOMAS
> Date: Tue, 29 Apr 2014 20:53:28 +0400
> From: alexander.doros...@jetbrains.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
>
> On 29.04.2014 20:23, Alex Harui wrote:
> > IMO, unless the discussion is going to cover proprietar
AS
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
> Date: Tue, 29 Apr 2014 16:41:33 +
>
>
>
> On 4/29/14 9:35 AM, "Frédéric THOMAS" wrote:
>
> >The integration of the worker code itself which requires, in orde
same message as for unresolved breakpoint is
probably ok.
Any thoughts ?
Frédéric THOMAS
Date: Tue, 29 Apr 2014 19:48:39 +0400
From: alexander.doros...@jetbrains.com
To: webdoubl...@hotmail.com
Subject: Re: [FDB] Integration
All bugs are there unfortunately.
On 4/29/14 9:35 AM, "Frédéric THOMAS" wrote:
>The integration of the worker code itself which requires, in order to be
>total, to modify the Ant script that build FDB in order to link the
>Falcon sources (AST classes used to evaluate the expression), at the
>moment I didn't do this part and the
I meant:
I wouldn't like to commit that in this state.
Frédéric THOMAS
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: [FDB] Integration
> Date: Tue, 29 Apr 2014 17:35:50 +0100
>
> The integration of the worker code itself which requires, in o
e some big interess, anyway, that's
something that will go soon in JIRA
Frédéric THOMAS
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
> Date: Tue, 29 Apr 2014 16:23:38 +
>
> IMO, unless the discussion is going to cover proprietary aspect
ll send
>>it to you.
>>
>> Unfortunately, I haven't been able to work on it yesterday but will
>>continue tonight.
>>
>> Frédéric THOMAS
>>
>> [1] https://github.com/doublefx/downloadFileWorker
>>
>>
>>> Date: Tue, 29 Apr 2014
Done !! :-)
Thanks,
Frédéric THOMAS
> Date: Tue, 29 Apr 2014 19:03:39 +0400
> From: alexander.doros...@jetbrains.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
>
> Yes, I'd gladly try it. We can switch to personal emails in order not to
> spam the list
sterday but will continue
tonight.
Frédéric THOMAS
[1] https://github.com/doublefx/downloadFileWorker
Date: Tue, 29 Apr 2014 15:25:23 +0400
From: alexander.doros...@jetbrains.com
To: dev@flex.apache.org
Subject: Re: [FDB] Integration
Hi Frédéric,
that's great that you are ready to put th
4 15:25:23 +0400
> From: alexander.doros...@jetbrains.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
>
> Hi Frédéric,
> that's great that you are ready to put the effort into fdb with workers
> support!
>
> I have to say that IntelliJ IDEA still doesn't sup
Hi Frédéric,
that's great that you are ready to put the effort into fdb with workers
support!
I have to say that IntelliJ IDEA still doesn't support debugging apps
with workers. I spent some time on it but faced some bugs in fdb that
were not that easy to workaround. That's not an excuse for
Awesome!
On 4/26/14 5:01 PM, "Frédéric THOMAS" wrote:
>Hi,
>
>To resume a bit what I did and discover today:
>
>1- I merged the donated code to the the current FDB, keeping the existing
>fixes and the current ExpressionEvaluator (I guess It is possible to use
>the new Falcon based implementation
68 matches
Mail list logo
