Icons in modules admin not displayed if is custom, this is a bit negative for customization, should have priority those modules rather than those of the media folder.

We forced to create another appropriate code for modules or you change the class in this sense?

Quote:

I do not understand! You put your icons in media folder.

Quote:

Now I don't know what you decided, but a few years ago when it came out the version 2.5.5 we talked via email with mamba and he told me not to weigh the Frameworks folder for the module icons, you must create a folder in modulename/icons/32, so all modules can have their own icons.

Given what you say, we can send in the media folder without any problems?

If so, why in other modules I have seen folders icons/32, and what are they for?

what i think he is talking about how xoops load the icons used in navigation render
i think its better that way because xoops check if they exist in /media folder if not he check in /module/icons/32 so you can custom it

EDIT: btw the 32 works fine but the 16x16 icons dont load in the info boxes genrated by module admin

The goal for us is to have a full set of "standard" icons, that can be used consistently for all XOOPS modules. This way the user is not confused by different icons that represent the same action (like Edit or Delete or View).

The current set is based on Crystal Icons, and I hope, will be able to provide the whole set as a sprite.

If the user (or theme designer) chooses, they can provide another set of icons, that would be placed in a theme folder, as Irmtfan suggested in another thread, and XOOPS would use them, instead of the default set.

The most important issue is that all modules will use the same set of icons, instead of each module using something different. This is similar to a theme - users can select any theme they want, and all modules will use it in the front end.

yes. as i stated somewhere it would be the best solution if we could leave core and modules untouched for all kind of customization. so with an update you can safely just copy paste the new core/module codes.
IMO all front side customizations (templates/css/js/images/icons/ even translations) should/could be done in themes. here the priority would be:
1- themes/THEME/modules/MODULE/icons/32 (IF EXIST for specific theme)
2- themes/default/modules/MODULE/icons/32 (IF EXIST for default(all) themes)
3- CORE260/media/xoops/images/icons/32 (IF NOT EXIST get from the core)

the issue is i still cannot see any standard for images | icons.
even a simple decision for "images" and "icons" folder locations are not consistent even in core 260

see:
CORE260/media/xoops/images/icons/32

then in system module:
CORE260/modules/system/images/icons

but in other modules:
CORE260/modules/page/images
CORE260/modules/page/icons

CORE260/modules/logger/images
CORE260/modules/logger/icons

just a simple standard for the location is required. images/icons OR /images and /icons.

personally i prefer to see all front side materials (templates(html files
)/css/js/images/icons/translations) in MODULE/templates folder. it will reduce the number of folders in each module root significantly and will make life easier for a webmaster like me that want to set a tight permission for his designer. (then I just need to define a ftp access to MODULE/templates and then for some other customization to themes folder)

In modules for custom icons just add in admin/menu.php as follows:



but if you want to use the icons in the media folder, as follows:



No need to add more code php of what already exists in the moduleadmin class, for the modules

Quote:

you can already do that its just


then it runs the tests
CORE260/media/xoops/images/icons/32 (IF EXIST get from the core)
modules/MODULE/icons/32 (IF EXIST get from MODULE)
but then if it doesnt exist it display an error image when it should have a default xoops icon instead imo.

Quote:

Yes Tarik! is true...!
(IF EXIST get from the core)
otherwise
get from MODULE

but if the same name of icons in module exists in the core, then changed it's name to module

yes, but still this test only on 32x32 icons but 16x16 icons for the info boxes in module admins are only got from core media folder.