Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #286600 +++ <response_by> Shenia Tang at 2009.08.13.10.48.51 </response_by> NLS Build Label: 20090811-1400-nl1-win32 Language: Traditional Chinese Must fix: YES Problem: There are some views that have the same description in dynamic help as for Problem view. Here I list most of them: CC++ perspective_Task view Database Development perspective_Bookmark view JAVA EE perspective_Marker view Plugin Development perspective_Task view Remote System Explorer perspective_Task view Resource perspective_Task view Team Synchronizing perspective_Task view <response_by> martine marin at 2009.08.13.15.00.06 </response_by> Same for France Martine <response_by> Kit Lo at 2009.08.14.01.01.01 </response_by> Same problem in English. Description for Problems view is displayed in Dynamic Help when Tasks/Bookmarks/Markers view is selected. <response_by> Kit Lo at 2009.08.14.01.01.17 </response_by> This article was reassigned from Category:''DVT,Inbox''.
This somehow slipped from my attention. This needs some thought given that generators can be reused by clients. Changing the current scheme may break some clients or takes away this flexibility. Also requires doc rework . See Bug 286600 Comment 18. Eric, should we go with the same fix? If so, we would need to apply patch from Bug 286600 ? Thanks.
Hitesh, when you say "Changing the current scheme may break some clients or takes away this flexibility." If this is existing behavior then these changes are likely out for 3.6, we're past API freeze (which includes existing behavior). If this is new behavior in 3.6 it's still dicey since it's very late in the cycle. What are the changes that would have to be made?
(In reply to comment #2) :) Thanks for the quick response Eric. I forgot to mention that I was referring to the clone Bug #286600. Comment 16 suggests that for 3.6 we enable specifying the help-context-ID declarativly as an attribute for the generator. Since views are paired with generators, this seems like a natural thing to do. But, Generators can be reused. For example consider a situation where I am contributing a view (call it StrangeMarkersView) that uses the Problems generator in addition to some filters and grouping. Here it maybe undesirable to have ProblemsView-specific help show up for the StrangeMarkersView(requires Doc rework). We are too late in the cycle for this,I agree. But that was not my question. About the patch, Bug #286600 Comment 18, I am under the impression it was applied to a specific stream only. Do we need to (re)apply this to 3.6 stream too? I had a doubt about this, hence the question. Thanks!!
Removed from 3.6. Owners can re-assess. PW
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
