|
1 | 1 | # XUiDesigner |
2 | | -Very early draft of a X11 LV2 GUI design tool |
| 2 | +A WYSIWYG LV2 X11UI GUI creator tool |
3 | 3 |
|
4 | 4 |  |
5 | 5 |
|
6 | 6 | ## Goal |
7 | | -Provide a easy to use GUI generator tool to create UI's for LV2 plugins. |
| 7 | +Provide a easy to use GUI generator tool to create X11 UI's for LV2 plugins. |
8 | 8 | Currently only libxputty is supported, but the generated GUI C file could be used probably with other |
9 | 9 | widget tool-kits as well, just a wrapper file is needed to translate the generated file to the needs of a toolkit. |
10 | 10 |
|
11 | 11 | ## Currently state |
12 | | -XUiDesigner could parse the ttl file from a selected plugin and generate the needed controller widgets. |
| 12 | +XUiDesigner parse the ttl file from a selected plugin and generate the needed controller widgets. |
13 | 13 | Supported been the usual lv2:port parameter and as well the new atom based LV2_PATCH__writable and LV2_PATCH__readable |
14 | 14 | so as LV2_ATOM__Path. |
15 | 15 | XUiDesigner use the environment variable LV2_PATH to scan for plugins when no path is given with the |
16 | 16 | -p command-line parameter. |
17 | 17 | So you could easily create a GUI for a existing plugin. |
| 18 | +A integrated Color chooser allow to create a Color theme for your GUI. |
18 | 19 | The created GUI could be saved as UI-Bundle, which then could be build (just make) and installed (just make install) |
19 | 20 | to replace or provide a new GUI for the plugin. |
20 | 21 |
|
21 | | -Additional control widgets could be created and moved freely around in the top Window, or, |
22 | | -a grid could be displayed and widgets could snap to grid (left, right, Center) to order them easily. |
| 22 | +You could as well create a LV2 plugin from scratch and save it as Full Plugin-Bundle to a selected location. |
| 23 | +The project settings window allow to setup the specs (like Author name, URI, Audio/Midi ports, etc.) for your plugin |
| 24 | +XUIDesigner save the bundle in a git repository format, contain a working LV2 plugin with all needed resources |
| 25 | +(ttl files, converted C files from used images, etc.) and build files to build, install and run the new generated plugin. |
| 26 | +All you need to do to finish your plug is to implement your DSP part. |
| 27 | + |
| 28 | +Control widgets could be created and moved/resized freely around in the top Window. |
| 29 | +A grid could be displayed and widgets could snap to grid (left, right, Center) to order them easily. |
23 | 30 | Control widgets could be grouped in a frame or a tab box and then the complete group could be moved to the final position in the Window. |
24 | 31 | Any control widget could be replaced with a other control widget, so for example a Toggle Button could be replaced with a ComboBox, |
25 | 32 | or a Knob could be replaced with a slider, or . . |
26 | 33 | You could set the range for a controller, and it's default value, You could create enums for a ComboBox, . . |
27 | 34 |
|
28 | 35 | Most Control widgets could be replaced with images you could select from a included file browser. |
29 | 36 |
|
30 | | -You could as well create a LV2 plugin from scratch and save it as Full Plugin-Bundle to a selected location. |
31 | | -The project settings window allow to setup the specs (like Author name, URI, Audio/Midi ports, etc.) for your plugin |
32 | | -XUIDesigner save the bundle in a git repository format, contain a working LV2 plugin with all needed resources |
33 | | -(ttl files, converted C files from used images, etc.) and build files to build, install and run it. |
34 | | -All you need to do to finish your plug is, implement your DSP part. |
35 | | - |
36 | 37 | XUIDesigner have a test-mode as well, which will build and run the created GUI, and give some useful information out in the terminal. |
37 | 38 |
|
38 | 39 | ## Currently supported widget types |
|
0 commit comments