This Fall Lookout mobile discovered that developers were writing some pretting interesting things to LogCat and the talked about their findings at DefCon.

While, as a dev, you should try to never put sensitive information in your logs, you can use this system to turn off logging in your releases.

At the beginning of each of my classes i write:

public class MyClass
{
    // Debugging
    private static final String TAG = "MyClass";
    private static final boolean GLOBAL_DEBUG = DebugMode.MODE;
    private static final boolean LOCAL_DEBUG = true;
    private static final boolean D = ( GLOBAL_DEBUG && LOCAL_DEBUG );

Notice the DebugMode.MODE is a separate class, and it’s a pretty simple one:

public class DebugMode
{
    public static final boolean MODE = true;
}

Anyways, then, when I want to put something in LogCat I write

if (D) Log.d ( TAG, "something interesting happened");

Finally, when I’m ready to release, I only have to change the DebugMode class to:

public class DebugMode
{
    public static final boolean MODE = false;
}

And voila! We now have both fine-grained, per-class control of how much info gets sent to LogCat, as well as a Global on/off switch that will help keep prying eyes out of our logs.

Anyways, hope that helps

filed under: Android, Interesting stuff, Scripts, Security | comments (0) | read more...

Some say the days of callbacks are still going strong. Others say events just rock.  Which is it? Heck, I’m not here to start a code-religion war so I’m not even going to begin to try and answer that one. Still, with all these fancy-pantsy, new-fangled events we have some big new challenges (and new opportunities too).  Luckily, we’ve had some good guides in the past.  Jason Cook’s great article Centralized Event Management in ActionScript 2.0 was a truly inspiring jump-off point, but now it’s time to jump a little farther and use some AS 3 in the process.

Read the rest of this entry »

filed under: ActionScript, Scripts, Tutorials | comments (11) | read more...