Is there a FluidAll.css?

[Aaron Zeckoski]

I don't think I am using the skinning system stuff. I am just using
the components (like Sakai).
I just want the accessible Javascript parts of Fluid for now.
-AZ

On Wed, Jul 29, 2009 at 5:21 PM, Jacob Farber<jacob.farber at utoronto.ca> wrote:
> There is indeed a documented load order:
> Please see: http://wiki.fluidproject.org/display/fluid/Fluid+Skinning+System+(FSS)#FluidSkinningSystem%28FSS%29-HowFSSworks
> Jacob
>
> -----Original Message-----
> From: fluid-work-bounces at fluidproject.org [mailto:fluid-work-bounces at fluidproject.org] On Behalf Of Aaron Zeckoski
> Sent: Wednesday, July 29, 2009 11:49 AM
> To: Aaron Brown
> Cc: fluid-work
> Subject: Re: Is there a FluidAll.css?
>
> If there are some load orders that need to be respected somewhere then
> I have not seen this in the documentation anywhere (for components
> anyway). If someone can point me to it then that would be great.
>
> Also, I see no import statements in any of these CSS files so I assume
> this is not an issue.
> -AZ
>
>
> On Wed, Jul 29, 2009 at 4:35 PM, Aaron Brown<aaron at thebrownproject.com> wrote:
>> Aaron Zeckoski wrote:
>>> I went ahead and wrote a shell command to build up the css files into
>>> a single one for now.
>>> find components/ -name *.css -exec echo "/*** file: {} */" \; -exec
>>> cat {} \; >> InfusionAll.css
>>
>> That's a somewhat risky method for collecting the styles all together.
>> When the CSS files are read by the web browser, they'll be read in the
>> order they're declared in or referenced by the master style sheet.  This
>> is important since later declarations of entities with the same name
>> will override previous declarations.  Your shell script will work
>> provided there are no overlaps between common classes or ids and their
>> attributes.  If there is an overlap, you'll get a different result using
>> the script-generated style sheet.
>>
>> If you want to write a script that produces an accurate
>> "InfusionAll.css", the script should follow rules similar to browser
>> processing and read/process all the nested @import statements to be sure
>> to concatenate the styles in the proper order.
>>
>>  - Aaron
>>
>> --
>> Aaron Brown :: aaron at thebrownproject.com :: www.thebrownproject.com
>>
>> _______________________________________________________
>> fluid-work mailing list - fluid-work at fluidproject.org
>> To unsubscribe, change settings or access archives,
>> see http://fluidproject.org/mailman/listinfo/fluid-work
>>
>
>
>
> --
> Aaron Zeckoski (azeckoski (at) vt.edu)
> Senior Research Engineer - CARET - University of Cambridge
> https://twitter.com/azeckoski - http://www.linkedin.com/in/azeckoski
> http://aaronz-sakai.blogspot.com/ - http://tinyurl.com/azprofile
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
>



-- 
Aaron Zeckoski (azeckoski (at) vt.edu)
Senior Research Engineer - CARET - University of Cambridge
https://twitter.com/azeckoski - http://www.linkedin.com/in/azeckoski
http://aaronz-sakai.blogspot.com/ - http://tinyurl.com/azprofile