LBRYCommunity/lbry-desktop
1
0
Fork 0
Code Issues 596 Pull requests 6 Projects Releases 238 Packages Wiki Activity

Video overlay #825

Closed
hackrush01 wants to merge 9 commits from video-overlay into master
pull from: video-overlay
merge into: LBRYCommunity:master
Conversation 5 Commits 9 Files changed 19 +374 -160
hackrush01 commented 2017-12-07 19:10:12 +01:00 (Migrated from github.com)
Copy link
No description provided.
neb-b (Migrated from github.com) reviewed 2017-12-08 06:17:24 +01:00
src/renderer/js/component/common.js
@ -0,0 +205,4 @@
return (
<div className="video__loading-screen">
<div>
{spinner && <div className="video__loading-spinner" />}
neb-b (Migrated from github.com) commented 2017-12-08 06:17:24 +01:00
Copy link

This should use the <Spinner /> component

This should use the `<Spinner />` component
hackrush01 (Migrated from github.com) reviewed 2017-12-08 11:24:38 +01:00
src/renderer/js/component/common.js
@ -0,0 +205,4 @@
return (
<div className="video__loading-screen">
<div>
{spinner && <div className="video__loading-spinner" />}
hackrush01 (Migrated from github.com) commented 2017-12-08 11:24:38 +01:00
Copy link

I noticed one thing. We already have a common.js file here(file 1), but the <Spinner /> component comes from here(folder 1), a new common folder with just that component.
Are we breaking down file 1 to individual components and putting them in folder 1? Or should I include <Spinner /> component in file 1. The latter option is better IMO as then we don't have to include different files for each "common" component, unless former is better for some use cases.

I noticed one thing. We already have a `common.js` file [here(file 1)](https://github.com/lbryio/lbry-app/blob/master/src/renderer/js/component/common.js), but the `<Spinner />` component comes from [here(folder 1)](https://github.com/lbryio/lbry-app/blob/master/src/renderer/js/component/common), a new common folder with just that component. Are we breaking down file 1 to individual components and putting them in folder 1? Or should I include `<Spinner />` component in file 1. The latter option is better IMO as then we don't have to include different files for each "common" component, unless former is better for some use cases.
kauffj (Migrated from github.com) reviewed 2017-12-08 17:03:16 +01:00
src/renderer/js/component/common.js
@ -0,0 +205,4 @@
return (
<div className="video__loading-screen">
<div>
{spinner && <div className="video__loading-spinner" />}
kauffj (Migrated from github.com) commented 2017-12-08 17:03:16 +01:00
Copy link

@hackrush01 @seanyesmunt @liamcardenas I think common.js should die and these should all just be individual components.

@hackrush01 @seanyesmunt @liamcardenas I think `common.js` should die and these should all just be individual components.
liamcardenas (Migrated from github.com) reviewed 2017-12-08 18:33:06 +01:00
src/renderer/js/component/common.js
@ -0,0 +205,4 @@
return (
<div className="video__loading-screen">
<div>
{spinner && <div className="video__loading-spinner" />}
liamcardenas (Migrated from github.com) commented 2017-12-08 18:33:06 +01:00
Copy link

I agree

I agree
lyoshenka commented 2018-02-05 21:48:55 +01:00 (Migrated from github.com)
Copy link

This is on hold. When we're ready to work on this, we should re-evaluate and figure out the right approach.

This is on hold. When we're ready to work on this, we should re-evaluate and figure out the right approach.

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear 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

Work is part of a proposal

  
area: reposts

   
area: rewards

   
area: search

   
area: security

   
area: subscriptions

   
area: sync

   
area: ux

   
area: viewer

   
area: wallet

   
BEAMER

Beamer is waiting on you!

  
channel

   
comments

   
community PR

   
consider soon

Discuss this issue at the next planning meeting, then remove this label

  
core team

   
css

   
dependencies

   
electron

   
Epic

   
feature request

   
first-timers-only

   
good first issue

   
hacktoberfest

Welcome to Hacktoberfest

  
help wanted

   
hub-dependent

   
icebox

Long-term storage

  
Invalid

   
level: 0

   
level: 1

No knowledge of the existing code required

  
level: 2

Some knowledge of the existing code is recommended

  
level: 3

Significant knowledge of the existing code is recommended

  
level: 4

Intimate knowledge of the existing code is recommended

  
merge when green

   
needs: exploration

Solution unclear, needs research

  
needs: grooming

Issue needs to be groomed before work can start

  
needs: priority

Priority level needs to be defined

  
needs: repro

Issue needs step-by-step instructions on how to reproduce in latest code

  
needs: tech design

Needs technical design signoff before implementation can begin

  
notifications

   
odysee

   
on hold

Temporarily paused

  
playlists

   
priority: blocker

Issue is blocking release, do ASAP

  
priority: high

Work needs to be moved into sprint ASAP

  
priority: low

Work should be done but can stay in the backlog for now

  
priority: medium

Work needs to be done within 2-3 sprints

  
protocol dependent

   
recsys

   
redesign

general redesign not prioritize for anyone release

  
regression

   
resilience

   
sdk dependent

Requires work on lbry-sdk repo

  
Tom's Wishlist

   
trending

   
type: bug

Existing functionality is wrong or broken

  
type: discussion

A conversation. No specific changes requested

  
type: improvement

Existing (or partially existing) functionality needs to be changed

  
type: new feature

New functionality that does not exist yet

  
type: refactor

Minimal user-visible changes, but significant internal work

  
type: task

Either work that's not related to the code, or a small chore that does not fit into other categories

  
type: testing

Solution needs additional user testing

  
unplanned

Work that was not planned into the spirnt, took priority over planned work

  
windows
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
LBRYCommunity/lbry-desktop!825
No description provided.