Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Profiling of results view topic #24

Open
mbakeranalecta opened this issue Aug 5, 2014 · 1 comment
Open

Profiling of results view topic #24

mbakeranalecta opened this issue Aug 5, 2014 · 1 comment
Labels

Comments

@mbakeranalecta
Copy link
Contributor

The editor-perspectives.dita file has a number of sub topics on the various views in the editor perspective. Currently all of those sub-topics are profiled eclipse only (and have eclipse screenshots). Only one topic, results-view.dita is unprofiled. editor-perspectives.dita is also unprofiled, which means that in the standalone documentation, results view is the only subtopic.

http://www.oxygenxml.com/doc/ug-editor/#topics/editor-perspective.html

I see that anonymous has commented on this in the online docs. It is not clear to me if this is a profiling error or a missing content error.

In any case, I have profiled results-view.dita to exclude it from the AuthorSDK and SVNClient docs, as this was causing validation errors due to unresolvable links.

@raducoravu
Copy link
Contributor

The "editor-perspective.dita" is so heavily profiled inside that it could probably be split in two topics, one for standalone (editor, author, developer) and one for eclipse (editor, author, developer). The same for "results-view.dita".

Also the "editor-perspective.dita" should contain links to the available views like Outline, Project, Attributes, Entities which are documented in some other topics.
But we've got both an "outliner-view.dita" which seems to be documented both for standalone and eclipse and an "outline-view.dita" which seems to have been created specifically for eclipse.

I'm not completely sure how this particular situation should be handled though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants