i'm currently evaluating WebStorm/PHPStorm and am very satisfied so far with all the features.
As a test, i created a small HTML File containing nothing much but some DIV with text. A CSS
File that is generated via a watcher from a LESS file.
I've read somewhere that JS files are being hot swapped and they should be "event driven" or cyclic
to make sure that live editing works with them.
Can anyone provide me with an example what that exactly means ?
This pretty much is the only thing preventing me currently from going all out and purchasing PHPStorm.
> I've read somewhere that JS files are being hot swapped and they should be "event driven" or cyclic
> to make sure that live editing works with them.
My colleague will get back to you to help you troubleshoort why it is not working. Meanwhile you could try the very simple example of a webpage with one button that alerts() on click, and try to change the message text via live edit...
Ok, i already suspected that it would be like that.
new files have been loaded that i could hook into to listen for changes?
That would be useful.
So i've been trying a couple things, and either i'm understanding this completely wrong or ... well.. i dunno.
So for completeness sake, here's what i'm trying to achieve.
I have a very rudimentary html file:
which overwrites the content of my DIV every second:
var myDiv = document.getElementsByTagName('div');
myDiv.innerHTML = testString;
What i expect to happen, is that when i edit the content of the testString variable, ideally it would
show me the new content of the variable in the DIV .. or that the entire file would be reloaded and start over
and still show me the new content in my DIV.
Neither of this is actually the case, the Interval continues running but with the same content of the variable before
i edited it.
So, what is it now? Do i understand this completely wrong? Did i stumble over a bug?
Cheers and thanks for all the help
bump, since i really would like to know if i'm asking for the moon or if this is supposed to work.
Just use literal instead of file-level variable ("someText" instead of testString). I don't know why, please watch http://youtrack.jetbrains.com/issue/WEB-7390
Google Chrome limitation — http://code.google.com/p/chromium/issues/detail?id=226083
I solved a similar issue by deleting the deployment.
File > Settings > Deployment > Hit the Minus and Apply