mechanism change suggestion

[SpectreMercury]

• Refreshing the page can cause progress to be lost. It is recommended to implement a simple progress-saving mechanism using local storage or session storage.
• There is a significant amount of whitespace in the final two text areas of the CKB basic practical operation.
• Built-in links should ideally open in a new page to avoid the occurrence of problem 1.
• In the CKB basic practical operation, the transaction fee is set to 0 in the first two steps when building a transaction JSON, but it is required in the final step. This may be confusing for beginners and result in errors.
  • A calculator application process (e.g., for calculating capacity) should be added to the process flow to show users how to use and when to use Hex To Decimal.
  • Several hints should be added to guide users on obtaining txhash from live cells and filling in the txHash field in the JSON structure from chainInfo.
• When saving in the final step, if you save twice and make modifications, multiple witnesses will be validated. Otherwise, an error will occur stating that witnesses[1] must be a hex string.

[oriole-pub]

@lee920217 Thank you very much for your feedback. I think your suggestions are very reasonable. As our fundamental course is a fast migration and refactoring for zero2ckb, there are still many shortcomings in the details. As you have described, we will optimize and improve certain features in the next version.

[oriole-pub]

@lee920217 If you are interested in contributing to these optimization efforts, you can directly submit a PR. We will try to discuss certain details through comments or communicate through Discord.

[SpectreMercury]

@lee920217 If you are interested in contributing to these optimization efforts, you can directly submit a PR. We will try to discuss certain details through comments or communicate through Discord.

OK~ no problem