Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.

  1. #1
    Sencha Premium Member
    Join Date
    Nov 2007
    Location
    Sydney
    Posts
    27
    Answers
    1
    Vote Rating
    4
    CaCtus491 is on a distinguished road

      0  

    Default Answered: Publishing confusion

    Answered: Publishing confusion


    Is there a clear reference for the building / publishing process for SA?

    When I select 'build web app' from the toolbar, I'd expect SA to build the environment currently selected under build settings, ie, regenerate the files in /build/production or /build/testing, and nothing more.

    When I click the 'publish' button from the toolbar, I'd expect SA to copy the contents from /build/production or /build/testing to the publish path. It may also complete a build if required.

    As of SA 3.0.4.1386, if I leave the publish path blank under build settings, then run a build, it behaves as proposed above. If I add a 'publish path' under build settings, it not only builds, but also copies the output to the specified path. Ok, we can work with this.

    This is where I think the confusion starts.
    Under build settings, we specified a publish path. One would expect when they click publish from the toolbar, this is where our compiled project output would end up. It isn't until one clicks 'project settings' and finds there is an option in there ALSO called 'publish path', and that this is the path that 'publish uses', with the 'publish' button copying most of the of the project to that location?

    At the very least, it seems that something should be renamed to clarify things?

  2. Quote Originally Posted by CaCtus491 View Post
    Is there a clear reference for the building / publishing process for SA?

    When I select 'build web app' from the toolbar, I'd expect SA to build the environment currently selected under build settings, ie, regenerate the files in /build/production or /build/testing, and nothing more.

    When I click the 'publish' button from the toolbar, I'd expect SA to copy the contents from /build/production or /build/testing to the publish path. It may also complete a build if required.

    As of SA 3.0.4.1386, if I leave the publish path blank under build settings, then run a build, it behaves as proposed above. If I add a 'publish path' under build settings, it not only builds, but also copies the output to the specified path. Ok, we can work with this.

    This is where I think the confusion starts.
    Under build settings, we specified a publish path. One would expect when they click publish from the toolbar, this is where our compiled project output would end up. It isn't until one clicks 'project settings' and finds there is an option in there ALSO called 'publish path', and that this is the path that 'publish uses', with the 'publish' button copying most of the of the project to that location?

    At the very least, it seems that something should be renamed to clarify things?
    Publish from the toolbar will publish your entire app. This path is edited from Project Settings.

    If you populate the publish path in the web build settings, it will move only the built bits to that directory.

  3. #2
    Sencha - Architect Dev Team
    Join Date
    Jan 2009
    Location
    Frederick, Maryland
    Posts
    741
    Answers
    54
    Vote Rating
    30
    jminnick will become famous soon enough jminnick will become famous soon enough

      0  

    Default


    Quote Originally Posted by CaCtus491 View Post
    Is there a clear reference for the building / publishing process for SA?

    When I select 'build web app' from the toolbar, I'd expect SA to build the environment currently selected under build settings, ie, regenerate the files in /build/production or /build/testing, and nothing more.

    When I click the 'publish' button from the toolbar, I'd expect SA to copy the contents from /build/production or /build/testing to the publish path. It may also complete a build if required.

    As of SA 3.0.4.1386, if I leave the publish path blank under build settings, then run a build, it behaves as proposed above. If I add a 'publish path' under build settings, it not only builds, but also copies the output to the specified path. Ok, we can work with this.

    This is where I think the confusion starts.
    Under build settings, we specified a publish path. One would expect when they click publish from the toolbar, this is where our compiled project output would end up. It isn't until one clicks 'project settings' and finds there is an option in there ALSO called 'publish path', and that this is the path that 'publish uses', with the 'publish' button copying most of the of the project to that location?

    At the very least, it seems that something should be renamed to clarify things?
    Publish from the toolbar will publish your entire app. This path is edited from Project Settings.

    If you populate the publish path in the web build settings, it will move only the built bits to that directory.
    Jason Minnick
    Sencha Architect Development Team

  4. #3
    Sencha Premium Member
    Join Date
    Nov 2007
    Location
    Sydney
    Posts
    27
    Answers
    1
    Vote Rating
    4
    CaCtus491 is on a distinguished road

      0  

    Default


    Thanks for the response. This lines up with what I found whilst writing my original post

    I still maintain that for the uninitiated, having two 'publish path' settings leads to confusion.
    Also, genuine follow up question, why would one want to publish the entire app, copying many thousands of files?

  5. #4
    Sencha - Architect Dev Team
    Join Date
    Jan 2009
    Location
    Frederick, Maryland
    Posts
    741
    Answers
    54
    Vote Rating
    30
    jminnick will become famous soon enough jminnick will become famous soon enough

      0  

    Default


    Quote Originally Posted by CaCtus491 View Post
    Thanks for the response. This lines up with what I found whilst writing my original post

    I still maintain that for the uninitiated, having two 'publish path' settings leads to confusion.
    Also, genuine follow up question, why would one want to publish the entire app, copying many thousands of files?
    Not every user chooses to "build" their app. So they use this to move their bits to a production location, or a staging location perhaps.
    Jason Minnick
    Sencha Architect Development Team

Thread Participants: 1