<div class="gmail_quote">On Thu, Mar 4, 2010 at 6:10 PM, Michael Hudson-Doyle <span dir="ltr"><<a href="mailto:micahel@gmail.com">micahel@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">On 5 March 2010 12:31, Kevin Horn <<a href="mailto:kevin.horn@gmail.com">kevin.horn@gmail.com</a>> wrote:<br>
> On Thu, Mar 4, 2010 at 5:05 PM, <<a href="mailto:exarkun@twistedmatrix.com">exarkun@twistedmatrix.com</a>> wrote:<br>
>><br>
>> On 10:49 pm, <a href="mailto:kevin.horn@gmail.com">kevin.horn@gmail.com</a> wrote:<br>
>> ><br>
>> > If you look up a class, like "twisted.internet.defer.Deferred" for<br>
>> >example,<br>
>> > the link looks like this:<br>
>> ><br>
>> ><br>
>><br>
>> > ><a href="http://twistedmatrix.com/documents/current/api/twisted.internet.defer.Deferred.html" target="_blank">http://twistedmatrix.com/documents/current/api/twisted.internet.defer.Deferred.html</a><br>
>> ><br>
>> > Pretty simple right? But if you look up a function or method like<br>
>> > "twisted.internet.defer.Deferred.callback", the link has an anchor,<br>
>> >like<br>
>> >so:<br>
>> ><br>
>> ><br>
>><br>
>> > ><a href="http://twistedmatrix.com/documents/9.0.0/api/twisted.internet.defer.Deferred.html#addCallback" target="_blank">http://twistedmatrix.com/documents/9.0.0/api/twisted.internet.defer.Deferred.html#addCallback</a><br>
>> ><br>
>> > So we'll need to do some checking on either the api docs or on twisted<br>
>> >itself<br>
>> > to determine what sort of object is being linked to. Shouldn't be<br>
>> > super-difficult, just haven't had time yet.<br>
>><br>
>> Did you notice that<br>
>><br>
>> <a href="http://twistedmatrix.com/documents/9.0.0/api/twisted.internet.defer.Deferred.addCallback.html" target="_blank">http://twistedmatrix.com/documents/9.0.0/api/twisted.internet.defer.Deferred.addCallback.html</a><br>
>> also exists?<br>
>><br>
>> Jean-Paul<br>
>><br>
><br>
> I hadn't actually. If all functions and methods have a similar page in the<br>
> PyDoctor output, then I think what I have now will pretty much work as-is<br>
> (almost). Do we think that just generating links to the individual<br>
> function/method pages is acceptable?<br>
<br>
</div></div>It's what the lore-processed documentation currently links to. It<br>
would be nice to fix this (and I sort of vaguely know how), but that<br>
should in no way hold up the move away from lore!<br>
<br>
Cheers,<br>
mwh<br>
<div><div></div><div class="h5"><br></div></div></blockquote></div><br>OK, if that's the way Lore does it, then I'm happy to call that "good enough for now". It seems to work here in my local version of the docs, I'll update the online stuff at <a href="http://twistedsphinx.funsize.net">http://twistedsphinx.funsize.net</a> soonish.<br>
<br>Kevin Horn<br>