One of the surprises to me in considering a useful tool for quick class information came when I looked around for something to get to javadocs quickly, and realized that Sun had a nice little system for how javadocs are layed out.
Trouble is, no human being wants to type in the long URL to get to a method, or remember where the javadocs are (though some I'm sure just saved favorite links) while for a computer, it's not an effort.
So Class Viewer is a user enabling interface which is a phrase I've noticed used by others, but I'm wondering why more haven't caught on!
Like, even with search engines, like Google is powerful, but there should be ways to automate much of what most people slog through doing with it.
Why isn't it being done?
Or is it?
I'd appreciate links to user enabling interfaces or automating processes. Or some reasons why such a neat idea as letting the computer take over tedium from the user is so slow to get traction.
James
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
One of the surprises to me in considering a useful tool for quick class information came when I looked around for something to get to javadocs quickly, and realized that Sun had a nice little system for how javadocs are layed out.
Trouble is, no human being wants to type in the long URL to get to a method, or remember where the javadocs are (though some I'm sure just saved favorite links) while for a computer, it's not an effort.
So Class Viewer is a user enabling interface which is a phrase I've noticed used by others, but I'm wondering why more haven't caught on!
Like, even with search engines, like Google is powerful, but there should be ways to automate much of what most people slog through doing with it.
Why isn't it being done?
Or is it?
I'd appreciate links to user enabling interfaces or automating processes. Or some reasons why such a neat idea as letting the computer take over tedium from the user is so slow to get traction.
James