Bitcoin Forum

Demo client ready
The working title of our stock market platform is BlackMarket.

Were building a client that will be available under the FreeBSD licence.

The client (bmc) is a console based application, because of the cryptography involved trades cannot be made using the web browser currently. One of the goals of this client is to make it very easy to use.

And so, with much thanks to Ryland Taylor-Almanza who is working on this we have the first available user interface to play with.

You'll need Linux, and a working installation of ruby(we're using 1.9.2 but I think 1.8.6/7 may work, have not tested).

Files to download are bmcmenu-0.0.1.gem (http://109.75.176.245/cgi-bin/bmc/artifact?name=60773cc05b7219fc0dec8373578d531cb16fb425) and bmc (http://109.75.176.245/cgi-bin/bmc/artifact?name=a6ccc4fe2f1e64754358f118608918e0890150cd)

Install with
then run bmc from the same directory with


I would recommend anyone who is investing in this to give the client interface a try and make any suggestions.

All suggestions welcome, also before anyone asks, the client when finally ready will automatically create a new trade account on the server when run for the first time, so it should be almost zero config to start using.

I have ruby 1.8.7 but not gem. Any idea what Fedora package contains gem?

Seriously your best option is to install rvm, and use that to install various versions of ruby, it makes it really easy.

http://rvm.beginrescueend.com/

If not then you can try to install ruby-gems

Download http://production.cf.rubygems.org/rubygems/rubygems-1.5.3.tgz
Unpack into a directory and cd there
Install with: ruby setup.rb (you may need admin/root privilege)

Seriously, if the BlackMarketClient requires messing about with dependencies, it's not going to take off.

I love ruby as an elegant and powerful programming language, and if I was developing for a ruby project I would willingly install all this stuff. But these dependencies are not appropriate for someone who just wants to run an end-user application.

Well this is the development stage, when we're working on basic functionality as opposed to ease of install. Once we do a major release, it really will be a case of download and run with no fuss, across a number of platforms (including windows).

You don't have to use rvm(I did give instructions for you to just go ahead and install ruby gems), it's just something I recommend if you're playing around with ruby.

I installed rubygems from the repos, and after a little tweaking (they made the executable named gem1.9 for some odd reason...) I got it installed...
I go to run it and I get this unusual error:


So, how do I fix?

I got it to work by using "ruby ./bmc" instead of "./bmc".

I also got this message when installing using Nefario's instructions, but I guess it's nothing to worry about:

So the error when just running bmc is that your ruby environment is not set in your shell (or something like that) and just going ruby bmc works just as well.

The error is absolutely nothing to worry about, it's just looking for rdoc which it doesn't need.

Thanks ribuck.

This one is not so innocent:

My bad, or yours? 'cause it might as well be greek to me, i don't know ruby from a hole in the ground.

This error means the bmcmenu gem has not been installed, at least thats what it normally means.

run this to see if you have it installed

If not install then in the directory with the gem file run

It's in there...

Could you tell me the output for
Have a look in the directories listed and see if the gems are in there. Tell us the output.

Also try
And let us know the results.

That directory was nonexistent. I forgot to "sudo gem install"... and it put it all in  ~/.gem

Copied the files over, and now I have:


Which is what I assume is what I'm supposed to see. :)  Sorry guys. Stupid, sleepy mistake.

That's exactly what you're supposed to see. It's just a menu, doesn't do anything yet but it will allow us to workout what people want. That's the whole point, this thing has to be easy to use.

Thanks for going to the trouble of installing, I appreciate it.

Once we get closer to the release, it will just be a simple bundle that's downloaded and should run without any configuration. Which will get rid of any of this messing about.

No problem. I figure, what better way to idiot-proof a program, than to throw an idiot at it...

when it comes time, I'd be glad to help you get it packed into a .deb package.