On Wed, Dec 19, 2012 at 4:44 AM, Łukasz Mach <[email protected]> wrote:
>
>
> C Anthony Risinger <[email protected]> napisał:
>
> (...) so far my
>>favorite idea there is a base.css with everything, as loading a few
>>more KiB is moot compared to latency of round trip HTTP.
>>
>
> Ok. I thought that it's totally not acceptable, so I even didn't proposed
> such solution.
heh :) ... yeah im not a big believer in this thing people call
"bloat" ... usually what i see is "less work" or "simpler deployment"
or "higher performance"... the unwaneing quest for "bloat" reduction
has yielded the obsessively excessively fragmented systems we have to
deal with.
i know several data back that mentality WRT CSS at least... i think
Paul Irish did a bit awhile back on this exact topic that led to HTML5
boilerplate... which, btw, includes print CSS inline -- for the same
reason -- and has numerous good tricks combined with good comments
why.
> Let start with it and then either base.css will be automatically generated in
> compile tome (if possible) or maybe css injecting only for not-base widgets.
sure -- if you want to combine the sheets/assets wel can go from
there... i'd like to see a flat static asset directory, where
images/etc are named in some repeatable way:
{ns}-{category}-{key}[-{props}...].{ext}
...eg:
pyjamas-any-plus_sign-huge-green.png
...or similar/better; this reduces complexity by only needing a single
path for static stuff (similar to lib/ for --dymanic-linking)
--
C Anthony
--
