Closed Bug 7864 Opened 25 years ago Closed 5 years ago

xpidl authoring guide needs to be finished

Categories

(Developer Documentation Graveyard :: Mozilla Platform, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mang, Unassigned)

References

()

Details

Depends on: 7863
Shaver, are you still working on this?
Status: NEW → ASSIGNED
Guess not. It's all up to me.
Random stuff left to document
- use of NS_DECL_*
- out parameters through XPConnect

Other
- "string passing" in best practices is really about implementation, not
interface
Also, need more docs on these keywords
- shared
- notxpcom
Mass reassign to mccabe since I'm outta here.
Mass accept as ASSIGNED of xpidl bugs
Component: xpidl → Mozilla Developer
Product: Browser → Documentation
Version: other → unspecified
[SPAM] Marking milestone 'future' as part of nsbeta3 triage.

(Actually, I think 'array' may be all we're missing.)
Target Milestone: --- → Future
Could also discuss use of %{C++ escape to define ProgID and CID in .idl file. 
IMO, this is marginally acceptable (stylistically) since there is often only one
component that implements that interface.  Should warn other implementers from
using the same CID.

Will add this and 'array' Real Soon Now.
Assignee: mccabe → mang
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
accepting QA for mozilla developer docs.

some of these bugs have been around for a _long_ time. Reporters, would you
please review the bugs, see if the issues have been resolved, and close bugs
appropriately.

I will do a full review of all bugs not touched in one week (8th April). 

Thanks.

</spam>
QA Contact: mike+mozilla → imajes
add url
taking over QA

reporter, is the guide finished?
QA Contact: imajes → stolenclover
yyyyyyyyyyyy
something
Assignee: mang → nobody
Status: ASSIGNED → NEW
Component: Mozilla Developer → Documentation Requests
OS: Linux → All
Priority: P3 → --
Product: Documentation → Mozilla Developer Center
QA Contact: danielwang → doc-request
Hardware: PC → All
Target Milestone: Future → ---
Blocks: 399537
Component: Documentation Requests → Documentation
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Reopening for review by Sheppy.
Assignee: nobody → eshepherd
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This still needs to be done. Anyone spend a lot of time in IDL that would like to finish this up?
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
Whiteboard: u=mozdev p=0
Component: General → Mozilla Platform
Whiteboard: u=mozdev p=0 → u=mozdev p=0 c=Platform
Trying to make this bug more clear for anyone who wants to work on this (this bug belongs to one of the very few open bugs where the ID is less than 10000!!!)

Looking at the inventory, there are the following docs for XPIDL on MDN:

https://developer.mozilla.org/en-US/docs/Mozilla/XPIDL
https://developer.mozilla.org/en-US/docs/Mozilla/XPIDL/Function_modifier
https://developer.mozilla.org/en-US/docs/Mozilla/XPIDL/Generating_xpt_on_Windows
https://developer.mozilla.org/en-US/docs/Mozilla/XPIDL/pyxpidl
https://developer.mozilla.org/en-US/docs/Mozilla/XPIDL/Syntax
https://developer.mozilla.org/en-US/docs/Mozilla/XPIDL/xpidl

These docs could need a review and are probably in need of some updates to reflect current reality.
There is also the archived material at http://www-archive.mozilla.org/scriptable/xpidl/idl-authors-guide/ which was requested to be migrated to MDN in bug 399537.

Sheppy, are you working on this in the foreseeable future? If not, please unassign so that this is open to anyone.
Flags: needinfo?(eshepherd)
Whiteboard: u=mozdev p=0 c=Platform
Assignee: eshepherd → nobody
Flags: needinfo?(eshepherd)
If there is no objection, I plan to archive this area in a few days. It is no longer in the scope of MDN and is unmaintained for years.

Finally closing this issue and archiving the XPIDL docs. They now live under https://developer.mozilla.org/en-US/docs/Archive/Mozilla/XPIDL

Status: REOPENED → RESOLVED
Closed: 12 years ago5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.