You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,7 @@
2
2
[](https://gitter.im/iurimatias/embark-framework?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
*[Libraries and APIs available](#libraries-and-languages-available)
26
28
*[Using and Configuring Contracts](#dapp-structure)
27
29
*[EmbarkJS](#embarkjs)
28
30
*[EmbarkJS - Storage (IPFS)](#embarkjs---storage)
@@ -75,7 +77,7 @@ Alternatively, to use an ethereum rpc simulator simply run:
75
77
$ embark simulator
76
78
```
77
79
78
-
By default embark blockchain will mine a minimum amount of ether and will only mine when new transactions come in. This is quite usefull to keep a low CPU. The option can be configured at config/blockchain.json
80
+
By default embark blockchain will mine a minimum amount of ether and will only mine when new transactions come in. This is quite usefull to keep a low CPU. The option can be configured at ```config/blockchain.json```. Note that running a real node requires at least 2GB of free ram, please take this into account if running it in a VM.
79
81
80
82
Then, in another command line:
81
83
@@ -131,6 +133,16 @@ DApp Structure
131
133
132
134
Solidity/Serpent files in the contracts directory will automatically be deployed with embark run. Changes in any files will automatically be reflected in app, changes to contracts will result in a redeployment and update of their JS Bindings
133
135
136
+
Libraries and languages available
137
+
======
138
+
139
+
Embark can build and deploy contracts coded in Solidity or Serpent. It will make them available on the client side using EmbarkJS and Web3.js.
140
+
141
+
Further documentation for these can be found below:
142
+
143
+
* Smart Contracts: [Solidity](https://solidity.readthedocs.io/en/develop/) and [Serpent](https://github.com/ethereum/wiki/wiki/Serpent)
144
+
* Client Side: [Web3.js](https://github.com/ethereum/wiki/wiki/JavaScript-API) and [EmbarkJS](#embarkjs)
145
+
134
146
Using Contracts
135
147
======
136
148
Embark will automatically take care of deployment for you and set all needed JS bindings. For example, the contract below:
Copy file name to clipboardExpand all lines: js/build/embark.bundle.js
+5-74Lines changed: 5 additions & 74 deletions
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ var EmbarkJS =
76
76
varself=this;
77
77
varcontractParams;
78
78
79
-
contractParams=args;
79
+
contractParams=args||[];
80
80
81
81
contractParams.push({
82
82
from: this.web3.eth.accounts[0],
@@ -5907,83 +5907,14 @@ var EmbarkJS =
5907
5907
/***/function(module,exports){
5908
5908
5909
5909
// shim for using process in browser
5910
-
varprocess=module.exports={};
5911
-
5912
-
// cached from whatever global is present so that test runners that stub it
5913
-
// don't break things. But we need to wrap it in a try catch in case it is
5914
-
// wrapped in strict mode code which doesn't define any globals. It's inside a
5915
-
// function because try/catches deoptimize in certain engines.
5916
5910
5917
-
varcachedSetTimeout;
5918
-
varcachedClearTimeout;
5919
-
5920
-
(function(){
5921
-
try{
5922
-
cachedSetTimeout=setTimeout;
5923
-
}catch(e){
5924
-
cachedSetTimeout=function(){
5925
-
thrownewError('setTimeout is not defined');
5926
-
}
5927
-
}
5928
-
try{
5929
-
cachedClearTimeout=clearTimeout;
5930
-
}catch(e){
5931
-
cachedClearTimeout=function(){
5932
-
thrownewError('clearTimeout is not defined');
5933
-
}
5934
-
}
5935
-
}())
5936
-
functionrunTimeout(fun){
5937
-
if(cachedSetTimeout===setTimeout){
5938
-
//normal enviroments in sane situations
5939
-
returnsetTimeout(fun,0);
5940
-
}
5941
-
try{
5942
-
// when when somebody has screwed with setTimeout but no I.E. maddness
5943
-
returncachedSetTimeout(fun,0);
5944
-
}catch(e){
5945
-
try{
5946
-
// When we are in I.E. but the script has been evaled so I.E. doesn't trust the global object when called normally
5947
-
returncachedSetTimeout.call(null,fun,0);
5948
-
}catch(e){
5949
-
// same as above but when it's a version of I.E. that must have the global object for 'this', hopfully our context correct otherwise it will throw a global error
5950
-
returncachedSetTimeout.call(this,fun,0);
5951
-
}
5952
-
}
5953
-
5954
-
5955
-
}
5956
-
functionrunClearTimeout(marker){
5957
-
if(cachedClearTimeout===clearTimeout){
5958
-
//normal enviroments in sane situations
5959
-
returnclearTimeout(marker);
5960
-
}
5961
-
try{
5962
-
// when when somebody has screwed with setTimeout but no I.E. maddness
5963
-
returncachedClearTimeout(marker);
5964
-
}catch(e){
5965
-
try{
5966
-
// When we are in I.E. but the script has been evaled so I.E. doesn't trust the global object when called normally
5967
-
returncachedClearTimeout.call(null,marker);
5968
-
}catch(e){
5969
-
// same as above but when it's a version of I.E. that must have the global object for 'this', hopfully our context correct otherwise it will throw a global error.
5970
-
// Some versions of I.E. have different rules for clearTimeout vs setTimeout
0 commit comments