Hello, Thank you! I have another unrelated question, if you don't mind (someone else asked me this question, but I don't really know the answer):
The person wants to write a portlet that will change its layout somewhat depending on the column width. For instance, if I have have the portlet on my page and I go and change my page layout from one-column to two-column, he wants his portlet to be able to detect that and rearrange its HTML some, to accommodate the new width. I think that he was hoping to accomplish this with some javascript that triggers on load, but I think that page layout changes do not trigger a page refresh, just some ajax, so his script is not firing off again. I am thinking that some javascript that detects div resizing (maybe http://api.jquery.com/resize/ or something like that) might work, but I figured I would ask in case there is some portlet-specific trigger or API or something that I don't know about. So the question is something like: is there a good way for a portlet to "find out" that the page layout has been changed, so that it can reorganize itself? Thank you! Jerry On 12/22/10 9:00 PM, "Eric Dalquist" <eric.dalqu...@doit.wisc.edu> wrote: >I believe we try very hard to make the skin and theme stable per minor >release. So a skin or theme that works on 3.2.0 will work on 3.2.1, >3.2.2, ... > >There are changes between 3.1 and 3.2 for example that generally require >some tweaking of the skin and theme. Essentially what we do is look at >the diff between our customized 3.x portal and then apply those changes >to our new 3.y portal. It is a little work but generally a good idea >because then you can really take advantage of new features in the themes >and skins that would not work if you just whole-sale copied your old >files over. > >-Eric > >On 12/20/10 4:21 PM, Jerry Shipman wrote: >> Hello, >> I am fairly new to uPortal - I apologize if this is too dumb of a >>question. >> >> I've been working on a custom "theme" and "skin". We started by taking >>the "universality" theme and I think the "ivy" skin, and making changes >>from there. >> >> My question is as we upgrade through minor revisions in uPortal >>(3.2.x), will I have to edit the theme and skin at all? If so, how will >>I be able to figure out what I have to change? >> >> We've avoided changing any skin javascript, which I think will help a >>lot. I've just been changing theme XSL files, and skin CSS files. (and a >>few peripheral things like skinList.xml.) >> >> For a bonus round, how much would I have to worry about upgrades that >>aren't classed as minor (e.g. from 3.2.x to 3.3.x)? >> >> I did notice that from 3.2.1 to 3.2.2 there was a change in the >>javascript for the skin (related to "channelID" changing from a string >>to an integer in some "preferences"-related ajax call). So, I am a >>little worried because of that. But, maybe changes to the javascript are >>more common than changes to the XSL or CSS? >> >> Thank you, >> Jerry >> > -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
