Closed wryk closed 10 years ago
shouldn't it imply --watch ?
actually --reload need an explicit --watch, should i make an implicit --watch on --reload ?
Either require it or make it implicit, imho.
Haha oh wow thanks @jonathanong :)
haha i always see you commenting and being helpful in every repo on github, so why not? :D
Travis failure looks like a transient failure ? Seems like it's #548
wow, @Nami-Doc in component organization, nice :3
first travis failure is my fault, but now it's just a malformed json from bitbucket on component install
yeah, i should fix that.
I wonder thogh, should this really be in the core ? Do we consider it's a common enough case ?
I see how --watch
is useful for nearly every component but I'm not that sure for --reload
(I'm actually wondering if people later will come and ask for another option to change port and stuff haha)
dunno. sounds like more options ~_~
these option lists are getting too long.
i'm not even a big fan of reload. makes sense for css, but sometimes reloading js just messes things up. but i think it's important for a lot of devs workflow.
anyone wanna try this out?
I'm not sure we even need watch really, just introduces a race between viewing something and having it build, vs building on demand
it's for components though. apps shouldn't be using it, but components don't have middleware to build on demand.
ah yeah true that makes more sense
having played around with a few webkit apps I really love watch, and for dev flow, I guess live reload is a neat feature
i forget that pull request i rebuild and now travis pass, others things to add ?
Looks good to me
How to let the users know that they should add livereload script in the html file to make livereload works?
I'll add a note in component/guide api.md file tonight
tonigth
ah ah ah ah :< component/guide@c55b9a4
514