For what it's worth, I was really impressed by the O3D documentation: http://code.google.com/apis/o3d/docs/index.html <http://code.google.com/apis/o3d/docs/index.html>Not sure how they did it, but I believe it was all generated. Not sure if that's close enough to what you had envisioned.
On Tue, Jun 23, 2009 at 11:36 AM, Aaron Boodman <[email protected]> wrote: > > We're getting to the point with the extensions project where we need > to figure out how our documentation will work. From working on Gears, > Greasmonkey, and other previous projects I have some strong feelings > about how it should *not* work, and that led naturally to: > > > http://sites.google.com/a/chromium.org/dev/developers/design-documents/extensions/doc-viewer-design-doc > > Feedback desired. > > Before people ask: No, I have not yet seriously investigated any > existing systems (Doxygen, Bigbook) that we could reuse, rather than > build. It could very well be that something like this -- or close > enough -- already exists. Part of next steps would be to investigate > reusing existing options. > > - a > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
