Closed coffee-tech closed 11 years ago
Hey @coffee-tech thanks for the feedback. I agree that it can be annoying and a distraction. When working with canvas-based snippets it can also be very SLOW!
You will note that in the beta (http://beta.plnkr.co/edit/?p=options) you can toggle auto-refresh. This is something that will soon come to the main site.
That being said, I think that there is still plenty of room for improvement. I would like to come up with some sort of heuristic to determine the right time to refresh.
What would be possible would be to refresh only when the background linter reports no errors and a certain duration has elapsed since the last keystroke. This could be a problem though if there is a known error in the code and the user wants to refresh anyway or if the linting settings are too strict and are reporting excessive errors.
What do you think?
I think the strategy for determine the right time to refresh is different for each type of projects. IMO that strategy should be provided as profiles for users to select. Sorry I can't help cause I'm pretty new to javascript and Web-dev P/s: I didn't know the beta's there ;) Great job
When a plunker is not completed or being heavily refactored, auto-refresh is inconvenient and brings distractions