Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alter flow of commission prices control panel #3

Merged

Conversation

hyena
Copy link

@hyena hyena commented Jan 9, 2017

PRESENTLY NONFUNCTIONAL. DO NOT MERGE Should be functional now.
Opening the PR anyway for feedback. Feel free to deracinate this, critique, etc. Frontend is definitely not my forte.

  • Re-organizes control panel into task-oriented rows.
  • Presently non-functional and should not be merged.
  • Introduces flexbox for layout.

Some notes:

  • Layout is not that great still. Feels kind of vast and barren
  • The checkboxes are rather awkward for a 2017 UI. How hard would it be to write javascript that dynamically fill in price information, commission class type, etc. when we select from the form?
  • I'm not married to the horizontal rules.

 - Re-organizes control panel into task-oriented rows.
 - Presently non-functional and should not be merged.
 - Introduces flexbox for layout.
}

#commishprices-content .di-tags {
width: 100%

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing a semicolon.

taedixon and others added 8 commits January 13, 2017 00:15
Remove redundant fields from commission class forms

Add preview of price display

Fix width of commish-tags column

Use radio buttons for cost types
 - This is replicated from the profile editting page
 - It should probably only exist on the commission price page
 - Note that this commit depends on some HTML5 features that aren't supported in IE9:
   formaction, formnovalidate
 - Used 'artist' instead of user to distinguish between the user searching and the results
 - Spelling error and renamed 'artist tags'
…sion class

 - Without this change, the prices for a deleted commission class would stick around and attach themselves to a new class that took up that id.
 - In theory there could be a small race condition between these two execute calls where a new commission class is made on the same user at the same time.
   Does using the same pg_connection for both executes prevent this? Regardless the timing is unlikely to ever come up.
 - Honestly the world would be much more sane if commission classes used a 'real' primary key.
@taedixon taedixon merged commit 2be7c39 into taedixon:marketplace Jan 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants