Closed Bug 114658 Opened 23 years ago Closed 9 years ago

clean up embedcomponents, appshell, appcomps, mozbrwsr

Categories

(Core Graveyard :: Embedding: APIs, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE
Future

People

(Reporter: alecf, Assigned: alecf)

References

Details

(Keywords: embed, topembed-)

Right now we have a bunch of dlls which have a bunch of somewhat related components in them: embedcomponents appshell appcomps mozxfer mozfind mozbrwsr shistory webbrwsr That's 8 dlls! We need to consolidate these into 3 dlls: Browser-only Embedding-only Browser/Embedding, shared We might want to split the last dll into "shared" and "shared, extended" where the "shared, extended" dll contains extra features that embeddors MIGHT want, but the browser definitely needs. The Embedding-only dll is likely to be pretty small. I went through the XPCOM module declarations for each module and determined everything that was in each one, and then tried to guess at who really needed each component. Browser-only ------- appshell: about ?? (about: or about:mozilla?) appshell: user info appshell: timing service appshell: Mac: MacMIME appshell: Mac: InternetConfig appshell: commandline service appshell: window mediator appcomps: autocomplete appcomps: bookmarks appcomps: directory viewer appcomps: local search, internet search appcomps: related links appcomps: font package handler (maybe not?) appcomps: Win: UrlWidget appcomps: LDAP autocomplete appcomps: global history (unless they want our impl?) mozxfer: file transfer? (embeddor said they need it?) mozbrwsr: nsBrowserInstance Embedding-only --------- webbrwsr: nsWebBrowser? webbrwsr: nsWebBrowserContentPolicy? webbrwsr: nsCommandHandler? embedcomp: find?? embedcomp: webbrowser persist? Shared ------ mozfind: find in page shistory: session history appshell: appshell service (includes nsWebShellWindow, contenttreeowner, chrometreeowner) embedcomp: appstartup embedcomp: dialog param block embedcomp: prompt service embedcomp: js console embedcomp: window watcher
cc'ing random, possibly interested parties. This is not something I have time for right now.. however for performance/bloat I wonder if someone else might be interested in tackling this :)
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → mozilla0.9.9
Priority: P2 → P3
Depends on: 83704
Summary: clean up embedcomonents, appshell, appcomps, mozbrwsr → clean up embedcomponents, appshell, appcomps, mozbrwsr
Target Milestone: mozilla0.9.9 → mozilla1.0
Keywords: topembed
Target Milestone: mozilla1.0 → mozilla1.1alpha
topembed- per EDT triage.
Keywords: topembedembed, topembed-
Priority: P3 → P2
woah, 1.1 came up quick. Throwing these bugs over to 1.2.. little or no work has been done and there is no way that these bugs can be fixed in 1.1.
Target Milestone: mozilla1.1alpha → mozilla1.2alpha
Blocks: 163737
mozilla 1.2alpha is more or less done. moving mozilla 1.2alpha bugs out to mozilla 1.2beta
Target Milestone: mozilla1.2alpha → mozilla1.2beta
No longer blocks: 163737
too much work for 1.2. moving out to 1.3.
Target Milestone: mozilla1.2beta → mozilla1.3alpha
QA Contact: mdunn → depstein
Furturing bugs that keep getting knocked from milestone to milestone...if you feel this is in error, please nominate this bug using the appropriate keyword.
Target Milestone: mozilla1.3alpha → Future
QA Contact: depstein → dsirnapalli
QA Contact: dsirnapalli → apis
Marking a bunch of bugs in the "Embedding: APIs" component INCOMPLETE in preparation to archive that component. If I have done this incorrectly, please reopen the bugs and move them to a more correct component as we don't have "embedding" APIs any more.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.