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.

Sign up for GitHub

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

Jump to bottom

Substance Reader requirements #30

Open

michael opened this issue Jun 3, 2015 · 0 comments

Member

michael commented Jun 3, 2015

Extension mechanism for content_panel (e.g. methods like markActiveTOCEntry) should be installed by extensions, reader listens for clicks on references while writer handles selection changes.
Maximum code share between Writer (disable editing but not loose ability to track selection changes)
Introduce generalized application api (2-panel) that reader and writer can use (same extension API)

Approach:

Bootstrap reader with Writer codebase but do refactorings to support the above usecases
Have in mind the writer case so we can later make the writer also conform to that new API

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment