-
Notifications
You must be signed in to change notification settings - Fork 246
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
rav1e_js: New demo website with react #2423
Conversation
I actually like plain HTML for the demo purpose, but I will have a look into this :D |
6ba4d58
to
7110a63
Compare
The |
It should only be grayed out when there are no frames yet to be encoded. |
it does not work this way right now :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Earlier when we try, we can send encode it close it,
Then send again, then encode it,
Now we have to send the frames, flush it, then receive it, which seems to be not the right way
Since after encoding we are flushing,
7110a63
to
202e288
Compare
fd1da65
to
3536e3c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The set looks more matured, I have few queries/concerns, please check the review comments :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have tested locally on both Safari and Chrome, seems to work fine,
It is now having proper Status for end-user with basic help.
No issues faced, the only thing in future for cosmetic changes we can do is having a better spacing between things, nevertheless not important.
Also, another minor thing we can debug in future is we have [Violation] 'click' handler took 210ms
warning in chrome when we do send and receive multiple long packets which is not big concern to see at this point.
Thanks a lot for the patchset.
Next thing we can do is, setting up a demo website and hosting it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, I would prefer cleaning up the commits before landing since there are some changes which are being replaced in further commits.
4a2bc6a
to
d9609e1
Compare
Squashed all the commits into one :) |
Changes: * javascript * interactive encoding with buttons * display encoded packets * HelpAndAbout section, which explains background and functionality * Display pretty-printed EncderConfig * rust * add EncoderConfig.toJSON()
d9609e1
to
dda14f6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems fine to me as well.
This PR rebuilds the example
rav1e_js
example website withreact.js
and makes it a bit more visual.