Quote from: Hueristic on December 30, 2016, 05:25:33 PM

Quote from: hyc on December 30, 2016, 05:18:19 PM

What's with all this GUI talk in the price speculation thread? There's a Support thread, why aren't people using it?

Quote from: Hueristic on December 29, 2016, 04:29:11 PM

Quote from: KeyJockey on December 29, 2016, 03:03:23 PM

...So, can these be 'directly RUN' from there in order to use the wallet the old-fashion way too, i.e. more control over typing commands (for "save" etc) in addition to using the GUI in a newbie-friendly way i.e. just double-click the icon?

Are there any warnings or danger to be aware of in this case, if so? Or would it still be better to pre-load the daemon etc from another normal copy of the downloaded command line set of Monero files?

(P.S. Sorry if it's a dumb question BUT this is the kind of thing that needs to be made simple, clear, and easy for NOOBS if HoneyPony is really ever going to gain mainstream use and acceptance!)

As I understand it, the GUI is a wrapper that passes calls to the daemon ergo if you use the cli to make those calls then you should not hurt anything. I am guessing as I did none of the programming. The only pitfall I can forsee is that the gui would not refresh from those cli calls and display previous data but that is a rookie move and I can't imagine this team putting out something that lame.

As usual feel free to correct me guys, I'm just making educated guesses from experience on other projects.

No, the GUI is not a wrapper. It is a full wallet, just like the CLI.

You need to keep some distinctions clear:

The monerod daemon syncs the entire blockchain from the P2P network. The blockchain is stored in an LMDB database as soon as each block arrives. You can exit the daemon any time you like and all of that syncing progress will be saved without any further action being needed.

The wallets scan the blockchain of the daemon you're pointed at, looking for transactions owned by your wallet address. The scan results are held in RAM until you exit the wallet, at which time the entire wallet cache file gets written to disk. If your computer crashes while the wallet is syncing with the daemon, all of your current progress in the wallet will be lost. But that's completely separate from the daemon's progress.

You cannot see your latest transactions in any wallet until the daemon is caught up with the rest of the network.

The CLI sends commands to the Daemon correct? That makes it a wrapper correct?

No. The CLI Wallet and the GUI Wallet are equivalent. Neither is a wrapper for the daemon. Both are a client of it.

Another way to put it... if the GUI was a wrapper, it would be a wrapper for the CLI wallet. It is not.