Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - valzav

Pages: 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 ... 20
91
Technical Support / Re: Full Windows Client
« on: October 24, 2015, 01:46:12 pm »
You can download BitShares-2.15.294-x64-cli-tools.exe and run the witness node (edit the config.ini, rpc endpoint: 127.0.0.1:8090)
Then run your light client and change the wallet server to 127.0.0.1:8090.

Now you have the full windows client.

There is no config.ini file. Just cli_Wallet, delayed_node, msvcp120.dll, msvcr120.dll and witness_node. Where is the config.ini file suppose to be?

I've installed qora, nxt, nem and eMunie today. This is by far the most frustrating.

Config file will be created in your data dir after your start witness_node, you would need to restart after you change config file.
For the best user experience I recommend to use light wallet.


92
General Discussion / Re: Graphene GUI testing and feedback
« on: October 24, 2015, 01:40:46 pm »
svk,
The last GUI (BitShares-light_2.15.288) is so bad in the light wallet...I had to downgrade... seriously the ability to actual click on the 'update your position' is kind of important- so it kind have to fit in the window...if you do want to do something with it ,that is.


PS
Anybody has any idea if the idiotic browser the light client is running inside of , has anything that  can do ctrl+/-?

I've never actually tried the light client myself, Valentine's the one handling that. I'll try to install it this weekend and see if I can make some improvements. I'm guessing I should test it on a low resolution screen?
1366 x 768 would be perfect for me. :(

tonyk, I'm aware of too large fonts Windows issue - will address this asap.

93
@jakub, checkout most recent version https://bitshares.openledger.info/#/markets - svk has fixed some of the issues today

94
Technical Support / Re: Loading stalls for OpenLedger web wallet
« on: October 23, 2015, 12:09:16 pm »
When you see the Loading... Message can you open a console and see if there is any error?

I have heard of the backup download problem on Safari. I wonder did it download and just not notify you and you might find it saved on your computer?
I opened the error console and it showed this (I could paste more error detail, but as a non-techie, I'd have to be advised on how secure that is):

Syntax Error: Unexpected token ' , '
XMLHttpRequest cannot load safari-extension://com.evernote.safari..../en_us/messages.json
XMLHttpRequest cannot load safari-extension://com.evernote.safari..../en/messages.json

2 other things, this loaded fine in safari earlier in the week, so something is different between then and now. It also does successfully load on my Chrome browser, which I'd be happy to use going forward, but given I created the wallet and imported the keys in Safari originally, can I do this?

Regarding the key backup subsequently attempted from OpenLedger, I searched all my recent files and can't find anything resembling a new key file. What would it be called?

Thanks.

Looks like Safari Evernote plugin has something to do with your issue. Do you remember if you were installing Evernote recently?
If you are planning to use Chrome I would suggest you to re-import your 0.x keys into Chrome's wallet.

 

95
"сколько раз сюда ходиу, было на много лучше, а сейчас как то не удалось"  :D если серьезно, на мой взгляд была задача в первую очередь запустить платформу, а потом все остальное, вот и реакция в виде такой цены, но кто понимает смысл платформы тот покупает не смотря ни на что...
Совершенно верно - BitShares это платформа, я вобще не понимаю смысла кошелька (в том понимании, например как кошелек в биткоине). Вон эфир сколько уже живет без гуевого клиента и ничего :)

96
General Discussion / Re: Open Ledger Market Pages Updated
« on: October 20, 2015, 07:38:00 pm »
Interesting.  everything has been slow since I imported my keys/accounts.

I closed and relaunch browser and now everything is gone.  No accounts, no market page


Xeldal, looks like for some reason your browser has reseted its cache. I would suggest you to use light wallet instead of a browser. You can either re-import your 0.x wallet keys or use backup if you created it in web wallet.

97
Спасибо, получилось. Жаль, что к этому моменту монеты заметно подешевели.
Ну это я думаю временное явление :)
Как кстати впечатления от новой версии?

98
Technical Support / Re: Bitshares OS X Wallet not able to connect
« on: October 20, 2015, 01:40:52 pm »
wmbutler,
I think there is some firewall that is blocking your web socket connections, not sure we can do anything about this.
286 refers to the graphene toolkit release, 288 is GUI version (we use day of the year as patch version )

99
Добрый день.
Подскажите, как найти потерянную транзакцию?
Отправлял  8,996.06076 BTS из своего кошелька djandre77 пользователю  poloniexwallet MEMO 3ffbd29ad1d38319
(+0.5 BTS fee) 16 october 2015 г., 18:22:08 GMT+6 монеты на биржу так и не пришли, говорят - спросите в сообществе bitshares.
Что говорит кошелек (версия):
Транзакция #bcd4ff9c
Блок #3829865 , Транзакция #0 , Следующая #1
Временная метка: 16.10.2015 18:25
Операции
Withdraw 899656076 satoshi amount of asset
 Deposit 8,996.06076 BTS

Здесь есть представители сообщества bitshares?

Andre,
13 октября после блока 3826176 BitShares переехала на версию 2.0 и новый блокчейн, ваша транзакция была сделана в старой версии кошелька и на старом блокчейне.
Вам совершенно неочем беспокоится - все деньги на месте, просто нужно экпортировать ключики из старой версии в новую.
Вот здесь подробная инструкция
http://docs.bitshares.eu/migration/howto-exporting-wallet.html
http://docs.bitshares.eu/migration/howto-exporting-wallet.html

100
General Discussion / Re: Core dev respond to GUI criticism
« on: October 18, 2015, 02:29:52 pm »
Great idea incomming commander: Make a button 'short USD with safe setting'

I don't understand the collateral and other shorting things. A setting with a 90% chance that I can get little richer in the future would be good.

I am sure many people are not talented in thinking about such complex thing.

Let's try to make a dummy button.

Good idea, we thought about this too. When we were planning Graphene one of the features we wanted to have was "market orders" - user specifies only amount and buy or sell order executes at current market price. So in Graphene order can be executed in the same block it's placed and also it can be marked as "fill or kill" - this makes market orders much easier to implement. Now we only need to add simple buy/sell/short form to the GUI where user can specify amount, click Place button, agree with price and confirm.


101
General Discussion / Core dev respond to GUI criticism
« on: October 17, 2015, 05:11:00 pm »
Initially I was planning to respond with this in one of the GUI criticism topics, but it grew pretty large, so I decided it deserves a separate forum thread. So in response of my post I would like to see your thoughts on "fundamental issue” I mentioned below as well as your questions about our future plans and your ideas and suggestions. (Please note, that when you say “NXT/Crypti/you-name-it-wallet is better/cleaner” or Poloniex exchange is better - it’s not really helpful). I think most helpful UX feedback comes in the following form: “As <experienced (or not experienced) forex trader> (or <paypal user>, etc) I do <some operation> very frequently so if would be very helpful you put <this data> at <the bottom>; or you put <this button> on <top of the page>; or you remove <something> because it bloats UI”.

I think the most fundamental issue is that half of the community would like to see BitShares GUI as exchange, the other half as cryptocurrency wallet with built-in exchange. And in general - there is no consensus on what BitShares is.

While we were planning the GUI we decided to try to satisfy both points of view and build reference wallet that would be easy to customize, so the exchanges would turn it into exchange UIs, wallet service providers into a simple wallet suitable for general public.
The idea behind BitShares 2.0 was to create "platform" and provide some basic infrastructure, like blockchain, close to real-time API, reference wallet, referral program and let third parties build and monetize their own solutions built on this platform.
Another goal for the BitShares 2.0 GUI was to have all the functionality of 0.x wallet, so the current users wouldn't feel 2.0 as downgrade. Even if 2.0 GUI may feel not accomplished but it serves both goals well - it gives you a taste of Graphene capabilities and performance and also it's far superior to 0.x wallet.

And we are not going to stop here - there are big plans: the help system is under heavy development, just take a look at Membership page to have some idea - we are planning to add detailed help content to almost every page, also there will be "app tour" for new users. React native mobile GUI for iOS and Android should be out in a couple of months, all the backend and keys management are already in place; more gateways support is on the way; most of the blockchain features like proposed transactions; blinded transfers; privatized bit assets - all these are planned to be implemented before the end of year. The architecture we’ve chosen for 2.0 GUI has proven itself to be very effective and we are really getting up to speed (remember on one of the mumble sessions BM said this is the future of web development), and take a look at number of commits to graphene-ui repo - it's close to 2k already - twice as much as toolkit has got being longer under development.

And all these despite the fact that core developers were struggling for months to feed their families due to BTS price decline and dev fund melt down; and the idea to give up and return back to real-world salaries looked very attractive, btw community support was very helpful during that time, so I want to thank all you guys for staying here, even those with negative feedback, if you are still on the forum and you are testing software - this means that you still believe in BitShares and this really gives us the hope.

102
Technical Support / Re: Bitshares OS X Wallet not able to connect
« on: October 16, 2015, 01:00:52 am »
Please upgrade to version 2.15.288 (find it here https://github.com/bitshares/bitshares-2/releases/tag/v2.15.286) and use this connection string wss://bitshares.openledger.info/ws

103
Technical Support / Re: Error during the import 0.9.3c to 2.0
« on: October 14, 2015, 02:28:35 pm »
Looks like it couldn't connect to the server via WebSocket protocol.
Make sure your firewall is not blocking WebSocket connections to remote port 443.
 

104
General Discussion / Re: Graphene GUI testing and feedback
« on: October 10, 2015, 02:04:57 pm »
The following Firefox error:
Quote
The connection to  .. was interrupted while the page was loading
Is know issue, it doesn't affect any functionality.

Testnet api connection string is wss://graphene.bitshares.org/ws, trailing slash is not necessary.

105
General Discussion / Re: Graphene GUI testing and feedback
« on: October 08, 2015, 02:55:50 pm »
Help files are in help/ folder of graphene-ui repo. They are static files so no need to fetch them on the fly.
We are using markdown (.md files) so it's very easy to edit them - you don't even need to know html. Also github shows .md files prerendered - this makes it very easy to browse and edit them. Here is an example https://github.com/cryptonomex/graphene-ui/blob/master/help/en/index.md
I'm very doubtful that external translation tool like Transifex would be helpful here - it just adds complexity..

Pages: 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 ... 20