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

[Feature] Optimize user experience of FastPR #905

Open
frank-zsy opened this issue Nov 9, 2024 · 7 comments
Open

[Feature] Optimize user experience of FastPR #905

frank-zsy opened this issue Nov 9, 2024 · 7 comments
Assignees
Labels
kind/feature Category issues or prs related to feature request.

Comments

@frank-zsy
Copy link
Contributor

Description

Enhance the user experience of the FastPR feature:

  • When a user selects a portion of text with their mouse, move the button to launch the editor near the selected text to facilitate quick access to the editor.
  • When a user opens the editor within the document, approximately estimate the current position in the document based on the scrollbar's position, and align the Markdown editor to that approximate location. This alignment does not need to be accurate.
@frank-zsy frank-zsy added the kind/feature Category issues or prs related to feature request. label Nov 9, 2024
@wangyantong2000 wangyantong2000 self-assigned this Nov 9, 2024
@wangyantong2000
Copy link
Collaborator

  • When a user selects a portion of text with their mouse, move the button to launch the editor near the selected text to facilitate quick access to the editor.
image

Is this expected to achieve a similar effect, or does it mean something else.

@frank-zsy
Copy link
Contributor Author

Yes, this is exactly what I mean~

@wangyantong2000
Copy link
Collaborator

For the second point, how to adjust the position of the navigation bar for the content in the stackdit. There is no similar functionality in the stackdit API.
If scrolling through stackdit to control page sliding, there is still a cross domain issue.

image image image

@frank-zsy
Copy link
Contributor Author

I just assume this will be quite helpful for long document but I am not sure this is feasible or not. I need do some experiment first and I think this may involve some hacking into StackEdit source code.

@frank-zsy
Copy link
Contributor Author

I can not find any method to do this neither so I opened an issue on StackEdit GitHub, but don't count on it because the project is not active for a long time. I think we can hold the issue and wait for a response. benweet/stackedit#1856

@wangyantong2000
Copy link
Collaborator

截屏2024-11-11 18 52 11 One more thing to add is the initial position of the button. Is the initial position reflected in the configuration file or elsewhere? Add a return item in the configuration file that represents several common positions such as top, bottom, left, right, bottom right, top right, etc

@frank-zsy
Copy link
Contributor Author

frank-zsy commented Nov 11, 2024

@wangyantong2000 Yes, the initial button position is very important, it should be in the config file. We can use common positions instead of x, y position numbers, this will be quite friendly for config. This could be a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Category issues or prs related to feature request.
Projects
None yet
Development

No branches or pull requests

2 participants