Accessing the documentation seems to force one to select module, then package, then class. I find this very difficult to internalise the underlying structure of API organisation.
I'm guessing I'm missing something 'obvious' because I've searched the Internet as well as forums here for some insight and guidance without success. I can't believe I'm the only person with this problem.
Thanks for reading and I hope that you can help :-)
My contempt for the people who removed the organizing frames from the api documentation has no bounds. The idea that a "good search" function can replace that is so deeply flawed I don't even know where to start. By all means, have a good search function, but don't obtain it at the sacrifice of the overall usability of the documentation. I used to laugh at what the MS world called .net "documentation" for its complete lack of transparency and organization. I'm not laughing anymore.
Thanks. I think I had an account here like 15 years ago, but I haven't been in a while.
I don't know why this frames thing has me so upset, but it does. I guess it suggests that the people at the top are visionless, clueless, backwards, and incredibly well insulated from reality. Since about 6 years ago have been increasingly suspected this to be the case, but actual confirmation is upsetting. I suppose their next step will be to get rid of the '*' operator -- because, well, you know you can accomplish the same thing with '+' and a loop.
I guess its time to finally make my own language ...
Ross Cohen wrote:I used to laugh at what the MS world called .net "documentation" for its complete lack of transparency and organization.
.NET documentation is really super weird. On the one hand is their API documentation, which is still really bad in many cases. On the other hand are their developer manuals for different technologies and frameworks, which are really well written. Examples of great documentation come from Entity Framework Core and ASP.NET Core.
Campbell Ritchie wrote:Agree that the old frames view was so useful.
Whenever I followed a link to an old version of the API, I would immediately click on the "NO FRAMES" link. I found the "FRAMES" version very annoying. Don't know why though. Takes all kinds to make a world.
I can't get on with that search function either, I badly wanted my frames back. Well, they are still present at the online apidoc (https://docs.oracle.com/javase/7/docs/api/index.html?index-filesindex-1.html). So my solution was to grab that entire pile using a free tool for offline browsing, named HTTrack (https://www.httrack.com) that converts all the links of a web structure to your local places. You have to decide how deep the linking will be performed, for internal resp. external links. Works fine for me , but maybe you already got your own offline reader that can manage the transaction just as well.