Neoray 2.0 has been released. This is a major update to Neoray. We updated the interface, usage flow, and contract invocation methods, greatly reducing the learning threshold for contract debugging and making it easier for newcomers to get started. The new version of the contract debugging process is still: compile code — deploy contract — call contract — debug contract. Neoray users can get started with it after a short while.

Start with the selecting code

When developers use the new version of Neoray, they first need to select the contract code that needs to be debugged. In Neoray 2.0 we support direct reading of the code files on the computer and saving the contract code locally. You can write the contract code in visual studio and import the code directly into Neoray for compilation and debugging. Of course, you can also edit the code directly in Neoray, and now the new editor will prompt you when you enter the keyword. The code you write will be saved in your browser cache, and you can continue to edit the previous code the next time you open Neoray.

After selecting the code, you can deploy and debug the contract.

debugging

In the olde version of Neoray, deploying contracts, calling contracts, and debugging contracts were three separate modules, each with separate pages and functionality. Developers will face three questions when they enter the new page process: What was I doing? What am I doing? What am I going to do next?

In Neoray 2.0, after the code is selected, the contract code being debugged can be seen throughout the debugging process, and all subsequent operations are performed for the current code. From the top to the bottom of the menu bar on the left is compile code, deploy contract, send transaction, debug transaction, you only need to execute in order.

In Neoray 2.0 we still keep the functionality of debugging assistance. Developers can send problematic contract hashes or transaction IDs to others, who can load your contract code and transactions with these parameters to assist you in debugging.

Operational status output

Unlike normal programs, debugging contracts involves sending transactions on the blockchain, and transaction confirmation on the blockchain takes time, so feedback on user operations and results on Neoray is asynchronous. We have added an output window to the interface, and Neoray will display the results in the output window when we receive the result of the transaction. Developers can view all recent operational records in the output window to help identify debugging issues.

Return to V1.0

In Neoray 2.0, we hand over the functionality related to packaging and sending transactions to the Teemo wallet to increase the stability of Neoray. Since Teemo Wallet only supports chrome browsers for a while, developers using other browsers are temporarily unable to use Neoray 2.0. We place a button that returns to V1.0 in the lower left of the compiler and you can click to jump to the old version of Neoray. The old version comes with the functionality to package and send transactions without using the Teemo wallet.

The NEO 3.0 TestNet has just been released recently. After the Teemo wallet completes the NEO 3.0 adaptation, Neoray will also follow up. The cost of publishing contracts and transactions will be greatly reduced. The new version of Neoray is https://neoray.nel.group

If you have any questions or problems during use, please feel free to contact us.