Page 1 of 1

XUiDesigner v0.4 released

Posted: Thu Jul 07, 2022 12:34 pm
by tramp
I'm pleased to announce the release v0.4 of XUiDesigner

A easy to use GUI generator/designer tool to create X11 based UI's for LV2 plugins.

Inspired by Glade and QT Designer

XUiDesigner allow to generate alternative UI's for existing LV2 plugins which could be installed and used parallel to the existing ones.

It allow as well to create full LV2 plugin bundles from scratch, were only the dsp part needs to be done.

With this version, it allow to generate LV2 plugin bundles from faust (*.dsp) files. Those could be simply drop on the XUiDesigner interface and XUiDesigner will create the UI for it. The UI could be reworked when needed (reorder the controls, implement colours or images, . . .) . Then the complete Bundle could be saved. All what needs to be done then is run make && make install on the bundle, to get the LV2 plug into the preferred LV2 host.

Still this is in the beta stage, so there may be come changes which are not backward compatible, but the generated LV2 bundles are all fully working.


Project page:

https://github.com/brummer10/XUiDesigner

release:

https://github.com/brummer10/XUiDesigne ... 0.4.tar.gz

regards

hermann

Re: XUiDesigner v0.4 released

Posted: Fri Jul 08, 2022 3:03 pm
by scott.thomason
Bingo. Exactly what I had hoped for when we were discussing the LV2 vs. CLAP post earlier. I wish the project great success.

Re: XUiDesigner v0.4 released

Posted: Sun Jul 10, 2022 6:22 pm
by tramp
Since the release there is already going some work into it. Beside some Bug fixes I've implement a ttl viewer, so now you could view how the ttl file looks ( what it contain) while you develop your plugin. That may help a lot to get some understanding how the LV2 turtle syntax works. (I hope) :)

Re: XUiDesigner v0.4 released

Posted: Tue Jul 12, 2022 4:24 pm
by tramp
So now I've implemented something I called "global image support", that means, when you enable this feature, all controllers of the same type will use by default the same underlying image. So you don't need any-more load a image for every single controller, just one per type and all following generations will use them. As long as you disable that, or load a other controller image.