ChainIDE-English
  • 1. ChainIDE Introduction
  • 2. ChainIDE Modules
    • 2.1. File System
    • 2.2. Editor
    • 2.3. File Preview
    • 2.4. Logger
    • 2.5. Compile
    • 2.6. Deployment and Interaction
    • 2.7. Plug-in System Module
      • 2.7.1 ChainIDE Debugger
      • 2.7.2. ChainIDE Flattener Plugin
      • 2.7.3. ChainIDE Scan Verifier
    • 2.8. Functions at Bottom Part of ChainIDE
  • 3. ChainIDE - Loading Your Work
  • 4. ChainIDE - Saving Your Work
  • 5. ChainIDE - Port Forwarding
  • ChainIDE
    • 1. Ethereum IDE
      • 1. Ethereum IDE Environment Configuration
      • 2. How to Use Ethereum IDE?
      • 3. Using Hardhat
      • 4. Using Ganache v7
      • 5. Using Truffle
    • 2. BNB Chain IDE
      • 1. BNB Chain IDE Environment Configuration
      • 2. How to Use BNB Chain IDE
      • 3. Using Hardhat
      • 4. Using Ganache v7
      • 5. Using Truffle
    • 3. Conflux IDE
      • 1. Conflux IDE Environment Configuration
      • 2. How to Use Conflux IDE
      • 3. Using Hardhat
      • 4. Using Ganache v7
      • 5. Using Truffle
      • 5. Using Conflux-Truffle
    • 4. Internet Computer IDE
      • 1. How to Use Internet Computer IDE
    • 5. Nervos IDE
      • 1. Nervos IDE Environment Configuration
      • 2. How to use Nervos IDE
      • 3. Using Hardhat
      • 4. Using Ganache v7
    • 6. Polygon IDE
      • 1. Polygon IDE Environment Configuration
      • 2. How to use Polygon IDE
      • 3. Using Hardhat
      • 4. Using Ganache v7
      • 5. Using Truffle
    • 7. Flow IDE
      • Learn how to use Flow IDE to develop dApps
    • 8. FISCO BCOS IDE
      • 1. FISCO BCOS Environment Configuration
      • 2. How to use FISCO BCOS IDE
    • 9. Sui IDE
      • 1. Sui Environment Configuration
      • 2. How to use Sui IDE
    • 10. Aptos IDE
      • 1. Aptos IDE Usage Process
      • 2. How to use Aptos IDE
    • 11. XDC IDE
      • 1. XDC IDE Environment Configuration
      • 2. How to Use XDC IDE
      • 3. Using Hardhat
      • 4. Using Ganache v7
      • 5. Using Truffle
    • 12. Astar IDE
      • 1. Astar Environment Configuration
      • 2. How to Use Astar EVM IDE
      • 3. How to Use Astar WASM IDE
    • 13. IRISnet IDE
      • 1. IRISnet Environment Configuration
      • 2. How to Use IRISnet EVM IDE
      • 3. How to Use IRISnet Native IDE
    • 14. Arbitrum IDE
      • 1. Arbitrum IDE Environment Configuration
      • 2. How to Use Arbitrum IDE
      • 3. Using Hardhat
      • 4. Using Ganache v7
      • 5. Using Truffle
    • 15. Starknet IDE
      • 1. Starknet IDE Environment Configuration
      • 2. How to Use Starknet IDE
    • 16. Mina IDE
      • 1. Mina IDE Environment Configuration
      • 2. How to Use Mina IDE
Powered by GitBook
On this page

Was this helpful?

4. ChainIDE - Saving Your Work

ChainIDE allows you to save/load your work to/from Github.

Previous3. ChainIDE - Loading Your WorkNext5. ChainIDE - Port Forwarding

Last updated 1 year ago

Was this helpful?

Saving to ChainIDE

ChainIDE now allows you to save your work. To save your work, select the following menu options.

Once you have completed your project, you need to sign in to save your work using ChainIDE, because sign-in information would be used against recording data and access the data from any other system for later usage. The sign-in option is available at the top-right, you can simply sign in using the Github profile.

Once the user sign-in, project work can be shown in the dashboard, to save it permanently as a template, a user need to save it.

There are three mentioned below options are available, once you create a project.

  1. Open: This option allows a user to open the smart contract for editing purposes.

  2. Delete: This option lets a user delete a project if the user wants to delete all the projects at once, then the user needs to select the "select all" option, and all the projects would be selected.

  3. Save: This option allows a user to save the project as a private template and provides access from any device.

To save the project as a private template, a user needs to provide a template name and description. Template type would be automatically selected as private because only the admin has the access to create public templates. Once you fill in all the required information and click "Ok", the project would be saved as a private template.

Once you save the projects as a private template, all projects can be found under the private template dashboard, user can make changes to these templates, edit the template information, and can delete also.

To make changes to the private templates, a user needs to go to "Private Template Manage" as shown in the figure below.

Once a user selects "Private Templates Manager", the user can edit, delete, and change the template name and description. As shown in the figure below, if a user wants to open the template, needs to select option 1, if want to delete the template, needs to select option 2, and if want to rename the template name, its description, or version, then need to select option 3.