build 676 - Publish
Come on, are you seriously planning to run a CMD window?
Have you considered how many times a user usually publishes to see the changes and how annoying it is to close a CMD window????
Please, revert to the old system. This is ABSOLUTELY TOO ANNOYING!
I agree. It is a strange move going from a user friendly design to a command prompt.. Even if 'programmers' are the target users.
Pretty annoying having to close all the windows as I deploy about every 5 minutes..
And, most of all, I would agree if you could eventually edit the command (fix the exclude file, for example)....
But just showing the command prompt is simply nagging!
I had turned this on for packaging and simulating re: running longer commands e.g. Sencha Cmd.
A more permanent solution would be to have a built in window that tailed the any and all commands executed.
I know we won't be making another push to 2.1 except critical bugs.
Would you consider a temporary build with just this "feature" removed?
I really think it's annoying and that it slows the day by day usage.
Would you also consider adding a ctrl+somekey combination for publish?
It would be handy to make a
to save and publish without moving hands from keyboard
Publish execute batch
The Publish should have, at least, executed a batch file instead of xcopy so we can customize what a deploy does and add a pause if we care.
This feature is an extra step for me with no gain. When i first saw it I went wow ok, maybe i can customise my deploy now. But this is completely featureless, so +1 to annoyance, -1 to gain
If i could actually work more with the deploy i would be happy, at the moment i run a batch file to "fix" my deploy. I'm using appfolders etc, its kind of kooky
You should have a little more confidence in your programming and only need to quadrouple check stuff when you're in unknown territory.