"site" but not for an application is not true either. There are plenty of
applications, whether desktop or HTTP based, that can benefit from
bookmarking. Quick made up example: say I have a human resources
application. The HR director is currently involved with unemployment
negotiations with one employee, and hiring negotiations for two others. The
HR director needs quick access to all their employee data on a daily basis.
Scenario A: He starts at the application's splash screen, selects
"Employees" from a menu, types somebody's first and last name into a search
box, then clicks to choose between "Smith, Joe D." and "Smith, Joe G.". He
has to do this every time he needs to bring the employment record up again.
Scenario B: HR director does that once, then bookmarks the employee file.
Afterwards, it's easy to get back to it, and when the negotiations
involving that employee are finished, he deletes the bookmark.
The benefit of the bookmark is the same regardless of whether the
*application* is a client-side executable or a site served up remotely via
HTTP and HTML.
Conan
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
