1. #1
    Sencha Premium Member
    Join Date
    Dec 2011
    Location
    London, UK
    Posts
    260
    Vote Rating
    8
    bseddon will become famous soon enough

      0  

    Default Control over Ext.Loader config options

    Control over Ext.Loader config options


    I find debug breakpoints are lost after deploying a project. The problem seems to be because the Ext.Loader prefers to disable caching which then seems to cause the browsers to forget any debug break points. If I add

    disableCaching: false;

    to the loader's setConfig options in designer.js then I'm able to debug until designer.js is re-generated. What am I doing wrong? Is there an option in the designer i can set to have it generate the extra loader configuration I seem to need. Is there an better way to be debugging?

  2. #2
    Sencha Premium Member
    Join Date
    May 2010
    Location
    Guatemala, Central America
    Posts
    1,306
    Vote Rating
    110
    ssamayoa is just really nice ssamayoa is just really nice ssamayoa is just really nice ssamayoa is just really nice ssamayoa is just really nice

      0  

    Default


    Mmmm....

    Rather than a property in the application may be different deploy and lauch options:

    Launch/Deploy with loader enabled / cache disabled (current behaviour)
    Launch/Deploy with loader enabled / cache enabled
    Launch/Deploy with loader disabled

    And make an application's option which one you want when just click launch or deploy.

    Regards.
    UI: Sencha Architect 3.x / ExtJS 4 & 5
    Server side: JEE / EJB 3.x / CDI / JPA 2.x/ JAX-RS / JasperReports
    Application Server: Glassfish / WildFly
    Databases: Oracle / DB2 / MySQL / Firebird

    If you like my answer please vote!

Thread Participants: 1