Hey,
�
� I am working on loading a saving a form
for the designer via xml formatted lfm file. Should I include TDesignerForm in the object structure so that from the designer you will just have to call save to lfm and read from lfm and read from dfm???
�
dvortex is working on the Designer so this
question is more have the parser built and am laying out the object structure now. You may wish to take a look at the class stubs to see if they make sense with what you have.
�
Cliff

Ok I think I can work with that...

Cliff

you wrote

There won't really be any designer form, we will just "teach" control to respond to "clicks" differently depending if they are being designed or not.. (with just a little bit of coding in TWinControl and TForm)

it should be done at a higher level than TWinControl shouldn't it? In the VCL it is done at TComponent level

*Delphi Help Snippit*
------------------------------------------
TComponent is the common ancestor of all VCL components

VCL components are persistent objects that have the following capabilities:

The ability to appear on Component palette and be manipulated in the form designer.
The ability to own and manage other components.

Do not create instances of TComponent. Use TComponent as a base class when declaring non-visual components that can appear on the component palette and be used in the form designer. Properties and methods of TComponent provide basic behavior that descendant classes inherit as well as behavior that components can override to customize their behavior. ------------------------------------------
*End Snippit*

The code should just be required in TComponent - and thereby inherently handled properly by any other component (TButton) or container (TForm)

AMC Enterprises P/L - Andrew Bednarz
First Floor - Senior Programmer
3 Chesterville Rd -
Cheltenham Vic 3192 - Ph: (03) 9584-2700
http://www.amc.com.au/ - Fax: (03) 9584-2755

There won't really be any designer form, we will just "teach" control to respond to "clicks" differently depending if they are being designed or not.. (with just a little bit of coding in TWinControl and TForm)

I have put the stub for 2 methods :
- LoadXMLFormRes(Filename: String)
- SaveXMLFormRes(FileName: String)

So, if you have these, i'll be interested.
Here is a little description of what i am doing..:

TObjectInspector
property CurrentObject
Property CurrentForm
Method Inspect(ThisObject)
LoadXML
SaveXML

The 2 properties are there so that you can make the inspection happen The "currentForm" is the form that you would see with the "csDesign" state that would respond to clicks and so forth (probably through messages...)

I will check that tomorow and let you know. but from what i have seen so far (the XML example file you send last week or so), it looks super good...