The problem with using seperate DLLs is depending on whether or not they have VST headers in them which then the host would pick up, though I can see how this is avoidable, but in the case of a host 'attempting' to load such as a VST when it's just GUI data, would it crash or would it just be bypassed?aciddose wrote:"Would that be even possible if some random decided to skin XHip as a single-page instead of the multi-page system, with how it's currently constructed?"
i've designed the code to make this possible. anyone capable of working with c++ code can easily write a gui for xhip using the code i've made available. i'll include that and distribute it for the author under the conditions that:
1) the resulting code is released either to the public domain (only the parts you add) or to me
2) no external libraries are applied (in other words, you may only add code which you can hand over to me or release into the public domain. also i'd prefer to stick with the structure i already have, redesigning the whole thing from scratch doesnt make sense)
"Like, someone can make a skin, then the user can change between that skin that uses multi-pages, and the other one that uses just a single page."
that is what i've always had in mind. i could do it right now actually but you'd need to select the gui with an external application or by editing a config file. all i'd need to do is compile the 'editor' portion into a seperate dll - you could then select which dll is loaded on start up.
actually though it may be possible to allow dynamic loading of the gui dlls by working in an extra layer with a menu for this.
the 'gui' components would also be best put into a seperate dll which would allow the 'editors' to dynamically load that rather than having it statically linked.
But anyway, that's great insight.
