It should be possible to support other languages than JavaScript.

We will have to change the preview to be out of process thought.

Could be an external window or simply use broadway GTK backend https://docs.gtk.org/gtk4/broadway.html

https://jwestman.pages.gitlab.gnome.org/blueprint-compiler/

The UI tab should support Blueprint. We probably want to turn UI - XML into a dropdown to select which format to use and default to xml

Some notes

• LSP Text Document Synchronization
• Blueprint textDocument/x-blueprintcompiler-compile

There are some shortcomings due to the Vala API not having access to the application class, but I think these translations are otherwise fairly faithful to the originals. Feel free to comment and criticize though.

Pasting this snippet, and then pressing "Show Preview Window" in the app crashes unconditionally.

If I run it in the terminal and follow the steps above, the terminal outputs this:

TheEvilSkeleton@TheMainDesktop ~> flatpak run re.sonny.Workbench

(workbench-vala-previewer:23): Adwaita-WARNING **: 12:19:46.876: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.
Couldn't obtain the bus name.

Adwaita-gtk_window_set_titlebar() is not supported for AdwWindow

The demo code used to work as expected. I tried to experiment a bit but ultimately ended by resetting the demo. Now, I cannot launch it anymore. The following message appears in the console:

Failed to register: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown

Started editing a blueprint to get some info on when this happens, but can't figure out where it's happening.

This is about where it started crashing, but it only happens randomly:

using Gtk 4.0;
using Adw 1;

template MainWindow : Adw.ApplicationWindow {
  Box main_box {
    Adw.HeaderBar {
      [title]
      Adw.ViewSwitch  // This is where it starts happening, as I'm typing out ViewSwitcherTitle it keeps randomly crashing after a few characters
    }
  }
}

So that the default is a simpler Gtk/CSS editor

It will look simpler / more accessible to beginner and I expect most application developers use Workbench for GTK/CSS only.

There are 2 use cases for this

1. Allow to render <GtkWindow/> , AdwHeaderBar, ...
2. Allow the user to arrange their workspace however they like (like resizing the preview window and set it to always on top)

In the future it will also enable https://github.com/sonnyp/Workbench/issues/17

The remaining question is do we need some mechanism to "Detach" the preview or should we just rely on <GtkWindow/> being the top level object in UI ?

(workbench-vala-previewer:38): Adwaita-WARNING **: 20:30:23.189: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.

(re.sonny.Workbench:4): GLib-GObject-ERROR **: 20:30:23.327: cannot create instance of abstract (non-instantiatable) type 'GtkWidget'

This is the file I want to edit:

using Gtk 4.0;
using Adw 1;

Widget {
    
}

I am guessing that this syntax is wrong 😅

The shortcut is <Ctrl><Shift>Return.

There were a few issues with our previous XML formatter, the biggest one is that it would behave differently than Blueprint formatter. So I wrote a custom XML formatter that behaves exactly like Blueprint xml_emitter.py .

https://gitlab.gnome.org/jwestman/blueprint-compiler/-/blob/59283a76adc8d270ff5f67b630b7dfa905ec34a9/blueprintcompiler/xml_emitter.py

@melix99 could you test this quickly? Building this branch in GNOME Builder should work just fine.

Feel free to review as well but that's not required .

Hey there, It appears that the preview is broken on flatpak: It's just a white box without any content. There is one error in the console: Promise timed out after 1000 milliseconds Why is this happening? Flatpak --version: 1.12.7, Workbench version: 42.0

• Make a mistake in the blueprint code (e.g. mis-spell widget name or property name)
• The error is now underlined in red
• Hover over the underlined code
• A popup with the error information appears, and then disappears instantly, making the error impossible to read

The Platform Tools module found in the Library says, at the bottom of its rendered output:

As with most GTK applications, you can use the keyboard shortcut to open the Inspector and select an object to see what it is made of.

Ctrl+Shift+I

Except... Ctrl+Shift+I doesn't open the inspector. On my Fedora 36 system, at least, a Ctrl+Shift+I in Nautilus (for example) results in a "Select All" being performed in the focused window.

Ctrl+Shift+D launches the GTK Inspector.

Edit: (In fact, Ctrl+Shift+I doesn't even open the inspector in Workbench. Even there, the only working shortcut AFAICT is Ctrl+Shift+D.)

I've just recently started learning GTK and Workbench has been great for experimenting with UIs but my workflow is being hampered due to the lack of vim support.

Other GTK4 applications such as Builder, Text Editor already have vim support, so it'd be great if Workbench could have support for it as well.

If I'm not wrong, I think GtkSourceView already has Vim emulation support, so I'd at least hope that it'd not be too complicated to add support for vim. I don't know much about GTK yet, so that's all the info I can provide regarding possible implementations. Thanks!

This is blocked by https://gitlab.gnome.org/GNOME/gjs/-/issues/72

https://gitlab.gnome.org/GNOME/gjs/-/issues/255 is a better explanation of the problem