Forum
Please
Log In
to post a new message or reply to an existing one. If you are not registered, please
register.
NOTE: Some forums may be read-only if you are not currently subscribed to
our technical support services.
Subject |
Author |
Date |
|
Andrew Harding
|
Mar 17, 2006 - 4:29 PM
|
Is there any plan to extend the state serialization functionality so that it can use XML? There are a few problems that we currently face with the registry and binary state files that would be greatly reduced by having a plain text hierachical format such as XML:
1. Whenever we create a new window in our product this invalidates the state files / registry settings of our users and we have to either nuke the old registry settings / file(s) or the customer will crash when they start their application. 2. Human readable XML would enable us to create windows programatically without having to recompile source code. (seems like a perfect merger with the new skinning mechanism) 3. Customers could share templates and modify the XML slightly to suit their individual need. (nice for situations where licensing issues are such that the person who knows how to modify the XML may not have a license to use the software, they could modify the code without having to run the software, administrators come to mind.) 4. Debugging situations where users report a crash would be eased if we could evaluate their system state and eliminate it as a possible cause of the crash.
|
|
Technical Support
|
Mar 20, 2006 - 2:47 AM
|
Thank you for the feature request. Yes, we plan to add an option to serialize the UI state to an XML-file. If fact, this feature with regard to toolbars and menus is already implemented in the Frame Features ActiveX control, which is completely based on Prof-UIS. The property pages and methods of this control allow you to save/load its design data and toolbar state to/from an XML file.
As not only you have requested this feature but others too, we will make this feature one of the top priorities.
|
|