Page 1 of 6 123 ... LastLast
Results 1 to 10 of 52

Thread: App Inspector for Sencha v2.0

  1. #1
    Sencha Developer
    Join Date
    Sep 2008
    Location
    Antioch, IL
    Posts
    1,516

    Lightbulb App Inspector for Sencha v2.0

    I am very excited to announce an update to the Sencha Labs project "App Inspector for Sencha":
    - https://github.com/senchalabs/AppInspector

    App Inspector for Sencha is an extension for Chrome's DevTools, allowing for easy debugging of Ext JS and Sencha Touch apps. You can install it directly into Chrome:
    - https://chrome.google.com/webstore/d...dbfbaacglkceae

    Under the hood it's built with Ext JS, Sencha Architect, Sencha Cmd and Node.js.

    Although we're at a 2.0 release, we are really looking for the community to begin testing (since I can't publish it in a "beta" release). Currently App Inspector supports Touch 2.x and Ext JS 4.x - but any bugs can be logged directly in the GitHub repo.

  2. #2

    Default

    Very cool, thanks for sharing! The new "events" list in particular looks useful... I'd been using a homegrown event log in the past for this, so having it in the devtools is even nicer.

  3. #3
    Sencha Premium Member MichaelOstrovsky's Avatar
    Join Date
    May 2008
    Location
    Tel Aviv, Israel
    Posts
    144

    Default

    Thanks, This tool has a great potential, but it does not working for me.I'm getting an exception when trying to inspect components :"isException: true value: TypeError: Cannot read property 'style' of null".And, also, A search is notably missing - for ids/itemIds/ maybe even componentQuery.
    Also, recording events throws "isException: true value: TypeError: Cannot read property 'eventCache' of undefined".

    ExtJS 4.2.2,
    Chrome 33.0.1750.146 m

  4. #4
    Sencha Developer
    Join Date
    Sep 2008
    Location
    Antioch, IL
    Posts
    1,516

    Default

    @MichaelOstrovsky - Thanks for the bug report here.

    "isException: true value: TypeError: Cannot read property 'style' of null"
    Does this happen on every component you try? Or only on certain components?

    When we first built this, I noticed errors like that happening only on hidden components. We fixed that bug (I think), so it sounds like something related is happening to you.

    When I run the Ext JS 4.2.2 examples locally, I can't seem to find a component which throws the error you mention - so any help you can offer to debug this will be critical for me!

    A search is notably missing - for ids/itemIds/ maybe even componentQuery
    Do you mean to perhaps filter the Component Tree? That would be a helpful feature, I'll create a task to tackle that.

    "isException: true value: TypeError: Cannot read property 'eventCache' of undefined".
    I definitely don't see that error, and that would indicate that App Inspector didn't correctly initialize itself. Does closing/reopening your DevTools fix it?

    Are you running v2.0.3 of our extension (which is the latest)? If so, then there's something about your Ext JS app which is very different than the apps we've been testing on.

    I'm running Chrome 33.0.1750.146 on Mac.

  5. #5
    Sencha Premium User
    Join Date
    Jan 2009
    Posts
    466

    Default

    I saw errors like this too

    "isException: true value: TypeError: Cannot read property 'style' of null"

    It only happened to me the first time I tried App Inspector. I navigated to a page with Ext JS on it with the dev tools closed, opened the dev tools, and then hit the refresh button in the Components tab. Every component I clicked generated this error. I then tried the browser refresh button. After that, the App Inspector worked as expected.

    It seems I could get around the error by refreshing the page with App Inspector open, though I don't know the root cause.



  6. #6
    Sencha Developer
    Join Date
    Sep 2008
    Location
    Antioch, IL
    Posts
    1,516

    Default

    Are you trying this on any page/app which is publicly accessible? I'd love to be able to repeat the problem in order to fix it. :-)

  7. #7
    Sencha Premium User
    Join Date
    Jan 2009
    Posts
    466

    Default

    My first test with the App Inspector was just to go to the Ext JS docs on sencha.com, so this is publicly accessible

    The weird thing is that I cannot recreate the error anymore, either. It literally only happened on the first page I tried and then refreshing the browser seemed to take care of it. It might just be some flakiness with the very first page after the extension is installed? I hadn't restarted Chrome after installing the extension, though I don't know that would matter much.

  8. #8
    Sencha Developer
    Join Date
    Sep 2008
    Location
    Antioch, IL
    Posts
    1,516

    Default

    Quote Originally Posted by firefoxSafari View Post
    My first test with the App Inspector was just to go to the Ext JS docs on sencha.com, so this is publicly accessible

    The weird thing is that I cannot recreate the error anymore, either. It literally only happened on the first page I tried and then refreshing the browser seemed to take care of it. It might just be some flakiness with the very first page after the extension is installed? I hadn't restarted Chrome after installing the extension, though I don't know that would matter much.
    Problem solved? Haha... at least it's working for you now.

    That's really strange, I never hit that problem when I install fresh or disable/enable the extension.

    At a high level, the extension injects some code into the inspected window on startup/refresh so if that fails (for whatever reason) you'd hit the errors you mention.

  9. #9
    Sencha Premium Member MichaelOstrovsky's Avatar
    Join Date
    May 2008
    Location
    Tel Aviv, Israel
    Posts
    144

    Default

    Same here. doesn't happen any more.

    Another issue : windows don't always marked when i click on them in the app inspector (components tab). Maybe a larger z-index should be used by the extension ?

  10. #10
    Sencha Developer
    Join Date
    Sep 2008
    Location
    Antioch, IL
    Posts
    1,516

    Default

    Ok, glad it's fixed for you as well. I'll make a note to investigate that problem on first load, but it sounds very hard to debug.

    As for the component highlighting, I'll take a look at that too. In some cases it won't highlight components hidden beneath (like inactive tabs and their children) but I'll try to make sure visible things are always highlighted.

Page 1 of 6 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •