Search Type: Posts; User: wgrant

Search: Search took 0.03 seconds.

  1. I'll give that a try. I think the best case would be to load the manifest json that is already there so that I don't have to re-declare all of that. I'll report what I find.

    Thanks.
  2. It's most likely that your store isn't loaded YET. Stores load asynchronously so you maybe loading the store and expecting the data to be there for the next line of code. You need to set an event...
  3. You really have to in 6 because you need the manifest to be able to be able to find classes now that they can be in classic, modern or app folders. Unfortunately 6 is not as simple as previous...
  4. Thank you. As to your problem of the Jasmine screen being replaced by your viewport, I have solved this in my environment.

    Basically, I changed my app.js to instantiate Application class like...
  5. I don't understand... If you are not bootstrapping your application, how are you getting the toolkit paths to resolve? For example, if the Ext.manifest is 'classic', then the framework should look...
  6. How about now?
  7. How about supporting multiple locales so that the user can switch between 3 or 4 different languages? I have this working beautifully in DEV but the PROD build does not include the locales.
  8. This is a surprising oversight for an 'Enterprise' level JavaScript library. Wouldn't it be standard practice to send the whole object to the back end and let the database handle the update in a...
  9. From the guide on Unit Testing in Ext JS 4.2.0 docs:


    Ext.require('Ext.app.Application');


    var Application = null;


    Ext.onReady(function() {
  10. After upgrading to Ext 4.2.0, I find the MVC Unit Testing Guide to no longer work. Specifically I get the following error in Chrome:

    Uncaught Ext.app.Application.constructor():...
Results 1 to 10 of 10