Roadmap?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
This is a roadmap discussion rather than a scoped implementation task, and it names no files, tests, or entry points. Start by reviewing the proposed WebSockets port, shared XRefresh/LiveReload server, full-path response format, and the linked strict-mode discussion; a decision on scope and acceptance criteria is needed before work can be considered done.
Written by the indexing model from the issue text.
Description
Some things have happened lately. Firefox 4 beta supports WebSockets. LiveReload pops out and its server is using WebSockets. As I see it, next reasonable steps would be:
- WebSockets-based XRefresh for Firefox
- The same file monitoring server for XRefresh and LiveReload
Current response format of LiveReload is just a filename string, like main.css or index.html. I think we should send full path, like /Users/nikitavasilev/Sites/tmp/test.html. Some benefits:
- The filename doesn't work well when few CSS/JS-files named the same. For instance,
foo/main.cssandbar/main.css. - A full path will allow as to do a "strict mode" when we edit something on
file://scheme.
darwin, how hard would be to port XRefresh to WebSockets?
LiveReload developers (andreyvit and dottedmag), what do you think about the same server?
- Dominant language
- C#
- Stars
- 65
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from binaryage/xrefresh
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Firefox 4 support Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in binaryage/xrefresh
Similar issues
-
effort:S P3 refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nightscout/nocturne#1532 ·
-
core dependencies
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
C#/.NET Roslyn LSP Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
DotNetNext/SqlSugar#1458 ·