-
Notifications
You must be signed in to change notification settings - Fork 7
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
bitcoinjs-gui: colorman: load color definitions #6
Comments
got it compiled/instaled on my CentOS vm. There should be only one source for defs defined or more ? Proposed implementation : loading defs configurable via some (hardcoded/configured?) list of sources - ie:
Final defs merged from the list in a sequence. |
Well, the general idea is that user should be able to add colors he is interested in, and list of colors should be preserved over page reloads (so that user does not need to add colors each time). Perhaps it should be persisted in same way wallets are. One way to do that is to add color definitions to bitcoinjs-gui wallet object so that they are persisted together. There are three ways to deal with sources:
Let's not make it too complex from start, whatever is easiest will work. But I guess there should be a default source of color definitions, for new users, so that they can try it right away without configuring anything. So, yeah, something like localdefsfile.js. |
OK understood. So there will be I think two types of sources for a start:
Both merged defs data and urls/paths will be stored with bitcoinjs-gui wallet and this will be loaded as current colorman.js/defs member. That's now clear for me. I think I am able to do the task (I'm fresh to the project) I'll take it next week if still unassigned. |
As much I hate to skip the line, it was kinda stopper for me. |
Currently color definitions are embedded in code. There should be a way to load them via URL. Perhaps it should be stored in local storage.
(Integration with bitcoinjs-gui front-end is necessary.)
Bounty: 0.5 BTC
The text was updated successfully, but these errors were encountered: