Would it be possible to code in customizable skins? Something like Hyp's wallet skin selector? That way we could potentially get some new visual styles working in the wallet
Possible, yes. It is a fair amount of work. Plus it requires some skin makers, not my specialty. I'm sure I can get the core of it going. Beauty over Function? |
|
|
|
|
What updates do we want to see for 2.3?
I have had a request for Autosavings updates, including custom send address. I can do that.
I was planning on doing the windows safe shutdown, and the combine/split threshold updates, to help keep blocks more manageable.
Obviously the new icons.
Anything else?
|
|
|
|
Alright I think all the int64 issues are taken care of now. This worked well for me on Ubuntu 12.04, gcc 4.6.3, QT 4.8.1 git clone https://github.com/Tranz5/HoboNickels
cd HoboNickels
qmake HoboNickels-qt.pro
make -f Makefile
sudo ./HoboNickels-qt Debian 6 & qt 4.6.3
This is a bit older version of QT. I will see if I can help you along. My lowest version is 4.8.1 |
|
|
|
Hi All can not build on ubuntu Server 14.04 the new Version in github. https://github.com/Tranz5/HoboNickels.gitHoboNickels/src: make -f makefile.unix Get this ERORR: -------------------------------------------------------------------------------------------- wallet.cpp:2151:59: note: candidates are: In file included from /usr/include/c++/4.8/bits/char_traits.h:39:0, from /usr/include/c++/4.8/string:40, from serialize.h:9, from bignum.h:9, from main.h:8, from txdb-leveldb.h:9, from txdb.h:14, from wallet.cpp:6: /usr/include/c++/4.8/bits/stl_algobase.h:216:5: note: template<class _Tp> const _Tp& std::max(const _Tp&, const _Tp&) max(const _Tp& __a, const _Tp& __b) ^ /usr/include/c++/4.8/bits/stl_algobase.h:216:5: note: template argument deduction/substitution failed: wallet.cpp:2151:59: note: deduced conflicting types for parameter ‘const _Tp’ (‘long int’ and ‘long long int’) nTargetSize = max(GetArg("-keypool", 100), 0LL); ^ In file included from /usr/include/c++/4.8/bits/char_traits.h:39:0, from /usr/include/c++/4.8/string:40, from serialize.h:9, from bignum.h:9, from main.h:8, from txdb-leveldb.h:9, from txdb.h:14, from wallet.cpp:6: /usr/include/c++/4.8/bits/stl_algobase.h:260:5: note: template<class _Tp, class _Compare> const _Tp& std::max(const _Tp&, const _Tp&, _Compare) max(const _Tp& __a, const _Tp& __b, _Compare __comp) ^ /usr/include/c++/4.8/bits/stl_algobase.h:260:5: note: template argument deduction/substitution failed: wallet.cpp:2151:59: note: deduced conflicting types for parameter ‘const _Tp’ (‘long int’ and ‘long long int’) nTargetSize = max(GetArg("-keypool", 100), 0LL); ^ make: *** [obj/wallet.o] Fehler 1 --------------------------------------------------------------------------------------------------------------- Can someone help with this issue? I am working on the fixes. I'll let you know when complete. You can recode if you want, just go up a few posts. Alternatively you can use the offical repo here. https://github.com/Crypto-Expert/HoboNickels it is version 1.4.0. I believe I should have all the int64 stuff cleaned up here tonight. |
|
|
|
thank you, excuse me, but did not have time to check but that's not all  next: In file included from src/qt/charitydialog.cpp:2:
build/ui_charitydialog.h: In member function ‘void Ui_StakeForCharityDialog::retranslateUi(QWidget*)’:
build/ui_charitydialog.h:120: error: ‘class QLineEdit’ has no member named ‘setPlaceholderText’
build/ui_charitydialog.h:124: error: ‘class QLineEdit’ has no member named ‘setPlaceholderText’
build/ui_charitydialog.h:130: error: ‘class QLineEdit’ has no member named ‘setPlaceholderText’
build/ui_charitydialog.h:135: error: ‘class QLineEdit’ has no member named ‘setPlaceholderText’
build/ui_charitydialog.h:156: error: ‘class QLineEdit’ has no member named ‘setPlaceholderText’
I have just about finished the updates to make this more compatible. What version of QT are you using? |
|
|
|
anywhere I can DL the blockchain from, yet?
I can resync the entire block chain if needed, I guess
If you still need this I can get one uploaded for you. CAPs wallet does sync with peers fairly quickly. |
|
|
|
Yeah, the one with this font is much better imo. Typography seems to need a little more centering though, but could just be me.
I am a fan of simplicity so I am already quite happy with the current looks although a nice red bottle cap on the overview button would seem like a nice finishing touch. I have another question though: are there any plans to update the 'autosave'-function with a programmable return address like HBN has as of lately? Cause it really works great! Yes I do plan to add some of the updates from HBN to CAPs. What you have mentioned plus the auto combining. Was waiting until we got some of the new icons ready. Looks like we are making progress. |
|
|
|
Perhaps a little bug, not a big trouble  When I tried to add my own address in address book, wallet tell me that it's already there, but as in pic, book is empty I'm using coin control to combine my block, and in the input the first time, i set my add in "Pay To", a label for the wallet to save it in address book. Since them wallet won't add my address to the book, but when I paste mine in coincontrol, he auto fill the Label. Perhaps I did something wrong, who know ^^ This is working as designed. That address is in your Receive Coins Tab. This is done to prevent the user from putting their own address into the "Sending" portion of the address book, to prevent confusion. The code could be changed to over-ride this safety net, but I am not sure it is a great idea to do so. |
|
|
|
... I agree with Tranz's initial picks, though of course I'd add TEK  Yeah, it's a personal bias. These were just off the top of my head, quick picks. In reality there would be more, and all thoroughly vetted. I like TEK and thundertoe. I rather see it have a little more solid, cleaner, development work. Lots of issues over there right now. But definite potential. |
|
|
|
I am glad that Tranz has agreed to stick to the plan set out when the coin was first launched.
There was never any question that it would be changed. We just had a hypothetical discussion on the benefits of High PoS. I think that all the different PoS % have distinct advantages and disadvantages. Eggs should be placed in different baskets, with care. What would be great would be an ETF type fund that used a basket of PoS coins and moved up and down based on the % it held and how each coin was doing. It would smooth out the ups and downs of individual coins, and help add liquidity as well. It would require an exchange and min 25-50 btc. It should hold at least 5-10 different coins. It could even pay out a dividend based on the staking. I would have it hold the following, just some quick picks: A few low coins like PPC, BC. A few medium HBN, CAP, NVC. and some high % like HYP,ORB . Some/all of the coins would stake as normal, those would be paid out in dividend to the buyers. The ETF would have to buy/sell coins and raise/lower the price, based on buyer/sellers of the fund and the market of each coin in the basket, respectively. The staking can be done very securely, in fact the wallet would never have to touch the internet to stake. It would only need a few trusted peers that are on a secure intranet. Those peers(on the intranet and internet) would connect to worldwide peers and the protected peer. The protected peer would only connect to the intranet peers. So the protected peer would contain the wallet that would stake, and would never have to be on the internet!  Anyway just some food for thought. |
|
|
|
I have noticed that when i send some coins and my wallet is locked sometimes after sending my wallet stays open and I have to manually lock it again. Does anyone else encounters this behavior too? I use 1.4.8.0. It's not a big deal of course but I though it would be good to report it.
It should re-lock, but I will take a look and make sure that is working correctly. Thanks! Found this bug. If you unlocked the wallet for PoS, and then later locked the wallet. The flag to tell the wallet to relock, upon sending, was not set. This one line should fix it. https://github.com/Tranz5/HoboNickels/commit/0b67b4db03783d05f512028d1251c1f930cc1b7aThanks for the bug report. Post and address, as I usually pay a bounty for them. |
|
|
|
This is an interesting discussion. I just want to set expectations, that I don't plan to change the PoS % now or ever. It would be completely unfair to change the rules in that way, especially considering we are over 1 year old. I can understand the reasoning why we would want to, but its not in the cards for me here. Perhaps a bootstrap fork in the future could be done. Yes, understand that. PoS is all about wallet function and issues. You have great skill, experience and consistency. I am not 100% sure which is the best way : Just wondering what exactly would be unfair about changing PoS % ? Does it not still give a level playing field for every current holder, as well as for the new buyers ? Its unfair because people bought into the coin with certain expectations. Changing the parameters this late in the game, just to chase the next big thing doesn't make sense. |
|
|
|
This is an interesting discussion. I just want to set expectations, that I don't plan to change the PoS % now or ever. It would be completely unfair to change the rules in that way, especially considering we are over 1 year old. I can understand the reasoning why we would want to, but its not in the cards for me here. Perhaps a bootstrap fork in the future could be done. |
|
|
|
Thanks, what version of QT were you using? I'll play with this over the weekend and see if I can get a cleaner version out there. |
|
|
|
The final beta version of 1.5 is now ready. https://github.com/Tranz5/HoboNickels/releases/tag/1.4.9.99I have 1 important message you should follow, if you are using Beta 1 or 2 and have S4C enabled, please disable it before shutting down the client. If you fail to do this you will get a wallet warning when starting the new version. To fix this warning(if you missed this), just press disable in the Stake For Charity dialog box, and then shut down and restart the client. You can then enable it as normal. Click here https://cryptocointalk.com/topic/13199-preparing-hbn-v15/?p=139751 for change log from Version 1.4 to now. All of this will be included in the final version 1.5, plus the hard forks. Which means you will still be required to upgrade to 1.5. wanted to look at the coin I only use Linux OMG, with qt5 build and new boost ?)) No, this is too much ... This is compatible with qt4 and 5 as well as boost below 1.5. If you are having a specific build issue, let us know. yes, of course )) Debian 6, amd64: .... cd /home/vit/build/wallets/HoboNickels-1.4.0.0; /bin/sh share/genbuild.sh /home/vit/build/wallets/HoboNickels-1.4.0.0/build/build.h fatal: Not a git repository (or any parent up to mount point /home) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). g++ -c -pipe -fstack-protector-all --param ssp-buffer-size=1 -msse2 -O2 -D_REENTRANT -fdiagnostics-show-option -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wstack-protector -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DBOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN -D__NO_SYSTEM_INCLUDES -DUSE_UPNP=1 -DSTATICLIB -DUSE_IPV6=1 -DUSE_LEVELDB -DHAVE_BUILD_INFO -DLINUX -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4 -Isrc -Isrc/json -Isrc/qt -Isrc/leveldb/include -Isrc/leveldb/helpers -I../boost_1_55_0 -Ibuild -Ibuild -o build/bitcoingui.o src/qt/bitcoingui.cpp src/qt/bitcoingui.cpp: In member function ‘void BitcoinGUI::connectionIconClicked()’: src/qt/bitcoingui.cpp:638: error: ‘currentDateTimeUtc’ is not a member of ‘QDateTime’ ../boost_1_55_0/boost/system/error_code.hpp: At global scope: ../boost_1_55_0/boost/system/error_code.hpp:222: warning: ‘boost::system::posix_category’ defined but not used [-Wunused-variable] ../boost_1_55_0/boost/system/error_code.hpp:223: warning: ‘boost::system::errno_ecat’ defined but not used [-Wunused-variable] ../boost_1_55_0/boost/system/error_code.hpp:224: warning: ‘boost::system::native_ecat’ defined but not used [-Wunused-variable] Thanks that was just a typo. Please try the Beta version, it will be release version soon enough. git clone git://github.com/Tranz5/HoboNickels |
|
|
|
I am currently running v1.4.0.0-g4ddc7a0a-hobo. Do I need to upgrade now, or can it wait for a bit?
You can wait. |
|
|
|
Looks like some people have managed to pick up some cheap coins, someones been dumping a reasonable amount on the market. Not sure why they dump it like this though, instead of trickling it to the market in chunks to get a good price they straight out dump it into the sell letting some get cheap coins but getting significantly less for themselves in the process.
Sometimes fast money is more important than more money. People fire sale everything from houses to cell phones to crypto. The market will find the correct level. |
|
|
|
The final beta version of 1.5 is now ready. https://github.com/Tranz5/HoboNickels/releases/tag/1.4.9.99I have 1 important message you should follow, if you are using Beta 1 or 2 and have S4C enabled, please disable it before shutting down the client. If you fail to do this you will get a wallet warning when starting the new version. To fix this warning(if you missed this), just press disable in the Stake For Charity dialog box, and then shut down and restart the client. You can then enable it as normal. Click here https://cryptocointalk.com/topic/13199-preparing-hbn-v15/?p=139751 for change log from Version 1.4 to now. All of this will be included in the final version 1.5, plus the hard forks. Which means you will still be required to upgrade to 1.5. wanted to look at the coin I only use Linux OMG, with qt5 build and new boost ?)) No, this is too much ... This is compatible with qt4 and 5 as well as boost below 1.5. If you are having a specific build issue, let us know. |
|
|
|
The final beta version of 1.5 is now ready. https://github.com/Tranz5/HoboNickels/releases/tag/1.4.9.99I have 1 important message you should follow, if you are using Beta 1 or 2 and have S4C enabled, please disable it before shutting down the client. If you fail to do this you will get a wallet warning when starting the new version. To fix this warning(if you missed this), just press disable in the Stake For Charity dialog box, and then shut down and restart the client. You can then enable it as normal. Click here https://cryptocointalk.com/topic/13199-preparing-hbn-v15/?p=139751 for change log from Version 1.4 to now. All of this will be included in the final version 1.5, plus the hard forks. Which means you will still be required to upgrade to 1.5. |
|
|
|
|
Show Posts
