DO NOT REPLY [Bug 18208] - [ENHANCEMENT] Enable "skinning" of action images

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18208>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18208

[ENHANCEMENT] Enable "skinning" of action images

weaver@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



------- Additional Comments From weaver@apache.org  2003-03-28 17:37 -------

per mine and Aurelien Pernoud's discussion, here is a revised version of
skinnable images:

NOTE: the getImage functionality is not limited to just action images. 
Theoretically, the skin developer could use this functionality for all types of
images including the portal logo by slightly modifying the controls/controllers.

Order of precedence when PortletSkin attempts to locate an image path through
the PortletSkin.getImage() method:

1. "image-{image name}" defined as a property within the current skin where the
value is the webapp-relative path of the image.

2. For the sake of a "clean" registry, the skin developer has the option, within
a a skin, to define a property, "image.paths", which would be a comma-delimited
list of directories, realtive to the {webapp.home}/images/{preferred media type}
directory, in which PortletSkin would attempt to located the requested image. 
For this to work, PortletSkin would have a setCapabilityMap() method that is
populated by the PortalToolKit service at PortletSkin creation time.  The image
name may or may not have an valid image extension (.gif, .jpg or .png).  If no
extension is provided, the skin will check the file system for the existence of
the image name plus each one of the valid image extensions within each of the
supplied image paths.  If the extension is supplied, we just check the file
system without appending each of the image extensions.

3. For an "the cleanest" registry, the skin developer can choose to specify
neither "image-{image name}" properties nor and "image.paths" attribute i.e. no
registry modifications whatsoever.  In this case, the same approach is used as
in step 2 now using the skin's name as opposed to the values in the image.paths
as the directory to look under.

Thanks to Aurelien Pernoud's great suggestions on alternative ways to implement
the skinnable inages.

-scott

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org