Topic: GLBSE 2.1 open for testing (Read 2411 times)

Yep, checks all addresses. New addresses get checked automatically, once they're re-used you need to use the button, we'll make this automatic in the future for it's ok for the moment.

teek, the order was brought over from 2.0, but because it's not on the one table anymore it looks backwards, I change that.

the asks are in the wrong order again.

Looks like it, there's now a button to re-check the deposit adress(es) for new deposits.

I want to make sure. We can reuse deposit address now?

Beautifulsoup + Python 4tw!

I fully agree with your feature request though and want to reiterate the request for a way to pay dividends via the API.

Another thing:
Sparklines seem to be scaled in a wrong/individual way instead of to 30 days. https://glbse.com/asset/view/PPT.B for example exists less than 30 days, still the sparkline looks like it does, making it hard to compare to other sparklines that have different scales on the x-axis.

Largest bids on top and smallest asks on top would also be great, but I already wrote that above.

Anyways, it really looks great live! Congratulations!

As I mentioned it earlier, any announcments should be public. Most fiat based stock exchanges have announcment section with RSS feed for each asset.

I'm not sure if it's already there in the mail function, but can you send a mail to all current holders of an asset?

More suggestions: in mail show which messages have been read and add a link back to Inbox/Outbox on page where you read the body of the message (next to Reply link).

Where is there the best place to post sugestions? Here?

Added sparklines

Your interface reminds me of a professional business site.

There was recently an advertisement in a business magazine I was reading bringing awareness to a business communication site that brought you to mind.

I think with further effort and promotion revenue can definitely precipitate.

This could be done by anyone else as well, doesn't need to be GLBSE (though it would be nice to get the transfer fees waived for the escrower).

If I take a look at http://dev.glbse.com/asset/view/BIG.ASS, it would make more sense to me to have the bids and asks below the chart like this:

The offer for 2 @ 2.0 HAS to be the one submitted earlier than the one with 10 @ 2.0!

So:
Bids - sorted highest to lowest first, lowest to highest timestamp second
Asks - sorted lowest to highest first, lowest to highest timestamp second

Bootstrap

looks nice!
what is the name of the CSS template that you use?

In ASK BUY and BID SELL part. It would be usefull to have some labels. There are two fields, obviously one is for price and other for quantity. However, it would be better to have them lableled, so I do not buy 1 share for 1000BTC instead of 1000 shares for 1BTC each  

Also web and email addresses could be linkns. (at the bottom of asset info page accessible from Market).

Pay dividends link should be only active when you act as an asset issuer.

When logging in on front page (at the top of the page) it is not clear whether one should enter login or email. Only email works.
Also when trying to recover the password, no email has been sent to my email. Not sure whether it is this way just in DEV.

Hide BTC asset in Market. There is no point of listing it there. Probably you could list USD instead

I also tried to pay dividend before IPO launch date and got server error: TypeError at /asset/makepayment/PR89.SHA nil can't be coerced into Fixnum (probably division by zero).

And of course, thanks, congratulations on fantastic job. Well done!

And humble sugestion: could you implement an escrow for shares, so they can be frozen as colateral in lending. It would work similar to transfer, but recipient does not get shares. Recipient may request escrow to be returned to owner when debt is paid back. Ability to borrow against an asset will help to keep its value. If there is danger of fire sales in low liquidity market, the price of assets suffers.

Now it looks much better !

Except in this case, you've seen how ugly GLBSE2.0 is.

Suggestions noted, I'll make updates regarding the colors (I like buttons with many colors  ).

A couple of CSS/style/ux things.

Slapping bootstrap on a project sadly doesn't make it insta-pretty! (TM pending) I have a couple of suggestions.

Rethink the menu structure
You currently have two types of navigation bars this is confusing and not needed. You can probably come up with a two dimension menu structure and group certain logical parts together. Not every link is as important as the next one. Should "create security" really be something that is prominently available in the main menu bar? Are all users going to be using that often? Think about which options are highly used and make those easily available and feel free to hide the others away in less used groups.

Remove the noisy background
The grid-like background on the body is very distracting and it kinda melts together with the lines of the standard bootstrap table style. Consider removing it all together.

Just because you can use all kinds of funky button colors doesn't mean you should

From a user experience standpoint this is a very weird thing to see. The text for the buttons is the same but the color somehow seems to hint that each button is somehow in a different state. Only use colors if they really add value to the user experience.

There are some other odds and ends but since it's a work in progress I will leave those be till you are further along.

That being said it already looks 100 times better then the current non-dev build. Keep it up

Yeah, there are a lot of rough edges. I'll devote a little time and love to the mail functionality in GLBSE 2.2 update, make it something usable.

Not a bug report but a suggestion.

Compose needs some CSS love.
 - http://dev.glbse.com/user/mail/compose

Also color for status message after successfully changing password is red.  Shouldn't OK / success be green?

All requests will be over SSL when in production so the API key will be fine.

Thanks for the tip on sparklines, will add that for 2.1.1