Closed
Bug 238376
Opened 20 years ago
Closed 1 month ago
container utils should expose a way to get an existing container
Categories
(Core Graveyard :: RDF, defect)
Core Graveyard
RDF
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: axel, Unassigned)
References
()
Details
All nsIRDFContainer objects should be retrieved thru container utils. Right now, you can a) create a container and Init it (calling Init is something dangerous in rdf code, so I discourage that) b) call MakeSeq or any of its friends, which will return a container object without modifying the datasource at all, if the resource is a container allready. Neither a) nor b) are really sweet and intuitive, so we should enhance the API of nsIRDFContainerUtils to return a nsIRDFContainer object for a nsIRDFResource and a nsIRDFDataSource which already make up a container. The lack of this api leads to code like in the xultutorial, which is not very pretty (look at the initSearchList function in findfiles.js)
Updated•15 years ago
|
QA Contact: rdf
Updated•6 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•