All of this is quite nice, until you realise that a lot is beyond our control. Apart from having no control over the the layout and presentation of the page, apart from via HTML, (IE does it all, which is not a bad thing) it is not future proof: MS could decide that COM objects running via a web page are a security risk (true), so could stop it happening full stop. Indeed, in Vista, this is becoming a real issue.
Hence, I want to do away with a browser control altogether.
It would not be too difficult to have an app read some "file" that contains information about what a "page" should look like. Where in HTML I would specify page backgrounds, and control locations, I would do exactly the same, except I would have to construct the controls myself. Whereas I might have
<input type = "button" value = "Button">
in HTML, I would have to call CButton::Create myself to "add the button to the page" as it were. Any page "background" would have to be blitted to the window, etc etc...
None of this is really difficult.
But now the issue. Look again at the button HTML, but this time add a handler in:
// Do stuff here
all nicely packed away in the HTML.
My question is simple: *how on earth could I have a button handler containing the code to be executed serialised away into my "file"?* Message maps are out of the question since they have to be compiled into the exe at build time...?!
Any advice or hints on this please?