[dev] [commits] Horde branch master updated. a96642d3db2e2910d3ad0c3d6224e4d214a4c224

[Ben Klang]

On May 18, 2010, at 2:21 PM, Michael M Slusarz wrote:

> Quoting Ben Klang <ben at alkaloid.net>:
> 
>>> You should be using Horde::img() (which, in turn will use Horde_Themes::img() to get the image URI) in places where you want to output an img tag for the image. Horde_Themes::img() only returns an object with the URI for the image...
>>> 
>> In both of these places I specifically do not want an <img> tag.  The Horde_Themes::img() feels a little ugly here (especially vs. what we did in Horde 3), but it was the only option I saw.  Any other suggestions?
> 
> What is ugly about Horde_Themes::img()?  In other words - what do you need to get back that can't currently be done?  This is useful information as we (read: me) try to finish up the API in this area.
> 
The main problem I had was trying to create non-HTML image references.  The old way of

$registry->getImageDir()
is simpler than
Horde_Themes::img(null, array('notheme' => true, 'nohorde' => true))
which was the only way I found to get the application's image directory without an image tag.  But this objection may be obviated by what you said next:

> Do note that doing something like grabbing an image dir and then manually appending various image names to it is  NOT supported in H4.
Well I guess I didn't realize that was the case.  I'll have to go back with that perspective and see if I can use Horde_Themes::img() to do that for me.

/BAK/
-- 
Ben Klang
Alkaloid Networks LLC
ben at alkaloid.net
404.475.4850
http://projects.alkaloid.net