browser vs. editor

Hello again,

I've noticed that a lot of times when Amaya behaves differently than how I
would expect, it's because Amaya was designed as both a web browser and
editor, while I'm used to having separate applications for these tasks. For
example:

- If I double-click a word that has a link applied to it, I would expect to
select the word for editing. Instead, Amaya navigates to the link.

- If I press Tab in a table cell, I would expect my cursor to move to the
next table cell. Insead, it moves to the next link.

- If I enter text into a field, I would expect the text to be saved as the
"value" attribute in the HTML. Instead, my text is lost when I close the
document.

I can understand the logic of these behaviors, but at the same time I intend
to use Amaya only as an editor and never as a browser, so I would prefer it
to be designed primarily for editing. How does this compare to other users?
Would the developers consider making the application more editing-oriented
if that were the consensus of users? Another option would be an explicit
"edit" and "browse" mode that behaved differently.

Thanks,
-Arlo

_______________________________

Arlo Leach
773.769.6106
http://arlomedia.com

Make friends with your computer
http://compyschool.com

Received on Thursday, 22 May 2008 14:31:04 UTC