@ -39,7 +39,7 @@ Validating a transaction take several seconds. During this time, the GUI shows i
and the transaction is added to the log (see :doc:`../terminal`)
Instance List
--------------
-------------
This section contains a list of instances to interact with.
@ -53,3 +53,199 @@ Several cases apply:
For more information about Solidity modifier, see `Solidity modifier <http://solidity.readthedocs.io/en/develop/miscellaneous.html?highlight=pure#modifiers>`_ .
If a function requires input parameters, it is required to specify them.
USING ABI
---------
Using ``Create`` or ``At Address`` is a classic use case of Remix. It is possible though to interact with a contract by using its ABI. The ABI is a JSON array which describe its interface.
To interact with a contract using the ABI, create a new file in Remix with extension ``*.abi`` and copy the ABI content to it.
Then in the input next to ``At Address``, put the Address of the contract you want to interact with. Click on ``At Address``,
a new "connection" with the contract will popup below.
USING THE RECORDER
------------------
The Recorder allows to save a bunch of transactions in a JSON file and rerun them later either in the same environment or in another.
Saving to JSON allows to easily check the transaction list, tweak input parameters, change linked library, etc...
We can find many use cases for the recorder, for instance:
- After having coded and tested contracts in a constrained environment (like the JavaScript VM), it could be interesting to redeploy them easily in a more persisted environment (like a Geth node) in order to check whether everything behaves normally in a classic environment.
- Deploying contract does often require more than creating one transaction.
- Working in a dev environment does often require to setup the state in a first place.
..image:: images/remix_recorder.png
Saving a record ends up with the creation of this type of content (see below):
In that specific record, 3 transactions are executed:
The first corresponds to the deployment of the lib ``testLib``.
The second corresponds to the deployment of the contract ``test``, the first parameter of the constructor is set to 11.
That contract depends on a library. The linkage is done using the property ``linkReferences``.
In that case we use the addres of the previously created library : ``created{1512830014773}``. the number is
the id (timestamp) of the transaction that leads to the creation of the library.
The third parameter corresponds to the call to te function ``set`` of the contract ``test`` (the property to is set to: ``created{1512830015080}``) . Input parameters are ``1`` and ``0xca35b7d915458ef540ade6068dfe2f44e8fa733c``
all these transactions are created using the value of the accounts ``account{0}``.