https://github.com/brian428/Swiz-Console

An implementation of the Kap Lab debugging console for the Swiz framework
https://github.com/brian428/Swiz-Console

Last synced: about 2 months ago
JSON representation

An implementation of the Kap Lab debugging console for the Swiz framework

• Host: GitHub
• URL: https://github.com/brian428/Swiz-Console
• Owner: brian428
• License: other
• Created: 2011-02-16T17:42:46.000Z (almost 14 years ago)
• Default Branch: master
• Last Pushed: 2011-06-29T06:44:05.000Z (over 13 years ago)
• Last Synced: 2024-08-04T05:03:01.651Z (5 months ago)
• Language: ActionScript
• Homepage:
• Size: 2.05 MB
• Stars: 13
• Watchers: 2
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: readme.txt
  • License: license.txt

Awesome Lists containing this project

• awesome-actionscript-sorted - Swiz-Console - An implementation of the Kap Lab debugging console for the Swiz framework (Frameworks / Logger Framework)

README

        
The Swiz Console (download swc) is an implementation of the Kap Lab debugging console. It offers a number of features that help in building and debugging Swiz-based applications. Note that right now this only works with the 4.x SDK, since building a 3.x SDK version will require conditional compilation to generate separate swcs.

Using the Swiz Console

After you add the swc to your project (typically in the /libs folder), using the console is very straightforward:

In whatever page contains your Swiz configuration (usually Application or WindowedApplication), add the namespaces for the custom metadata processors and the custom logging class:

xmlns:logging="org.swizframework.console.logging.*"

xmlns:processors="org.swizframework.console.processors.*"

Next, modify your Swiz configuration to use the custom logger and processors:

	

		

	

	

		

	

	

		

		

	

	

		

	

The custom Array is there as a convenience, to cover most situations. If you have your own custom processors in use already, just add all of the custom Swiz console processors (InspectableDispatcherProcessor, InspectableEventHandlerProcessor, InspectableInjectProcessor, InspectablePostConstructProcessor, InspectablePreDestroyProcessor, InspectableSwizInterfaceProcessor, InspectableViewProcessor, and InspectableSwizProcessor) individually.

Finally, add an onApplicationComplete handler and initialize the console:

private function onApplicationComplete() : void

{

	var p : SwizConsole = new SwizConsole();

	p.showPopup();

}

If you close the console (or you remove the showPopup() call if you don't want it to show up immediately), you can open the console by doing a control-alt click on the application.