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

Added a keymap for VS Code #7682

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Conversation

rothardo
Copy link
Contributor

@rothardo rothardo commented Aug 17, 2024

Description:

This is a draft pull request designed to facilitate the migration of keybindings from VSCode to NetBeans, aiming to ensure a smooth transition for users without altering their familiar keybinding setup.

Fixes the Issue

Add a keymap for VS Code #6458

Changes:

  • Mapped VSCode Keybindings: Replaced the keybinding file names and actions from VSCode with their corresponding NetBeans equivalents.
  • Preserved Functionality: Maintained the original functionality of keybindings to provide a seamless transition.

Current Status:

  • Partial Functionality: While several keybindings have been successfully mapped, only a few are currently working as intended. For example, the A-F1.shadow file is mapped to the VSCode equivalent action, but issues remain in accurately mapping actions such as Actions/Window/org-netbeans-core-windows-actions-SwitchToRecentDocumentAction.instance.

Next Steps:

  • Action Mapping: I am still working on identifying and mapping the correct actions from the stringvalue attribute in NetBeans to ensure complete functionality.
  • Request for Assistance: I would appreciate any guidance or suggestions on navigating through this process. Additionally, I am exploring alternative approaches to achieve the desired results.

Objective:

Enable users migrating from VSCode to NetBeans to retain their existing keybindings and workflows effectively.

Attachments:

  • Screenshot of the updated NetBeans keymap reflecting the VSCode keybindings.
    Screenshot (543)

By opening this pull request you confirm that, unless explicitly stated otherwise:

  • The changes are all your own work, and you have the right to contribute them.
    Yes
  • The contributions are made solely under the terms and conditions of the Apache License 2.0 (see section 5 of the license for more information).
    Yes

@rothardo rothardo marked this pull request as ready for review August 17, 2024 15:34
@rothardo rothardo changed the title Add a keymap for VS Code #6458 Add a keymap for VS Code Aug 17, 2024
@rothardo rothardo marked this pull request as draft August 17, 2024 15:35
@rothardo rothardo changed the title Add a keymap for VS Code Added a keymap for VS Code Aug 17, 2024
@mbien mbien added Editor VSCode Extension [ci] enable VSCode Extension tests and removed VSCode Extension [ci] enable VSCode Extension tests labels Aug 17, 2024
@mbien mbien linked an issue Aug 18, 2024 that may be closed by this pull request
@rothardo
Copy link
Contributor Author

any comments on this draft?
I want to know how to move forward with this solution actually

@alexmigf
Copy link

alexmigf commented Oct 4, 2024

I would also be interested in this.

@rothardo
Copy link
Contributor Author

rothardo commented Oct 4, 2024

I would also be interested in this.

you have any further ideas onto going forward with this? If yes then we can work collaboratively onto finishing this PR

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

Successfully merging this pull request may close these issues.

Add a keymap for VS Code
3 participants