> Would programming an XNode be just a matter of suitable documentation - without releasing proprietary information?
Yes and no. They are suitable for some things, but they become unstable when used for other things, and adequately documenting that gray line is not something we feel can be done. NI has backed away from XNodes for many types of internal development because the instability is ill-defined. They work great for small tasks, but it isn't a technology that we feel we can give to customers. Although we have in the past released products that were "use at your own risk", they were products that produced good results so that if you did manage to use them, you could pass the result along without spreading the instability. Here we have a feature that has the potential to work great on your machine, but becomes problematic when you give it to someone else to use, problematic to the point of corrupting their VI beyond recovery.
