Pages:
Author

Topic: Armory 0.93 testing release! (with 0.05 BTC bug bounty) - page 12. (Read 35695 times)

sr. member
Activity: 672
Merit: 250
Most Advanced Crypto Exchange on the Blockchain
No, using the latest stable version 0.92.3.
I tried opening in offline mode and the program opens just fine.
Only crashes at Building Databases then the Armory-QT service
will crash at the same percentage every time.

Is there another more appropriate thread here I can post on
for support?

Are you using the testing version?
hero member
Activity: 563
Merit: 500
It's certainly true that the free versions of Visual Studio and xCode are highly usable products atm, not sure whether the legal publishing limitations are the most restrictive part of using them

And I don't really see that changing.  The platforms need the teenagers and the college students who are learning to program to be able to use their platform otherwise they are just hurting their future supply of professional developers.  AIUI, even iOS development has become less onerous over the years, both in terms of fees and in terms of what you have to agree to in the developer agreement.  A software ecosystem that excludes developers from it can't survive in the long term.

EDIT: Anyway, we're probably going way off topic for the thread here Smiley
legendary
Activity: 3430
Merit: 3079
It's certainly true that the free versions of Visual Studio and xCode are highly usable products atm, not sure whether the legal publishing limitations are the most restrictive part of using them
hero member
Activity: 563
Merit: 500
If it causes any other problems at all with development, I'd like to register my interest in removing support for OSX. It's a minority user group [...]

OS X is a minority user group in much the same way that Linux is a minority user group.  They're broadly comparable in size. [EDIT: which is larger seems to depend on who you ask and what metric for "larger" you choose.]

I'd always assume that Linux is way smaller, in fact. There's a significant difference though: Apple forces large costs onto the developer in the shape of licences for it's development tools (which get updated every time OSX does, which is at least $1000 annually IIRC). Maybe someone at ATI can chime in: are we at the point yet where Apple are charging in a 365-days type licence? (i.e. once 12 months expires, development suite locks the user from compiling or similar)

As for the future... did you see that Google Drive and (official) .NET runtime are being cultivated for Linux? You will be assimilated  Cheesy


Last time I downloaded Xcode it was free.  Pretty sure you can still develop for OS X without paying.  [EDIT: And have you any idea how much an MSDN/Visual Studio subscription costs per year?  But you can still develop with Visual Studio Express for free]
legendary
Activity: 3430
Merit: 3079
If it causes any other problems at all with development, I'd like to register my interest in removing support for OSX. It's a minority user group [...]

OS X is a minority user group in much the same way that Linux is a minority user group.  They're broadly comparable in size. [EDIT: which is larger seems to depend on who you ask and what metric for "larger" you choose.]

I'd always assume that Linux is way smaller, in fact. There's a significant difference though: Apple forces large costs onto the developer in the shape of licences for it's development tools (which get updated every time OSX does, which is at least $1000 annually IIRC). Maybe someone at ATI can chime in: are we at the point yet where Apple are charging in a 365-days type licence? (i.e. once 12 months expires, development suite locks the user from compiling or similar)

As for the future... did you see that Google Drive and (official) .NET runtime are being cultivated for Linux? You will be assimilated  Cheesy
hero member
Activity: 563
Merit: 500
If it causes any other problems at all with development, I'd like to register my interest in removing support for OSX. It's a minority user group [...]

OS X is a minority user group in much the same way that Linux is a minority user group.  They're broadly comparable in size. [EDIT: which is larger seems to depend on who you ask and what metric for "larger" you choose.]

Sure, it remains to be seen which way Windows and OS X are heading - without a crystal ball it's impossible to tell - but it's quite possible [EDIT: even quite likely] that in the very long term they'll both evolve into walled gardens, and FOSS operating systems will be the only unrestricted general purpose operating systems.

