Step 3 of the section "Debug your application using the command line" should be equivalent to pressing the "Install Now" button on the Install tab of the graphical aid. I have only used the graphical aid a couple times long ago but I seem to remember that it didn't do SWF builds, only BAR builds. So just to stress this again but your SWF needs to be compiled w/debug options or you won't get any trace output. If you don't have an IDE based debugger and therefore only have fdb as an option, the procedure from the link in my earlier reply should get you going, just with the substitution that you're pressing a button in a GUI to install and launch your app vs. entering a command on the commandline.
This is just my opinion but while the graphical aid is nice for getting folks up and running, the better long term solution for folks who don't use an IDE and who want to have products in App World that they intend to sell, upgrade, and support is to create your own commandline build flow in your own scripts. Using the graphical aid makes you unncessarily dependent on RIM for tooling upgrades and bug fixes on something that I suspect is not a high priority for RIM. With your own build flow scripts you have full visibility into every step, and furthermore you can manage your build flow under version control software. The moment you have a bug report and start editing your code to try to fix a bug, one question that for sure you are not going to want nagging you is whether you are building your source code changes with the same setup and options as the version of your app that's out in the wild.
