I don't use xml, but in a similar vein, I think there should be a way to default the UIR editor to always use and save .tui instead of .uir. And of course load the .tui from LoadPanel() which is already possible.
The reason is that it would facilitate use of version management tools which work much better on text than binary.
Basically I'm asking for the replacement of .uir by .tui. Yeah, I know it's slower, but it's not like you load user interfaces 10 times per second.
I'd second the suggestion to have a textual format that can be merged with "simple" merge tools like RCS/CVS/MKS. This shouldn't have much run time impact as long as the UIR code can be embedded into a .DLL or .EXE (as it can with CVI 9, for instance).
I like the original suggestion from Peter: version management is really difficult with uir format (you must save as tui and diff the files as described here, but it's a slow process).
I think that a new text-based format for user interface files should be introduced; xml style would be OK, I think.
The most important thing is that CVI IDE must show the graphical layout of the panel (as for uir files) when the developer opens this new file with the IDE itself.
Vix ------------------------------------------- In claris non fit interpretatio
------------------------------------------- Using LV from 7 Using LW/CVI from 6.0
Yes, I want an easy managment of the "uir"-file in a version managment and also would like to edit and parse the uir file (xml-file) with standard tools. I.e. aut-create of description tooltips or get the tooltips to automatically create an help file.
You can run .tui files from your program with LoadPanel, right ?
So why not simply allow opening .tui files in the editor instead of only importing them ? This way you also save them as .tui, put them in SVN and everybody's happy. Should be a very simple fix too.
