Jean-Marc Paratte
01-19-2012, 09:15 AM
Hi all,
Since some months, I'm developing some plugins for a new project.
The main problem to develop FPP plugins is not only to understand the FPP Engine (pano.swf and hotspots.swf), but also to get a debug environment. The FPP Engine is a black box which transform the debugging in a huge task. And then Flash CS4 'debug mode' is of no help (I've tried 'remote debugging' but it's very defficult to get 'trace results').
So I've designed a debug environment which starts pano.swf like an HTML file does it with an url and parameters, all in the Flash Player and OUTPUT window of Flash CS4.
I'm very happy with the solution. FPP Engine is always a black box but I receive 'trace' messages from the plugin IN TRUE USAGE.
Here is an example of the OUTPUT window:
Attemping to launch and connect to Player using URL C:\develop\FPP\develop\pano_231\debug231.swf
[SWF] C:\develop\FPP\develop\pano_231\debug231.swf - 4401 bytes after decompression
[debug:MainTimeline:30] root1,[object MainTimeline]
[debug:MainTimeline:38] root1,
[SWF] C:\develop\FPP\develop\pano_231\pano.swf - 32089 bytes after decompression
CubePanorama v2.3.1 loaded.
[SWF] C:\develop\FPP\develop\pano_231\pano.swf - 3136 bytes after decompression
[debug:MainTimeline:43] contentLoaderInfo_initHandler,[object PanoController]
[debug:MainTimeline:47] contentLoaderInfo_completeHandler,[object PanoController]
[debug:MainTimeline:53] enterFrameHandler,[object PanoController]
[debug:MainTimeline:53] enterFrameHandler,[object PanoController]
[debug:MainTimeline:65] fpp_engine_debugging_initHandler
[SWF] C:\develop\FPP\develop\pano_231\pano.swf - 90 bytes after decompression
Load XML: pano.xml
Load layer ...
The debug231.swf source and code are zipped at:
http://jmpicture.com/technique/FPP/debug231/debug231.zip
Good luck...
jmP
Since some months, I'm developing some plugins for a new project.
The main problem to develop FPP plugins is not only to understand the FPP Engine (pano.swf and hotspots.swf), but also to get a debug environment. The FPP Engine is a black box which transform the debugging in a huge task. And then Flash CS4 'debug mode' is of no help (I've tried 'remote debugging' but it's very defficult to get 'trace results').
So I've designed a debug environment which starts pano.swf like an HTML file does it with an url and parameters, all in the Flash Player and OUTPUT window of Flash CS4.
I'm very happy with the solution. FPP Engine is always a black box but I receive 'trace' messages from the plugin IN TRUE USAGE.
Here is an example of the OUTPUT window:
Attemping to launch and connect to Player using URL C:\develop\FPP\develop\pano_231\debug231.swf
[SWF] C:\develop\FPP\develop\pano_231\debug231.swf - 4401 bytes after decompression
[debug:MainTimeline:30] root1,[object MainTimeline]
[debug:MainTimeline:38] root1,
[SWF] C:\develop\FPP\develop\pano_231\pano.swf - 32089 bytes after decompression
CubePanorama v2.3.1 loaded.
[SWF] C:\develop\FPP\develop\pano_231\pano.swf - 3136 bytes after decompression
[debug:MainTimeline:43] contentLoaderInfo_initHandler,[object PanoController]
[debug:MainTimeline:47] contentLoaderInfo_completeHandler,[object PanoController]
[debug:MainTimeline:53] enterFrameHandler,[object PanoController]
[debug:MainTimeline:53] enterFrameHandler,[object PanoController]
[debug:MainTimeline:65] fpp_engine_debugging_initHandler
[SWF] C:\develop\FPP\develop\pano_231\pano.swf - 90 bytes after decompression
Load XML: pano.xml
Load layer ...
The debug231.swf source and code are zipped at:
http://jmpicture.com/technique/FPP/debug231/debug231.zip
Good luck...
jmP