Issue Details (XML | Word | Printable)

Key: FDT-1361
Type: Featurerequest Featurerequest
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: FDT Team
Reporter: Jacob Wright
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
FDT

Provide robust code logging/profiling for Flash applications.

Created: 25/Sep/10 03:54 PM   Updated: 22/Jun/12 06:42 PM
Component/s: Debugger, Profiler, UI
Affects Version/s: None
Fix Version/s: None
Security Level: public

Time Tracking:
Not Specified

Environment: All


 Description  « Hide
Firefox (with Firebug), Chrome, and Safari all have robust logging and profiling capabilities through the use of the console object. High-level information can be found about it here: http://getfirebug.com/logging.

I would like to be able to do the same.

For logging (trace): I could write a Console object that was globally accessible and prepend "<<error>>" or "<<info>>" to the beginning of statements traced out with it, but could we have the console take messages that started with <<error>> and put a red icon with an exclamation mark next to it, etc.

For console.trace (could be called stack to avoid confusion): is it possible to get the current stack via actionscript and dump it to the console?

For profiling: this is the biggest feature in this request (most important). If we could programmatically start profiling and stop it we would have much better fine-grained control over data we need to see. We often know where a problem might be, but we can't profile just the one problem because we can only profile the app at a general level. It would help us so much to profile individual functions with a simple console.profile(); myMethod(); console.endProfile();

Other things like logging an interactive listing of an object to the console or grouping would be the bomb!



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jacob Wright added a comment - 25/Sep/10 03:56 PM
The overall concept behind this feature is to provide developers a way to better debug and profile their applications from the code. We shouldn't ever have to create buttons in our interface that we push just to get a breakpoint hit for viewing objects.

Meinhard Gredig added a comment - 04/Oct/10 12:22 PM
Profiling in Flash can only be done globally, profiling can also be started with the new ANT Task startProfiler in FDT 4.0.

Jacob Wright added a comment - 05/Oct/10 03:14 PM
But could it grab the global profile between a "start" and a "stop" which might be called from code? You could take two memory snapshots and see what objects were created when a function is called for example.

Alan K (Deprecated) added a comment - 07/Apr/11 09:05 PM
This is solved with our new Profiler correct?