Results 1 to 7 of 7

Thread: Changed application appFolder writes designer.[js|html] always in the root deploy dir

    Looks like we can't reproduce the issue or there's a problem in the test case provided.
  1. #1
    Sencha Premium Member
    Join Date
    Feb 2012
    Posts
    6
    Vote Rating
    0
      0  

    Default Changed application appFolder writes designer.[js|html] always in the root deploy dir

    Designer files (.js and .html) are always written to the deploy root, all MVC files are written to the changed appFolder, e.g.:

    Deploy path in Settings: /deploy/
    The changed appFolder: ext/app

    designer.[js|html] -> /deploy/
    MVC files -> /deploy/ext/app

    screenshot.png

    Best regards,

    Andreas

  2. #2
    Sencha User Phil.Strong's Avatar
    Join Date
    Mar 2007
    Location
    Olney, MD
    Posts
    1,953
    Vote Rating
    65
      0  

    Default

    This is by design! How/why would you have liked it to work?
    Phil Strong
    @philstrong

  3. #3
    Sencha User
    Join Date
    Apr 2012
    Posts
    1
    Vote Rating
    0
      0  

    Default deploy into an environment with static-route

    I also find it strange that the deploy route is affected by the appFolder. Why should a deploy behaviour be changed by a project configuration? Well this is to general... An example for a potential problem:

    I use a web-app, which serves the javascript files via "/static/js/". This means that I'd set the appFolder respectively and would expect the app.js and the "app"-directory to appear under this path. But if I now put the deploy setting to "/webapp/static/js" then an additional "/webapp/static/js/static/js/app/ .." is created.

    Am I missing something? Thanks for your help and a great project. love it so far!

  4. #4
    Sencha User Phil.Strong's Avatar
    Join Date
    Mar 2007
    Location
    Olney, MD
    Posts
    1,953
    Vote Rating
    65
      0  

    Default

    well your double entering it in this case. Simply make your deploy path /webapp/

    The limitation is that by convention MVC requires an app folder that has models/ views/ controllers/ etc .. underneath it.

    Know that in the future we'll be evolving the deploy to do move than rsync / xcopy files. Think "sencha app build production" aka better integration with SDKTools to deploy your application for production
    Phil Strong
    @philstrong

  5. #5
    Sencha User
    Join Date
    Apr 2012
    Location
    Mxico
    Posts
    11
    Vote Rating
    1
      0  

    Default

    I was wondering, is there is a way to configure appFolder directory to be relative to the app.js file? due when i call app.js it look for the app folder in the root folder, that is not correct.

  6. #6
    Sencha User Phil.Strong's Avatar
    Join Date
    Mar 2007
    Location
    Olney, MD
    Posts
    1,953
    Vote Rating
    65
      0  

    Default

    Can you give me example pathing? I'm not fully understanding the question.
    Phil Strong
    @philstrong

  7. #7
    Sencha User
    Join Date
    Apr 2012
    Location
    Mxico
    Posts
    11
    Vote Rating
    1
      0  

    Default

    Sure, I'm currently working with MVC 3 as server tech, and here paths are in this way http://server/controller/action but my js are in http://server/javascript/controller/accion, but if i don't set appFolder loader tries to get app folder in the root I mean http://server/app that is not correct, even that if i set appFolder var in architect as /javascript/controller/action/app it creates all those folders and at the end app folder is http://server/javascript/controller/...ler/action/app. Is there any way to acomplish this? perhabs if appFolder could be relative to app.js file I don't know

Posting Permissions

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