WS-Blog

18 Responses to “The new ThunderBolt AS3 Console based on Adobe AIR”

1. Francis Gabon Says:
   June 2nd, 2008 at 7:20 am

   Hi there,

   That console looks great, congrats.

   Is there a way to use it with AS-only projects too?
   Actually I spent half the day trying to make the Flex logging API working in a simple AS project but I couldn’t. I think I correctly imported the framework.swc and the locale swcs, but I keep getting the following error: “Error: No class registered for interface ‘mx.resources::IResourceManager’.”
   Any clue?

   Thx a lot!

2. ThunderBolt AS3 Console : flash und so… Says:
   June 2nd, 2008 at 7:58 am

   [...] das Loggingtool ThunderBold gibt es nun auch eine kleine AIR Anwendung im [...]

3. sectore Says:
   June 2nd, 2008 at 9:49 am

   Francis,

   the ThunderBolt AS3 Console works fine for “pure” AS 3 projects. Grab the source (” ThunderBoltAS3Console.zip”) and add the “ThunderBoltAS3_Flash_v2beta.swc”, which is located within the *.zip, to your project. Run ThunderBoltAS3Console.app after installing the Console and log your app as described here:
   “ThunderBolt AS3 for logging ActionScript 3 including Flex 2/3 projects”

   Note: To avoid logging using Firebug within Firefox and to use ThunderBolt AS3 Console only, place the following snippet within your code once:

   Logger.console = true;

   That’s all

   -Jens

4. Francis Gabon Says:
   June 3rd, 2008 at 9:40 am

   Hi Jens and thanks for your help,

   Unfortunately my logs are still not generated in the console. I actually noticed that trace() or Logger.info() are correctly written in flashlog.txt, provided that I don’t open the console! If I open the console, flashlog.txt is empty, if I close the console, it works again and logs are generated.

   As you suggested, I linked ThunderBoltAS3_Flash_v2beta.swc to the library path of my AS3-only project in FB3.

   Do you have any clue? Did I miss something?

   Thank you very much

5. sectore Says:
   June 3rd, 2008 at 1:57 pm

   Francis,

   all you have written sounds good . However, have you started the logging process pressing the button called “start” within the console?

   Don’t worry about clearing the flashlog.txt after starting the console, because AIR is used to clear it every time while starting an AIR app. This means that you have pointed the flashlog.txt correctly to the console

   UPDATE: Please use the latest the swc-file (“ThunderBoltAS3_Flash_v2.01beta.swc”). I found a bug – it’s fixed now.

   -Jens

6. Francis Gabon Says:
   June 4th, 2008 at 4:10 am

   Thanks Jens.

   It’s weird actually. The console works totally fine on my Mac but I still got the same symptoms on my Windows setup. I imported the new SWC (by the way, I couldn’t find it on the SVN, there’s just the Flex version there , I traced the player version (9.0.124.0 isDebugger->true) but the console still returns nothing except “===== log data is cleared =====”.

   I’m gonna look further. If I may guggest, a small wishlist
   - the console is stopped when clicking “Clear”
   - console’s size isn’t saved

   Cheers

7. Francis Gabon Says:
   June 4th, 2008 at 4:21 am

   I tried a few things, for example linking the console to another flashlog.txt (located outside the default folder) and the console correctly returned the logs and traces.
   Unfortunately, the last versions of the Flash Player cannot link anymore to a flashlog.txt outside the default folder so that doesn’t help. It seems that the player cannot write on flashlog.txt anymore when the console is launched.
   Hope it helps

8. Ryan Stewart - Rich Internet Application Mountaineer » Debug Flash Applications with FireBug and ThunderBolt Says:
   June 4th, 2008 at 3:01 pm

   [...] the on AIR tour in Berlin I just saw a really cool project called Thunderbolt by Jens Krause that lets you debug Flash applications in the browser using the very popular Firebug [...]

9. sectore Says:
   June 7th, 2008 at 3:29 pm

   Hey Francis,

   thanks for your detailed feedback – it helps a lot! You’re right, it seems that an opened AIR app locks the “flashlog.txt” on Windows. I’m on a Mac and I have the same issue using Parallels.

   Googling around I’ve found the following entry at
   Adobes Bug System: “AIR puts a read-only lock on flashlog.txt”

   Hope, this issue will be fixed by Adobes AIR team soon – for all the ThunderBolt AS3 Console users on a Windows system

   [UPDATE 06/08/08] Today I’ve got an answer from Oliver Goldman, an Engineer of the Adobe AIR Team: “There’s no current workaround for this.” Check this post at Adobes AIR Forum.

   -Jens

10. Francis Gabon Says:
    June 9th, 2008 at 4:31 am

    Hi Jens,

    Wow, that pretty sucks. I guess we just have to stick with the firebug console on Windows for the time being. Too bad…

    Thanks a lot for the help.

11. Dmitry Says:
    June 12th, 2008 at 5:29 am

    I tried ThunderBolt in pure AS Flex project and it is not producing anything. In normal Flex project it works like a charm. What could be the issue with ActionScript projects?

    Thanks.

12. sectore Says:
    June 12th, 2008 at 7:16 am

    Dmitry,

    it could be anything . Some questions: What version of ThunderBolt are you using (1.0 or beta)? SWC or “original” Logger.as? Are you using Firebug or AIR based ThunderBolt AS3 Console? How does look you log statement within code?

    Feel free to send me your example directly or use the ThunderBolt mailinglist as well to solve your problem

    -Jens

13. Dmitry Says:
    June 12th, 2008 at 2:55 pm

    Hi Jens,

    My apology, it was a false alarm – had a bug in the code and late night coding… Anyway, thanks for the great product and your reply.

14. Simon Bailey Says:
    August 17th, 2008 at 10:03 pm

    Hi Jens,

    Nice app and a job well done, thanks a lot man

    Simon

15. Rahul Says:
    October 15th, 2008 at 5:02 am

    Ya! it seems quite cool to me……….let me check once…..

16. 80s team blog » Blog Archive » AIR??Flash Console Says:
    November 24th, 2008 at 5:06 am

    [...] ?????????? [...]

17. Brenda Says:
    October 19th, 2009 at 8:17 pm

    I’m using FlashBuilder 4 pre-release. When trying to compile the source for the console I get this error:
    Description Resource Path Location Type
    Could not resolve to a component implementation. StandardButtonSkin.mxml ThunderBoltAS3Console/src/skins line 16 Flex Problem

    The ‘GraphicBorderSkin’ is from the degrafa swf but the mxml StandardButtonSkin source doesn’t recognize that as a component. Any suggestions?

    Thanks
    Brenda

18. sectore Says:
    October 20th, 2009 at 7:49 am

    Have you tried to use Flex SDK 3.4.x (not 4.x)? I have no trouble using latest Flash Builder Beta…

    PS: If you have further questions, please use the Google Thunderbolt Group.

    -Jens

Leave a Reply

Name (required)

Mail (will not be published) (required)

Website

CAPTCHA Code