Date: Fri, 15 Dec 2017 21:12:59 -0800
Subject: [PATCH 06/19] Updated contribution process
---
CONTRIBUTING.md | 36 +++++++++++++++++++++++++++++++++++-
1 file changed, 35 insertions(+), 1 deletion(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index e7d0dce20..a64256fb0 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,3 +1,37 @@
## Contributing to LBRY
-https://lbry.io/faq/contributing
+You found this page! That means you are well on your way to contributing to the LBRY app. This application is primarily written in JavaScript and is built on [Electron](https://electronjs.org) while utilizing [React](https://reactjs.org) and [Redux](https://redux.js.org) for UI and application state.
+
+LBRY is an open source project, and therefore is developed out in the open for everyone to see. What you see here are the latest source code changes and the issues.
+
+Since LBRY is an based around a decentralized community, we believe that the app will be strongest if it receives contributions from individuals outside the core team -- such as yourself!
+
+In order to make contributing as easy and rewarding of possible, we have instituted the following system:
+
+* Anyone can view all issues in the system by clicking on the [Issues](https://github.com/lbryio/lbry-app/issues) button at the top of the page.
+...Feel free to add an issue if you think we have missed something (and you might earn some LBC in the process because we do tip people for reporting bugs).
+* Once on the [Issues](https://github.com/lbryio/lbry-app/issues) page, a user can filter issues by the [Help Wanted](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) label to see a curated list of suggested issues with which community members can help.
+* Every [Help Wanted](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) issue is ranked on a scale from zero to four.
+...--- | ---
+...[**level 0**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+0%22) | Typos and text edit -- a tech savvy non-programmer can fix these
+...[**level 1**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+1%22) | Programming issues that require little knowledge of how the LBRY app works
+...[**level 2**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+2%22) | Issues of average difficulty that require the developer to dig into how the app works a little bit
+...[**level 3**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+3%22) | Issues that are likely too tricky to be level 2 or require more thinking outside of the box
+...[**level 4**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+4%22) | Big features or really hard issues
+...The process of ranking issues is highly subjective. The purpose of sorting issues like this is to give contributors a general idea of the type of issues at which they are looking. It could very well be the case that a level 1 issue is more difficult than a level 2, for instance. This system is meant to help you find relevant issues, not to prevent you from working on issues that you otherwise would. If these rankings don't work for you, feel free to ignore them.
+* After deciding what to work on, [fork](https://help.github.com/articles/fork-a-repo/) this repository, make your changes, and submit a [pull request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/).
+* Once your pull request is visible in the LBRY repo, a LBRY team member will review it and make sure it is up to our standards. At this point, you may have to change your code based on our suggestions and comments.
+* Then, upon a satisfactory review your code, we will merge it and send you a tip (in LBC) for your contribution.
+
+We are dedicated to be fair and friendly in this process. In __general__, level 4 issues will be paid more than level 3 issues which will be paid more than level 2, and so on. However, this is not due to their labels, but rather how difficult they ended up being. Maybe an issue was labeled level 1 but was actually very difficult-- in this case we would be **more than happy** to tip accordingly. If you do good work, we want you to be rewarded for it.
+
+Also, we are here to enable you. We want you to succeed, so do not hesitate to ask questions. If you need some information or assistance in completely an issue, please let us know! This is what we are here for-- pushing development forward.
+
+Lastly, don't feel limited by this list. Should LBRY have built in VPN/proxy support? Add it! It's not in the issue tracker but maybe it's a good idea. Do you think the search layout is unintuitive? Change it! We welcome all feedback and suggestions. That said, it may be the case that we do not wish to incorporate your change, if you don't check with us first. If you want to add a feature that is not listed in the issue tracker, go ahead and [create an issue](https://github.com/lbryio/lbry-app/issues/new), and say in the description that you would like to try to implement it yourself. This way we can tell you in advance if we will accept your changes and we can point you in the right direction.
+
+## Get In Touch
+[Liam](https://github.com/liamcardenas) is the application engineer in charge of community development. He is the person to contact with any development/contribution related questions. Discord: liamsdouble, Email: liam@lbry.io
+[Tom](https://github.com/tzarebczan) is the community manager. He knows more than anyone about the app and all of its flaws. Reach out to him with any questions about how the app works, if a bug has been reported, or if a feature should be requested. Discord: jigglytom, Email: tom@lbry.io
+[Sean](https://github.com/seanyesmunt) is an application engineer who focuses largely on UI/UX. If you have a design or implementation question, feel free to reach out to him. Discord: sean, Email: sean@lbry.io
+
+More information about contributing to LBRY [here](https://lbry.io/faq/contributing).
From 8d28babaf1fa5d1a8722cf52442f1f2f67201573 Mon Sep 17 00:00:00 2001
From: Liam Cardenas
Date: Fri, 15 Dec 2017 21:42:55 -0800
Subject: [PATCH 07/19] Fixed typos and formatting issues
---
CONTRIBUTING.md | 53 +++++++++++++++++++++++++++++--------------------
1 file changed, 31 insertions(+), 22 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a64256fb0..e9d7c9811 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,37 +1,46 @@
-## Contributing to LBRY
+# Contributing to LBRY
You found this page! That means you are well on your way to contributing to the LBRY app. This application is primarily written in JavaScript and is built on [Electron](https://electronjs.org) while utilizing [React](https://reactjs.org) and [Redux](https://redux.js.org) for UI and application state.
-LBRY is an open source project, and therefore is developed out in the open for everyone to see. What you see here are the latest source code changes and the issues.
+LBRY is an open source project, and therefore is developed out in the open for everyone to see. What you see here are the latest source code changes and issues.
Since LBRY is an based around a decentralized community, we believe that the app will be strongest if it receives contributions from individuals outside the core team -- such as yourself!
In order to make contributing as easy and rewarding of possible, we have instituted the following system:
-* Anyone can view all issues in the system by clicking on the [Issues](https://github.com/lbryio/lbry-app/issues) button at the top of the page.
-...Feel free to add an issue if you think we have missed something (and you might earn some LBC in the process because we do tip people for reporting bugs).
-* Once on the [Issues](https://github.com/lbryio/lbry-app/issues) page, a user can filter issues by the [Help Wanted](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) label to see a curated list of suggested issues with which community members can help.
+* Anyone can view all issues in the system by clicking on the [Issues](https://github.com/lbryio/lbry-app/issues) button at the top of the page. Feel free to add an issue if you think we have missed something (and you might earn some LBC in the process because we do tip people for reporting bugs).
+* Once on the [Issues](https://github.com/lbryio/lbry-app/issues) page, a potential contributor can filter issues by the [Help Wanted](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) label to see a curated list of suggested issues with which community members can help.
* Every [Help Wanted](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) issue is ranked on a scale from zero to four.
-...--- | ---
-...[**level 0**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+0%22) | Typos and text edit -- a tech savvy non-programmer can fix these
-...[**level 1**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+1%22) | Programming issues that require little knowledge of how the LBRY app works
-...[**level 2**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+2%22) | Issues of average difficulty that require the developer to dig into how the app works a little bit
-...[**level 3**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+3%22) | Issues that are likely too tricky to be level 2 or require more thinking outside of the box
-...[**level 4**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+4%22) | Big features or really hard issues
-...The process of ranking issues is highly subjective. The purpose of sorting issues like this is to give contributors a general idea of the type of issues at which they are looking. It could very well be the case that a level 1 issue is more difficult than a level 2, for instance. This system is meant to help you find relevant issues, not to prevent you from working on issues that you otherwise would. If these rankings don't work for you, feel free to ignore them.
-* After deciding what to work on, [fork](https://help.github.com/articles/fork-a-repo/) this repository, make your changes, and submit a [pull request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/).
-* Once your pull request is visible in the LBRY repo, a LBRY team member will review it and make sure it is up to our standards. At this point, you may have to change your code based on our suggestions and comments.
-* Then, upon a satisfactory review your code, we will merge it and send you a tip (in LBC) for your contribution.
-We are dedicated to be fair and friendly in this process. In __general__, level 4 issues will be paid more than level 3 issues which will be paid more than level 2, and so on. However, this is not due to their labels, but rather how difficult they ended up being. Maybe an issue was labeled level 1 but was actually very difficult-- in this case we would be **more than happy** to tip accordingly. If you do good work, we want you to be rewarded for it.
+Level | Description
+--- | ---
+[**level 0**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+0%22) | Typos and text edits -- a tech savvy non-programmer can fix these
+[**level 1**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+1%22) | Programming issues that require little knowledge of how the LBRY app works
+[**level 2**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+2%22) | Issues of average difficulty that require the developer to dig into how the app works a little bit
+[**level 3**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+3%22) | Issues that are likely too tricky to be level 2 or require more thinking outside of the box
+[**level 4**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+4%22) | Big features or really hard issues
-Also, we are here to enable you. We want you to succeed, so do not hesitate to ask questions. If you need some information or assistance in completely an issue, please let us know! This is what we are here for-- pushing development forward.
+The process of ranking issues is highly subjective. The purpose of sorting issues like this is to give contributors a general idea of the type of issues at which they are looking. It could very well be the case that a level 1 issue is more difficult than a level 2, for instance. This system is meant to help you find relevant issues, not to prevent you from working on issues that you otherwise would. If these rankings don't work for you, feel free to ignore them.
-Lastly, don't feel limited by this list. Should LBRY have built in VPN/proxy support? Add it! It's not in the issue tracker but maybe it's a good idea. Do you think the search layout is unintuitive? Change it! We welcome all feedback and suggestions. That said, it may be the case that we do not wish to incorporate your change, if you don't check with us first. If you want to add a feature that is not listed in the issue tracker, go ahead and [create an issue](https://github.com/lbryio/lbry-app/issues/new), and say in the description that you would like to try to implement it yourself. This way we can tell you in advance if we will accept your changes and we can point you in the right direction.
+* After deciding what to work on, a potential contributor can [fork](https://help.github.com/articles/fork-a-repo/) this repository, make his or her changes, and submit a [pull request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/).
+* Once the pull request is visible in the LBRY repo, a LBRY team member will review it and make sure it is up to our standards. At this point, the contributor may have to change his or her code based on our suggestions and comments.
+* Then, upon a satisfactory review of the code, we will merge it and send the contributor a tip (in LBC) for the contribution.
-## Get In Touch
-[Liam](https://github.com/liamcardenas) is the application engineer in charge of community development. He is the person to contact with any development/contribution related questions. Discord: liamsdouble, Email: liam@lbry.io
-[Tom](https://github.com/tzarebczan) is the community manager. He knows more than anyone about the app and all of its flaws. Reach out to him with any questions about how the app works, if a bug has been reported, or if a feature should be requested. Discord: jigglytom, Email: tom@lbry.io
-[Sean](https://github.com/seanyesmunt) is an application engineer who focuses largely on UI/UX. If you have a design or implementation question, feel free to reach out to him. Discord: sean, Email: sean@lbry.io
+We are dedicated to being fair and friendly in this process. In __general__, level 4 issues will be paid more than level 3 issues which will be paid more than level 2, and so on. However, this is not due to their labels, but rather how difficult they ended up being. Maybe an issue labeled "level 1" turned out to be very difficult. In this case we would be **more than happy** to tip accordingly. If you do good work, we want you to be rewarded for it.
+
+Also, we are here to enable you. We want you to succeed, so do not hesitate to ask questions. If you need some information or assistance in completing an issue, please let us know! That is what we are here for-- pushing development forward.
+
+Lastly, don't feel limited by this list. Should LBRY have built-in Tor support? Add it! It's not in the issue tracker but maybe it's a good idea. Do you think the search layout is unintuitive? Change it! We welcome all feedback and suggestions. That said, it may be the case that we do not wish to incorporate your change if you don't check with us first (also, please check with us especially if you are planning on adding Tor support :P). If you want to add a feature that is not listed in the issue tracker, go ahead and [create an issue](https://github.com/lbryio/lbry-app/issues/new), and say in the description that you would like to try to implement it yourself. This way we can tell you in advance if we will accept your changes and we can point you in the right direction.
+
+# Get In Touch
+Name | Role | Discord | Email
+--- | --- | --- | ---
+[Liam](https://github.com/liamcardenas) | The application engineer in charge of community development. He is the person to contact with any development/contribution related questions. | liamsdouble | liam@lbry.io
+[Tom](https://github.com/tzarebczan) | Community manager. He knows more than anyone about the app and all of its flaws. Reach out to him with any questions about how the app works, if a bug has been reported, or if a feature should be requested. | jigglytom | tom@lbry.io
+[Sean](https://github.com/seanyesmunt) | An application engineer who focuses largely on UI/UX. If you have a design or implementation question, feel free to reach out to him. | sean | sean@lbry.io
+
+Join our discord [here](https://chat.lbry.io/).
+
+# More Information
More information about contributing to LBRY [here](https://lbry.io/faq/contributing).
From bd3aa1b3493ea3ec03fde94c3c4ee388f6abcf45 Mon Sep 17 00:00:00 2001
From: Travis Eden
Date: Mon, 18 Dec 2017 12:02:55 -0500
Subject: [PATCH 08/19] Pushing for help with Redux selectors
---
.../component/fileDownloadLink/index.js | 2 ++
.../component/fileDownloadLink/view.jsx | 9 +++++-
src/renderer/component/video/index.js | 2 ++
.../component/video/internal/player.jsx | 12 +++++++-
src/renderer/component/video/view.jsx | 5 ++++
src/renderer/constants/action_types.js | 5 ++++
src/renderer/redux/actions/video.js | 24 +++++++++++++++
src/renderer/redux/reducers/video.js | 29 +++++++++++++++++++
src/renderer/redux/selectors/video.js | 9 ++++++
src/renderer/store.js | 4 ++-
10 files changed, 98 insertions(+), 3 deletions(-)
create mode 100644 src/renderer/redux/actions/video.js
create mode 100644 src/renderer/redux/reducers/video.js
create mode 100644 src/renderer/redux/selectors/video.js
diff --git a/src/renderer/component/fileDownloadLink/index.js b/src/renderer/component/fileDownloadLink/index.js
index d7988c067..9b1141802 100644
--- a/src/renderer/component/fileDownloadLink/index.js
+++ b/src/renderer/component/fileDownloadLink/index.js
@@ -9,6 +9,7 @@ import { makeSelectCostInfoForUri } from "redux/selectors/cost_info";
import { doFetchAvailability } from "redux/actions/availability";
import { doOpenFileInShell } from "redux/actions/file_info";
import { doPurchaseUri, doStartDownload } from "redux/actions/content";
+import { setVideoPause } from "redux/actions/video";
import FileDownloadLink from "./view";
const select = (state, props) => ({
@@ -24,6 +25,7 @@ const perform = dispatch => ({
openInShell: path => dispatch(doOpenFileInShell(path)),
purchaseUri: uri => dispatch(doPurchaseUri(uri)),
restartDownload: (uri, outpoint) => dispatch(doStartDownload(uri, outpoint)),
+ videoPause: val => dispatch(setVideoPause(val)),
});
export default connect(select, perform)(FileDownloadLink);
diff --git a/src/renderer/component/fileDownloadLink/view.jsx b/src/renderer/component/fileDownloadLink/view.jsx
index 32d0fe3c4..68499c273 100644
--- a/src/renderer/component/fileDownloadLink/view.jsx
+++ b/src/renderer/component/fileDownloadLink/view.jsx
@@ -42,8 +42,15 @@ class FileDownloadLink extends React.PureComponent {
purchaseUri,
costInfo,
loading,
+ videoPause,
} = this.props;
+ const openFile = () => {
+ openInShell(fileInfo.download_path);
+ console.log("FileDownloadLink view");
+ videoPause(true);
+ };
+
if (loading || downloading) {
const progress =
fileInfo && fileInfo.written_bytes
@@ -93,7 +100,7 @@ class FileDownloadLink extends React.PureComponent {
button="text"
icon="icon-external-link-square"
className="no-underline"
- onClick={() => openInShell(fileInfo.download_path)}
+ onClick={() => openFile()}
/>
);
}
diff --git a/src/renderer/component/video/index.js b/src/renderer/component/video/index.js
index a9b0ed62d..1b79f8275 100644
--- a/src/renderer/component/video/index.js
+++ b/src/renderer/component/video/index.js
@@ -14,6 +14,7 @@ import {
} from "redux/selectors/file_info";
import { makeSelectCostInfoForUri } from "redux/selectors/cost_info";
import { selectShowNsfw } from "redux/selectors/settings";
+import { selectVideoPause } from "redux/selectors/video";
import Video from "./view";
import { selectPlayingUri } from "redux/selectors/content";
@@ -27,6 +28,7 @@ const select = (state, props) => ({
playingUri: selectPlayingUri(state),
contentType: makeSelectContentTypeForUri(props.uri)(state),
volume: selectVolume(state),
+ videoPause: selectVideoPause(state),
});
const perform = dispatch => ({
diff --git a/src/renderer/component/video/internal/player.jsx b/src/renderer/component/video/internal/player.jsx
index 9d7b6608f..5c885bc80 100644
--- a/src/renderer/component/video/internal/player.jsx
+++ b/src/renderer/component/video/internal/player.jsx
@@ -5,6 +5,9 @@ import player from "render-media";
import fs from "fs";
import LoadingScreen from "./loading-screen";
+import { connect } from "react-redux";
+import { selectVideoPause } from "redux/selectors/video";
+
class VideoPlayer extends React.PureComponent {
static MP3_CONTENT_TYPES = ["audio/mpeg3", "audio/mpeg"];
@@ -121,6 +124,11 @@ class VideoPlayer extends React.PureComponent {
}
}
+ pauseVideo() {
+ console.log("pauseVideo called");
+ this.refs.media.children[0].pause();
+ }
+
componentDidUpdate() {
const { contentType, downloadCompleted } = this.props;
const { startedPlaying } = this.state;
@@ -157,13 +165,15 @@ class VideoPlayer extends React.PureComponent {
}
render() {
- const { mediaType, poster } = this.props;
+ const { mediaType, poster, videoPause } = this.props;
const { hasMetadata, unplayable } = this.state;
const noMetadataMessage = "Waiting for metadata.";
const unplayableMessage = "Sorry, looks like we can't play this file.";
const needsMetadata = this.playableType();
+ console.log("VideoPlayer render; videoPause:", videoPause);
+
return (
diff --git a/src/renderer/index.js b/src/renderer/index.js
index d5154b084..e3ed7836b 100644
--- a/src/renderer/index.js
+++ b/src/renderer/index.js
@@ -73,7 +73,8 @@ document.addEventListener("click", event => {
if (target.matches("a") || target.matches("button")) {
// TODO: Look into using accessiblity labels (this would also make the app more accessible)
let hrefParts = window.location.href.split("#");
- let element = target.title || (target.text && target.text.trim());
+ let element =
+ target.title || (target.textContent && target.textContent.trim());
if (element) {
amplitude.getInstance().logEvent("CLICK", {
target: element,
@@ -84,6 +85,7 @@ document.addEventListener("click", event => {
amplitude.getInstance().logEvent("UNMARKED_CLICK", {
location:
hrefParts.length > 1 ? hrefParts[hrefParts.length - 1] : "/",
+ source: target.outerHTML,
});
}
}
From 3f067f13cfdd011f04db196cfbc83c8ccc26fa2e Mon Sep 17 00:00:00 2001
From: Liam Cardenas
Date: Mon, 18 Dec 2017 23:25:58 -0800
Subject: [PATCH 13/19] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 22 +++++++++++++---------
1 file changed, 13 insertions(+), 9 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index e9d7c9811..3724771ff 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -9,29 +9,33 @@ Since LBRY is an based around a decentralized community, we believe that the app
In order to make contributing as easy and rewarding of possible, we have instituted the following system:
* Anyone can view all issues in the system by clicking on the [Issues](https://github.com/lbryio/lbry-app/issues) button at the top of the page. Feel free to add an issue if you think we have missed something (and you might earn some LBC in the process because we do tip people for reporting bugs).
-* Once on the [Issues](https://github.com/lbryio/lbry-app/issues) page, a potential contributor can filter issues by the [Help Wanted](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) label to see a curated list of suggested issues with which community members can help.
-* Every [Help Wanted](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) issue is ranked on a scale from zero to four.
+* Once on the [Issues](https://github.com/lbryio/lbry-app/issues) page, a potential contributor can filter issues by the [Help Wanted](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+no%3Aassignee) label to see a curated list of suggested issues with which community members can help.
+* Every [Help Wanted](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+no%3Aassignee) issue is ranked on a scale from zero to four.
Level | Description
--- | ---
-[**level 0**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+0%22) | Typos and text edits -- a tech savvy non-programmer can fix these
-[**level 1**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+1%22) | Programming issues that require little knowledge of how the LBRY app works
-[**level 2**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+2%22) | Issues of average difficulty that require the developer to dig into how the app works a little bit
-[**level 3**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+3%22) | Issues that are likely too tricky to be level 2 or require more thinking outside of the box
-[**level 4**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+4%22) | Big features or really hard issues
+[**level 0**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+0%22+no%3Aassignee) | Typos and text edits -- a tech savvy non-programmer can fix these
+[**level 1**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+1%22+no%3Aassignee) | Programming issues that require little knowledge of how the LBRY app works
+[**level 2**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+2%22+no%3Aassignee) | Issues of average difficulty that require the developer to dig into how the app works a little bit
+[**level 3**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+3%22+no%3Aassignee) | Issues that are likely too tricky to be level 2 or require more thinking outside of the box
+[**level 4**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+4%22+no%3Aassignee) | Big features or really hard issues
The process of ranking issues is highly subjective. The purpose of sorting issues like this is to give contributors a general idea of the type of issues at which they are looking. It could very well be the case that a level 1 issue is more difficult than a level 2, for instance. This system is meant to help you find relevant issues, not to prevent you from working on issues that you otherwise would. If these rankings don't work for you, feel free to ignore them.
-* After deciding what to work on, a potential contributor can [fork](https://help.github.com/articles/fork-a-repo/) this repository, make his or her changes, and submit a [pull request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/).
+* After deciding what to work on, a potential contributor can [fork](https://help.github.com/articles/fork-a-repo/) this repository, make his or her changes, and submit a [pull request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/). A contributor wanting to reserve an issue in advance can leave a comment saying that he or she is working on it. Contributors should respect other people's efforts to complete issues in a timely manner and, therefore, not begin working on anything reserved (or updated) within the last 3 days. If someone has been officially assigned an issue via Github's assignment system, it is also not available. Contributors are encouraged to ask if they have any questions about issue availability.
* Once the pull request is visible in the LBRY repo, a LBRY team member will review it and make sure it is up to our standards. At this point, the contributor may have to change his or her code based on our suggestions and comments.
* Then, upon a satisfactory review of the code, we will merge it and send the contributor a tip (in LBC) for the contribution.
-We are dedicated to being fair and friendly in this process. In __general__, level 4 issues will be paid more than level 3 issues which will be paid more than level 2, and so on. However, this is not due to their labels, but rather how difficult they ended up being. Maybe an issue labeled "level 1" turned out to be very difficult. In this case we would be **more than happy** to tip accordingly. If you do good work, we want you to be rewarded for it.
+We are dedicated to being fair and friendly in this process. In __general__, level 4 issues will be paid more than level 3 issues which will be paid more than level 2, and so on. However, this is not due to their labeling, but rather how difficult they end up being. Maybe an issue labeled "level 1" turns out to be very difficult. In this case we would be **more than happy** to tip accordingly. If you do good work, we want you to be rewarded for it.
Also, we are here to enable you. We want you to succeed, so do not hesitate to ask questions. If you need some information or assistance in completing an issue, please let us know! That is what we are here for-- pushing development forward.
Lastly, don't feel limited by this list. Should LBRY have built-in Tor support? Add it! It's not in the issue tracker but maybe it's a good idea. Do you think the search layout is unintuitive? Change it! We welcome all feedback and suggestions. That said, it may be the case that we do not wish to incorporate your change if you don't check with us first (also, please check with us especially if you are planning on adding Tor support :P). If you want to add a feature that is not listed in the issue tracker, go ahead and [create an issue](https://github.com/lbryio/lbry-app/issues/new), and say in the description that you would like to try to implement it yourself. This way we can tell you in advance if we will accept your changes and we can point you in the right direction.
+# Tom's "Voice of the User" Wishlist
+
+[Anything marked with **both** "Help Wanted" and "Tom's 'Voice of the User' Wishlist"](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22Tom%27s+%5C%22Voice+of+the+User%5C%22+Wishlist%22+label%3A%22help+wanted%22+no%3Aassignee) will earn you an extra 50 LBC on top of what we would otherwise tip you.
+
# Get In Touch
Name | Role | Discord | Email
--- | --- | --- | ---
From 1325b940318c27e0fbd51085ce760c76eeabaa2a Mon Sep 17 00:00:00 2001
From: Liam Cardenas
Date: Mon, 18 Dec 2017 23:30:49 -0800
Subject: [PATCH 14/19] Added TL;DR
---
CONTRIBUTING.md | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 3724771ff..b6a4d8676 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -2,6 +2,14 @@
You found this page! That means you are well on your way to contributing to the LBRY app. This application is primarily written in JavaScript and is built on [Electron](https://electronjs.org) while utilizing [React](https://reactjs.org) and [Redux](https://redux.js.org) for UI and application state.
+## TL;DR?
+* [Here](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+no%3Aassignee) is a list of help wanted issues.
+* Comment on an issue to let us know if you are going to work on it, don't take an issue that someone has reserved less than 3 days ago
+* Submit a pull request and get paid in LBC
+* Don't hesitate to contact us with any questions or comments
+
+## Longer Version
+
LBRY is an open source project, and therefore is developed out in the open for everyone to see. What you see here are the latest source code changes and issues.
Since LBRY is an based around a decentralized community, we believe that the app will be strongest if it receives contributions from individuals outside the core team -- such as yourself!
From 2f409a6cbd506a8e4079ab295c3675df81dc1ad8 Mon Sep 17 00:00:00 2001
From: Travis Eden
Date: Tue, 19 Dec 2017 11:34:39 -0500
Subject: [PATCH 15/19] getting closer...
---
src/renderer/component/video/view.jsx | 74 ++++++++++++++-------------
src/renderer/redux/selectors/video.js | 10 ++--
2 files changed, 44 insertions(+), 40 deletions(-)
diff --git a/src/renderer/component/video/view.jsx b/src/renderer/component/video/view.jsx
index 5a2b5fc99..cb474ea72 100644
--- a/src/renderer/component/video/view.jsx
+++ b/src/renderer/component/video/view.jsx
@@ -8,15 +8,16 @@ import NsfwOverlay from "component/nsfwOverlay";
class Video extends React.PureComponent {
constructor(props) {
super(props);
- console.log("video view props", props);
+ // console.log("video view props", props);
this.state = {
showNsfwHelp: false,
+ // videoPause: false,
};
}
- componentWillReceiveProps() {
- console.log("!!VIDEO PLAYA RECIEVE PROPS:", this.props);
- // console.log("pauseVideo called");
+ componentWillReceiveProps(nextProps) {
+ console.log("VIDEO COMPONENT WILL RECIEVE NEXTPROPS:", nextProps);
+ // this.setState({videoPause: nextProps.videoPause});
// this.refs.media.children[0].pause();
}
@@ -63,10 +64,10 @@ class Video extends React.PureComponent {
changeVolume,
volume,
uri,
- // videoPause,
+ videoPause,
} = this.props;
- // console.log("VIDEO VIEW videoPause:", videoPause);
+ console.log("VIDEO VIEW videoPause:", videoPause);
const isPlaying = playingUri === uri;
const isReadyToPlay = fileInfo && fileInfo.written_bytes > 0;
@@ -102,35 +103,38 @@ class Video extends React.PureComponent {
const poster = metadata.thumbnail;
return (
-
);
}
diff --git a/src/renderer/redux/selectors/video.js b/src/renderer/redux/selectors/video.js
index fc124a69a..e79bf8765 100644
--- a/src/renderer/redux/selectors/video.js
+++ b/src/renderer/redux/selectors/video.js
@@ -1,9 +1,9 @@
import * as settings from "constants/settings";
import { createSelector } from "reselect";
-const _selectState = state => state.videoPause || false;
+const _selectState = state => state.video.videoPause || {};
-export const selectVideoPause = createSelector(
- _selectState,
- state => state.videoPause || false
-);
+export const selectVideoPause = createSelector(_selectState, state => {
+ console.log("VIDEO PAUSE SELECTOR", state);
+ return state.videoPause;
+});
From 6175a464937ae1a587584c914018c9ef2110df90 Mon Sep 17 00:00:00 2001
From: Liam Cardenas
Date: Tue, 19 Dec 2017 08:54:06 -0800
Subject: [PATCH 16/19] Reworded sentence
---
CONTRIBUTING.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index b6a4d8676..10d01b548 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -28,7 +28,7 @@ Level | Description
[**level 3**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+3%22+no%3Aassignee) | Issues that are likely too tricky to be level 2 or require more thinking outside of the box
[**level 4**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+4%22+no%3Aassignee) | Big features or really hard issues
-The process of ranking issues is highly subjective. The purpose of sorting issues like this is to give contributors a general idea of the type of issues at which they are looking. It could very well be the case that a level 1 issue is more difficult than a level 2, for instance. This system is meant to help you find relevant issues, not to prevent you from working on issues that you otherwise would. If these rankings don't work for you, feel free to ignore them.
+The process of ranking issues is highly subjective. The purpose of sorting issues like this is to give contributors a general idea about the type of issues they are looking at. It could very well be the case that a level 1 issue is more difficult than a level 2, for instance. This system is meant to help you find relevant issues, not to prevent you from working on issues that you otherwise would. If these rankings don't work for you, feel free to ignore them.
* After deciding what to work on, a potential contributor can [fork](https://help.github.com/articles/fork-a-repo/) this repository, make his or her changes, and submit a [pull request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/). A contributor wanting to reserve an issue in advance can leave a comment saying that he or she is working on it. Contributors should respect other people's efforts to complete issues in a timely manner and, therefore, not begin working on anything reserved (or updated) within the last 3 days. If someone has been officially assigned an issue via Github's assignment system, it is also not available. Contributors are encouraged to ask if they have any questions about issue availability.
* Once the pull request is visible in the LBRY repo, a LBRY team member will review it and make sure it is up to our standards. At this point, the contributor may have to change his or her code based on our suggestions and comments.
From 92de445e1e1a51cfe77bddff3a4775e20cb43b05 Mon Sep 17 00:00:00 2001
From: Travis Eden
Date: Tue, 19 Dec 2017 13:20:53 -0500
Subject: [PATCH 17/19] fixed selector; pause working; still need to call
action from child component
---
.../component/fileDownloadLink/index.js | 2 +-
.../component/fileDownloadLink/view.jsx | 5 +-
src/renderer/component/video/index.js | 1 +
.../component/video/internal/player.jsx | 15 ++--
src/renderer/component/video/view.jsx | 79 +++++++++----------
src/renderer/redux/selectors/video.js | 2 +-
6 files changed, 52 insertions(+), 52 deletions(-)
diff --git a/src/renderer/component/fileDownloadLink/index.js b/src/renderer/component/fileDownloadLink/index.js
index 9b1141802..e35dc5b94 100644
--- a/src/renderer/component/fileDownloadLink/index.js
+++ b/src/renderer/component/fileDownloadLink/index.js
@@ -25,7 +25,7 @@ const perform = dispatch => ({
openInShell: path => dispatch(doOpenFileInShell(path)),
purchaseUri: uri => dispatch(doPurchaseUri(uri)),
restartDownload: (uri, outpoint) => dispatch(doStartDownload(uri, outpoint)),
- videoPause: val => dispatch(setVideoPause(val)),
+ setVideoPause: val => dispatch(setVideoPause(val)),
});
export default connect(select, perform)(FileDownloadLink);
diff --git a/src/renderer/component/fileDownloadLink/view.jsx b/src/renderer/component/fileDownloadLink/view.jsx
index 68499c273..0619460dd 100644
--- a/src/renderer/component/fileDownloadLink/view.jsx
+++ b/src/renderer/component/fileDownloadLink/view.jsx
@@ -42,13 +42,12 @@ class FileDownloadLink extends React.PureComponent {
purchaseUri,
costInfo,
loading,
- videoPause,
+ setVideoPause,
} = this.props;
const openFile = () => {
openInShell(fileInfo.download_path);
- console.log("FileDownloadLink view");
- videoPause(true);
+ setVideoPause(true);
};
if (loading || downloading) {
diff --git a/src/renderer/component/video/index.js b/src/renderer/component/video/index.js
index 1b79f8275..04c223f61 100644
--- a/src/renderer/component/video/index.js
+++ b/src/renderer/component/video/index.js
@@ -35,6 +35,7 @@ const perform = dispatch => ({
play: uri => dispatch(doPlayUri(uri)),
cancelPlay: () => dispatch(doSetPlayingUri(null)),
changeVolume: volume => dispatch(doChangeVolume(volume)),
+ setVideoPause: val => dispatch(setVideoPause(val)),
});
export default connect(select, perform)(Video);
diff --git a/src/renderer/component/video/internal/player.jsx b/src/renderer/component/video/internal/player.jsx
index a8b4572c1..42b9b4bf2 100644
--- a/src/renderer/component/video/internal/player.jsx
+++ b/src/renderer/component/video/internal/player.jsx
@@ -4,9 +4,7 @@ import { Thumbnail } from "component/common";
import player from "render-media";
import fs from "fs";
import LoadingScreen from "./loading-screen";
-
-// import { connect } from "react-redux";
-// import { selectVideoPause } from "redux/selectors/video";
+import { setVideoPause } from "../../../redux/actions/video";
class VideoPlayer extends React.PureComponent {
static MP3_CONTENT_TYPES = ["audio/mpeg3", "audio/mpeg"];
@@ -23,6 +21,13 @@ class VideoPlayer extends React.PureComponent {
this.togglePlayListener = this.togglePlay.bind(this);
}
+ componentWillReceiveProps(nextProps) {
+ if (nextProps.videoPause) {
+ this.refs.media.children[0].pause();
+ this.props.confirmVideoPause(false);
+ }
+ }
+
componentDidMount() {
const container = this.refs.media;
const {
@@ -160,15 +165,13 @@ class VideoPlayer extends React.PureComponent {
}
render() {
- const { mediaType, poster, videoPause } = this.props;
+ const { mediaType, poster } = this.props;
const { hasMetadata, unplayable } = this.state;
const noMetadataMessage = "Waiting for metadata.";
const unplayableMessage = "Sorry, looks like we can't play this file.";
const needsMetadata = this.playableType();
- console.log("VideoPlayer render; videoPause:", videoPause);
-
return (