Gregory's ServerIf you use, like or dislike Workbench, please let me know.
I'm always happy to get feedback and interested in understanding how Workbench can help you learn and build.
|
5 comments
 @sonny I think it's a great idea for getting started and prototyping stuff, but as a C developer I don't want write python and then convert it to C to actually use it :) I'm not sure how workbench works internally but maybe something like https://bellard.org/tcc/ could bring C into the mix? But then of course I'd want my custom libraries and widgets and stuff too which would make things even more confusing. At any rate, just some random ramblings ;)  @grimmy C support could be added pretty easily. And would be a good addition for the Library which is sort of a Rosetta Stone for GNOME. Importing libraries and stuff is probably out of scope but hopefully we'll bring the live preview to GNOME Builder. Then it's just a matter of copy pasting C examples there. Thanks for the feedback @sonny I need to give GNOME Builder another try soon. Last time I was struggling with difference from sublime text and found myself having to write a number of plugins which is of course keeping me from working on the stuff I should be working on. The one I remember struggling with the most was trying to add mercurial support and not being able to follow through the git plugin at all. That said this was like 2 years ago or so. GNOME Builder is seriously impressive but yeah it's hard to keep up with VSCode and Sublime teams. It's just a matter of time though. Regardless, I believe we will be able to bring the live preview to any code editor / IDE (as long as the preview happens in a separate window). There is a GSoC project towards that https://gsoc.gnome.org/2024/#improve-workbench-previewer |
Also - GNOME 46 release notes for developers has a section on the changes between Workbench 45 and 46.
Very proud of what we accomplished within 6 months or (volunteer!) work.
https://release.gnome.org/46/developers/index.html#workbench