Community
Participate
Working Groups
Show short configuration instructions on the web repository connector setting page. This would help to reduce confusion for configuring tricky repositories like Sourceforge and can also explain where to get repository-specific parameters.
Where are you proposing to show these, in the dynamic help which will cause the dialog to expand to the right? That's pretty straightforward to add and would not pollute the rest of the UI. The only other standard place to show such documentation is in tooltips (MS Office 2007 has taken on that convention and it works reasonably well).
Help and tooltips are NOT intuitive, so it has to be shown next to the repository configuration that you hid at the last moment before 2.0 release. Note that this request don't meant to generalize this feature and targeting web connector component only. Also note that for the web connector we should NOT hide table with the repository parameters (see bug 195058) and these instructions need to be shown next to that table.
It is generally a bad idea to add documentation/instructions inline in the UI in this way, but I do understand if the complexity of the generic web connector warrants this. Marking P4 but feel free to change the priority if you take it on.
(In reply to comment #3) > It is generally a bad idea to add documentation/instructions inline in the UI > in this way I don't see why it is a bad idea. Look at CVS repository settings dialog. Both general configuration and server encoding have some explanation along. For web connector such info will come from repository template... At this moment there is no point to take this on until bug 195058 is resolved.
There is anything I can do about this issue since required dependency on bug 195058 is not going to be resolved.
The dependency on bug 195058 is bogus. Whether you like the approach or not, such documentation can be shown either in a foldable section or using one of the standard mechanism in Eclipse (already pointed this out, but if I wasn't clear see http://www.ibm.com/developerworks/library/os-eclipse-ua/index.html Figure 4). No plans for Mylyn to support or invent custom/alternate user assistance beyond the other suggestion in comment#1.
(In reply to comment #6) > No plans for Mylyn to support or invent custom/alternate user > assistance beyond the other suggestion in comment#1. Have you read comment #4 at all? Anyways, feel free to close this issue as won't fix if you don't want to support the requested enhancement. I've been trying to explain to you that splitting related configuration elements into irrelevant sections does make configuration more misleading and complicated, so splitting that would defeat the purpose of this request. I don't see why are you trying generalize stuff that don't have to be generalized and why are trying to put your judgment into something that could have its own justifications. So, there is no point to cut the flexibility in a favor of overgeneralization. There are connectors that have their own take on how their settings should look like, but current API is forcing them into something that may not fit their needs. Web connector is one illustrative example of such, the email connector is the other one (in a user friendly UI it shouldn't even have url but would have some other mandatory settings) and I am pretty sure that there are other examples.
One of the themes for 3.0 is ensuring sufficient flexibility for connectors (while maintaining simplicity for end-users). Instructions will be a part of that, although I'm still weary of putting significant instructions into the UI widgets themselves for reasons discussed. It would be helpful if you could sketch out the instructions and widgets that you would like to have for the web connector. I also added this to the UI design questions for our presentation to the UI Best Practices Working Group: http://wiki.eclipse.org/Mylyn_Focused_UI_Design#Questions
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
