Preparing for wx --> qt switch - page 3.

ThiagoCMC

legendary

Activity: 1204

Merit: 1000

฿itcoin: Currency of Resistance!

Mmm...

> Does not generate new receiving addresses automatically (good idea, I think, but may be controversial).

I like this feature. I do not want to see it removed. I like to keep track of all my "DYMANIC" and of my "STATIC" addresses... This should NOT be changed.

BTW, I don't like QT... It is a ugly toolkit... GTK3 is much nicer... But, I appreciate the effort!!

Anyway, do you know, more or less, when the Bitcoin core will be decoupled of the GUIs?! I mean, when will be only somekind of oficial LibBitcoin and a lots of GUIs, like QT, WX, GTK3, GTK2... Huh

Thanks!
Thiago

btcbaby

member

Activity: 87

Merit: 10

QT is an awesome platform, good move.

Gavin Andresen

legendary

Activity: 1652

Merit: 2216

Chief Scientist

Quote from: nibor on September 16, 2011, 03:58:37 PM

Could you or someone provide a list of future version numbers you are intending to use?

0.4.0 : Out real soon (0.4.0 release candidate 2 binaries are available on sourceforge now)

0.4.1 : I'd give about a 80% chance of happening (major bug or security problem found in 0.4.0)
0.4.2 : I'd give about a 20% chance of happening (major bug or security problem found in 0.4.1)

0.5.0 : Will be the Qt release.

Beyond that... who knows?

nibor

sr. member

Activity: 438

Merit: 291

Gavin,

Could you or someone provide a list of future version numbers you are intending to use?

I will then add them all in one go to the rrd charts of versions running at:
http://bitcoinstatus.rowit.co.uk/versions.html

It is very dull job adding them and I would much rather add a load in one go!

Thanks

nelisky

legendary

Activity: 1540

Merit: 1001

Quote from: Gavin Andresen on September 16, 2011, 01:07:21 PM

So you can run the GUI with the -server switch, but you'll have to talk to it using (for example)
bitcoind getinfo

That's perfectly acceptable. I thought the rpc server was being removed for whatever reason, but if it's just the cli client for the GUI then it makes perfect sense.

Quote from: Gavin Andresen on September 16, 2011, 01:07:21 PM

RE: why switch: because no wxwidgets programmers stepped up and made it better. And from what I can see, QT is more popular and supported (so there are more programmers able and willing to help improve).

That's more than fair

I am not a die hard wxwidgets coder, nor a GUI coder tbh. I actually have "I suck at designing user interfaces" in my CV, though not in those exact words! I was just curious about some shortcoming of wx that I was unaware of. All good

Gavin Andresen

legendary

Activity: 1652

Merit: 2216

Chief Scientist

RE: cannot act as a RPC client:

I believe it will still be able to act as a RPC server.

So you can run the GUI with the -server switch, but you'll have to talk to it using (for example)
bitcoind getinfo

... as opposed to today, where you can run "bitcoin -server" to get the GUI and then run "bitcoin getinfo" to talk to the running GUI process.

RE: why switch: because no wxwidgets programmers stepped up and made it better. And from what I can see, QT is more popular and supported (so there are more programmers able and willing to help improve).

RE: screen shots: See the bitcoin-qt thread in the Alternative Clients sub-forum here.

nelisky

legendary

Activity: 1540

Merit: 1001

Quote from: Gavin Andresen on September 16, 2011, 11:49:34 AM

Cannot act as a rpc client (ok with me, we'll still compile/ship a headless bitcoind)

Is there a reason for this or is it just "the way it got coded"? It helps me somewhat to be able to have rpc to the running GUI bitcoin client. Either that or the priv key import/export *hint*

Also, this may not be the right place to ask, but why the move from wx to qt? I know a better GUI was long due, but I happen to know and like wx (have no quarrel with qt, mind you) and I don't think there's much if anything that you can do with one and not with the other...

bcforum

full member

Activity: 140

Merit: 100

Quote from: Gavin Andresen on September 16, 2011, 11:49:34 AM

Cannot act as a rpc client (ok with me, we'll still compile/ship a headless bitcoind)

Can you expand on this? I currently run 'bitcoin -server' on my linux machine. This gives me the GUI for monitoring transactions and the RPC functions to support solo mining. If the RPC client is removed, I'll have to run 'bitcoin' and 'bitcoind', but there is (I think) a conflict with the port address and the second client will not run. I will also need to download and maintain two copies of the block chain (a minor annoyance)

Remember remember the 5th of November

legendary

Activity: 1862

Merit: 1011

Reverse engineer from time to time

Can you provide a screenshot for a reference?

Gavin Andresen

legendary

Activity: 1652

Merit: 2216

Chief Scientist

So the plan is for the next release of bitcoin to switch from the wxWidgets GUI we have now to the vastly nicer QT GUI that John Smith created.

I spent some time yesterday compiling Qt and bitcoin-qt, and some time this morning doing a very quick code review (executive summary: looks great!).

I'm mostly posting this as a brain dump of "stuff not to forget" when it is time to pull QT and remove WX.

Major behavioral differences I noticed during code review:

Does not generate new receiving addresses automatically (good idea, I think, but may be controversial).
Cannot act as a rpc client (ok with me, we'll still compile/ship a headless bitcoind)

Will-need-to-be-done stuff:

Find and replace or remove references to wxwidgets in documentation, makefiles, etc.
Change makefiles to track rpc.cpp --> bitcoinrpc.cpp name changes
The QT library is LGPGL licensed; do we need to change READMEs or other files?

... and probably a bunch of other little things I didn't notice or I forgot to write down.

Topic: Preparing for wx --> qt switch - page 3. (Read 6499 times)