Lukas Ocilka wrote:
Duncan Mac-Vicar Prett wrote:
Lukas Ocilka wrote:
It's not a good idea to put that icon to your RPM because user can have several icon-themes installed in /usr/share/YaST2/theme/ directory at once. The current theme in use is symlinked from the "current" directory ... and yes, we know it is confusing :) ;) we now it is not ideal ...
(back to the old discussion), it actually makes sense. Otherwise a theme has to know all icons for all modules.
Continuing with the old discussion ...
What actually makes sense? To package your own icons? Of course it "makes sense" but *not* with the current implementation, we have to change the core functionality, define rules first:
* order of paths to search for icons * default paths * packaging rules
Would you like to create an easy to understand proposal how to change the current behavior with minimal effort for developers that use it?
Well, the pattern is there, the proposal would need to get the YaST paths there, still needs to be done.
That would need to have a designer creating all the icons for all themes.
No, nothing is worse than in the current case. It fixes sane dependencies (no need to update the theme package all the time). The designer provides icons for the themes he can provide icons to (normally at least one per icon). Is reposability of the iconloader to get the right one given name and size, and doing the right fallback if certain themes are not available. The logic of the fallback (ie: try to use the most similar theme) is encapsulated there. Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org