1. Move the portlet JS into it's own file in uportal-war/src/main/webapp/media/skins/universality/common/javascript then add that file to uportal-war/src/main/webapp/media/skins/universality/common/common_skin.xml 2. Move the portlet CSS into uportal-war/src/main/webapp/media/skins/universality/common/css/portlet.css
Other than that the changes look great! -Eric On 10/05/2011 06:46 AM, Arvīds Grabovskis wrote:
Hi,Yesterday on IRC there was a little conversation about Translator portlet that would enable database entity translation. I've created a very simple wireframe of a portlet and attaching it to email. Everything is intended to be loaded by AJAX - by selecting entity type to translate, appropriate values to translate will be loaded. For example, if one selects portlet definition to translate, then all portlet definitions will be loaded into list and upon clicking each portlet, translation form will be enabled.If entities can be added (like in case with message keys), then additional creation form will be available.Currently i see only two entity types to be translated - portlet definitions and messages (see https://issues.jasig.org/browse/UP-3097). In future groups and layout structure elements can be added.I'd love to hear your thoughts about it. -- Arvīds -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
smime.p7s
Description: S/MIME Cryptographic Signature
