Sie sind nicht angemeldet.

Lieber Besucher, herzlich willkommen bei: krpano.com Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.

1

Dienstag, 28. Juli 2009, 12:54

Debugging plugin

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

2

Dienstag, 28. Juli 2009, 17:06

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

Mittwoch, 29. Juli 2009, 08:51

Are you talking about flex profiling?

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

4

Mittwoch, 29. Juli 2009, 09:07

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

Schüler

Beiträge: 71

Wohnort: Grand Rapids, Michigan, USA

  • Nachricht senden

5

Montag, 17. August 2009, 17:34

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

6

Montag, 17. August 2009, 17:37

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

Schüler

Beiträge: 71

Wohnort: Grand Rapids, Michigan, USA

  • Nachricht senden

7

Montag, 17. August 2009, 17:44

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

Schüler

Beiträge: 71

Wohnort: Grand Rapids, Michigan, USA

  • Nachricht senden

8

Montag, 17. August 2009, 17:49