That looks very good, have you got it running with Lazarus? I could only find mention of Delphi 2006+ and we were last on Delphi 2005 Pro
Sometimes I don't think I would need the full on Ext Js or the php Vcl thing, and actually need something a bit simpler.
If
http://wiki.lazarus.freepascal.org/DELPHI_FORM_TO_HTML_CONVERTER is going to be too hard to convert to Lazarus ...
I have been looking at the XML export of the Lazarus form.
It is very well formed and leads me to speculate about writing something to convert specified elements into html (jQuery even) with attached .css and skeleton .js
In a sense I would find it very useful just to have a utlity for Lazarus forms that will produce .html and .css with a dummied up .js perhaps auto writing in appropriate jQuery skeletons or simple JavaScript barebone function holders - when obvious.
Then I can take my Lazarus client project and start the process of moving it to the intranet/ or web. When needed. I dont mind hand coding the rest of the business logic, it woiuld be neat just to have the WYSIWYG part covered.
<component name="Button1" class="TButton">
<properties>
<integer name="Left" value="585"/>
<integer name="Height" value="25"/>
<integer name="Top" value="362"/>
<integer name="Width" value="75"/>
<string name="Caption" value="Button1"/>
<integer name="TabOrder" value="1"/>
</properties>
</component>
Unlike the text of the .lfm, the xml export has no indication of any event handling
object Button1: TButton
Left = 585
Height = 25
Top = 362
Width = 75
Caption = 'Button1'
OnClick = Button1Click
TabOrder = 1
end
Is there any option to turn on the XML export of the form with inclusion of indications of events and procedure names? Or I suppose I could just parse the .lfm text
(For the .js just need to think about there being an indication at least of any wanted event handling on each element that needs to be written in JavaScript/jQuery etc. Be nice if I could pick up the Lazarus procedures themselves and put them as comments in the generated JavaScript function place holders)
When a Lazarus project is compiled, does it still "know" it's text origins. I.e. could I walk the application as an object (while running) and get enough out of it to create my html, css and Js skeleton? Would a running Lazarus application still "know" what the comments were in procedures - the very inner text of the procedures themselves? That would be a neat OO and clean way to do this if so. Just add a routine (even as a component) to run through the application while running to make the necessary files on disk.
Thoughts to this point any way...
Paul