system-glitch / solidity-ide Goto Github PK

Description

ABI and compiled contracts should be saved to the file system, ideally in a build folder.

Benefits

Deploying the contract in production or on a testnet would be easier and wouldn't require the use of another tool.

Possible drawbacks

Potential conflict with user-created build directory. This directory should be ignored in the compilation process.

Additional information

node_modules folder should be ignored too.

Sometimes the output section of the newly selected tab after closing another tab takes the value of the closed tab. This must be a bug on ace's end.

Proposed solution: use a single ace editor for outputs. There is no need to have an separated output section for each contract.

node_modules/ace-mode-solidity/test_browserify/data/Block.sol:2:1: ParserError: Expected pragma, import directive or contract/interface/library definition. {} ^

Description

Embark is a framework for DApps development. Using embark is easy to create a React DApp, using IPFS/Swarm, Whsiper and Ethereum.

Would be nice if the IDE could recognize the settings on the Embark Project, by locating the .embark folder, and provide the contracts interface by reading the chains.json config.
So when I type embark run (or could be a play button in your ide) the IDE would also connect and render the interface of same contracts deployed by embark.

Comparison

Other frameworks don`'t provide decentralized storage and decentralized messenging

Benefits

A integrated framework for DApp development makes easier to do tedious tasks, such as compiling for IPFS, setting up private networks, integrating ENS,

Possible drawbacks

Might not be interesting to all devs.

Additional information

It would be possible to integrate embark only for developers that want.
Embark itself is easy to integrate to your IDE, by simply setting the same used settings in your IDE, but it don't recognize contracts deployed by embark.

Branch: v2.0
Environment: Local on OSX
Reproduces: Always

I can't zoom on the code editor when i'm scrolling

How it occurred

1. Run IDE
2. Create a .sol file
3. Write something
4. Try to scroll

Expected result:
A better view of the code editor

Description

I normally have my own ganache that I have running. Can I connect to this instead of spawning a new one?

Description

Branch: master
Commit: 7dec7de
Environment: All
Reproduces: always

import directives don't work because the import callback is not defined in solc-server.

When a VM Exception is returned when testing contract functions, the error message is not displayed in the output section.

All events in the global event bus are not unbound on destroy, creating memory leaks. (Main editor should also be destroyed).

Description

Branch: develop
Commit: 2b3cdac
Environment: Windows
Reproduces: always

Directory creation fails when creating a file at project's root since it shouldn't run at all.

How it occurred

1. Run the IDE
2. Create a file from the browser panel (not containing any slash)
3. Couldn't create file: ENOENT: no such file or directory, mkdir

Description

I tried to deploy a contract that requires an argument in its constructor, but the feature is not implemented.

Benefits

The ability to deploy non-empty constructor contracts.

Description

The tool cannot really be used offline currently as fonts are fetched from google fonts.

Benefits

Locally stored fonts would allow for proper offline usage.

Possible drawbacks

Overall heavier package.

The output section should be replicated for each tab instead of using the same ace editor.

Description

For integration purposes, if we can run npm run server with file or directory, and for this directory solidity files to be automatically loaded, this would allow better user experience for the users.

Description

When multiple contracts are opened in the IDE, clicking on the deploy button automatically deploys all of the contracts.

Benefits

Being able to deploy contracts one by one would be practical, especially when we work with contracts that interact between them.

Description

Related to #6 , If I am able to load a directory of solidity files, and I make changes to it, I would love for these changes to be propagated to the actual file on the file system.