Can you post your glade code conversion somewhere for me to look at. I never looked at glade and I would be interested in seeing how you are converting it. I assume the modifications are going to force us to store our version along with our code. Therefore, simply update the cvs tree with a sub directory so I can view the code.....

Thanks
Shane

>> 04/25/00 11:11PM >>>

Ok it looks even better than I had originally thought. First of all the component names are wrong luckily they are easy to change in glade. I will remove the ones that do not pertain an change the names to reflect our components. Glade takes a project file in our case it will be the lfm as a command line argument.

My plan it to create a TDesigner object that is going to wrap the load call to glade. When a form is selected this object will create a LFM in xml and then launch the modified glade against it. This should make things look very seemless. Glade is going to continue to run as it's own process and in the mean time TDesigner will monitor the file for any changes. If a change occurs it will parse the contents probably with the xmlparser I posted a few weeks ago and update the pp unit and raise a changed event so that the editor can reload the file.

The only reason I am going to use the xml parser I wrote is that it is event driven and ideal for this type of job. The parser will just use a state machine internal to load the file definition into a source accumulator.

Like I said the only problem is that the IDE is not going to be exactly like delphi because the pallet will be seperated from the top toolbar. Frankly I do not care about that as long as we still have full functionalitly.

At some late time we can always replace TDesigner with a Lazarus built one.

Cliff

_________________________________________________________________ To unsubscribe: mail with
"unsubscribe" as the Subject
archives at http://www.miraclec.com/list_archives/lazarus

Ok it looks even better than I had originally thought. First of all the component names are wrong luckily they are easy to change in glade. I will remove the ones that do not pertain an change the names to reflect our components. Glade takes a project file in our case it will be the lfm as a command line argument.

My plan it to create a TDesigner object that is going to wrap the load call to glade. When a form is selected this object will create a LFM in xml and then launch the modified glade against it. This should make things look very seemless. Glade is going to continue to run as it's own process and in the mean time TDesigner will monitor the file for any changes. If a change occurs it will parse the contents probably with the xmlparser I posted a few weeks ago and update the pp unit and raise a changed event so that the editor can reload the file.

The only reason I am going to use the xml parser I wrote is that it is event driven and ideal for this type of job. The parser will just use a state machine internal to load the file definition into a source accumulator.

Like I said the only problem is that the IDE is not going to be exactly like delphi because the pallet will be seperated from the top toolbar. Frankly I do not care about that as long as we still have full functionalitly.

At some late time we can always replace TDesigner with a Lazarus built one.

Cliff

When making modifications I am just placing a comment above the mod that starts
with /*lazarus my comments*/ this allows me to grep the files for the changes. Mostly I am
just disabling stuff that does not apply. Like Marc had mentioned the event thing worries me since the original is geared towards C. I will try to add a event panel this evening to the object inspector and generate the event structure to the xml file. The GLADE ide is coded very clean and should be a easy task.

I am still not totally commited to it but it sure does look like a very promising deal. As for layout I do not think there will be any difference in the generated code and what you see on screen.

Cliff