Closed Bug 107059 Opened 23 years ago Closed 1 month ago

remove rdf requirements from embedding

Categories

(Core Graveyard :: RDF, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE
mozilla1.5alpha

People

(Reporter: alecf, Assigned: alecf)

References

(Depends on 1 open bug)

Details

(Keywords: embed, topembed-)

There are 2-3 major spots where we're requiring RDF for an embedding build. This
bug will track them. A few that I know about:
1) XUL template stuff - kind of irrelevant if you don't use XUL, but as we don't
have the NO_XUL flag working yet, it is still a build-time dependency
2) nsWindowMediator - uses lots of RDF, it's unclear how much is required.

That's all I know off the top of my head.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.7
Priority: -- → P2
The only ones that are interesting to us are: (from REQUIRES lines)

appcomps -> rdf;
  not sure how important appcomps is
appshell -> rdf;
  this is at least for nsWindowWatcher - we need a non-rdf implementation
chrome -> rdf;
  not sure embedding needs chrome
content -> rdf;
  for xul templates
content_xul -> rdf;
  for xul templates
exthandler -> rdf;
  unclear what to do here - not sure how important exthandler is to embedding..
possible that we should move exthandler into appcomps
history -> rdf;
  there's another bug on this somewhere, but we're not really expecting
embeddors to use our history implementation
layout_xul -> rdf;
  this is for xul templates
uriloader -> rdf;
  this is because of the exthandler dependency above

Given the hugeness of this, moving out a milestone so I can focus on simpler things.
Target Milestone: mozilla0.9.7 → mozilla0.9.8
bad news: gotta move these bugs to 0.9.9, I have too much on my plate right now.
Target Milestone: mozilla0.9.8 → mozilla0.9.9
Priority: P2 → P3
Depends on: 119923
Target Milestone: mozilla0.9.9 → mozilla1.0
Keywords: topembed
Depends on: 132175
this is a tracking bug, and there's no way we can finish the two dependent bugs
by 1.0 :( moving out
Target Milestone: mozilla1.0 → mozilla1.1beta
Keywords: topembedembed, topembed-
an update:
appcomps -> rdf;
  appcomps is not part of the embedding build
history -> rdf;
  really part of appcomps, but the bug in question is bug 71481
appshell -> rdf;
  just waiting on reviews see bug 132175
chrome -> rdf;
  I'll be doing a minimal chrome reg in bug 119923
content -> rdf;
content_xul -> rdf;
layout_xul -> rdf;
  for xul templates - no progress here, probably safe for now but engineering
fix will be hard
exthandler -> rdf;
uriloader -> rdf;
  unclear what to do here - not sure how important exthandler is to embedding..
possible that we should move exthandler into appcomps. also, chimera wants
helper app support, so maybe this needs to move to something that chimera can
use, but embedding doesn't need.
moving bugs to mozilla 1.2alpha that missed 1.1beta
Target Milestone: mozilla1.1beta → mozilla1.2alpha
pushing a few bugs out to 1.2beta - too much stuff on my 1.2alpha plate!
Target Milestone: mozilla1.2alpha → mozilla1.2beta
Depends on: 164172
unfortunately RDF is too ingrained in the chrome registry right now to be able
to fix this for 1.2. Moving out to 1.3, which will require a change to the
chrome registry format, probably to some sort of "contents.txt" solution.
Target Milestone: mozilla1.2beta → mozilla1.3beta
Target Milestone: mozilla1.3beta → mozilla1.4beta
Depends on: 190195
Blocks: 190207
*** Bug 194295 has been marked as a duplicate of this bug. ***
QA Contact: tever → nobody
Target Milestone: mozilla1.4beta → mozilla1.5alpha
Blocks: 213938
Please see embedding/minimo/chromelite which no longer requires RDF and is a
complete replacement of chrome and the chrome registry.  We should eventually
merge this work and what you have been doing.
QA Contact: nobody → rdf
Product: Core → Core Graveyard
Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.