Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Such Project, Much GUIs #6
Can you please explain me why two gui's for wownero? Is the sumokoin gui intended to replace the other one or each one is for a different purpose?
Remember than the sumokoin gui is just a wrapper to monero-wallet-rpc, and its basically a html page with some controls embedded. Not sure if its secure or not but pyside seems old and I can't find a proper event filter (e.g: to prevent click hijacking).
On the other side the monero gui is full of features that wownero may not need (support for ios/android, support for bootstrapping, remote nodes, support for detached daemon manager, etc).
Yes. I am comparing which of two is more maintainable, at least for me, since I am the one (of two) trying to make something out of it. I have 0 experience with QML, C, C++ and related but a lot of experience with Python.
Both should serve the same purpose, but I think that at this point no one can say for sure which one will do that in the end.
I am personally very aware of that and I think rest of devs are too.
God bless the one who wants to click-hijack Wownero GUI wallet for any purpose in this world. I assume that would mean that Wownero actually has some value. :)
All stated is 100% correct and I personally 100% agree :)
All that said, Wownero GUI wallet is definitely not finished yet and I think that there is no definite decision which of two versions (or maybe even some third?) will be developed in the future.
@bomb-on thanks for the feedback.
Good to know, please send me some wownero when you have time :p
Being so WOW, I think wownero deserves its own frontend. Maybe sumokoin idea isn't bad (i mean the wrapper around rpc wallet) but I would ditch pyside and go for qt instead (for the frontend) and lua to encode/decode json queries. This way the gui can be easily extendable (based on current rpc methods) without much C++ understanding.
You are more than welcome!
All my wow is safely locked on various exchanges in forms of 5000+ satoshi sell orders, so this might be a bit difficult :)
Tbh, I am open for any "solution" but because of lack of experience with cross-platform GUI apps in general is at this moment I am unable to decide which of mentioned paths would be "the best", while "the easiest to maintain" in the same moment :) I like the idea of making a wrapper around existing binaries very much and I will definitely try to google a bit about your suggestions! If you feel like you can share some hints and tips feel free to do so, or even better, join us in #wownero on IRC and let's have a quick chat about it sometimes...
I did some work today on a new gui. It is just a showcase, showing a dashboard tab. Was tested on linux against monerod, not wownerod, but should work on both.
My idea is implement other components as closable tabs, leaving the dashboard always opened. I'm not sure what is the best idea, maybe a tab per wallet? maybe one tab per view (transfer,receive,history)?. Feedback would be WOW!
This is way easier so I'm going to do that. Not sure about the workflow. Bitcoin-qt is tied to a specific wallet.dat and allow us to import/generate all new adresses we want. Monero-gui remembers last open wallet and ask for a password at start.
I like the decred way. Recover/create a new wallet on start and use that unless the user closes it. Then wizard again.
I think suchwallet needs to be KIWS (keep it Wow & stupid) and skip all the open/close wallet nonsense.
I copied those from IRC. They are stored in a lua table.
referenced this issue
Jun 30, 2018
At the end I'm going to integrate all the widgets in the mainwindow, a la Electrum and use monero wallet api instead of the wallet_rpc
Dashboard tab always visible
Here is a sneak peak:
closable views (need to make addressbook visible only when wallet is opened)
one tab was invoked from the view menubar.
this tab can't be invoked again until that tab is closed.
basic support for completion (for daemon console)