User avatar sizes differ from widget to widget

[bchapin]

Icon sizes range in size from widget to widget - in both the dashboard and group views.

[cash]

Do you have a screenshot of this?

[bchapin]

Attached file.

[cash]

OK - you are referring to the avatar sizes - I understand now

[bchapin]

Right... avatars. I tend to lump them all under icons...

[cash]

Yeah, we introduced the term avatar in 1.8 to keep distinguish them - especially since we put a lot of time into having better support for icons.

[bchapin]

Makes sense. Something about avatar reminds me of sci fi... in a bad way - but I'll adjust. So I am unfamiliar with what was added for better icon support. Can you enlighten me?

[cash]

Sure. We now have a set of sprites and you can use them like this: elgg_view_icon('delete')

There were other improvements but that is the main one. Before ever time you wanted to add an icon, it involved a lot of ugly cut and paste.

[cash]

Looks like this is mainly the activity widget using large user avatars. The pages and file plugin also may want to use a smaller version of their icons if one is available.

[brettp]

This inconsistency is a larger problem throughout the site--It's only mirrored here because of the object / river views. Do we:

• Use the same size icons in widgets as the river / entity listing pages? (Makes /activity/ look a little cramped.)
• Use smaller icons in widgets, and larger icons on listing pages? (Would require logic in views for context.)
• Use small icons on widgets, and not care about the listing pages. (Less logic in views.)

[brettp]

Pushing this out to 1.8.5 since fixing the activity stream widget involves touching all the river views.

[Brett Profitt <brett.profitt@…>]

In 29606e1ecc874452f4d047a25e07755fcb7d7ac4/elgg:

Refs #3907. Changed river icons to tiny size if used within a widget.

[brettp]

• Files don't create a tiny size thumbnail.
• Pages don't have a tiny size icon.
• The Friends widget has a size setting.

I don't think these changes are appropriate for a bugfix release, so I've created tickets (#4967, #4966) for the other issues we can resolve in 1.9.