Replies: 1 comment 1 reply
-
My sense is that it's not worth the effort. But please take that in the context that I don't have any experience with xsd and have no understanding of how we would change labwc, labwc-tweaks, documentation or example config files if we were to adopt this. I you feel that an xsd approach would help us more that it would hurt us, then a best next step is probably to work up a high-level case with some pros/cons and some early thoughts on implementation (changes required to labwc and tweaks). That way we can critique it and move the conversation forward. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
One thing I had in mind with my idea to use a xsd schema based configurator was, other than define and manage the structure of the types, the default values, to avoid to hard code them in the code/UI, and so avoid to keep in sync in different places (rc.xml.all, manual..).
Any idea?
Beta Was this translation helpful? Give feedback.
All reactions