-
Notifications
You must be signed in to change notification settings - Fork 2
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
move to react #1
Comments
Yes this sounds good to me.
The gateway might have some small differences in experience from the
desktop app, since it's the opportunity to reach 1000's of people who don't
yet have Livepeer installed. So it could include some educational text and
calls to action to download and run Livepeer, or at least learn more about
it. Also, keep in mind that we may have some more branding/identity/logo
guidelines shortly. So it might be worth focusing more on the functionality
than the design right at this moment.
…On Mon, Sep 11, 2017 at 11:14 AM, buildog ***@***.***> wrote:
The idea is to extract the renderer of https://github.com/livepeer/
LivepeerDesktop (after Emitter stuff will be ready)
So we will have something like:
*livepeer-emitter* (shared lib/api)
*livepeer-gateway* (renderer)
*livepeer-desktop* (electron) + (renderer, aka gateway) + (emitter)
sound good @ericxtang <https://github.com/ericxtang> @dob
<https://github.com/dob> ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AAAolWzN_2YPJ9sOT1Vg8mWqsjuNCpdTks5shU5FgaJpZM4PTUk0>
.
|
@buildog we are working on some interface updates on the Livepeer node, so the interface may undergo some changes. Want to make sure this doesn't affect your development too much. I think I'll have a PR and update the doc in the next 2-3 weeks. My goal is to have a readthedocs site that documents the endpoints to the node, similar to the raiden docs. Want to make sure I understand the benefit of extracting these 3 modules. Are we basically importing the emitter into livepeer-desktop after this? And this means other Node.js apps can import the emitter or the renderer to interact with Livepeer? |
awesome for the doc @ericxtang! and yes, it's exactly what it is about, it's split concerns so projets have re-usable and stable components. |
The idea is to extract the renderer of https://github.com/livepeer/LivepeerDesktop (after Emitter stuff will be ready)
So we will have something like:
livepeer-emitter (shared lib/api)
livepeer-gateway (renderer)
livepeer-desktop (electron) + (renderer, aka gateway) + (emitter)
sound good @ericxtang @dob ?
The text was updated successfully, but these errors were encountered: