Addon Installation Consistency #50273

New Issue

sicutunum · 2016-12-18T19:00:25+01:00

sicutunum commented

2016-12-18 19:00:25 +01:00

This simple logic tree would solve a lot of confusion for installing 3rd party addons and can be easily implemented with Python OS functions.

• Case. Trying to install Addon.py shipped in a zip file (small addons are often delivered via zip file with other documentation or external assets):

User presses Install with zip file selected
    Zipped folder not contain __init__.py? 
        Import Addon.py file found in folder into addons only.

The second tree would use a pop-up message to ensure the init.py parent directory was for the actual addon and not a large system folder or some other unintentional thing (before proceeding with import).

• Case. Trying to install init.py file in a folder that must be zipped to be installed (should a browser automatically unzip the download or else user does unknowingly):

User presses Install with __init__.py file selected
    Get parent directory of __init__.py
        Invoke pop-up message "Do you want to install the addon",parentDirectpry,"?"
            Import parent directory as though zipped.

This simple logic tree would solve a lot of confusion for installing 3rd party addons and can be easily implemented with Python OS functions. • Case. Trying to install Addon.py shipped in a zip file (small addons are often delivered via zip file with other documentation or external assets): ``` User presses Install with zip file selected Zipped folder not contain __init__.py? Import Addon.py file found in folder into addons only. ``` The second tree would use a pop-up message to ensure the __init__.py parent directory was for the actual addon and not a large system folder or some other unintentional thing (before proceeding with import). • Case. Trying to install __init__.py file in a folder that must be zipped to be installed (should a browser automatically unzip the download or else user does unknowingly): ``` User presses Install with __init__.py file selected Get parent directory of __init__.py Invoke pop-up message "Do you want to install the addon",parentDirectpry,"?" Import parent directory as though zipped. ```

sicutunum commented

2016-12-18 19:00:25 +01:00

Changed status to: 'Open'

sicutunum commented

2016-12-18 19:00:25 +01:00

Added subscriber: @sicutunum

sicutunum commented

2016-12-18 19:01:57 +01:00

Removed subscriber: @sicutunum

sicutunum commented

2016-12-19 02:22:06 +01:00

Added subscriber: @sicutunum

Brendon Murphy was assigned by Aaron Carlisle

2016-12-20 18:51:12 +01:00

Brendon Murphy commented

2017-02-21 09:52:56 +01:00

Changed status from 'Open' to: 'Archived'

Brendon Murphy closed this issue

2017-02-21 09:52:56 +01:00

Brendon Murphy commented

2017-02-21 09:52:56 +01:00

I think here it's known that this happens, many 3rd party devs use a folder structure & single file init inside to prevent this issue, possibly a check could be added, not sure if this is overkill or not, 3rd party addons should follow blender guidelines & examples.
Closing as we will think further on this for 2.8.
thanks for ideas.

I think here it's known that this happens, many 3rd party devs use a folder structure & single file __init__ inside to prevent this issue, possibly a check could be added, not sure if this is overkill or not, 3rd party addons should follow blender guidelines & examples. Closing as we will think further on this for 2.8. thanks for ideas.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Addon Installation Consistency #50273