Community
Participate
Working Groups
Build: 3.5 RC3 The JDT user doc contains information on the import/export wizards for launch configurations and breakpoints. This information should be moved to the platform user doc because these wizards are defined outside JDT in the Eclipse platform. The import wizards should be added to org.eclipse.platform.doc.user/reference/ref-70.htm, and the export wizards in ref-71.htm.
Created attachment 138073 [details] Screen shot I happened to be creating screen shots of this for the doc, so for reference here are the wizards available in the platform runtime binary download (no JDT or PDE installed).
The whole Debug doc is in jdt.doc mainly because it describes the JDT case and the pictures also reflect that. As a result there is no doc at all for any debug component including F1/context help if JDT is not installed. Definitely too late to change for 3.5.
I can understand some of the generic platform debug would be hard to document without using a concrete case like JDT. I think the way to approach this is that it doesn't have to be all or nothing. For example the import/export wizard docs don't seem to have any JDT content, so we could move them to platform doc so that someone using CDT for example would have the documentation available.
I think Pawel is interested in splitting up the debug doc a bit - so CDT can share. I agree this it is too late for such a restructuring in 3.5.
(In reply to comment #3) Yes, I agree. Even for features that have a platform and a JDT component, such as the Debug view, I think it would make sense to document the common functionality in platform. I would like to investigate this post 3.5.
*** Bug 209606 has been marked as a duplicate of this bug. ***
(In reply to comment #5) > (In reply to comment #3) > Yes, I agree. Even for features that have a platform and a JDT component, such > as the Debug view, I think it would make sense to document the common > functionality in platform. I would like to investigate this post 3.5. Pawel, what's the status of this, did you get time to look into it for 3.6 or 3.7? Thanks! :) Helmut
Back in June I looked at what it would take to tease out the generic from JDT-specific documentation in debug and I thought it would take me about a week. So I moved onto other problems.
(In reply to comment #8) > Back in June I looked at what it would take to tease out the generic from > JDT-specific documentation in debug and I thought it would take me about a > week. So I moved onto other problems. Thanks Pawel :) Sounds like this is unlikely to happen, the reason being the quite big effort, right? Is there any way we could help you splitting things? Helmut
(In reply to comment #9) > Thanks Pawel :) > Sounds like this is unlikely to happen, the reason being the quite big effort, > right? > Is there any way we could help you splitting things? > Helmut Of course :-), contributions are most welcome. I estimated 40 hours, but this may be a little optimistic if we have multiple contributors. Since these changes would involve a lot of file creation/destruction CVS patches would not be the most convenient way of communicating. Let's at least wait until we move JDT to git later this month then fork the doc plugin on github.
CQ:WIND00091153
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. -- The automated Eclipse Genie.
Anyone interested in helping us out?
