Closed hced closed 9 years ago
It appears doable. Looked at it a little bit. Doesn't seem like too much code. Just have to understand how it works a little better than I do.
Looked again, seems there is a lot involved.
Worth mentioning, there is very little set up for live reload. Mimosa's live reload isn't this livereload. There's no browser plugin. Mimosa manages it all itself. Most any of the skeletons and the mimosa new
projects will come with live reload just working without you needed to do a thing.
Ah, I see. I thought it required the browser plugin-thingy in your link. All good and thanks for taking a look!
I personally favor BrowserSync over LiveReload. Would it be considerable adding support for the former out of the box?
tl;dr
My personal opinion is that BrowserSync provides a more competent solution, especially thanks to its simultaneous multi-device testing and hassle-free setup. Maybe it's just me, but I also have a feeling that it is live-updating in a slightly snappier fashion. Maybe because LiveReload uses redundant animations when things change, if I'm not mistaken.
Disclaimer: I'm not a programmer by any stretch. So please forgive me if the operation of hooking up BrowserSync in your Mimosa-based tooling should be fairly obvious. Even if so, perhaps it could be documented somewhere to make the ride as silky smooth as possible for the weak programmers among us?