Skip to content

Conversation

@laanwj
Copy link
Member

@laanwj laanwj commented May 19, 2013

This adds an introduction screen that is shown when the client is first started in which the user can choose a data directory.

It is also possible to force the intro screen to appear using command line argument -choosedatadir.

The data directory is remembered in the QSettings.

The user is warned that the client will download and store 10Gb of data. The intro screen shows how much space is available on the device that contains the chosen directory and warns if this is less than the 10Gb.

To make it possible to translate the introduction dialog, the initialization sequence is changed so that translations are loaded before the data directory. This has the by-effect that it is no longer possible to specify a language in bitcoin.conf inside the data directory.

Please help testing!

@Diapolo
Copy link

Diapolo commented May 19, 2013

I'm going to take a look next week, can you post a screen until I do :)?

@laanwj
Copy link
Member Author

laanwj commented May 20, 2013

OK selection

x01

Warning when directory already exists, user can still click OK

x02

Invalid or unreachable path

x03

Too little free space on device

x04

@laanwj
Copy link
Member Author

laanwj commented May 20, 2013

Changed Gb -> GB, checking now happens in separate thread to prevent blocking the GUI thread.

@Diapolo
Copy link

Diapolo commented May 20, 2013

Just some small comments:

  • Do you allow OK even when low disk space was detected, looks like OK is available there.
  • Do you intend to show this even for existing installations or just new ones (and for existing ones when supplying -choosedatadir)?
  • What happens when a user supplies -choosedatadir, will you copy old to new or just switch from old to new?
  • Do we want to place a clickable URI to official Bitcoin site here or anywhere else in the client? I think that would be a good addition.
  • Perhaps display none for available space when case "Invalid or unreachable path"
  • Perhaps we could also add a clickable button for launching -choosedatadir into the options dialog, when I finish my work there?

@laanwj
Copy link
Member Author

laanwj commented May 20, 2013

> Do you allow OK even when low disk space was detected, looks like OK is available there.

Yes. The user can choose OK in all cases where it's possible to create the directory. They may plain on cleaning up the drive immediately (ie, deleting one blueray image should be enough to make space). In the end it's their own responsibility.

> Do you intend to show this even for existing installations or just new ones

