You are not logged in.

Dear visitor, welcome to krpano.com Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Tuesday, July 28th 2009, 12:54pm

Debugging plugin

Is it possible to debug plugin in flex builder for example?

nelk

Intermediate

Posts: 358

Location: Paris

  • Send private message

2

Tuesday, July 28th 2009, 5:06pm

It's possible to "profil" the swf, I tried it yesterday.

But the thing is : it crash my firefox after 30sec ... *sad*
VideoStitch, a video stitching engine / blog sur les visites virtuelles ( french ).

3

Wednesday, July 29th 2009, 8:51am

Are you talking about flex profiling?

It's really difficult to develop plugin without instruments to debug it in krpano.

nelk

Intermediate

Posts: 358

Location: Paris

  • Send private message

4

Wednesday, July 29th 2009, 9:07am

Hi,

You can trace variable (with trace and flash debug / flash tracer or krpano.trace), I debug things with it.

And basically, the plugin I've made until now are just add basic MouseEvent and display stuff, it's not so complicated
VideoStitch, a video stitching engine / blog sur les visites virtuelles ( french ).

kyle

Trainee

Posts: 71

Location: Grand Rapids, Michigan, USA

  • Send private message

5

Monday, August 17th 2009, 5:34pm

If you install the debug version of the flash plugin for use by your browsers, you can attach the fdb cli debugger to your plugin while running it in krpano in your browser. Steps:

1. Get flash debug plugin from adobe and install system-wide.
2. Generate debug .swf plugin by compiling with debug=true.
3. Create test html page and krpano xml file that loads your debug .swf into krpano.
4. Start command line debugger:
a. Type fdb at command-line
b. Then type run. Debugger will wait for connection from flash player when you open test page in browser.
5. Open test page in browser. Flash player will halt when it loads your plugin.
6. Set breakpoints in fdb, then type continue to run the plugin in flash player. Debug as normal.

Note: I'm using flex sdk mxmlc compiler. If you are using Flash authoring tool or FlexBuilder, some steps may be different

nelk

Intermediate

Posts: 358

Location: Paris

  • Send private message

6

Monday, August 17th 2009, 5:37pm

interesting, it doesn't make your navigator crash ?

With my experience with Flash Builder and the native debugging tool ( = Flex Builder 4 ), it does *unsure*
VideoStitch, a video stitching engine / blog sur les visites virtuelles ( french ).

kyle

Trainee

Posts: 71

Location: Grand Rapids, Michigan, USA

  • Send private message

7

Monday, August 17th 2009, 5:44pm

The browser would become unresponsive until I typed continue at the fdb prompt as the flash player was blocking until it received a signal from the debugger, but it still worked. I could step through the program line-by-line. I'm using Safari on a Mac and running Flash 10 debugger.

Also, I'm not sure how the FlexBuilder environment differs from the flex sdk command line tools, but perhaps it does not install the debugger version of the Flash Player system-wide. I had to do that manually by downloading it from adobe. Just scroll down on the flash player downloads page until you find the debug versions.

But I agree with nelk. Tracing works very well in many situations.

kyle

Trainee

Posts: 71

Location: Grand Rapids, Michigan, USA

  • Send private message

8

Monday, August 17th 2009, 5:49pm