10-27-2005 10:29 AM
DFgray,
I see your point about XMLs difficulties. I have struggled to incorporate XML and have been slowly replacing .ini files with XML formatted data. I do agree that for data XML has its limitations. XML is not the cure-all that it was hyped to be but it does serve its purpose as an open extensible format for data interchange. This is why I think a flatten control/object by reference could be so powerful, because it will focus on storing a controls properties, as a structured object-oriented XML representation, the value is just one field of the controls code. The Flatten would be polymorphic and cover the entire gObject hierarchy. Now we could store the state of all objects on the front panel in a platform independent extensible and uniform way. Loading back these files could dynamically re-work a GUI and save enormous amount of GUI coding (in my opinion LABVIEWS weakest feature). Imagine storing the state of the GUI altering it on the fly and then re-drawing it as needed. Different users could view the application without reprogramming, just loading a different preference file or even just a different style. I am not an XML expert and still learning but the ability to switch between controls and an open representation of them might be a good option to have. If you want to internationalize an application you could change all captions, description, and tool tips in the XML file and rename it and just reload file back to the controls. Just something to think about, I could be totally wrong about this though.
Paul
10-28-2005 09:17 AM
10-28-2005 09:45 AM