ofn3-resource-manager

[Ofnuts]

A partial rewrite and conversion of the ofn-addon-manager for Gimp v3

Some changes:

• No longer supports scripts (who has so many scripts anyway)
  
• INI file syntax is a bit different to take advantage of Python3 capabilities
  
• Always activates collections as directories
  
• Not longer explicitly maintains a list of activated collections or resources. A folder in the active Gimp folder that has the same name as one in the storage folder is considered to be the activated  instance.
  

Plugin is here (note: inaugurating new "management" section).

Enjoy.

[saberwarthog]

Thanks a lot for your work !
But it seems to me that the archive is lacking some of the py files, namely "configuration.py", "container.py" & "manager.py" ?
At least gimp doesn't seems to find the module called 'configuration' when it's querying the ofn3-resource-manager.py file (it gaves an error on line 49).


(unless i missed something, which is quite possible)

[Ofnuts]

You are perfectly correct. Uploaded fixed (I hope) package.

[saberwarthog]

Yep, it works !
I was even able to point to another folder in my Home as I did on the previous version, but the ini file is way easier to understand & modify now.

The only (extremely minor) problem is that the "manage set" line in each of the assets menus is at a different place, but that's not really a problem to me, because the manager does work beautifully ! 
(I think it's simply because some menus have specific lines for the assets, like all of the brushes creation options, if I'm ever bothered by this in the future I'll find how to properly rearrange that)
(Funnily, the "Dynamics" one create a submenu under the Dynamics menu... it may come from the localization ? Idk, but I don't have personalized dynamics, soo...)

Thanks a lot again, this plugin has helped me for a long time on the previous version of Gimp & it is one of the plugins I have in mind for a future presentation about the Gimp & FOSS software at work in the future.

[Ofnuts]

(6 hours ago)saberwarthog Wrote: The only (extremely minor) problem is that the "manage set" line in each of the assets menus is at a different place, but that's not really a problem to me, because the manager does work beautifully ! 
(I think it's simply because some menus have specific lines for the assets, like all of the brushes creation options, if I'm ever bothered by this in the future I'll find how to properly rearrange that)

I have no control over that. The menu label is inserted in alphabetical other in the midst of all other additional functions for that specific dialog.

(6 hours ago)saberwarthog Wrote: (Funnily, the "Dynamics" one create a submenu under the Dynamics menu... it may come from the localization ? Idk, but I don't have personalized dynamics, soo...)

This comes from this bug which implies that we have to know the actual phrasing of the menu to insert our thing. In 2.10, we could just use <dynamics>, now we have to also use the actual main menu label and the rules used for other resources:  brushes and Brushes Menu don't work for dynamics (<dynamics> and Paint dynamics Menu). If that bothers you can can replace the menu_path for [dynamics] in the configuration file.

OTOH I don't expect people to have so many dynamics that the manager is really helpful there and they can be disabled.

[saberwarthog]

(6 hours ago)Ofnuts Wrote:

(6 hours ago)saberwarthog Wrote: The only (extremely minor) problem is that the "manage set" line in each of the assets menus is at a different place, but that's not really a problem to me, because the manager does work beautifully ! 
(I think it's simply because some menus have specific lines for the assets, like all of the brushes creation options, if I'm ever bothered by this in the future I'll find how to properly rearrange that)

I have no control over that. The menu label is inserted in alphabetical other in the midst of all other additional functions for that specific dialog.

Oh then it would be easy for anyone to arrange then, it's only a question of finding a menu label for each asset type that would get it at a place someone wants, and putting it in the specific section devoted to it in the ofn3-resource-manager.ini file.

Ofnuts

Quote:This comes from this bug which implies that we have to know the actual phrasing of the menu to insert our thing. In 2.10, we could just use <dynamics>, now we have to also use the actual main menu label  and the rules used for other resources:  brushes and Brushes Menu don't work for dynamics (<dynamics> and Paint dynamics Menu). If that bothers you can can replace the menu_path for [dynamics] in the configuration file.


OTOH I don't expect people to have so many dynamics that the manager is really helpful there and they can be disabled.

Indeed, the diverse dynamics already in place covers already a lot of possible use case... I use 1 or 2 maximum anyway.