One way or another, I have come to realise that creating a chrome based stand-alone application with mozilla is going to require significant custom code just for the basics, let alone specifics to my application's requirements.
Before I invest the time required for this basic application code I would like to ask if you would advise me to base my code on the embedder code base, i.e. mfcembed as a model, or the firefox application model.
Being a chrome based application, the windowing system will have to use the chrome properties to discover persisted and/or chrome-calculated window size, window type(app, dialog, etc.), etc.
Running my XUL application through firefox has no problems with this, but I am having difficulty getting mfcembed to work with a XUL based application.
The first crack at the application will only support a Windows app, a multi-platform app-launcher will have to wait, I assume the mozilla system sufficiently allows this prioritizations in iterations. The first code base will use WTL for the application base code using VC++2002.
Thanks for any advise. _______________________________________________ mozilla-embedding mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-embedding
