-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kazai777 Builder Journey #80
Comments
Update To begin with, I've integrated the Then I integrated I'm currently working on the automatic addition of packages used in the code but not yet imported, as well as the deletion of imports not used in the code. I think I'll be able to propose a V1 by the end of the week. |
Checking in, as I was looking at the similar Jetbrains' IntelliJ IDE plug-in issue: gnolang/gno#2732 Has the unofficial gno VSCode extension been a useful reference? What needs to be iterated on? https://marketplace.visualstudio.com/items?itemName=harry-hov.gno |
of course, I took a lot of inspiration from this existing plugin by making some modifications for it. I have also made changes to gnopls as mentioned above |
Update ! I've finalized the first version of the intellisense plugin for https://github.com/kazai777/vscode-gno/tree/zak-dev |
Update 🚀 I've finished the first version of the plugin for VSCode, I'm waiting for more information from the team regarding publication on the vscode marketplace. I'm currently finalizing the wiki and README. I'm also thinking about this issue, which aims to integrate |
After @gfanton developed a new version of In the meantime, feel free to try out the plugin and let me know if you encounter any issues or have any suggestions for improvement. https://github.com/gnoverse/vscode-gno/tree/kazai777/v0.1.0 |
For my grant renewal, I talked with @mous1985 about my project idea, which was to create something like O1 : Create a dApp with these different realms and packages I genuinely believe this dApp can add significant value to the Gno ecosystem, as it addresses a real need and demand. Our aim is to develop, maintain, and evolve this dApp over time, with the vision of transforming it into a startup, going beyond just the creation of a single project. The business model is straightforward: it involves taking a small percentage on payments made between project owners and developers, along with other potential revenue streams currently under consideration, making the dApp economically viable. Please feel free to reach out if you have any questions or need further clarification.
|
To continue my adventure with gno, the things I'll be doing over the next few days are :
See you soon, for the next steps. 🚀 |
UpdateIt’s been a while since I last updated my Hackerspace. After spending a lot of time developing the vscode-gno extension, I’m excited to let you know that I’ve finished version V0.1.0 🎉. As you start using it, there will likely be a few minor bugs to fix here and there, but the core functionality is working, and there are quite a few new commands compared to the older version currently on the marketplace. This version of vscode-gno is designed to work with the gnopls LSP, which, for now, has two main issues mentioned in the following issues:
Once these issues are resolved, the experience should be smooth for all vscode-gno users. Over time, I’ll be adding new commands based on the feedback I get and the needs of the community. I also hope that other contributors will join in to add new features and improve the extension. What’s next for me?First, I’m planning to create a homepage: After that, I’d like to work on something to better organize all the packages/realms so that developers can quickly find what they need. This would also include a way to check community reviews for those packages. I’ve shared my idea here: I’ll keep you updated on my progress soon. See you around! ✌️ |
Since my last update, and exchanges with the gno team. I've added a debugger to my vscode extension, which you can find right here. Currently, the Gno debugger does not integrate the DAP protocol. This version implements the debugger using the Bridge Pattern, which works as follows:
This implementation is not fully optimized yet, so I am marking this PR as a draft until the DAP protocol is implemented to ensure an optimal debugger in the extension. The last small problems remaining with the use of the extension come from |
I'm writing this message from a secondary account, as I currently don't have access to my main GitHub account. It will be merged to the main branch very soon, as soon as I regain access to my main GitHub account.
This resolves the problem with documentation links for imports, where packages I'll keep you updated as soon as there's progress. |
Update ! 🚀 I have currently started developing the KONTRIBZ dApp. It aims to have a project and bounties manager that is 100% onchain. I had already proposed this idea a few months ago, but since I had to finish the first version of the VSCode plugin as a priority, I hadn't started it yet. You can find all the information about this project and its progress in this journey: The first objective will be to set up the part for organizations, so they can create their profile, assign roles to their contributors (admin, core team, contributor, etc.) and create projects/bounties. I will keep you informed of the different advances of the project. |
Hi everyone,
My name is Zak and I live in France. After doing the student programs, I'm starting my individual grant. I will keep you informed of my progress on my different tasks here.
This week, I'm going to develop an Intellisense VSCode plugin for Gno which has been requested on this issue.
To start with, I analyzed the gnopls code in order to integrate it into my plugin, this took me some time as
gnopls
lacks a bit of documentation 😅.I'm now starting to develop the plugin that will integrate
gnopls
, and I'll keep you posted on my progress here.See you soon 🚀
The text was updated successfully, but these errors were encountered: