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
