Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#12015 closed defect (fixed)

dojo.hitch documentation is missing

Reported by: Adam Peller Owned by:
Priority: high Milestone: 1.6
Component: Documentation Version: 1.5
Keywords: Cc: Tom Trenka
Blocked By: Blocking:

Description

Change History (5)

comment:1 Changed 9 years ago by Adam Peller

Cc: Tom Trenka added

could this have something to do with the vararg syntax in the docs {/*,...*/}? ttrenka, are there any errors showing up?

comment:2 Changed 9 years ago by Tom Trenka

Um, dojo.hitch shows up just fine--but you'll find it under the dojo object itself (since it is a method of dojo):

http://dojotoolkit.org/api/1.5/dojo

(look in the methods summary list and click on it).

I agree that this may not seem the most intuitive and may be something to add in later on as an additional feature, but the *only* things that are addressable by URL at this point are actual objects. Then again, there are cases (dojo.query comes to mind) where it *seems* like it's just a method but the doc parser system sees it as an object; in that particular case, it is because there is a "_psuedos" property attached directly to the function.

comment:3 Changed 9 years ago by bill

I've been confused by this too, or rather, confused that functions like dojo.hitch() don't show up in the tree on the left. Perhaps we should change this to an enhancement request to make everything accessible by URL and from the tree on the left?

Either that or close the ticket as invalid?

comment:4 Changed 9 years ago by Tom Trenka

Resolution: fixed
Status: newclosed

Actually, this doesn't lead to an error anymore; I set some things up so that if I'm not finding the actual object initially I go digging in fields, and try to scroll to it if I find it. So I'll close the ticket as fixed.

As far as the tree is concerned, I would call it "wontfix" because the overhead of the tree is huge as it is, and I'm already not including any private objects in it. Current tree data weighs in at something like 350K; I would really hate to push it any further.

comment:5 Changed 9 years ago by bill

I see you are downloading all the tree data up front, rather than on opening each node, which would be better.... still, it's only 35K, not 350K.

Note: See TracTickets for help on using tickets.