Results 1 to 5 of 5

Thread: 2 possible bugs/issues with v3.0.0.230

    You found a bug! We've classified it as SDKTOOLS-253 . We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
  1. #1
    Ext JS Premium Member cmeans's Avatar
    Join Date
    Jun 2010
    Location
    Chicago, IL USA
    Posts
    115
    Vote Rating
    7
      0  

    Default 2 possible bugs/issues with v3.0.0.230

    I'm running this on Windows XP SP3.

    ExtJS v4.1.1a commercial.

    Quite possibly I just have something configured wrong...

    #1
    Whenever I run "sencha app build", I get a new (empty) directory called "build" (one level above at the level of my application directory).

    The "build" directory inside my application directory is created and populated correctly...it's just weird getting that extra "build" directory above.

    #2
    The build "process" did not detect that I had an xtype=form, with standardSubmit = true.

    Once I added 'Ext.form.action.StandardSubmit' to the requires array in the app.js, all was good...but I would have expected the process to detect it's requirement from the code.

    Are these problems mine (configuration/understanding), or elsewhere?

    Thanks.

  2. #2
    Sencha - Sr Software Engineer mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    39,556
    Vote Rating
    1272
      0  

    Default

    #1 Is the build directory weird or the app name directory within the build directory? Remember you can have multiple workspaces now so I'm not too sure why it's weird.

    #2 Cmd will auto-detect some things but not everything yet. It's a good rule of thumb that if the Ext JS class you are extending does not require it, you must. For your case, neither Ext.form.Panel and Ext.form.Basic require Ext.form.action.StandardSubmit so you must.
    Mitchell Simoens @LikelyMitch
    Sencha Inc, Senior Software Engineer
    ________________
    Learn BBCode and use it! Checkout the CODE tag!

    Check out my GitHub, lots of nice things for Ext JS and Sencha Touch
    https://github.com/mitchellsimoens

  3. #3
    Ext JS Premium Member cmeans's Avatar
    Join Date
    Jun 2010
    Location
    Chicago, IL USA
    Posts
    115
    Vote Rating
    7
      0  

    Default

    #1
    I'm using the default "build" directory name: build.

    The app name is "Locator".

    I checked two other projects that I've been working on, and it's not happening there.

    The only thing I note that's different is that the Eclipse project name & main folder has underscores "_" in the folder name.

    #2
    Understood. It just means that we need to remember to test every single part of the UI after a code change to be sure we've confirmed that all library code we need has been added.

    But, that's reasonable.

    Thanks.

    -Chris

  4. #4
    Ext JS Premium Member cmeans's Avatar
    Join Date
    Jun 2010
    Location
    Chicago, IL USA
    Posts
    115
    Vote Rating
    7
      0  

    Default

    #1
    I appear to have tracked down where the issue is:

    If I leave the default (initial) setting:

    Code:
    workspace.build.dir=${workspace.dir}/build/${app.name}
    in .sencha/workspace/sencha.cfg, then I get that extra (but empty) "build" folder.

    If however, it set it to something else like:

    Code:
    workspace.build.dir=${workspace.dir}/../../PrecompiledWeb/${app.name}
    I then don't appear to get any extra folders created anywhere.

    -Chris

  5. #5
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Location
    Kansas
    Posts
    1,725
    Vote Rating
    248
      0  

    Default

    We are missing some entries in our auto-dependency configuration file ... for standardSubmit - thanks!

Posting Permissions

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