Re: [uportal-dev] Recommend SASS for CSS development
This looks really cool and looks like it would REALLY simplify the uPortal CSS code. Especially with the variable replacement bits would it be valuable to move adopters to use the SASS files as well? I know I'd love it if I could change all the occurrences of the blue tab background by just tweaking a variable in one location. Also the syntax looks close enough to CSS that I don't think it would be too onerous for people to get familiar with. If this is valuable we could look at if it is possible to fold the SASS - CSS generation into the uPortal build so we just have SASS files in the source and the CSS files are all created at build time. -Eric On 05/10/2011 11:33 AM, Gary Thompson wrote: Hey all, I heard about SASS (http://sass-lang.com/) not long ago, and had an opportunity to use it in the recent uPortal Mobile work. In my opinion, SASS is CSS Awesome. It is everything that CSS development should be, and makes CSS truly programmatic with things like variables, mixins, loops, and functions. I will be using SASS for all my future CSS development. I'd like to recommend using SASS for uPortal CSS development. Impacts to uPortal: For front-end developers, an uptake of SASS. Source code CSS would be done in SASS. SASS exports to pure CSS, which would be the uPortal skins. SASS runs on Ruby. CSS development and maintenance becomes *much* easier. For portal adopters, the impact is probably nothing. Adopters would be working with the resultant CSS file (and likely never interface with SASS), and any customizations to a skin would be done in the same manner as before. Thoughts? Gary -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: eric.dalqu...@doit.wisc.edu 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
Re: [uportal-dev] uPortal 4 Release Schedule
Just realized that trunk still depends on a few snapshot dependencies. I can't cut a release with the snapshot dependencies and with the current time frame I'm just going to skip the M2 release. We will still be having an RC1 release next week. -Eric On 05/05/2011 01:28 PM, Eric Dalquist wrote: Well due to the time-sucking wonders that was a state-wide HR system upgrade I lost a big chunk of time for uPortal 4 work. Just to keep everyone here in the loop the current plan is to do a uPortal 4.0.0-M2 on 5/9 and then get the RC1 cut right before the conference. So if you have new-feature work that you have planned for uPortal 4 please plan on trying to have it complete by 5/18. Thanks! -Eric smime.p7s Description: S/MIME Cryptographic Signature
Re: [uportal-dev] Recommend SASS for CSS development
On 5/10/2011 9:42 AM, Eric Dalquist wrote: If this is valuable we could look at if it is possible to fold the SASS - CSS generation into the uPortal build so we just have SASS files in the source and the CSS files are all created at build time. Sounds perfect. There should be a maven plugin for SASS. drew -- 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
Re: [uportal-dev] Recommend SASS for CSS development
Dojo started using the LESS CSS framework with their 1.6 release. I haven't had a chance to play with it, but it might be a good idea to compare LESS/SASS. http://lesscss.org/ On 05/10/2011 09:33 AM, Gary Thompson wrote: Hey all, I heard about SASS (http://sass-lang.com/) not long ago, and had an opportunity to use it in the recent uPortal Mobile work. In my opinion, SASS is CSS Awesome. It is everything that CSS development should be, and makes CSS truly programmatic with things like variables, mixins, loops, and functions. I will be using SASS for all my future CSS development. I'd like to recommend using SASS for uPortal CSS development. Impacts to uPortal: For front-end developers, an uptake of SASS. Source code CSS would be done in SASS. SASS exports to pure CSS, which would be the uPortal skins. SASS runs on Ruby. CSS development and maintenance becomes *much* easier. For portal adopters, the impact is probably nothing. Adopters would be working with the resultant CSS file (and likely never interface with SASS), and any customizations to a skin would be done in the same manner as before. Thoughts? Gary -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: awh...@calpoly.edu To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- 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
Re: [uportal-dev] Recommend SASS for CSS development
Unfortunately there is not and doubly it is a Ruby app. There is a Maven JRuby plugin that allows you to call a Ruby script from Maven so in theory that should work but before I spend a bunch of time hacking on that I wanted to get Gary's view on having SASS as the primary language we do skinning in instead of CSS. -Eric On 05/10/2011 12:14 PM, Drew Wills wrote: On 5/10/2011 9:42 AM, Eric Dalquist wrote: If this is valuable we could look at if it is possible to fold the SASS - CSS generation into the uPortal build so we just have SASS files in the source and the CSS files are all created at build time. Sounds perfect. There should be a maven plugin for SASS. drew smime.p7s Description: S/MIME Cryptographic Signature
Re: [uportal-dev] Recommend SASS for CSS development
I would love to see Sass in uPortal if at all possible. It will make things a lot easier for both developers and non-developers as it allows for abstraction right in the CSS (complex sets of CSS rules can get abstracted into simple one-line mixins). This kind of abstraction also allows for more semantic and meaningful markup (no more fl-col-C8jk9 class tags). Jacob UX, Unicon - Original Message - From: Bruce Tong zzt...@gmail.com To: uportal-dev@lists.ja-sig.org Cc: jasig-ue jasig...@lists.ja-sig.org Sent: Tuesday, May 10, 2011 10:31:26 AM Subject: Re: [uportal-dev] Recommend SASS for CSS development I'm not familiar with it, so my perspective on SASS could be completely ludicrous. When I see technologies strongly suited to the graphic arts become more programmatic, I worry that the skill set related to it might move from those people to programmers. We already program in something like four languages and there is an industry-wide shortage of programmers. Does SASS raise the bar further or can persons of the graphic arts be as equally effective with it as CSS? If it does raise the bar, does a more programmatic approach really take the industry where it needs to go? I don't want to resist change -- I might find SASS to be really cool -- though I do worry about the big picture not just for uPortal, but other applications as well that universities develop, maintain, and deploy. I'm curious about your perspectives. On Tue, May 10, 2011 at 12:33 PM, Gary Thompson g...@unicon.net wrote: Hey all, I heard about SASS (http://sass-lang.com/) not long ago, and had an opportunity to use it in the recent uPortal Mobile work. In my opinion, SASS is CSS Awesome. It is everything that CSS development should be, and makes CSS truly programmatic with things like variables, mixins, loops, and functions. I will be using SASS for all my future CSS development. I'd like to recommend using SASS for uPortal CSS development. Impacts to uPortal: For front-end developers, an uptake of SASS. Source code CSS would be done in SASS. SASS exports to pure CSS, which would be the uPortal skins. SASS runs on Ruby. CSS development and maintenance becomes *much* easier. For portal adopters, the impact is probably nothing. Adopters would be working with the resultant CSS file (and likely never interface with SASS), and any customizations to a skin would be done in the same manner as before. Thoughts? Gary -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: zzt...@gmail.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- Bruce Tong Software Engineer Office of Information Technology Ohio University -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: jlich...@unicon.net To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- 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
Re: [uportal-dev] Recommend SASS for CSS development
If you're interested in seeing an example of what SASS in uPortal would look like, Gary's been testing it with the uMobile theme. The default skin for the muniversality theme should give a general idea of what some of the code looks like. - Jen On May 10, 2011, at 9:42 AM, Eric Dalquist wrote: This looks really cool and looks like it would REALLY simplify the uPortal CSS code. Especially with the variable replacement bits would it be valuable to move adopters to use the SASS files as well? I know I'd love it if I could change all the occurrences of the blue tab background by just tweaking a variable in one location. Also the syntax looks close enough to CSS that I don't think it would be too onerous for people to get familiar with. If this is valuable we could look at if it is possible to fold the SASS - CSS generation into the uPortal build so we just have SASS files in the source and the CSS files are all created at build time. -Eric On 05/10/2011 11:33 AM, Gary Thompson wrote: Hey all, I heard about SASS (http://sass-lang.com/) not long ago, and had an opportunity to use it in the recent uPortal Mobile work. In my opinion, SASS is CSS Awesome. It is everything that CSS development should be, and makes CSS truly programmatic with things like variables, mixins, loops, and functions. I will be using SASS for all my future CSS development. I'd like to recommend using SASS for uPortal CSS development. Impacts to uPortal: For front-end developers, an uptake of SASS. Source code CSS would be done in SASS. SASS exports to pure CSS, which would be the uPortal skins. SASS runs on Ruby. CSS development and maintenance becomes *much* easier. For portal adopters, the impact is probably nothing. Adopters would be working with the resultant CSS file (and likely never interface with SASS), and any customizations to a skin would be done in the same manner as before. Thoughts? Gary -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: eric.dalqu...@doit.wisc.edu To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- 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
Re: [uportal-dev] Recommend SASS for CSS development
Variables, Nesting, Mixins, and Selector Inheritance all seem okay. It doesn't include logical components like decisions and loops, so I think any concerns I had at first seem unfounded. On Tue, May 10, 2011 at 2:43 PM, Jen Bourey jennifer.bou...@gmail.com wrote: If you're interested in seeing an example of what SASS in uPortal would look like, Gary's been testing it with the uMobile theme. The default skin for the muniversality theme should give a general idea of what some of the code looks like. - Jen On May 10, 2011, at 9:42 AM, Eric Dalquist wrote: This looks really cool and looks like it would REALLY simplify the uPortal CSS code. Especially with the variable replacement bits would it be valuable to move adopters to use the SASS files as well? I know I'd love it if I could change all the occurrences of the blue tab background by just tweaking a variable in one location. Also the syntax looks close enough to CSS that I don't think it would be too onerous for people to get familiar with. If this is valuable we could look at if it is possible to fold the SASS - CSS generation into the uPortal build so we just have SASS files in the source and the CSS files are all created at build time. -Eric On 05/10/2011 11:33 AM, Gary Thompson wrote: Hey all, I heard about SASS (http://sass-lang.com/) not long ago, and had an opportunity to use it in the recent uPortal Mobile work. In my opinion, SASS is CSS Awesome. It is everything that CSS development should be, and makes CSS truly programmatic with things like variables, mixins, loops, and functions. I will be using SASS for all my future CSS development. I'd like to recommend using SASS for uPortal CSS development. Impacts to uPortal: For front-end developers, an uptake of SASS. Source code CSS would be done in SASS. SASS exports to pure CSS, which would be the uPortal skins. SASS runs on Ruby. CSS development and maintenance becomes *much* easier. For portal adopters, the impact is probably nothing. Adopters would be working with the resultant CSS file (and likely never interface with SASS), and any customizations to a skin would be done in the same manner as before. Thoughts? Gary -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: eric.dalqu...@doit.wisc.edu To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: zzt...@gmail.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- Bruce Tong Software Engineer Office of Information Technology Ohio University -- 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
Re: [uportal-dev] Recommend SASS for CSS development
I hate to keep posting. Y'all have no-doubt thought through all of this already. I talked with a couple of our graphic artists about SASS. They were intrigued by the new ideas SASS brings to the table, and there were some observations that may, or may not, apply to the portal. They usually work in sites that are far less complex that the portal's CSS. * Since SASS builds CSS, it would make some of their tools useless, like Dreamweaver. Only a couple of them use tools like that. Others work in text files. * Using Firebug to work with the resulting CSS would require mental work to translate it back to SASS. For a simple site, that's no big deal. Then again, for a simple site, CSS was probably okay. * For the portal, where programmers seem to do all the layout work (here), fitting it into the build process is no big deal. For many of the things they support there is no chance to mix it into a build process. They would have to make their own build process. For some, that would be possible. For others it would certainly be a change to their normal work flow. I don't know if that helps anyone or not, but I wanted their perspective. On Tue, May 10, 2011 at 3:01 PM, Bruce Tong zzt...@gmail.com wrote: Variables, Nesting, Mixins, and Selector Inheritance all seem okay. It doesn't include logical components like decisions and loops, so I think any concerns I had at first seem unfounded. On Tue, May 10, 2011 at 2:43 PM, Jen Bourey jennifer.bou...@gmail.com wrote: If you're interested in seeing an example of what SASS in uPortal would look like, Gary's been testing it with the uMobile theme. The default skin for the muniversality theme should give a general idea of what some of the code looks like. - Jen On May 10, 2011, at 9:42 AM, Eric Dalquist wrote: This looks really cool and looks like it would REALLY simplify the uPortal CSS code. Especially with the variable replacement bits would it be valuable to move adopters to use the SASS files as well? I know I'd love it if I could change all the occurrences of the blue tab background by just tweaking a variable in one location. Also the syntax looks close enough to CSS that I don't think it would be too onerous for people to get familiar with. If this is valuable we could look at if it is possible to fold the SASS - CSS generation into the uPortal build so we just have SASS files in the source and the CSS files are all created at build time. -Eric On 05/10/2011 11:33 AM, Gary Thompson wrote: Hey all, I heard about SASS (http://sass-lang.com/) not long ago, and had an opportunity to use it in the recent uPortal Mobile work. In my opinion, SASS is CSS Awesome. It is everything that CSS development should be, and makes CSS truly programmatic with things like variables, mixins, loops, and functions. I will be using SASS for all my future CSS development. I'd like to recommend using SASS for uPortal CSS development. Impacts to uPortal: For front-end developers, an uptake of SASS. Source code CSS would be done in SASS. SASS exports to pure CSS, which would be the uPortal skins. SASS runs on Ruby. CSS development and maintenance becomes *much* easier. For portal adopters, the impact is probably nothing. Adopters would be working with the resultant CSS file (and likely never interface with SASS), and any customizations to a skin would be done in the same manner as before. Thoughts? Gary -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: eric.dalqu...@doit.wisc.edu To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: zzt...@gmail.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- Bruce Tong Software Engineer Office of Information Technology Ohio University -- Bruce Tong Software Engineer Office of Information Technology Ohio University -- 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
Re: [uportal-dev] Recommend SASS for CSS development
The input is REALLY valuable. It always makes me happy when people are keeping up with uPortal development and giving their input into the decisions about where to go with the framework. On 05/10/2011 03:04 PM, Bruce Tong wrote: I hate to keep posting. Y'all have no-doubt thought through all of this already. I talked with a couple of our graphic artists about SASS. They were intrigued by the new ideas SASS brings to the table, and there were some observations that may, or may not, apply to the portal. They usually work in sites that are far less complex that the portal's CSS. * Since SASS builds CSS, it would make some of their tools useless, like Dreamweaver. Only a couple of them use tools like that. Others work in text files. * Using Firebug to work with the resulting CSS would require mental work to translate it back to SASS. For a simple site, that's no big deal. Then again, for a simple site, CSS was probably okay. * For the portal, where programmers seem to do all the layout work (here), fitting it into the build process is no big deal. For many of the things they support there is no chance to mix it into a build process. They would have to make their own build process. For some, that would be possible. For others it would certainly be a change to their normal work flow. I don't know if that helps anyone or not, but I wanted their perspective. On Tue, May 10, 2011 at 3:01 PM, Bruce Tongzzt...@gmail.com wrote: Variables, Nesting, Mixins, and Selector Inheritance all seem okay. It doesn't include logical components like decisions and loops, so I think any concerns I had at first seem unfounded. On Tue, May 10, 2011 at 2:43 PM, Jen Boureyjennifer.bou...@gmail.com wrote: If you're interested in seeing an example of what SASS in uPortal would look like, Gary's been testing it with the uMobile theme. The default skin for the muniversality theme should give a general idea of what some of the code looks like. - Jen On May 10, 2011, at 9:42 AM, Eric Dalquist wrote: This looks really cool and looks like it would REALLY simplify the uPortal CSS code. Especially with the variable replacement bits would it be valuable to move adopters to use the SASS files as well? I know I'd love it if I could change all the occurrences of the blue tab background by just tweaking a variable in one location. Also the syntax looks close enough to CSS that I don't think it would be too onerous for people to get familiar with. If this is valuable we could look at if it is possible to fold the SASS - CSS generation into the uPortal build so we just have SASS files in the source and the CSS files are all created at build time. -Eric On 05/10/2011 11:33 AM, Gary Thompson wrote: Hey all, I heard about SASS (http://sass-lang.com/) not long ago, and had an opportunity to use it in the recent uPortal Mobile work. In my opinion, SASS is CSS Awesome. It is everything that CSS development should be, and makes CSS truly programmatic with things like variables, mixins, loops, and functions. I will be using SASS for all my future CSS development. I'd like to recommend using SASS for uPortal CSS development. Impacts to uPortal: For front-end developers, an uptake of SASS. Source code CSS would be done in SASS. SASS exports to pure CSS, which would be the uPortal skins. SASS runs on Ruby. CSS development and maintenance becomes *much* easier. For portal adopters, the impact is probably nothing. Adopters would be working with the resultant CSS file (and likely never interface with SASS), and any customizations to a skin would be done in the same manner as before. Thoughts? Gary -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: eric.dalqu...@doit.wisc.edu To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: zzt...@gmail.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- Bruce Tong Software Engineer Office of Information Technology Ohio University smime.p7s Description: S/MIME Cryptographic Signature
