Would it help to do the following?
1. Create one module per cluster where we pull all the images together.
2. Add some API around the icon names, so the place of the usage would
be decoupled from the place of the storage.
3. Normalize the storage inside the icon module
3. Create some build check that detects direct icon usage, that may or
may not fail the build...
There is two 3. point as they can be done in parallel.
On 9/18/20 9:17 AM, Neil C Smith wrote:
On Fri, 18 Sep 2020 at 17:04, Jeremy Cavanagh <jeremy.cavan...@orange.fr> wrote:
We need a different approach to the icons, they should be held in a
single place. At the moment they are littered throughout the code like
discarded toffee wrappers.
+1 to all of it, particularly +1 to this. I've said before I think we
need an icon strategy with logical names in modules. eg. something
akin to
https://specifications.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html
In particular the use of dashed names for icon hierarchies is nice.
And it opens up the possibility for anyone to make up icon sets for
the IDE or a platform application.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
