Integration of KapInspect Into Your Flex/AS3 Application
This is the last in a three-article series. This explains in detail the different ways of integrating KapInspect into your applications.
How to include KapInspect into your application?
There are different methods to include KapInspect into your application, depending on what packaging you use:
1°) With KapInspect.swc
Just add this library to your project, and add either
- tag into your main MXML application: <kapit:KapInspect/>
- “new KapInspect()” line into you application initialization code (initialize, creationComplete or applicationComplete code)
2°) With KapInspectModuleLoader.swc
In a very similar manner, include this SWC into your project, and add either:
- tag into your main MXML application file: <kapit:KapInspectModuleLoader/>
- “new KapInspectModuleLoader()” line into application initialization code
Do not forget to copy KapInspectModule.SWF into the directory that contains your application SWF file.
How to launch KapInspect?
Once your application starts, just hit any of the following keystroskes :
- Ctrl + Alt + F12 (does not work on some systems that override F12 key, such as some Dell laptops, or Macs with default dockbar shortcuts activated)
- Ctrl + Alt + Left Click, that should work on any system
Notice that
- the first keystroke is the default one, and it can be overridden with key combination of your choice, using KapInspect attribute
- the second keystroke cannot be overridden, however it may be disabled (see below for options)
KapInspect startup main options
- Shortcut: Defines the key combination to start KapInspect, defaults to ‘ctrl+alt+123′ for Ctrl+Alt+F12. See online documentation for key codes
- Use MouseShortcut: true(default)|false. Indicates if the ctrl+alt+click shortcut is activated or not
- logApplicationEvents = true|false (default). When activated along with static linking, it will set an EventLogger on the application, and when you start KapInspect, you will see all the initialisation events of your application, including children creation and add events. This option is mainly for discovering initialization event flow, and to discover what’s behind the scene.
- pluginModules: Optional list of extra modules to load into KapInspect. It should be the relative (to application deploy directory) pathnames of the module files (without .SWF extension).
About KapLab
KapLab is the result of a deliberate effort to develop innovative components for Flex, as we are committed to playing a role in the Flex community.
We provide great components for free, as shown below:
- Flex Diagrammer (with Layout algorithms):
- Graph visualizer:
- Radar Chart:
- Treemap:
Please feel free to try and use them.
All components that we provide are 100% free, and may be used in any product that you develop with them (they cannot be resold as components though). We publish new versions very often. You are welcome to leave comments and encouraged to submit bugs or feature requests through our integrated JIRA database. Each component has a user guide, an integration guide, ASDoc, and live demonstration
You will have to register first on KapLab to be able to download any component, or to post comments or bugs.
As Cyril Daloz, CEO says: “Kap Lab exists because in innovation we trust. Enjoy our products and help us to give you the best.“
Leave a Comment
If you would like to make a comment, please fill out the form below.
Recent Comments