After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 781035 - Tool Presets Editor as Assets Preset Manager
Tool Presets Editor as Assets Preset Manager
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: General
git master
Other All
: Normal enhancement
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2017-04-07 13:52 UTC by jose americo gobbo
Modified: 2018-05-24 17:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
See Figure 1 - Assets Preset Manager | Proposal (48.50 KB, image/jpeg)
2017-04-07 13:52 UTC, jose americo gobbo
Details
Figure 2 - Assets Preset Manager | Assets Flow (224.98 KB, image/jpeg)
2017-04-07 13:53 UTC, jose americo gobbo
Details
Figure 1 - Assets Preset Manager | Proposal (50.16 KB, image/jpeg)
2018-04-04 12:08 UTC, jose americo gobbo
Details

Description jose americo gobbo 2017-04-07 13:52:04 UTC
Created attachment 349481 [details]
See Figure 1 - Assets Preset Manager | Proposal

1) What is the current Tool Presets Manager
When we use this dialog the first idea is that this effectively a preset editor, but in realty the actions are all related with the assets, only to enable the asset choices made previously on Tool Options instances.

---
2) Proposal in short
My proposal is modify the scope of this editor to control/manage all assets of each tool preset in an effective way.

See Figure 1 - Assets Preset Manager | Proposal
See Figure 2 - Assets Preset Manager | Assets Flow Proposal

* The first improvement is to change the title from 'Tool Presets Editor' to 'Assets Preset Manager'.
* The second thing, is linking all assets of the preset in a visual way, icon, name, enable link of asset on preset.

So, the proposal is to change the current editor in something that really does the managing the assets:

# Which is the asset used and how is, e.g., if it must be linked on the preset or not (actually is the unique option present in this editor).
# Have a big picture of the preset that previously was made by user.

---
2a) Features of the new Assets Preset Manager
The main features of this manager second my proposal are:

* Have the possibility to showing when a tool preset is changing its status -- for instance: 'in editing' (italic style) or 'saved' (normal style).
* Showing all assets linked on the Tool Preset.
* Have the possibility to choose another asset from this manager, clicking on the icon of the each asset (it opens the list dialog of this asset).

The manager have for each preset... all assets that can be used on this kind tool preset:

* Icon Tool Preset button.
* Tool Preset Name.
* Icon Asset button preview for each asset.
* Asset Name.
* Check to apply/link or not the asset on the current tool preset [change the asset status on the gtp archive].
* Author Notes field.
Comment 1 jose americo gobbo 2017-04-07 13:53:10 UTC
Created attachment 349482 [details]
Figure 2 - Assets Preset Manager | Assets Flow

All Flows with the Proposal.
Comment 2 jose americo gobbo 2018-04-04 12:08:16 UTC
Created attachment 370525 [details]
Figure 1 - Assets Preset Manager | Proposal
Comment 3 Michael Natterer 2018-04-04 12:39:35 UTC
Thanks. Seems to make a lot of sense to be able to edit the actual object
instead of just checking "use saved foo".

I don't think we need to rename the thing, it's still editing tool presets.
Comment 4 jose americo gobbo 2018-04-04 12:48:00 UTC
> I don't think we need to rename the thing, it's still editing tool presets.
I think that you have the reason... between 'Asset Preset Manager' and 'Tool Presets Editor' we are talking about the same thing with other words ;-)
Comment 5 GNOME Infrastructure Team 2018-05-24 17:43:03 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/1083.