Closed corysimmons closed 8 years ago
There is no development happening. However, Autosave still works well with the latest stable Chrome.
Why do you think workspaces are useless?
It just seems half finished.
doesn't save dom changes
This one is hard to implement. You probably wouldn't want to save DOM changes made by JS—only by the devtools. There's currently no easy way to distinguish the two.
You may have a better luck asking for this feature on Chromium bug tracker.
have to have selectors already existing in .html/.css
You can add rules to a specific CSS file:
preprocessing is borked (you can change pre-existing scss but if you add a new declaration to a ruleset it applies your changes to the css -- not the scss file)
This one is hard to implement, too.
There is something happening with sass/scss in Chrome DevTools: https://code.google.com/p/chromium/issues/detail?id=527993 I don't understand what exactly as they don't talk about the user impact.
All your complaints are completely valid, though.
Awesome, thanks for the help.
It's still unusable and probably will be for the foreseeable future. It's too bad. Live editing could be amazing..
You can add rules to a specific CSS file
Unfortunately that doesn't work with preprocessors, just .css -- making it useless.
Sorry I'm cranky. Hate spending hours learning tools just to discover they're complete junk.
Are any of these things possible with your project? Or possible for a third party project at all?
Are any of these things possible with your project?
No at this stage, no.
Or possible for a third party project at all?
None that I know of, I'm afraid.
Okay, well, thank you.
Is this still under development or do you think workspaces fills this roll now?
I think workspaces is completely useless and there's a huge void to fill there.