[As a complete aside, I've seen one commentary that suggested that the reason for Valve's interest in developing their Linux-based Steam Machines is precisely because they are worried that in the long term (think >10 years) Windows may well stop being an open platform where their users can install games via their Steam platform - rather than being limited to only installing software via Microsoft's app store.]

roy
legendary
Activity: 3738
Merit: 1360
Armory Developer
Are you using the testing version?
sr. member
Activity: 672
Merit: 250
Most Advanced Crypto Exchange on the Blockchain
Question for the Armory support guys here.

I had Armory recently crash and then would not open properly anymore, so I did a
factory reset / re-download the blockchain.  This didnt help.

Now Armory always crashes at the exact same point when it is at the
step - building database.

Ive even done a full uninstall of armory, delete all its program files and appdata
folders, reinstall armory, full download of the blockchain, but Armory still always
crashes at the same exact percentage of building databases.

I even re-installed it under a new user account in Win7 but crashes the same.

Ive done a reset / re-download of the blockchain at least 4 or 5 times with the
torrent option enabled and disabled.  Always crashes.  However BitcoinQT always
opens no problem when I check the status of that.

I verified bitcoinQT opens properly, got the green check mark and is fine but
the armory app always crashes now no matter what I try.  Any idea here
how to fix this?  I cant get armory to load anymore so Im kinda locked out
of the wallet if I needed it.


E$
sr. member
Activity: 255
Merit: 250
Senior Developer - Armory
On OS X, file dialog is even worse now. It loads the Qt file dialog, but after that it loads the OS X one, and on top of that, it doesn't even load the file in.

Should already be patched. I derped and didn't clean something up properly. (Sorry!) (EDIT: .6) should be fine.
full member
Activity: 120
Merit: 100
Java Coder
On OS X, file dialog is even worse now. It loads the Qt file dialog, but after that it loads the OS X one, and on top of that, it doesn't even load the file in.
legendary
Activity: 3738
Merit: 1360
Armory Developer
void BlockDataViewer::registerAddressBatch(

Classic msvc to gcc snafu: can't declare methods in .h with the class name prefix in gcc. I was merging a bunch of changes back and forth and didnt check the build on Debian. I'll get it under control.
legendary
Activity: 1400
Merit: 1013
aa5db7de00ec7876173bdbabe559deb297c3034d doesn't build:

Quote
g++  -Icryptopp -Imdb -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS -I/usr/include/python2.7 -I/usr/include/python2.7 -std=c++11 -O2 -pipe -fPIC -c UniversalTimer.cpp
g++  -Icryptopp -Imdb -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS -I/usr/include/python2.7 -I/usr/include/python2.7 -std=c++11 -O2 -pipe -fPIC -c BinaryData.cpp
g++  -Icryptopp -Imdb -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS -I/usr/include/python2.7 -I/usr/include/python2.7 -std=c++11 -O2 -pipe -fPIC -c lmdb_wrapper.cpp
g++  -Icryptopp -Imdb -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS -I/usr/include/python2.7 -I/usr/include/python2.7 -std=c++11 -O2 -pipe -fPIC -c StoredBlockObj.cpp
g++  -Icryptopp -Imdb -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS -I/usr/include/python2.7 -I/usr/include/python2.7 -std=c++11 -O2 -pipe -fPIC -c BtcUtils.cpp
g++  -Icryptopp -Imdb -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS -I/usr/include/python2.7 -I/usr/include/python2.7 -std=c++11 -O2 -pipe -fPIC -c BlockObj.cpp
g++  -Icryptopp -Imdb -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS -I/usr/include/python2.7 -I/usr/include/python2.7 -std=c++11 -O2 -pipe -fPIC -c BlockUtils.cpp
g++  -Icryptopp -Imdb -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS -I/usr/include/python2.7 -I/usr/include/python2.7 -std=c++11 -O2 -pipe -fPIC -c EncryptionUtils.cpp
g++  -Icryptopp -Imdb -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS -I/usr/include/python2.7 -I/usr/include/python2.7 -std=c++11 -O2 -pipe -fPIC -c BtcWallet.cpp
In file included from BtcWallet.cpp:11:0:
BlockDataViewer.h:112:9: error: extra qualification ‘BlockDataViewer::’ on member ‘registerAddressBatch’ [-fpermissive]
    void BlockDataViewer::registerAddressBatch(
         ^
Makefile:87: recipe for target 'BtcWallet.o' failed
make[1]: *** [BtcWallet.o] Error 1
make[1]: Leaving directory '/home/justus/src/BitcoinArmory/cppForSwig'
Makefile:9: recipe for target 'all' failed
make: *** [all] Error 2
full member
Activity: 120
Merit: 100
Java Coder
Unrelated Question: Is anyone else not receiving emails regarding new replies on this topic? I tried disabling/reenabling notifications and nothing.
I don't know where else to put this.
sr. member
Activity: 255
Merit: 250
Senior Developer - Armory
We currently have good cause the believe our OSX related GUI issues would go away with Qt5. Qt5 would require Python3 and that is desirable on its own. The move the Python3 is expensive but something we eventually need to do. It's more a matter of "when" and priorities than "should we". The move to Qt5 should be rather cheap past that point.

Now, if we get through all of this and OSX is still not behaving, our stance towards this OS could very well change. Our current position hinges on our assumption that a strong solution to the OSX snafu exists, and that there are a lot of other benefits to leverage from that change.

On top of Qt5 appearing to have better OSX support, the upgrade to Qt5 also potentially allows us to leverage the codebase and get Armory or some variant onto iOS and Android. I'M NOT SAYING WE'LL BE ON MOBILE PLATFORMS. I'm just saying that, depending on which way Armory breaks in the coming year, we may have no choice but to upgrade. (Well, we kinda don't anyway, but the more reasons other than "Because Py2/Qt4 are hitting EOL," the better. Smiley )

Anyway, yes, part of the problem is that these are "expensive" upgrades, even Qt, which probably won't take more than a couple of days to switch before testing. There are lots of underlying parts that can play with Python and Qt in unexpected ways. Just this weekend, I tinkered with the SWIG parameters on my machine (long story), and I think that caused Armory's behavior to change a bit. If changing a simple compilation parameter can cause the code to act differently, changing virtually all the code will require loads of testing. It is what it is.
legendary
Activity: 2912
Merit: 1060
Coinbase is hipster and does use os x. They could be a client so os x could be relevant.

Anyway, .99 is awesome now! Thanks armory.
legendary
Activity: 3738
Merit: 1360
Armory Developer
As long as your investors are willing to foot the bill for the way this unfolds, then I can't find any fault with that. I predict serious problems with getting yourself inside Apple's walled garden without being coerced into compromising the product. There's a big danger you might be put in a position where you spend more money on OSX development than for any other platform, and end up having thrown all that money away. Investors wouldn't be impressed if so.

We currently have good cause the believe our OSX related GUI issues would go away with Qt5. Qt5 would require Python3 and that is desirable on its own. The move the Python3 is expensive but something we eventually need to do. It's more a matter of "when" and priorities than "should we". The move to Qt5 should be rather cheap past that point.

Now, if we get through all of this and OSX is still not behaving, our stance towards this OS could very well change. Our current position hinges on our assumption that a strong solution to the OSX snafu exists, and that there are a lot of other benefits to leverage from that change.

Ok can we at least agree not to support any other coins?

Haha, sure
legendary
Activity: 2912
Merit: 1060
Ok can we at least agree not to support any other coins?
legendary
Activity: 3430
Merit: 3079
Some of our investors and publicly prominent users run on OSX. And generally, while we'd like to stop supporting some outdated OSes eventually, OSX doesn't fall in that basket and we can't just outright pull the rug.

As long as your investors are willing to foot the bill for the way this unfolds, then I can't find any fault with that. I predict serious problems with getting yourself inside Apple's walled garden without being coerced into compromising the product. There's a big danger you might be put in a position where you spend more money on OSX development than for any other platform, and end up having thrown all that money away. Investors wouldn't be impressed if so.

Apple on the other hand takes an open source kernel without a GDE and instead the proper hooks in place to support any, forces its GDE on it and breaks GUI interoperability mechanics from version to version, on what I can only call a whim.

A whim that they charge both the users and the developers handsomely to indulge. It's whimsical profiteering, if you like.
legendary
Activity: 3738
Merit: 1360
Armory Developer
If it causes any other problems at all with development, I'd like to register my interest in removing support for OSX. It's a minority user group and it's expensive to develop for (both in maintaining the latest version of the development suite, and in the time spent wrestling with what sounds like a very badly supported GUI framework).

Not gonna happen. Some of our investors and publicly prominent users run on OSX. And generally, while we'd like to stop supporting some outdated OSes eventually, OSX doesn't fall in that basket and we can't just outright pull the rug.

Windows 8 too. They're turning powerful computers into a toy like a tablet. It's a joke.

I know Microsoft deserves a lot of the heat it gets, but that one is a bit harsh. MS has a long history of maintaining backwards compatibility and supporting deprecated calls for... pretty much ever. Also consider that the upcoming Windows 10 still runs on the same kernel (6.x) as Vista. On top of that, maybe 99% of the basic GUI WinAPI calls are shared with kernel 5.x (WinXP and 2k). What's stopping me from running Armory on Win2k is its very lack luster threading API, not the GUI code.

Compared to that, Apple likes to bin certain GUI API calls from a minor version to another. Not playing in the same league at all.

There is something the be said about that. While MS chooses to integrate its GDE its closed source kernel, at least they have the common sense of insuring a lot of backwards compatibility between builds. Apple on the other hand takes an open source kernel without a GDE and instead the proper hooks in place to support any, forces its GDE on it and breaks GUI interoperability mechanics from version to version, on what I can only call a whim.
legendary
Activity: 2912
Merit: 1060
Os x is moving to an app model anyway

Sounds like Game Over. Apple are turning into the AOL of the operating system world (i.e. rich grandmas need only apply). It's sad stuff.

Windows 8 too. They're turning powerful computers into a toy like a tablet. It's a joke.
Pages:
Jump to: