New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for remote presentating. #9

Closed
wants to merge 3 commits into
base: master
from

Conversation

Projects
None yet
2 participants
@noffle
Member

noffle commented May 1, 2016

This adds the optional switches '-p|--present' and '-s|--speaker'.

--speaker will act the same as tslide normally does, except it will also host a local HTTP server that another terminal can connect to using --present. All connections will see the same slides, except with blockquotes stripped -- this lets the speaker see notes on their terminal but not expose them to the viewers.


I was considering forking to add this, since it does expand the scope of the module a bit. All functionality is opt-in though, and no server is started unless --speaker is provided. I figured I'd pass it by you in case it's something you'd also wouldn't mind seeing in tslide! Let me know if there's any UX you think could be made better.


This is blocked on substack/node-charm#28 getting merged, since I'm piping different charm instances locally vs to each viewer.


example

noffle added some commits May 1, 2016

Add support for remote presentating.
This adds the optional switches '-p|--present' and '-s|--speaker'.

--speaker will act the same as tslide normally does, except it will also
host a local HTTP server that another terminal can connect to using
--present. All connections will see the same slides, except with
blockquotes stripped -- this lets the speaker see notes on their
terminal but not expose them to the viewers.
@noffle

This comment has been minimized.

Show comment
Hide comment
@noffle

noffle May 2, 2016

Member

Woo substack/node-charm#28 is merged (and covered under your semver ranges). I added a commit here to update the charm dep in package.json to ~1.0.1.

Member

noffle commented May 2, 2016

Woo substack/node-charm#28 is merged (and covered under your semver ranges). I added a commit here to update the charm dep in package.json to ~1.0.1.

@noffle

This comment has been minimized.

Show comment
Hide comment
@noffle

noffle May 16, 2016

Member

ping

Member

noffle commented May 16, 2016

ping

@dominictarr

This comment has been minimized.

Show comment
Hide comment
@dominictarr

dominictarr May 17, 2016

Collaborator

sorry @noffle how about I add you as a maintainer? then you can merge this your self

Collaborator

dominictarr commented May 17, 2016

sorry @noffle how about I add you as a maintainer? then you can merge this your self

@dominictarr

This comment has been minimized.

Show comment
Hide comment
@dominictarr

dominictarr May 17, 2016

Collaborator

@noffle okay you are a collaborator and npm owner too now.

Collaborator

dominictarr commented May 17, 2016

@noffle okay you are a collaborator and npm owner too now.

@noffle

This comment has been minimized.

Show comment
Hide comment
@noffle

noffle May 17, 2016

Member
Member

noffle commented May 17, 2016

@noffle

This comment has been minimized.

Show comment
Hide comment
@noffle

noffle May 26, 2016

Member

Closed. We can do better using pipes and composition! I wrote a bit about how to go about doing this same feature using named pipes and a bit of grepping instead of bloating the tool with more features: http://blog.eight45.net/2016/05/26/tslide.html

Superseded by #10.

Member

noffle commented May 26, 2016

Closed. We can do better using pipes and composition! I wrote a bit about how to go about doing this same feature using named pipes and a bit of grepping instead of bloating the tool with more features: http://blog.eight45.net/2016/05/26/tslide.html

Superseded by #10.

@noffle noffle closed this May 26, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment