https://github.com/EOSIO/eos/wiki
*EOS REST API MetaList:
https://t1api.eos.io/v1/docs/#api-Account-GetAccount
Web Wallet:
Dev Testnet Account Signup:
https://docs.google.com/forms/d/e/1FAIpQLSel3HVFb22zYaAJfUtu_IzFgIJ4OATb0jQ3H2FV-HbwnJ090g/viewform
Basic Github Tutorial:
https://github.com/EOSIO/eos/blob/master/README.md
More good EOSIO code Documentation:
https://eosio.github.io/eos/modules.htmlhttps://steemit.com/eos/@dan/does-freedom-require-radical-transparency-or-radical-privacy
https://steemit.com/eos/@dan/inter-blockchain-communication-via-merkle-proofs-with-eos-io
https://steemit.com/eos/@eosio/eos-io-dawn-2-0-released-and-development-update
https://steemit.com/eos/@dan/eos-example-exchange-contract-and-benefits-of-c
https://steemit.com/eos/@dantheman/web-assembly-on-eos-50-000-transfers-per-second
https://steemit.com/@dantheman
If anyone is having trouble developing with a foreign library without a dedicated compile environment or are unfamiliar with C/C++, here are a few tips. The team points out their favorite method here, “Caveman” debugging. Coming from an embedded background, this is all we ever have to work with. So in case the concept is foreign to you, the basic idea is to make a simple debug macro, something like:
#def DEBUG_ON – toggle debug here, can also add as a flag in a make/header file
#ifdef DEBUG_ON
…
TRACE_IN MACROs – put the trace-ins at beginning of function calls, would looks something like printf("%d", __LINE__, __FILE__);
TRACE_OUT’s MACROs – basically same as trace in, end of function calls
…
These debug tactics in conjunction with your eclipse set up should put you in a very good dev environment. Another decent strategy is to wrap all your debug print’s in #ifdef’s, although it makes the code quite ugly. But it does allow you to toggle them on/off at will, and easily strip them out before production. Also, be sure to make use of asserts in failure cases!
Here is a decent reference to “line control.” I have not yet tried this in an EOS implementation, but I should get there in a week or so, so I will report back my findings:
https://gcc.gnu.org/onlinedocs/cpp/Line-Control.html
@tokenika have been putting out some awesome stuff the past few months, be sure to check them out!
https://steemit.com/eos/@tokenika/using-eclipse-ide-for-eos-smart-contracts
https://steemit.com/eos/@tokenika/compiling-eos-smart-contracts-in-eclipse-using-llvm-clang
PPT and Notes from the above presentation:
https://github.com/tokenika/tokenika.github.io/blob/master/WarsawBlock(8).pptx
https://github.com/tokenika/tokenika.github.io/blob/master/WarsawBlock(8).docx
