On Mon, Feb 22, 2010 at 10:57:18PM +0100, Gianluca Montecchi wrote: > ... > Wait. This div is only usefull to generate a nice (?) looking tree > to indent the comments. Perhaps I don't explain myself: for "access > a comment" I intend to have a direct link to the comment somwehere > in the html code. So you are somewhat right, I access the comment, > but only to read the comment and put it in the html file of the > bug. But since the comment it is not a separated html file, you > cannot access directly the comment with the browser.
Direct browser access to a comment (with my untruncated IDs): http://www.physics.drexel.edu/~wking/code/be/bugs/bugs/12c986be-d19a-4b8b-b1b5-68248ff4d331/#13012b22-2d02-444c-87c0-8cf0f17137ae > 1) we export all the comments to separated html files, and in the > html file of the bug we put only the header of the comment (or just > an extract) and load the comments on demand, this might require some > javascript or AJAX, and can be usefull with long threads. We already do the separate file thing for non text/* or image/* comments, but we just print: '<a href="./%s/%s">Link to %s file</a>.' \ % (self._truncated_bug_id(bug), self._truncated_comment_id(comment), comment.content_type) > 2) we put in the actual html file of the bug, with all the comments, > an anchor to be able to do something like > "http://www.somewhere.org/bugs/123.html#23k"; to access directly the > comment. See above. It's the "id" attribute of the <div> field that defines the anchor [1]. Cheers, Trevor [1] "id" is a valid attribute of <div>: http://www.w3schools.com/tags/tag_div.asp#table3 "id" creates anchors: http://www.w3.org/TR/html401/struct/links.html#h-12.2.3 -- This email may be signed or encrypted with GPG (http://www.gnupg.org). The GPG signature (if present) will be attached as 'signature.asc'. For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt
pgpSmMrotTQbc.pgp
Description: PGP signature
_______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
