I’m just about to try to develop my first real tools, but am a little confused: there’s clib and vlib, both seem partially to do the same like file operations or xml digestion, but seemingly in different ways? Why this redundancy? Did I get it right and clib is the slim toolkit, while vlib gets more into the big world with gui action and stuff like this?
Am I right best to spread some love for others would be to package the tool with a suitable clib/vlib version completely stuffed inside?
The whole thing actually started as xLib, my attempt at streamlining some of my own tools.
Since, xLib grew into quite a big thing and I had to split it into the “core” cLib, the “visual” vLib and finally, the renoise-specific xLib
Redundancy is bad - I’m trying to get rid of what little that remains. You’re right about the XML parser, I think it’s stated in the class itself.
As for filesystem, some vLib classes are using cLib - is this what you mean?
And I’m open for discussion about which things actually belong where - before more people step aboard and begin using these classes as starting points
I’m in a good position, as I can simply modify my own tools and make them fit with whatever we agree on
Also, Raul complained that the libraries are quite big. Which is true, especially with vLib including hundreds of (hardly used) BPM images. I’ve never really given this much thought, except that I have a function that strips debug (TRACE) messages from the tool+libraries. I use that as part of my release cycle.
I could add an additional method that could wipe everything but the files included by main.lua - brute-force, but that would slim down any c/v/xLib tools considerably.
I was thinking about this yesterday… isn’t the osc server available in the preferences.xml? (tickbox and server/port/protocol) That would be reachable if that’s the case and should be highly usable for warning the user. (even though it wouldn’t be verifying it is actually online and available… can’t ping it)
You mean config.xml?
Well, the config is (AFAIK) not updated in realtime, so this information is not really reliable?