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

Ideas for enhancing markbind serve -o #1405

Open
2 of 3 tasks
ang-zeyu opened this issue Dec 5, 2020 · 1 comment
Open
2 of 3 tasks

Ideas for enhancing markbind serve -o #1405

ang-zeyu opened this issue Dec 5, 2020 · 1 comment

Comments

@ang-zeyu
Copy link
Contributor

ang-zeyu commented Dec 5, 2020

Is your request related to a problem?

markbind serve -o allows serving a single page from a site quickly without building the whole site, and rebuilds the page whenever its dependencies change. It also allows for on-demand building of other pages when navigated to.

Issues:

  • Still some amount of time spent observing the spinning logo wheel 🤔
  • Author cannot 'develop on multiple tabs', because only the last visited page is tracked for dependency changes.
  • Search results are only available for the pages that are built, and may be outdated for some pages.

Describe the solution you'd like

Some ideas:

  • Maintain a most-recently-visited list of pages instead of just tracking the last visited page Track all opened pages in browser according to last visited (Lazy serve: Track opened pages for dependency changes #1513), then rebuild these pages in order of most-recent when any of their dependencies change
  • Page removals / additions - apply the same idea of lazy building (no new pages should ever need to be built in which case, but, flagged for building when visited later) (pages may need to rebuilt however (missing page-dependencies-turned-non-missing)
  • Background building / rebuilding of pages not in this most-recently-visited list, allowing search results to be gradually populated
  • Maybe with these enhancements, we can make markbind s -o the default behaviour

Additional context

Original issue: #1007

@kaixin-hc
Copy link
Contributor

@ang-zeyu Hi! Could you explain this unchecked point a bit more, I don't really understand

Page removals / additions - apply the same idea of lazy building (no new pages should ever need to be built in which case, but, flagged for building when visited later) (pages may need to rebuilt however (missing page-dependencies-turned-non-missing)

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

No branches or pull requests

2 participants