On Apr 24, 11:27 am, Jean-Baptiste Queru <[email protected]> wrote: > There's no standard yet that I know of. I put my doc in the source > tree because I feel that's the most natural place for it, and because > I wanted it to be visible outside of Google (even though it's > incomplete and outdated). From that point, docs/index.html felt like > the most natural filename. It'd be good for someone to build a list of > all such documentation in the source tree, establish a pattern, and > make things fit into that pattern. Putting stubs for the projects that > don't have any documentation wouldn't hurt either. > > Ideally, such a list of links would be stored in the source tree > itself, to keep the source tree somewhat self-contained. Bonus points > for making it work both when browsed through gitweb and when stored > locally in a checked-out tree (make sure that the file is at the root > of the source tree).
The Dalvik docs — perhaps unsurprisingly, at <dalvik/docs> in the source tree — suffer in gitweb from the fact that many of the html files have associated css files, and gitweb doesn't provide the css files at sufficiently mangle-free URLs. If there is a reasonable solution beyond viewing them from your local checkout directory, I would love to know about it. -dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
