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 request: ability to close Kanban #21

Open
katchy3132 opened this issue Feb 27, 2022 · 4 comments
Open

feature request: ability to close Kanban #21

katchy3132 opened this issue Feb 27, 2022 · 4 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@katchy3132
Copy link

When I use the Kanban, I usually want to check it , make a modification and then switch to another note and put the screen space to better use . Currently the only way to get the Kanban off the screen is to switch to another notebook - something easier to use - would be much appreciated.

two ideas :

  1. Put an an "X" to close the panel - maybe a keyboard shortcut too .
  2. Just have the Kanban on screen when the Kanban note is open - if you switch to anther note it disappears.
@mablin7 mablin7 added enhancement New feature or request good first issue Good for newcomers labels Mar 2, 2022
@VikramDigra
Copy link

i want to work on this issue please assign me

@PackElend
Copy link
Collaborator

PackElend commented Jan 9, 2023

@VikramDigra No need to asign anyone, just said you want to work on this so simply do it 🙂

@benlau
Copy link
Collaborator

benlau commented Jun 16, 2023

For those who may be interested, I have made an experimental implementation in my forked branch:

  • Added a close button to the left of the title.
  • Disabled auto-closing of the board on note changes.

It is still under testing. I will clean up the code and make a pull request (PR) later.

https://github.com/benlau/joplin-plugin-kanban

@PackElend
Copy link
Collaborator

@benlau we are still searching for a new maintainer but as you familiar (a bit) with the codebase of the plug-in would are ok with checking the other PRs.
I can't call myself experienced enough, but if some of the others would check each other's PRs, it can be said that the code is safe, so I merge it.
At least there would be some progress
thx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

5 participants