John wrote:
So, if I understand you're points, you suggest using the existing apprunner/appshell to interface to the native main() and windowing system required to start the application and house the XUL windows.
Exactly.
Ok, I think this is a great idea, is there any documentation, newsgroup postings, or history of anyone creating there own stand-alone application apart from MOZ_PHOENIX, MOZ_THUNDERBIRD, or MOZ_STANDALONE_COMPOSER?
Most of your program is going to be exactly the same as firebird...
Correct.
the only
part you need to change is the last part where firebird builds browser/ you need to build your own top-level directory. Building chrome files is very easy... building C++ is more complicated, but not overly so. I can help you with the few tweaks you will need to make in the configure script.
This, as I see it, is the crux of the problem. My requirements: 1) A custom output .exe name 2) An isolated profiles folder 3) A custom default .xul file to load
Questions:
1) I'm not sure what you mean by "building chrome files" are you talking about the chrome\contents.rdf? Does this have to do with requirement (3)?
I suppose I could hack browser.xul after building with MOZ_PHOENIX, but that is really ugly.
1a) Do I still need to build with MOZ_PHOENIX, or will MOZ_XUL_APP suffice?
2) What configure files do I need to change for requirements (1) and (2), I think (2) comes for free with (1) but I don't know. I don't ask this whimsically, I have looked at client.mk, configure.in, and makefile and nothing is clear to me, yes this is a very big, complex system :)
3) Get a basic app working which calls XRE_Main and sets up a chrome window...
Don't I get this for free by making the required changes to the make and config files?
4) then design the rest of your UI and whatever C++ components you need
Add then I'm in heaven :) _______________________________________________ mozilla-embedding mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-embedding
