1. #11
    Sencha User
    Join Date
    Nov 2012
    Posts
    1
    Vote Rating
    0
    dcarl1 is on a distinguished road

      0  

    Default


    Anyone have any luck with this?

    I've tried everything mentioned in this thread and am getting flooded with:

    Javascript Intellisense Message: \AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\OYL2KFH5\ext-all-fds90[1]..js(27:339144) : Function expected

    messages followed by a timeout and sometimes an overflow.

    This is my view:

    <link rel="stylesheet" type="text/css" href="http://localhost/extjs/resources/css/ext-all.css" />
    <link rel="stylesheet" type="text/css" href="http://localhost/extjs/examples/shared/example.css" />


    <script type="text/javascript" src="http://localhost/extjs/ext-all.js"> </script>
    <script type="text/javascript">
    /// <reference path="C:\inetpub\wwwroot\extjs\ext-all-dev.js" />

  2. #12
    Sencha Premium Member
    Join Date
    Jul 2012
    Posts
    31
    Vote Rating
    1
    Qube is on a distinguished road

      0  

    Default


    The JavaScript interpreter in VS2010 is a bit shaky. It's the same one used in WSH and older IE. I've found it falls over a short way into parsing the Ext library.

    I know this doesn't solve your immediate issue, but thankfully 2012 is much better in this regard. It uses the Chakra engine which seems to do a much better job of understanding Ext. It's more robust all round.

    That said, the reliance on object literals means there isn't actually that much autocomplete to provide. That is, until someone makes some TypeScript interface definitions

  3. #13
    Sencha User
    Join Date
    Mar 2009
    Posts
    17
    Vote Rating
    0
    aricc is on a distinguished road

      0  

    Default it works well

    it works well


    Ext4.1 & VS2010
    add code below
    ///<reference path="ExtJS/ext-all-debug.js" />

    then intellisense works

  4. #14
    Sencha Premium Member
    Join Date
    Jul 2012
    Posts
    31
    Vote Rating
    1
    Qube is on a distinguished road

      0  

    Default


    It does "work", but I'm not sure I'd say it works well in VS2010. Using your exact example with 4.1.0, the intellisense service starts falling over at about line 8,000. There is no autocomplete for anything defined after that point (which is the reason for this topic).

    For example, type:
    Ext.Msg.

    ...and you'll get nothing (Ext.Msg isn't defined until line ~150,000).

    On the other hand, if I use VS2012 and put ext-all-dev.js (highly recommended vs debug) in the new _references.js file, there is complete support for the whole library.

    Not trying to be argumentative, but that's just the state of VS2010 with Ext JS.