App Navigation and Wallet pages groundwork #936
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#936
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?
A lot of files but most are small JSX/css changes and Flow additions
Focus:
Add side nav/improve header (search)
Use Feather Icons (needs standarization)
Sub-link navigation (subheader reworked)
Home page cleanup
Wallet Pages (Basic stuff. I'll go more in depth later, just getting stuff looking kinda ok)
Added flow to a lot of components (going to add it to more redux stuff in another pr)
This is preventing a draggable window. Should be a simple fix but definitely getting rid of the title bar. Need to explore how it looks on window/linux though
@ -49,23 +47,27 @@ export default (props: Props) => {
} = props;
return (
I think I'm going to change this to
FormElement
and keepFormRow
which just allows severalFormElement
s side by side@ -14,1 +12,4 @@
export default class Address extends React.PureComponent<Props> {
constructor() {
super();
Using render props makes it really simple add additional items to the form field like this button. Instead of having a huge
FormField
element that can do everything, allowing the user of the component to do whatever they want can be really nice.Using
render
andchildren
are really similar. Maybe we should just choose one and use it everywhere. The additional feature thatrender
gives you is that you can pass state/computed values into the render function and allow consuming components to interact with it in a more customizable way.This will be removed
This wasn't being used anywhere
@ -2,2 +1,3 @@
export const LOCAL = 'folder';
export const FEATURED = 'Award';
export const LOCAL = 'Folder';
export const FILE = 'file';
Going to add every icon to this file and only change every Icon use to constants
@ -2,2 +1,3 @@
export const LOCAL = 'folder';
export const FEATURED = 'Award';
export const LOCAL = 'Folder';
export const FILE = 'file';
wow this is massive! this is my first go through... i havent run the code yet. I will check it out and then see if i have any more comments
should this be git ignored?
@ -5,3 +5,3 @@
import classnames from 'classnames';
import Icon from 'component/common/icon';
// import Icon from 'component/common/icon';
i assume you will remove the commented code here and elsewhere before we merge
@ -2,2 +1,3 @@
export const LOCAL = 'folder';
export const FEATURED = 'Award';
export const LOCAL = 'Folder';
export const FILE = 'file';
is there a reason why the ones you just added are upper case but the others are lower?
@liamcardenas Not sure why I can't respond to your comment about icons. The old icons used lowercase. This new module
react-feather
uses uppercase. One of the reasons I want to use constants for all of them.yes
@ -5,3 +5,3 @@
import classnames from 'classnames';
import Icon from 'component/common/icon';
// import Icon from 'component/common/icon';
I wasn't planning on it. Mostly they are just reminders to come back to something. I'm not sure if I need to keep this, but I will know when I start on the File Page (next)
@seanyesmunt makes sense!
@ -5,3 +5,3 @@
import classnames from 'classnames';
import Icon from 'component/common/icon';
// import Icon from 'component/common/icon';
sounds good
Just removed these and added to the .gitignore
Gonna merge this. I will come back to every file touched here at least once more. Please let me know if you see something that looks funky.