Table of contents
- Debug/Logging Client-Side – Part 1
- Debug/Logging Client-Side – Part 2
One of the most common problems in developing new applications is their debugging. There are several methods to do this in Flex (trace, alert – like somebody once said: “Alert till death”). But what happens if you want the same logging that you had on your work environment to also be available when the application is distributed to the customer?
There are several methods to do this: logging into a field in the application, logging to the customer database (if the application uses a database) or using TraceTargets. There may be other methods to do this, but this are the main ones.
I will not talk about the database approach, but I will concentrate on the TraceTarget approach.
Imagine you have an application that is distributed to a lot of clients and one of them tells you he has a problem. In this case you can ask him for a description of the problem and try to replicate it. That often is not successful. What if you could instruct the application you developed to send you the trace information without having to write a lot of code?
… More to come in the next post. (Including some source code)
Tags: ActionScript, flex, RIA, XMLSocket
This post was written by Virgil Cristea
Views: 3408
Articles
[...] my previous post I started to talk about how you can see the same trace messages you were used from developing [...]
[...] Having your app keep a detailed log can be indispensable for figuring out tricky user-reported bugs. This is easy on the server-side, where you can use any logging framework or just write to a file. Flash includes the trace function, which is useful while developing, but nearly impossible to get from an end-user. Flex, however, has a good logging api that lets you put log statements anywhere you want. I’ve always wanted the interface to be as easy as trace, so I write a couple of scripts to make it easier. [...]