d5410fd4a9
* qt: User border-image in place of image For some reason image produced weird outputs on some resolution screens. * qt: Fix layout issues in TransactionView * qt: Fix layout issues in OverviewPage * qt: Replace transparent with #00000000 in stylesheets * qt: Use #a84832 as red where possible. This includes css files and any color usage in code. * qt: Finetune QPushButton style * qt: Customized QSlider (used in the Debug window -> NetworkTraffic) * qt: Finetune QToolbar style * qt: Customized QProgressBar * qt: Customized QCalendarWidget * qt: Finetune QStatusBar style - Give the progress label a name as css reference - Set min height and margins * qt: Finetune QMenu style - Set a light rounded border - Color for disabled items - Color/Style for seperator - Give the items padding * qt: Customized QGroupBox * qt: Customized QToolTip * qt: Give inputs widgets a proper hover/focus/selected/disabled style * qt: Finetune SendCoinsDialog - Add light line below the coincontrol frame - Add light line above fee frame - Increase header font size - Remove button layout changes of CoinControl button - Fix Layout/Alignment of balance labels * qt: Customized RPC console's autocompletition popup * qt: Add stylesheets to Intro This is the datadir selection dialog. * qt: OptionsDialog - Give the reset button the "light button" style * qt: Finetune shared styles in general.css * qt: Finetune coloring in dark.css * qt: Finetune coloring in light.css * More fixes for traditional.css No text colors, s/transparent/#00000000/ * qt: Run update-css-files.py Co-authored-by: UdjinM6 <UdjinM6@users.noreply.github.com> |
||
|---|---|---|
| .github | ||
| .tx | ||
| build-aux/m4 | ||
| ci | ||
| contrib | ||
| depends | ||
| doc | ||
| docker | ||
| share | ||
| src | ||
| test | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .travis.yml | ||
| autogen.sh | ||
| CMakeLists.txt | ||
| configure.ac | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| INSTALL.md | ||
| libdashconsensus.pc.in | ||
| Makefile.am | ||
| README.md | ||
Dash Core staging tree 0.17
master: 
develop: 
What is Dash?
Dash is an experimental digital currency that enables instant, private payments to anyone, anywhere in the world. Dash uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Dash Core is the name of the open source software which enables the use of this currency.
For more information, as well as an immediately useable, binary version of the Dash Core software, see https://www.dash.org/get-dash/.
License
Dash Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.
Development Process
The master branch is meant to be stable. Development is normally done in separate branches.
Tags are created to indicate new official,
stable release versions of Dash Core.
The contribution workflow is described in CONTRIBUTING.md.
Testing
Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.
Automated Testing
Developers are strongly encouraged to write unit tests for new code, and to
submit new unit tests for old code. Unit tests can be compiled and run
(assuming they weren't disabled in configure) with: make check. Further details on running
and extending unit tests can be found in /src/test/README.md.
There are also regression and integration tests, written
in Python, that are run automatically on the build server.
These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py
The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, and that unit/sanity tests are run automatically.
Manual Quality Assurance (QA) Testing
Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.
Translations
Changes to translations as well as new translations can be submitted to Dash Core's Transifex page.
Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.
Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.
Translators should also follow the forum.