Extend image helper, then wrap in xhp about concrete5-xhp HOT 3 CLOSED

After implementing the form helper, I'm questioning if getThumbnailXhp() type of logic is ever necessary. The naming conventions would get confusing, and it might collide with overrides for the most commonly overridden classes. It's also not always true that one helper == one class.

The entire concept of a 'helper' is completely unnecessary from the view if you're on xhp, so I should be ignoring those. Instead, just define new elements, which may need to reference helper logic if that's the best way to get the data needed.

from concrete5-xhp.

One thing I hadn't considered, is that these images will frequently just be added as style attributes, for when they're set as the background of an element. Perhaps the avatar is a more useful place to start.

from concrete5-xhp.

Added the avatar in a57a40e
It's composed of the element, so any img attributes you add that aren't picked up will fall through to the rendered .

Simply call like:
<c5:avatar user={$ui} aspect-ratio="0.9" />
and it will render the avatar for that user. If no avatar is set, it will fall back to the default image for avatars (same as the ConcreteAvatarHelper.)

from concrete5-xhp.