lbryio/lbry-desktop

Add detailed view to Downloads/Publishes with additional card/batch options

Open

#1394 opened on Apr 26, 2018

View on GitHub
 (2 comments) (3 reactions) (0 assignees)JavaScript (3,596 stars) (412 forks)batch import
area: creatorarea: uxarea: viewerhacktoberfesthelp wantedlevel: 2odyseetype: new feature

Description

The Issue

Discussed this with Sean briefly and it was also brought up by a reddit user.

Problem: Currently, to take any actions (edit/delete/tip) you need to go into each claim to perform them.

The enhancement would be to have a more detailed, list like, view for both Downloads/Publishes that would condense the claim information so they can be more easily managed. This would also include direct actions to delete/tip/edit/report/open externally as appropriate.

Batch actions (by selecting multiple files/claims, select all option) can be added to allow deleting multiple items with a few clicks.

We would also display detailed claim information like the URL, claim bid, total supports, total tips, if it's the vanity URL, etc.

System Configuration

  • LBRY Daemon version:
  • LBRY App version:
  • LBRY Installation ID:
  • Operating system:

Anything Else

Screenshots

Contributor guide

Tech stack
javascriptelectronreact
Domain
frontenddesktop
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptReactElectron
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Start by exploring the current Downloads and Publishes views in the codebase, likely in the ui/component directory. Understand the data flow from LBRY daemon claims. Propose a component structure for the detailed list view and batch actions. Reference similar implementations in other parts of the app or open source projects.