Re: An Update to the Roadmap

Atle Smelvær wrote:
I believe there are different views here. This is not the most imporant
issue as long as the others are considered.

In the future, it might be best to pick one issue at a time. :)

There are benefits here. We could use these internal methods to save our own
objects, and have them saved in XML instead.

AFAIK, dfm streaming is built into TPersistent.

And .dfm streaming could have
compatibility with .NET serialization. This is possible today also with the
use of third party tools, but why not have it in one standard way.

So advocate the goal (i.e. compatibility with .NET serialization), not
the methodology (i.e. replace dfm with xml). Simply because you convert
..dfm to xml doesn't ensure this.

The ultimate reason I want this is to have compatibility with the .NET
serialization. If dfm could be saved the same way as .NET serialization it
could help for transitions between .NET and Win32.

So ask for that, don't offer up a solution that might not be a solution
to what you want anyway. As customers, it's not our job to solve the
problem, it's only our job to identify it.

--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.

Relevant Pages