Replies: 1 comment 1 reply
|
Hi @otykier! I'm primarily a .NET dev, and wanted to write the whole IDE in .NET. I was using a NuGet package wrapping Monaco for Blazor, but it didn't have wrappers for everything I would need for e.g. syntax highlighting, completions etc. I would have to write more JSInterop myself, which I did not want to do. I also personally dislike JavaScript with a passion. At the same time, I didn't want to re-invent the wheel regarding an editor, and I was aware of Godot's CodeEdit node, which could do everything I wanted. That was basically my thought process, hope that helps :) |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I’m starting a new cross-platform project where I need a .NET backend and a web-based frontend, and I was considering Photino.NET as a lightweight way of scaffolding that. My app will also have a code editor front and center, so I was hoping to use Monaco for that. I came across SharpIDE (very impressive work, btw!) but noticed the deprecation notice on the Photino version and was wondering if you would care to elaborate on why you decided to move away from Photino for this project? AFAIK, you’re not restricted to razor/blazor but can put any arbitrary html/css/js/ts including React on the frontend, so it’s not clear to me what obstacles you were facing with Monaco in this context. I don’t need a detailed response - just if you can remember any specific challenges that arose, then I can easily Claude my way to a more elaborate explanation.
Thank you kindly in advance.
All reactions