widening audience. danm and sfraser have been thinking about where to dump things for embedding and the overall app recently. Jud
Chak Nanga wrote: > Any suggestion on where in the mozilla directory structure this > (source) could fit in? I'm thinking xpfe/appshell, just because it's been kind of a dumping ground for this kind of thing. Embedding may want to reevaluate that dll to find out what's actually required, but that's a whole other ball of wax... Alec > > Thanks > Chak > > > Alec Flett wrote: > >> Chak Nanga wrote: >> >>> Hi Alec, >>> >>> I'm working on >>> http://bugzilla.mozilla.org/show_bug.cgi?id=68720 >>> >>> which depends on >>> http://bugzilla.mozilla.org/show_bug.cgi?id=60117 - where you >>> propose a startup notification mechanism. >>> Since we need a similar scheme in the embedding scenario as well >>> what's the best way to implement this feature so that the same code >>> can be shared by apprunner as well as by >>> the embedding APIs? >>> Does implementing this as a service make sense or is there a better >>> way to do this? >> >> >> >> absolutely! We need some way to say something as simple as >> >> nsCOMPtr<nsIObserver> startupService = >> do_CreateInstance(NS_STARTUPSERVICE_CONTRACTID); >> >> to kick off the activation. I only propose nsIObserver because we >> might want to send messages to the startupService for some reason, >> and nsIObserver might be a good mechanism. If we don't need even >> that, then we can probably just make it an nsISupports. >> >> Alec >> >>> >>> Thanks >>> Chak >>> >>> >>> >> >> >
