Go to file

Wladimir J. van der Laan fe4a655042 Fine-grained UI updates Gets rid of `MainFrameRepaint` in favor of specific update functions that tell the UI exactly what changed. This improves the efficiency of various handlers. Also fixes problems with mined transactions not showing up until restart. The following notifications were added: - `NotifyBlocksChanged`: Block chain changed - `NotifyKeyStoreStatusChanged`: Wallet status (encrypted, locked) changed. - `NotifyAddressBookChanged`: Address book entry changed. - `NotifyTransactionChanged`: Wallet transaction added, removed or updated. - `NotifyNumConnectionsChanged`: Number of connections changed. - `NotifyAlertChanged`: New, updated or cancelled alert. As this finally makes it possible for the UI to know when a new alert arrived, it can be shown as OS notification. These notifications could also be useful for RPC clients. However, currently, they are ignored in bitcoind (in noui.cpp). Also brings back polling with timer for numBlocks in ClientModel. This value updates so frequently during initial download that the number of signals clogs the UI thread and causes heavy CPU usage. And after initial block download, the value changes so rarely that a delay of half a second until the UI updates is unnoticable.		2012-05-20 10:41:54 +02:00
contrib	Update changelog to match reality.	2012-05-06 21:09:37 -04:00
doc	Replace debug window icon with LGPL-licensed one (fixes #1348 )	2012-05-19 12:47:01 +02:00
share	Increase client version to 0.6.99	2012-05-08 15:22:02 -04:00
src	Fine-grained UI updates	2012-05-20 10:41:54 +02:00
.gitattributes	Build identification strings	2012-04-10 18:16:53 +02:00
.gitignore	Add build directory to .gitignore, so that it's not tracked.	2012-05-17 19:09:21 +01:00
COPYING	Update all copyrights to 2012	2012-02-07 11:28:30 -05:00
INSTALL	Update build instructions for the new, no-wxwidgets world	2011-09-26 11:40:43 -04:00
README	directory re-organization (keeps the old build system)	2011-04-23 12:10:25 +02:00
README.md	Updated readme file with timers.	2011-09-26 22:22:19 -04:00
bitcoin-qt.pro	Add /bin/sh to bitcoin-qt.pro - as some filesystems don't have the execute flag.	2012-05-17 18:48:09 +01:00

README.md

Bitcoin integration/staging tree

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the bitcoin development team members simply pulls it.

If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list: http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if they don't match the project's coding conventions (see coding.txt) or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are regularly created to indicate new official, stable release versions of Bitcoin. If you would like to help test the Bitcoin core, please contact QA@BitcoinTesting.org.

Feature branches are created when there are major new features being worked on by several people.

From time to time a pull request will become outdated. If this occurs, and the pull is no longer automatically mergeable; a comment on the pull will be used to issue a warning of closure. The pull will be closed 15 days after the warning if action is not taken by the author. Pull requests closed in this manner will have their corresponding issue labeled 'stagnant'.

Issues with no commits will be given a similar warning, and closed after 15 days from their last activity. Issues closed in this manner will be labeled 'stale'.

Requests to reopen closed pull requests and/or issues can be submitted to QA@BitcoinTesting.org.