Quote from: etotheipi on September 19, 2013, 05:51:31 PM

Quote from: redphlegm on September 19, 2013, 05:26:09 PM

Quote from: etotheipi on September 19, 2013, 05:23:46 PM

Updates:

Linux: The app technically works, but it's got some serious usability bugs. Importing, sweeping and restoring wallets causes the app to freeze until it finishes. It also frequently freezes when new blocks come in or it checks for a new version. Quite a few other quirks, too. But all these issues are related to usability -- the core functionality seems to be in excellent shape! The app successfully saves its entire state between loads, and only takes about 10-30 seconds to startup and pickup where it left off (longer if you haven't loaded it in a while and Bitcoin-Qt/bitcoind needs to catch up).

Also, building and scanning (on all OS) is much slower than I was expecting. Again, it's only a usability problem, and I am aware of multiple places that I missed optimizations that would improve all this. I plan to dig into those when I get out a testing version.

Windows: The good news is that I got everything compiling and working in Windows using native python (thanks goatpig!). I haven't gotten very far into Windows testing, but so far it appears to work the same as the Linux version though even slower (probably related to the ancient version of LevelDB that i hope goatpig will help me figure out how to upgrade for another 1 BTC

).

The bad news is that the process of creating a .exe file is failing, and may take a bit of work to fix. py2exe has given me quite a bit of trouble in the past, and when I did get it working I had no idea what I did. Therefore, it technically works on Windows, but only if you install python and like eight different python packages. When I do finally get py2exe working, I can put out a pre-testing-testing version that should let people get access to their funds but not use it for regular use (it's going to be very rough around the edges).

For those inclined to compile on Windows, I can tell you that part of the process has been restructuring everything. All the old MSVS 2005/2008 projects have been destroyed, and rebuilt with MSVS 2012 Express. This makes it free to compile (if you register MSVS w/ Microsoft), but it's still going to take a bit of tinkering. If someone wants to try it, I can post a list of packages that need to be installed.

OSX: If anyone wants to help with this, please let me know. The new LevelDB stuff needs to be compiled & tested on the OSX side, and I have no idea how much of a PITA it is. Perhaps Red Emerald is in good shape to try this out.

Great! Thanks for the update. Waiting for this with much anticipation (OSX and Windows).

I forgot to mention that RAM usage on Windows looks to be about the same as Linux. 600-700 MB while the DB is building, then about 300 MB under normal operation. In exchanges for the improved load time and RAM usage is 14 GB of disk space used for databases (which will be reduced in the future, but this was the easiest implementation for now). So it's only a tad more than Bitcoin-Qt itself uses, which is about 11-12 GB currently (i.e. the storage efficiency of all that data in Armory's LevelDB database is only about 10-20% overhead).

I have a question about the upcoming RAM-reduction update. Will there be any option for people to turn off the more hard-drive intensive version of Armory and keep the RAM-intensive version for people who have a lot of RAM? I don't know if this would be a major pain to code or not, but it'd be a nice feature to have.