Hi everyone. Here again with another exploratory question which I can't seem to figure out how to do or if it is even feasible.

Just today I was exploring other front-end frameworks and found Slint fascinating (more because I can easily specify and set it up to use winit and femtovg-wgpu )

I was playing around and created my own local repo with small examples, then I thought of the main binary (since my examples are inside a rust project in /examples directory).

My conceptual design for the main binary is in the form of a plugin launcher like this:

Supposedly, the main binary is a launcher, its job is to run small independent Slint apps within it in the form of plugins (which are the small projects) .

When ran the first time. The launcher is initially empty, it lets you open a file picker to open a compiled plugin file. Once picked, a vertical navigation tab on the left will appear which has the name of the plugin as one of the items, then on the right it initializes/runs the plugin.

Let's say it's a calculator plugin, after I import its plugin file, a nav item called "Calculator" is supposed to be created within the navigation tab on the left. Once it is selected, it runs the plugin and spawns a usable calculator WITHIN it on the right side.

Now one of the biggest question here is how to even tackle this plugin design in the first place?

Does the plugin project need to be compiled in a unique way?

How would the client launcher even parse the plugin?

Just one of the many questions I have from that idea alone. Because I really love the idea of fine-grained control and portability to probably unhealthy levels.

1 post - 1 participant

Read full topic