[redesign] File page #963
No reviewers
Labels
No labels
accessibility
app-parity
area: creator
area: daemon
area: design
area: devops
area: discovery
area: docs
area: installer
area: internal
area: livestream
area: performance
area: proposal
area: reposts
area: rewards
area: search
area: security
area: subscriptions
area: sync
area: ux
area: viewer
area: wallet
BEAMER
channel
comments
community PR
consider soon
core team
css
dependencies
electron
Epic
feature request
first-timers-only
good first issue
hacktoberfest
help wanted
hub-dependent
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
merge when green
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
notifications
odysee
on hold
playlists
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
recsys
redesign
regression
resilience
sdk dependent
Tom's Wishlist
trending
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-desktop#963
Loading…
Reference in a new issue
No description provided.
Delete branch "redesign-wip"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I did:
Basic styling/layout for file page components
What I need to come back to:
The video player doesn't scale properly. I spent some time on it and was having issues, just going to leave it for now and come back later
Send tip modal (style)
Download progress/open/remove/report buttons inside of the file viewer
For the buttons inside the file viewer I didn't spend much time on them. I think more discussion is needed on if we actually want them there, and if so what the exact behavior should be.
@ -1,14 +1,14 @@
// @flow
Changed the spinner to not actually be a spinner, but might as well keep the name as is
@ -19,1 +5,3 @@
}
type Props = {
play: string => void,
isLoading: boolean,
Play/pause from the spacebar seems to work fine without this. Maybe it's need for other OS's?
I'll come back to this later
Not sure if we need this, I'll come back to it
@ -19,1 +5,3 @@
}
type Props = {
play: string => void,
isLoading: boolean,
yeah it should be fine without this... ill check linux
yeah it should be fine without this, I will check linux
As usual, I'm very happy with this. I have two comments about the code. And then I will post a follow up comment talking about the aesthetics.
Fine to merge at your convenience
@ -19,1 +5,3 @@
}
type Props = {
play: string => void,
isLoading: boolean,
ok i figured our why it was there.
When you load the page, don't click anything, and press the space bar, this starts the video / initiates the download. When you take this out, it no longer works -- at least on linux.
That said, I think its better to take out this functionality, since we are going to implement autoplay soon anyway.
@ -21,0 +34,4 @@
const { claim_id: claimId, uri, sendSupport, sendTipCallback } = this.props;
const { amount } = this.state;
sendSupport(amount, claimId, uri);
I dont think it really matters, but isn't the better way to do this to make a type for WalletSendTip?
@seanyesmunt I think the video player is too small, and the font "Published on ..." is too big and far away from the video title if that makes sense. Also maybe the line spacing in the title is too large.
@liamcardenas Agreed the video player is too small. That is pretty much the min height. When you shrink the window down all the way that is what it will be. I spent some time trying to get it to scale/grow nicely as the width increases, but got mad and gave up.
Valid concerns, that will be something we can discuss with nicholas on a group call when I come back around to this.
@ -21,0 +34,4 @@
const { claim_id: claimId, uri, sendSupport, sendTipCallback } = this.props;
const { amount } = this.state;
sendSupport(amount, claimId, uri);
Not sure I follow