Thanks Mike,

I got it debugging in the meantime taking the debugger from an old version of 
the SDK !!

Frédéric THOMAS

> Date: Thu, 14 May 2015 09:31:52 -0400
> Subject: Re: [FlexJS] IntelliJ Integration
> From: teotigraphix...@gmail.com
> To: dev@flex.apache.org
> 
> Fred I am using the Flex SDK debugger in 4.14.0
> 
> 1. I downloaded the latest nightly
> 2. I built it, took about 4 minutes, the AIR sdk for me takes awhile to
> download. (ant -f installer.xml)
> 3. Create a new project and followed this video;
> 
> https://www.youtube.com/watch?v=NBJEjIcfNs8
> 
> This is my debug target;
> 
> http://snag.gy/3m5Ua.jpg
> 
> Other than that it just works, took me about 3 hours to get to this point.
> 
> the FLEX_HOME and FALCON_HOME screwed me up until I realized I had it set
> wrong because it was still pointing to the locations I needed for the
> actuall compiler build. Once I change them to point to the nightly built
> FlexJS directory, it worked.
> 
> Mike
> 
> 
> On Thu, May 14, 2015 at 9:23 AM, Frédéric THOMAS <webdoubl...@hotmail.com>
> wrote:
> 
> > Hi Mike,
> >
> > You should be able to use a normal lib instead, good catch !!
> >
> > What are the steps to debug inside IJ ? on mine, it doesn't stop, maybe I
> > should update the FlexJS SDK ? I didn't follow the last posts0
> >
> > Thanks,
> > Frédéric THOMAS
> >
> > > Date: Thu, 14 May 2015 09:07:47 -0400
> > > Subject: Re: [FlexJS] IntelliJ Integration
> > > From: teotigraphix...@gmail.com
> > > To: dev@flex.apache.org
> > >
> > > YES! This screenshot should make all IntelliJ users happy that want to
> > get
> > > the full meal deal with FlexJS.
> > >
> > > http://snag.gy/iLLrP.jpg
> > >
> > > - MXML/ActionScript code completion
> > > - MXML strucutre view
> > > - Breakpoints working for SWF build
> > > - and the rest of the IntelliJ goodness.
> > >
> > > The secret sauce "for now" with code completion is make a global library,
> > > add all the SWCs to it and include that in your module, voila, you have
> > > code completion.
> > >
> > > Mike
> > >
> > >
> > > On Thu, May 14, 2015 at 8:22 AM, Michael Schmalle <
> > teotigraphix...@gmail.com
> > > > wrote:
> > >
> > > > I tried everything you guys are doing and get;
> > > >
> > > >
> > > > C:\Users\Teoti\Documents\ApacheFlex\FlexJS-Nightly\bin\mxmlc.bat
> > > > -debug=true
> > > >
> > C:\Users\Teoti\Documents\ApacheFlex\FlexJS-Nightly\examples\DataBindingTest\src\MyInitialView.mxml
> > > > Using Falcon codebase:
> > > > C:\Users\Teoti\Documents\ApacheFlex\falcon\compiler\generated\dist\sdk
> > > > Using Flex SDK: C:\Users\Teoti\Documents\ApacheFlex\sdk
> > > > Loading configuration:
> > > > C:\Users\Teoti\Documents\ApacheFlex\sdk\frameworks\flex-config.xml
> > > >
> > > >
> > > >
> > C:\Users\Teoti\Documents\ApacheFlex\FlexJS-Nightly\examples\DataBindingTest\src\MyInitialView.mxml:20
> > > > Error: This tag could not be resolved to an ActionScript class. It
> > will be
> > > > ignored.
> > > > <js:ViewBase xmlns:fx="http://ns.adobe.com/mxml/2009";
> > > > ^
> > > >
> > > >
> > > > Process finished with exit code 2
> > > >
> > > > I don't know why it's trying to load the wrong flex-config and you guys
> > > > have it working.
> > > >
> > > >
> > > >
> > > > On Thu, May 14, 2015 at 6:48 AM, kevin.godell <kevin.god...@gmail.com>
> > > > wrote:
> > > >
> > > >> Alex Harui wrote
> > > >> > On 5/13/15, 10:10 PM, "piotrz" <
> > > >>
> > > >> > piotrzarzycki21@
> > > >>
> > > >> > > wrote:
> > > >> >
> > > >> >>Mike,
> > > >> >>
> > > >> >>Great idea to reach someone from Jetbrains we really need some help
> > from
> > > >> >>that point from them. Thank you!
> > > >> >
> > > >> > Alexander Doroshko is still subscribed as of April so maybe he just
> > > >> hasn’t
> > > >> > noticed this thread.
> > > >> >
> > > >> >>
> > > >> >>Maybe I will describe our current problems:
> > > >> >>
> > > >> >>1) We have successfully configured External Tools both on Mac OSX
> > > >> (Thanks
> > > >> >>Kevin!) and Win [1]
> > > >> >>2) Once we use FlexJS in section "Use debugger from SDK" we are
> > getting
> > > >> >>following error [2]
> > > >> >>3) Once we change it in section "Use debugger from SDK" from FlexJS
> > to
> > > >> >>Flex
> > > >> >>SDK our debugger is working fine. Take a look at film created by
> > Kevin
> > > >> [3]
> > > >> >>especially at 3:48 and compare console output with mine from FlexJS.
> > > >> >>-classpath in mine output is different.
> > > >> >
> > > >> > Have you tried the latest combination of changing the version of
> > > >> > flex-sdk-description.xml in the FlexJS  folder as well as copying
> > the
> > > >> > fdb.jar, swfutils.jar and asc.jar from the Flex SDK?
> > > >> >
> > > >> > Thanks,
> > > >> > -Alex
> > > >>
> > > >> I tried it with the 3 files copied and the flex-sdk-description.xml
> > edited
> > > >> to show 4.15.0. Still failed, but atleast the error message got
> > smaller:
> > > >>
> > > >>
> > /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java
> > > >> -d32
> > > >>
> > > >>
> > -Dapplication.home=/Users/kevinGodell/Documents/flexJS-nightly_air-17_fp-17
> > > >> -Dfile.encoding=UTF-8 -Djava.awt.headless=true -Duser.language=en
> > > >> -Duser.region=en -Xmx512m -classpath "/Applications/IntelliJ IDEA
> > > >>
> > > >>
> > 14.app/Contents/plugins/flex/lib/idea-fdb-4.0.0.14159-fix.jar:/Users/kevinGodell/Documents/flexJS-nightly_air-17_fp-17/lib/fdb.jar"
> > > >> flex.tools.debugger.cli.DebugCLI
> > > >> Exception in thread "main" java.lang.IllegalAccessError: tried to
> > access
> > > >> method flex.tools.debugger.cli.FaultActions.<init>()V from class
> > > >> flex.tools.debugger.cli.DebugCLI
> > > >>         at flex.tools.debugger.cli.DebugCLI.<init>(DebugCLI.java:381)
> > > >>         at flex.tools.debugger.cli.DebugCLI.main(DebugCLI.java:318)
> > > >> java.io.IOException: Stream closed
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> View this message in context:
> > > >>
> > http://apache-flex-development.2333347.n4.nabble.com/Re-FlexJS-IntelliJ-Integration-tp46486p46504.html
> > > >> Sent from the Apache Flex Development mailing list archive at
> > Nabble.com.
> > > >>
> > > >
> > > >
> >
> >
                                          

Reply via email to