Welcome to the Doomsday Console 2.0 project
The Doomsday Console is a development and debugging utility for Adobe Flash 10 and up. It aims to offer simple, direct introspection and access to methods and display list via a command-line interface much like Bash or CMD.
Flash on the beach 2010
Yesterday I got back from this year's Flash On The Beach, and it was great as always. I did a 3 minute "elevator pitch" on why I feel developer consoles are important and why we need them in Flash, and also a summary of the core functionality of the Doomsday Console. Absolutely nerve wracking, but fantastic fun.
The response was precisely what I was hoping for; This is definitely a niche, but it's a niche which is very easy to define. I've always said that the people that need it will know instantly if they do, and anyone confused doesn't really need to be "converted".
Documentation relocation
Migrating the googlecode wiki to the Atrium notebook feature. Any new documentation should be properly nested and organized and prettified. Although that's kind of hard right now. Stupid html/markdown!
Added documentation for every plugin + all the googlecode wiki pages.
- Login to post comments
sprintf available
Added the de.popforge sprinft() to the console, accessible through, you guessed it. ConsoleUtil.sprintf(format,...args):void;
It prints directly to the console in with the messagetype OUTPUT.
- Login to post comments
Writing console plugins
The first version of the plugin framework is ready. Check the referenced page for an overview+example.
In general terms, everything that CAN be moved into its own plugin SHOULD be moved into its own plugin. This is to ensure the console remains pure at its core; an interpreter and logger. Utilities like controllers, colorpickers, measuring tools etc are natural plugins.
Functionality currently moved into their own plugs:
- Batch file running
- HexDump utility
- ProductInfoUtil
- ClassFactoryUtil ("new" and "getClass" commands)
Flash on the beach 2010
2010.. Wtf.
Anyway; I'll be shopping DDConsole at FOTB this year as one of the elevator pitchers. This is a golden opportunity to look awesome, though 3 minutes to sell something this abstract is going to be a real puzzle. I'd love to see some input and suggestions as to how to sell it as quickly and succinctly as possible; what features to demonstrate, what philosophy to preach.
- Login to post comments
2.0 mindmap
Here's a quick mind map of need-to-haves for 2.0 (the FOTB release) I use freemind (http://freemind.sourceforge.net/wiki/index.php/Main_Page) for my mindmapping so hopefully it should be cross platform editable
- Login to post comments
ConsoleUtil Lock++
As The Keyboard Sequences was introduced. It was natural to add lock functionality for the Console.
The Console can be locked such that only a keyboard sequence or secret password is the only way to unlock and toggle on the Console.
Silver Death source control information
We've migrated to Beanstalk.
DConsole 2.0 (Silverdeath) dev is currently closed at Beanstalk over here.
Beanstalk offers both git and svn repositories, and allows a repository to be opened for public anonymous access. This completes our move away from googlecode.
We'll be creating hooks for beanstalk to post updates and releases to Central Control. In other words, this site will become the development portal for the console in the foreseeable future.
Parsing expressions and commands
Currently, handling accessors and variables in the console using the set/get commands is somewhat awkward. Ok let's be honest, it's MAD awkward.