search

yanne / api-testing

I am using this to test GitHub API
1 stars 0 forks source link

Setting fields should be directly editable #70

Closed yanne closed 10 years ago

yanne commented 10 years ago

It seems very strange that I'm required to click on an edit button to edit the documentation for a test. There doesn't seem to be any valid reason (from a usability point of view) to require me to go to the extra steps of dealing with the dialog. It just adds an unnecessary extra step.

This issue was originally reported to Google Code on Mar 31, 2009.

yanne commented 10 years ago

Original comment by janne.t....@gmail.com on Apr 27, 2009.

You are correct. There are plans to reimplement parts of the current UI to improve usability.

yanne commented 10 years ago

Original comment by janne.t....@gmail.com on Apr 27, 2009.

(No comment was entered for this change.)

yanne commented 10 years ago

Original comment by janne.t....@gmail.com on Apr 27, 2009.

(No comment was entered for this change.)

yanne commented 10 years ago

Original comment by janne.t....@gmail.com on Sep 22, 2009.

Core team does not have resources to change this functionality before 1.0. Contributions are welcome!

yanne commented 10 years ago

Original comment by janne.t....@gmail.com on Sep 22, 2009.

Issue 125 has been merged into this issue.

yanne commented 10 years ago

Original comment by janne.t....@gmail.com on Sep 22, 2009.

This applies to all settings not just documentation.

yanne commented 10 years ago

Original comment by pekka.klarck on Nov 24, 2009.

Issue 323 has been merged into this issue.

yanne commented 10 years ago

Original comment by pekka.klarck on Nov 24, 2009.

Settings were changed in 0.19 so that clicking the text field opens the editor dialog automatically. After the latest enhancements (to be released in 0.20) these dialogs *) can be closed simply by pressing enter even when you have focus on the text field. Editing setting is thus as easy as 1) clicking the setting text field in RIDE, 2) editing the setting as needed in the opened dialog, and 3a) pressing enter to accept changes and close the dialog, or 3b) pressing escape to discard changes and close the dialog. This is close enough to editing settings directly, with the bonus that dialogs can validate the entries and show help texts, that I lower this issues priority.

*) The only exception to this rule are documentation editors where enter is used to add actual new lines to the documentation. With these dialogs you need to hit tab first to change the focus to the OK button.