Only for new installations (when the default data directory doesn't exist). Otherwise it will confuse users into making a new data directory and they will wonder where their block chain / wallet will have gone.

> Do we want to place a clickable URI to official Bitcoin site here or anywhere else in the client? I think that would be a good addition.

I'm not sure why, unless it links to an explanation about data directories. But feel free to add more flair to the window later. I'm just focusing on the functionality for now.

> Perhaps display none for available space when case "Invalid or unreachable path"

Yeah... or N/A

> Perhaps we could also add a clickable button for launching -choosedatadir into the options dialog, when I finish my work there?

I don't want to support changing the data directory while the client is running.

If the user wants to move the data directory they can do so themselves while the client is not running, and the "choose data directory" dialog will automatically pop up on next run as the software notices that the data directory does not exist.

src/util.cpp Outdated
Copy link

Choose a reason for hiding this comment

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

I guess Gavin would love to see some unit test for this :-P. Btw. I also thought about such a thing a few days ago ^^.

Copy link
Member Author

Choose a reason for hiding this comment

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

I didn't like adding this function, but I didn't see another way to do this (well ok it's possible to assign to mapArgs directly, as it is exported outside util.cpp, this is done in rpcmining.cpp for example... but that wouldn't be better would it).
SetSoftArg is not good enough as the directory selected in the dialog should override everything, even the data directory passed on the command line, otherwise it'd be confusing. Another solution would be to not show the dialog at all when the datadir is overridden on the command line. Hmm that may be better.

@gmaxwell
Copy link
Contributor

ObUIshedpaint (feel free to ignore): The first "Warning:" is perhaps a bit intense and should probably be more reserved for things with risk of irreparable harm (encrypting wallets, deleting wallet directories, sending a 1000 BTC fee, etc.). Using space is just a fact of normal software operation and is nothing to be concerned about... unless you don't have enough— so I think it's okay in a low/insufficient space case...

@laanwj
Copy link
Member Author

laanwj commented May 20, 2013

@gmaxwell: fixed that, all the warnings was indeed a bit over the top

@BitcoinPullTester
Copy link

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/ff78dd81170c15f7fed00f803dde109283e78c72 for binaries and test log.
This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/
Contact BlueMatt on freenode if something looks broken.

@rebroad
Copy link
Contributor

rebroad commented May 21, 2013

"official bitcoin site"?!

I suspect you mean "original satoshi client site"...

Do we want to place a clickable URI to official Bitcoin site here or
anywhere else in the client? I think that would be a good addition.

@jbreher
Copy link

jbreher commented May 21, 2013

Just a question. When you write 'GB', do you really mean 'GB' - i.e. 10^9, or do you instead mean 'GiB' - i.e. 2^30 ?

On May 20, 2013, at 7:41 AM, Wladimir J. van der Laan wrote:

Changed Gb -> GB, checking now happens in separate thread to prevent blocking the GUI thread.


Reply to this email directly or view it on GitHub.

@laanwj
Copy link
Member Author

laanwj commented May 21, 2013

@rebroad No, he means the Armory site obviously...

@jbreher GB as in 10^9. This is Bitcoin, we use SI units.

@Diapolo
Copy link

Diapolo commented May 21, 2013

I really hate that GiB stuff, for me all units are 1024 based but I would never use GiB, KiB or such nonsense ^^.

@BitcoinPullTester
Copy link

Automatic sanity-testing: FAILED BUILD/TEST, see http://jenkins.bluematt.me/pull-tester/55605706a21e2325720c989ad690f83aa2934f78 for binaries and test log.

This could happen for one of several reasons:

  1. It chanages paths in makefile.linux-mingw or otherwise changes build scripts in a way that made them incompatible with the automated testing scripts (please tweak those patches in contrib/test-scripts)
  2. It adds/modifies tests which test network rules (thanks for doing that), which conflicts with a patch applied at test time
  3. It does not build on either Linux i386 or Win32 (via MinGW cross compile)
  4. The test suite fails on either Linux i386 or Win32
  5. The block test-cases failed (lookup the first bNN identifier which failed in https://github.com/TheBlueMatt/test-scripts/blob/master/FullBlockTestGenerator.java)

If you believe this to be in error, please ping BlueMatt on freenode or TheBlueMatt here.

This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/
Contact BlueMatt on freenode if something looks broken.

@laanwj
Copy link
Member Author

laanwj commented May 21, 2013

Ugh, I'm trying to find out the OS path separator using make_preferred() for a message but this doesn't exist on the ancient boost used by pulltester.

@laanwj
Copy link
Member Author

laanwj commented May 21, 2013

Should be solved now.

@Diapolo
Copy link

Diapolo commented May 21, 2013

@laanwj I also think we should drop support for ancient Boost version. I never understood, why it is a problem to do so anyway.

@BitcoinPullTester
Copy link

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/e024910520ab3868240beebfacec04de15c929ca for binaries and test log.
This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/
Contact BlueMatt on freenode if something looks broken.

@jbreher
Copy link

jbreher commented May 21, 2013

I understand that many hate it. However, your insistence on casually using units which never had any standards organization bless them in any way leaves you perpetuating a needless ambiguity, and in conflict with SI, ANSI, NIST, ISO, IEC, ITC, IETF, BSA, and just about any accredited standards organization one might care to name. All of whom have issued clear guidance that (e.g.) GB always refers to 10^9, and GiB always refers to 2^30.

https://en.wikipedia.org/wiki/IEEE_1541

http://physics.nist.gov/cuu/Units/binary.html

On May 21, 2013, at 12:07 AM, Philip Kaufmann wrote:

I really hate that GiB stuff, for me all units are 1024 based but I would never use GiB, KiB or such nonsense ^^.


Reply to this email directly or view it on GitHub.

@rebroad
Copy link
Contributor

rebroad commented May 22, 2013

As someone who has been using computers since 1979, I can confirm that KB
always referred to 1024 and only recently did I notice that people
confusingly started using KB to refer to 1000, and this confusion has been
further compounded by the addition of the term KiB.
On May 22, 2013 5:58 AM, "Joe Breher" [email protected] wrote:

I understand that many hate it. However, your insistence on casually using
units which never had any standards organization bless them in any way
leaves you perpetuating a needless ambiguity, and in conflict with SI,
ANSI, NIST, ISO, IEC, ITC, IETF, BSA, and just about any accredited
standards organization one might care to name. All of whom have issued
clear guidance that (e.g.) GB always refers to 10^9, and GiB always
refers to 2^30.

https://en.wikipedia.org/wiki/IEEE_1541

http://physics.nist.gov/cuu/Units/binary.html

On May 21, 2013, at 12:07 AM, Philip Kaufmann wrote:

I really hate that GiB stuff, for me all units are 1024 based but I
would never use GiB, KiB or such nonsense ^^.


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHubhttps://github.com//pull/2670#issuecomment-18247220
.

@laanwj
Copy link
Member Author

laanwj commented May 22, 2013

Can you take the units discussion elsewhere please? These kinds of
discussions can go on for centuries (let's settle imperial versus metric
first when we're at it) and still go nowhere. We don't have time for that.

@Suffice
Copy link

Suffice commented May 31, 2013

Perhaps have two choices when the client starts up for the first time, the first to download the block chain with all the defaults, and the second being to change the data directory or whatever. This will alleviate the technicality of it for non-technical people, and make the first dialogue screen more welcoming.

Something maybe like:

Start Block Chain | Change Directory

@sipa
Copy link
Member

sipa commented May 31, 2013

@Suffice As a follow-up, maybe there can be some menu option "Move datadir", which requires a restart immediately afterwards (or not, but that's definitely a lot more work). I think that's independent from this pullreq, which already improves 99% of use cases.

@laanwj
Copy link
Member Author

laanwj commented May 31, 2013

@Suffice yeah maybe... but I do want to make sure people see the warning about downloading 10Gb, as one of the reasons for this is that people don't get freaked out later when they see their harddisk being filled up. In any case they already accept the default by clicking "OK" immediately. On a fresh install, it will initially show the default data directory.

@sipa Could be useful option. But I feel better about that once block chain dir != wallet dir. No problem with moving the block chain, it can be redownloaded if the user makes a mistake, but as moving implies a delete I don't really want to "move" the wallet.dat. Copy at most. Let people that know what they're doing do this manually for now.

@sipa
Copy link
Member

sipa commented May 31, 2013

@laanwj ACK, separating datadir from wallets must happen first.

@laanwj
Copy link
Member Author

laanwj commented May 31, 2013

default

@Suffice this is better I think. It makes clear that the initially selected directory is the default, and requires an extra radio button click to change it to prevent it from being changed cluelessly. And it still shows what the default data directory is (though disabled), and whether there is enough space there.

@Suffice
Copy link

Suffice commented May 31, 2013

I don't know anymore. . Pulling this off in best way possible is tricky. This is how most program installs look:

capture

Perhaps something like this:

Some concise text here for an explanation of something

The block chain and your wallet files will go here...
[ C:\Program Files (x86)\Bitcoin           ]   [ Browse... ]


Space required:   10.3 GB's
Space available:  32.4 GB's
The space required for the block chain will increase over time as the chain grows.
(The block chain is essentially a ledger of every bitcoin transaction ever.)

                                               Some buttons here

I noticed that the block chain is currently stored in the AppData directory on Windows, will that change?

It would be nice if the wallet auto purged parts of the block chain that are no longer needed, and perhaps requests parts of the chain that it needs again, like in the event of importing addresses. (Tricky)

New clients could start from the near end of this chain, as they won't likely need the whole chain.

@laanwj
Copy link
Member Author

laanwj commented May 31, 2013

I noticed that the block chain is currently stored in the AppData directory on Windows, will that change?

After this pull it will be possible to change that, at least on new installs, that's the point of it.

@BitcoinPullTester
Copy link

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/e8d6ef18ac4d38ca93827f739aa560345c5fcff1 for binaries and test log.
This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/
Contact BlueMatt on freenode if something looks broken.

@BitcoinPullTester
Copy link

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/aaa6b5e87b69f6cbcca3d1fc430d8bc9f73ac609 for binaries and test log.
This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/
Contact BlueMatt on freenode if something looks broken.

@BitcoinPullTester
Copy link

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/4c7685061d2437b9c3a1c61e490dd673d9a7ed6e for binaries and test log.
This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/
Contact BlueMatt on freenode if something looks broken.

src/qt/intro.cpp Outdated
Copy link

Choose a reason for hiding this comment

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

Can you add a small comment that this is 10GB and below 1GB currently :)?

Copy link
Member Author

Choose a reason for hiding this comment

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

Indeed could be clarified. But as such comments tend to go out of date,
making it clear in the code through multiplying 10 with a constant GB may
be better.

Copy link

Choose a reason for hiding this comment

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

Yeah, so perhaps just switch the 2 and use GB_BYTES * 10 then :).

@Diapolo
Copy link

Diapolo commented Jun 6, 2013

It behaves a little weird, let me explain:

  • default selected (C:\Users\Diapolo\AppData\Roaming\Bitcoin)
    -- message 9GB of free space available (of 10GB needed). displayed
  • switching to custom, message is the same
    -- it doesn't show that this directory already exists
    -- adding a \ leads to Directory already exists...
    -- adding a \test\ leads toWarning: Low disk space on device``

Edit: Sorry, I didn't have the recent rebase changes in my local branch... will test again!

Edit 2: Behaviour is the same, I would await, that C:\Users\Diapolo\AppData\Roaming\Bitcoin is detected as existing path already, even without the \ at the end.

@laanwj Did you take a look at this comments yet?

src/qt/intro.cpp Outdated
Copy link

Choose a reason for hiding this comment

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

Can you explain to me what this is for?

Copy link
Member Author

Choose a reason for hiding this comment

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

When you enter a path that does not exist, it has to find the first parent
path up the tree that does exist to be able to determine the free space
on that file system. Boost will not accept non existing paths.

@Diapolo
Copy link

Diapolo commented Jun 10, 2013

@laanwj Can you test if you are able to use a non-default language (no english) and that this is loaded? Either there is a bug in this pull or I have a problem with my local build related to this in combination with my QSettings work (or a problem with this and #2700?).

Copy link

Choose a reason for hiding this comment

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

You've got some nasty bug in this code part.

Step 1:
de_DE
Step 2 (because of a QSetting):
de
Step 3 (still from the QSetting):
de

lang = de and after this line it is just empty, which leads to the default language getting activated!

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks for testing and reporting, I'll take a look.

Copy link

Choose a reason for hiding this comment

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

After your recent changes the thing here is like this:

  1. lang_territory = de_DE
  2. lang_territory = de (as that is my stored QSetting)
  3. lang_territory = de (as I didn't pass -lang)

So lang = de before doing the truncate() and is empty afterwards. So you pass an empty variable lang into the further calls, where it should be de and de (via lang_territory) where it should be de_DE, right? It seems to work okay, but I'm not sure if this is intended :).

Copy link
Member Author

Choose a reason for hiding this comment

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

That's how it always worked -- if lang_territory contains a string such as "de_DE", lang will be "de" and both will be loaded. If lang_territory contains a string such as "de", lang will be "" and just "de" will be loaded. It will indeed pass an empty string, but as it cannot find a translation with an empty name that's a no-op.

@laanwj
Copy link
Member Author

laanwj commented Jun 11, 2013

Rebased, and language problem solved (the QTranslators were getting freed).

@BitcoinPullTester
Copy link

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/6aad2cacef1af45185773622548ba74c755bbe79 for binaries and test log.
This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/
Contact BlueMatt on freenode if something looks broken.

@laanwj
Copy link
Member Author

laanwj commented Jun 14, 2013

@Diapolo does it still show the strange behavior on Windows? If so, any idea what causes that?

@Diapolo
Copy link

Diapolo commented Jun 14, 2013

Sugestion: Can you make the info/error messages selectable and show the beam-cursor?
I also think the dialog could be a little smaller in height.

Translations are working again!

Anyway, I'll report what is happening, my default datadir is: C:\Users\Diapolo\AppData\Roaming\Bitcoin.

Start with -choosedatadir and default selected:
8GB free of 10GB needed message shown.

Change from default to custom:
8GB free of 10GB needed message shown.

Change path into C:\Users\Diapolo\AppData\Roaming\Bitcoi:
8GB free of 10GB needed message shown.
Warning: Low disk space on device shown.

Change path into C:\Users\Diapolo\AppData\Roaming\Bitcoin\
8GB free of 10GB needed message shown.
Directory already exists. Add \name... and so on, shown.


I think the default detected path C:\Users\Diapolo\AppData\Roaming\Bitcoin should show the Directory already exists message but the current implementation does this only after applying the \, which I don't expect.

Copy link

Choose a reason for hiding this comment

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

Can you change these style-sheets to color: #800000; to be CSS standard-conformant?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm pretty sure this is not required by the standard (stack overflow agrees, see top answer here http://stackoverflow.com/questions/11939595/leaving-out-the-last-semicolon-of-a-css-block ). Can you quote me the part of the standard where it says that the last declaration needs a ; separator?

Copy link

Choose a reason for hiding this comment

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

This adds an introduction screen that is shown when the client is first
started in which the user can choose a data directory.

It is also possible to force the intro screen to appear using command
line argument `-choosedatadir`.

The user is warned that the client will download and store 10Gb of data.
The intro screen shows how much space is available on the device that
contains the chosen directory and warns if this is less than the 10Gb.

To make it possible to translate the introduction dialog, the initialization
sequence is changed so that translations are
loaded before the data directory. This has the by-effect that it is
no longer possible to specify a language in bitcoin.conf inside the data
directory.
@laanwj
Copy link
Member Author

laanwj commented Jun 16, 2013

Should be solved now.

@Diapolo
Copy link

Diapolo commented Jun 16, 2013

The directory things and disk-space stuff is fixed, great :).
Only thing left is the layout / size, I still think the dialogs height is too large and I would perhaps align the input field for the path and the message labels with the left border (like the selection boxes).

@laanwj
Copy link
Member Author

laanwj commented Jun 16, 2013

Feel free to play with the layout a bit...

@Diapolo
Copy link

Diapolo commented Jun 16, 2013

GUI can be improved later :-).

ACK

@BitcoinPullTester
Copy link

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/be77b637fcf5983286382a9b9677fb97b026abe2 for binaries and test log.
This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/
Contact BlueMatt on freenode if something looks broken.

Copy link

Choose a reason for hiding this comment

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

Perhaps you can update this to use TestNet() from chainparams.h, which you need to include here then? Otherwise I can do this after it's merged :).

Edit: We don't need chainparams.h as it's coming from init.h alreay.

Copy link
Member Author

Choose a reason for hiding this comment

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

Are you sure that will work? The reason for looking for testnet arg here
directly is that it is called before Init.

Copy link

Choose a reason for hiding this comment

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

I tried it and it doesn't work, as we are before init here. I think it would be nice, if we could achieve to use TestNet() with re-ordering the code, but my try doesn't yet do this work ^^. See #2788

Anyway, I would suggest you merge this pull and we can look into this afterwards.

@Diapolo
Copy link

Diapolo commented Jul 13, 2013

@laanwj Can we perhaps merge this now :)?

@sipa
Copy link
Member

sipa commented Jul 14, 2013

ACK - seems to work fine.

laanwj added a commit that referenced this pull request Jul 19, 2013
qt: allow user to choose data directory
@laanwj laanwj merged commit 4eab2dc into bitcoin:master Jul 19, 2013
@laanwj laanwj deleted the 2013_05_datadir branch April 9, 2014 14:19
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants