Yep -- there they are. Mysteriously named --
Digging through the source, in the /configuration/ subdirectory you will find the display_settings.jsp. Here you will find this:
and if we look at the AssetPublisherDisplayContext.getDisplayStyles(), the mystery of how they get into the list is solved.
... so looks like you can control this list from the Control Panel > Configuration > System Settings > Assets > Asset Publisher (widget scope). I guess this means you can add your own with aJSP hook and then configure the name of the file in the config settings. Very cool. Thanks for the helping hand Olaf!
- view_asset_entries_table.jsp
- view_asset_entries_title_list.jsp
- view_asset_entries_list.jsp
- etc.
Digging through the source, in the /configuration/ subdirectory you will find the display_settings.jsp. Here you will find this:
<div class="display-template">
<liferay-ddm:template-selector className="<%= AssetEntry.class.getName() %>" defaultDisplayStyle="<%= assetPublisherDisplayContext.getDefaultDisplayStyle() %>" displayStyle="<%= assetPublisherDisplayContext.getDisplayStyle() %>" displayStyleGroupId="<%= assetPublisherDisplayContext.getDisplayStyleGroupId() %>" displayStyles="<%= Arrays.asList(assetPublisherDisplayContext.getDisplayStyles()) %>" label="display-template" refreshURL="<%= configurationRenderURL.toString() %>" />
</div>and if we look at the AssetPublisherDisplayContext.getDisplayStyles(), the mystery of how they get into the list is solved.
public String getDisplayStyle() {
if (_displayStyle != null) {
return _displayStyle;
}
_displayStyle = GetterUtil.getString(
_portletPreferences.getValue(
"displayStyle",
_assetPublisherPortletInstanceConfiguration.
defaultDisplayStyle()));
return _displayStyle;
}
... so looks like you can control this list from the Control Panel > Configuration > System Settings > Assets > Asset Publisher (widget scope). I guess this means you can add your own with aJSP hook and then configure the name of the file in the config settings. Very cool. Thanks for the helping hand Olaf!
Fair enough. But then ... WHY AREN'T THEY ADTs ALREADY?!
I have taken "the alternate" approach a few times in the past though when I had to build something ALMOST the same with just a few tweaks. Some of those JSPs would be difficult-to-complicated to turn into ADTs -- and you might not have access to some of the classes you need maybe? Like the AssetPublisherDisplayContext?
I have taken "the alternate" approach a few times in the past though when I had to build something ALMOST the same with just a few tweaks. Some of those JSPs would be difficult-to-complicated to turn into ADTs -- and you might not have access to some of the classes you need maybe? Like the AssetPublisherDisplayContext?
Community
Company
Feedback