nov 25 2014 17:49 Barney Carroll barney.carr...@gmail.com:
A task runner like Gulp would be useful for this kind of thing. This guy
wrote an excellent introduction (and starter kit) [0] that covers automated
SASS Browserify code compilation and filesystem-browser synchronisation.
I've
Are there any good lists--populated by serious developers, like this
one--wear on topic includes all the trades real developers use, like
server side scripting, databases, javascript AND CSS? There are many such
forums. But forums tend to be populated by beginners while lists tend to
be
As I often feel inclined to use vendor-prefixes in order to meet business
requirements, my CSS typically don’t validate fully. I always know why and
using SASS have shielded me somewhat from seeing this issue, as I can postpone
any prefixes to the final phase. Are you developers handling this
A task runner like Gulp would be useful for this kind of thing. This guy
wrote an excellent introduction (and starter kit) [0] that covers automated
SASS Browserify code compilation and filesystem-browser synchronisation.
I've used Gulp for my last 2 major project for all my development and
Den 25.11.2014 10:50, skrev MiB:
As I often feel inclined to use vendor-prefixes in order to meet business
requirements, my CSS typically don’t validate fully. I always know why and
using SASS have shielded me somewhat from seeing this issue, as I can postpone
any prefixes to the final phase.
I only run stylesheets through the validator when: 1) I can not find one
of my own disable this declaration markers, 2) I can not manage to debug
a problem in browsers locally, and/or 3) I have to share my CSS code with a
developer who is paranoid when it comes to validity -- something I am
Validating CSS : When ? --
For me :
a) Whenever something does not behave as anticipated;
b) Before signing anything off as complete.
If it fails at either stage, then ensure that any deviations from the
specification are (a) intentional, (b) essential, and (c) have no
undesirable or
On Tuesday, 25 November 2014, Philip Taylor p.tay...@rhul.ac.uk wrote:
…HTML 5, but ONLY if new elements such as audio, video or canvas are
required.
That's an interesting approach. Any particular reason not to use HTML5 at
all times?
--
Regards,
Barney Carroll
barney.carr...@gmail.com
Barney Carroll wrote:
That's an interesting approach. Any particular reason(s) not to use HTML5
at all times?
Yes, but this is not the place to discuss it/them !
Philip Taylor
__
css-discuss [css-d@lists.css-discuss.org]
