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

Extending the pages tag #1455

Open
wants to merge 16 commits into
base: main
Choose a base branch
from

Conversation

maxbruening
Copy link
Contributor

This pull request aims to extend the pages tag and applies the new commands for foxit, Sumatra, and the adobe pdf reader.

Currently, the pages tag seems to be used by document viewers, mostly pdf readers. This type of software typically has the ability to rotate pages, and also to go back and forth when users click on an internal link. this pull request adds these functions to the pages tag.

Copy link
Collaborator

@fidgetingbits fidgetingbits left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea and lgtm

tags/pages/pages.py Outdated Show resolved Hide resolved
@AndreasArvidsson
Copy link
Collaborator

We had a discussion about this in the community backlog session and we think we prefer user.go_back and user.go_forward that could be a generic navigation command used by different applications.

@maxbruening
Copy link
Contributor Author

I renamed user.page_go_back to user.go_back and user.page_go_forward to user.go_forward.

however, the general, empty definition of these functions with only the docstring is now being done in pages.py. Is there a better place to do this?

@AndreasArvidsson
Copy link
Collaborator

AndreasArvidsson commented Jun 25, 2024

Yeah we should probably move those somewhere else. Personally I have a separate navigation file for them.
https://github.com/AndreasArvidsson/andreas-talon/blob/4e7080423eecbd6a3998b0321bddc04cdb04df12/core/navigation/navigation.py

@maxbruening
Copy link
Contributor Author

A new navigation tag? That then forms a subtag of the pages tag? This would be a very small tag...

As an alternative, just create the empty functions in the core directory (without a tag). And just call these functions in the pages tag/wherever?

@AndreasArvidsson
Copy link
Collaborator

Doesn't necessarily need the tag, but I don't think we should put those actions in pages. Putting a new python file directly in the core directory sounds reasonable.

Copy link
Collaborator

@nriley nriley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please take a look at @AndreasArvidsson 's request? Thanks!

@maxbruening
Copy link
Contributor Author

Will have time in about 10 days

@AndreasArvidsson
Copy link
Collaborator

@maxbruening I will be happy to do them move myself? It's just moving those two actions out of the pages file.

@AndreasArvidsson
Copy link
Collaborator

I made a separate pull request where I implement that go back and go forward actions as well as actually using them in different applications. Once this is merged I will rebase this pull request.
#1490

@AndreasArvidsson
Copy link
Collaborator

AndreasArvidsson commented Jul 9, 2024

The navigation refactoring is now on main. I'm happy, but since I've made changes I would like another developer to take a look at it before we merge.
@nriley you have requested changes so probably best if you have a look at it :)

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

Successfully merging this pull request may close these issues.

5 participants