- SamuelBernou changed review status to Awaiting Review
- 3 mo
This addon helps interact with filesystem locations relative to current blend file.
Here is a video demo of the main features : https://www.youtube.com/watch?v=MUz2RAfHA3I
See here for illustrated doc : https://github.com/Pullusb/SB_path_actions
The main feature: A cute little folder button appear on header's top-right that will open current blend's folder in OS file browser.
Modifier-keys + click on the button to trigger other actions:
Ctrl+Click
: Copy file pathCtrl+Shift+Click
: Copy directory pathAlt+Click
: Copy file nameShift+Click
: Open Side BlendClicking on filename open it in your current instance (careful, no warning) Clicking on the blender file icon open the file in another instance.
Add a shortcut to pop up a search field to open blends from history (Ctrl+ Shift + Alt + o
).
Add buttons to open blender app related folders (addons, config, etc).
Open any addons folder (button in list or using search feature)
Button to set browser where the blend is
Button to open browsed folder in operating system file browser.
This is called through F3 search operator, (if you have developer extras
enabled in preferences > interface)
If developer mode is ticked in preference, another button appears at the top corner next to the folder icon. It triggers a full refresh of the blend (launch the file in a fully new blender instance and close the current),
Useful for super quick reload when developing addons without IDE debugger.
List permissions in manifest file
permissions = ["files", "clipboard"]
This extension requests the following permissions:
Add-on expects to have access to filesytem.
Add-on can read and write to the system clipboard.
Converted to Draft
Ready for review
Thanks for the submission Samuel.
I think one this this is missing is the obvious permission for Files :) When you update I'll approve.
Ah, I didn't see it was commented out in toml file ! I need syntaxic coloration for those files type :) ! Now fixed.
Thanks!
Hey everyone,
Just a heads-up about a recent change regarding the licensing of add-ons on the Blender extension platform. Moving forward, all add-ons will need to be released under the GNU/GPL 3.0 license (SPDX:GPL-3.0-or-later). This is mainly to keep things simple and consistent across the board.
Previously, we accepted various licenses as long as they were compatible with Blender’s distribution. However, to avoid any confusion and streamline the process, all add-ons using the bpy API should now be presented as GPL 3 (the same license the Blender bundle is distributed). Regardless of whether the original code was under GPL 2, or something else like MIT or ZLIB.
Existing add-ons versions won't be affected. However, new updates will need to comply to the revised requirements.
Thanks for understanding, and feel free to reach out if you have any questions.
Sign in to comment.
Ready for review