[uportal-dev] trunk skin.xml organization

[Eric Dalquist]

I'm updating the resource aggregator in trunk and noticed that most of the skin.xml files have css entries that alternate source paths like:

 <!-- For layout of portlet content. Common to all skins using the universality 
theme. -->
  <css>../common/css/layout-portlet.css</css>

  <!-- Visual style for the portal. -->
  <css>portal.css</css>

  <!-- Default visual style for portlet content. -->
  <css>../common/css/portlet.css</css>

  <!-- Local skin override for visual style for portlet content. -->
  <css>portlet.css</css>

  <!-- Support for legacy uPortal css classes. -->
  <css>legacy.css</css>

  <!-- Styles for the tokeninput jQuery plugin. -->
  <css>../common/css/token-input.css</css>




 <!-- For layout of portlet content. Common to all skins using the universality 
theme. -->
  <css>../common/css/layout-portlet.css</css>

  <!-- Default visual style for portlet content. -->
  <css>../common/css/portlet.css</css>

  <!-- Styles for the tokeninput jQuery plugin. -->
  <css>../common/css/token-input.css</css>

  <!-- Visual style for the portal. -->
  <css>portal.css</css>

  <!-- Local skin override for visual style for portlet content. -->
  <css>portlet.css</css>

  <!-- Support for legacy uPortal css classes. -->
  <css>legacy.css</css>

I wanted to check with Gary & Matt if we could re-order these CSS files so that all of the files from a specific directory are listed together. Due to CSS using relative URLs internally for images and such the aggregator can't group files from different directories together and it honors ordering. So for the above example from SVN we end up with 5 CSS files after aggregation. If we could re-order the CSS files like below we would end up with 2 files:

smime.p7s
Description: S/MIME Cryptographic Signature