electrum

History

Neil Booth aa6de86c27 Once a user inputs a fee, retain it. It has long been a minor annoyance that this isn't the default behaviour. Semantics are as follows: - Fees are calculated automatically, as usual, and shown in black - If the user inputs a fee, it is retained, and shown in blue to indicate it is user-overridden - The user can switch back to automatic fee calculation mode in two ways: press Clear, or blank out the fee field - User fees are also cleared by do_clear(), for instance when the payment is sent I have checked all usage combinations I could think of, including the ! case, and all work in a sensible and natural fashion. This also fixes issue #995.		10 years ago
..
README	plugins readme	10 years ago
__init__.py	move openalias from plugins to core	10 years ago
audio_modem.py	transaction_dialog: allow plugins manipulate transaction sharing buttons	10 years ago
btchipwallet.py	Only rescan the dongle when it has been disconnected	10 years ago
cosigner_pool.py	Split tx dialog buttons	10 years ago
exchange_rate.py	Once a user inputs a fee, retain it.	10 years ago
greenaddress_instant.py	Split tx dialog buttons	10 years ago
labels.py	fix trezor initialiation hook (pass window in load_wallet)	10 years ago
plot.py	make plugins available without the GUI	10 years ago
trezor.py	fix is_address (forgot p2sh)	10 years ago
trustedcoin.py	generic m of n multisig	10 years ago
virtualkeyboard.py	make plugins available without the GUI	10 years ago

README

Plugin rules:

 * The plugin system of Electrum is designed to allow the development
   of new features without increasing the core code of Electrum.

 * Electrum is written in pure python. if you want to add a feature
   that requires non-python libraries, then it must be submitted as a
   plugin. If the feature you want to add requires communication with
   a remote server (not an Electrum server), then it should be a
   plugin as well. If the feature you want to add introduces new
   dependencies in the code, then it should probably be a plugin.

 * We expect plugin developers to maintain their plugin code. However,
   once a plugin is merged in Electrum, we will have to maintain it
   too, because changes in the Electrum code often require updates in
   the plugin code. Therefore, plugins have to be easy to maintain. If
   we believe that a plugin will create too much maintenance work in
   the future, it will be rejected.

 * Plugins should be compatible with Electrum's conventions. If your
   plugin doe