I would like to create a stand-alone chrome based application that has an html editor and an svg editor.
How is this different/parallel to mozilla composer and NVU?
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.
Copy, copy, copy. The code you need is already there, don't rewrite from scratch.
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.
Definitely firefox. mfcembed is designed for a native (MFC) frontend, not for XUL. You can also reuse large parts of the toolkit and apprunner from firefox.
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.
what is WTL? I would suggest following the mozilla cross-platform programming model, and plain-old-C++. Staying within the mozilla makefile system would probably help you also.
--BDS _______________________________________________ mozilla-embedding mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-embedding
