Question is pretty well covered by the title of the post. I would love for this feature.
I think it’d be nice to possibly also compile or export a solution as a “plugin”. I would appreciate more as an organizational feature than anything else. On a similar topic, since Linx organizes solutions in a hierarchal structure. I believe it would be possible to come across Windows path length limits. I could see this leading to an issue saving projects that might not be the easiest to find the culprit of. So maybe a check for this if there’s not one already. Or something to add to the docs. Just a thought.
Hi Ferula
We don’t have a plan for a ‘use Linx to build a plugin’ feature. However, Linx 7 will build containers from Linx solutions which will make re-use and distribution of solutions easier.
You can theoretically already build your own plugin, but it’s not easy, and deployment will be complicated because it doesn’t form part of our official feed. Let our support team know if you want to give it a try.
I haven’t seen or heard of Windows path length limit problems when saving solutions from Linx Designer, so I assume we already take care of it. Let support know if you can break it!
Sorry I didn’t specify where my impulsive thought didn’t relate to the original message. Horrible habit of mine haha.
So when it comes to Community plugins, I don’t mean to have them developed with linx itself. It could any IDE. So pretty much the exact same things you guys do internally to create and add plugins. Just allow for parts of the code to be exposed for community members to develop their own “plugin”. Then potentially, gui based import to load these plugins.
My impulsive thought was pretty different. Yet related enough for me to be confusing with what I meant I think. So they other thought would of been more a purely aesthetic organizer. So for example, if I had developed a fairly extensive networking solution. Having the ability to organize it as a folder in the plugins panel. So nothing to do with any behind the scenes interaction so much as just folders that move between panels.
Sorry again for the confusing original post!
The original concept for community plugins could be further elaborated on by exposing a “mod API”.
An example would be functions relating to the Linux GUI management having an exposed function call for external developers to create custom GUI interactions.
Another example plugin
A developer could have an already compiled C# library. Maybe a JSON configuration file “documenting” the usage of the library, functions, parameters, value types, return type, so on and so forth. This would be the configuration file telling linx everything it needs to know to properly use the library and to allow proper debug mode usage. That’s what comes to mind for me. Don’t know if it helped me communicate my concept better. Let me know if you have any questions!