VIP Model Call Girls Kalyani Nagar ( Pune ) Call ON 8005736733 Starting From ...
Â
Rapid Templating with Serve
1. Rapid Templating:
âDESIGNING IN THE BROWSERâ
with Sass, Compass, and Serve
Nathan Smith â Principal UI Architect, projekt202
HTML5.tx â Austin, TX â February 2, 2013
2. I do mobile/web
UX + JavaScript at
(me, on Twitter: @nathansmith)
http://projekt202.com
3. Relax, donât stress out
taking notes. You can
get the slides hereâŠ
http://j.mp/get-serve
4. It used to be, that you could make
a picture of a website, chop it up,
put it back together with code,
and with a little luck, maybe even
turn it into a real website!
(Confession: I miss those days.)
5. Which isnât to say we werenât using CSSâŠ
html body * div#id table
tbody tr td a.special span {
/*
Dear next developer:
Please forgive me!
*/
color: red !important;
}
13. The term âResponsive Web Designâ
was coined by Ethan Marcotte, in an
an article published by A List Apart.
Loosely deïŹned, it means adapting
to various screen sizes, using a ïŹuid
grid and @media queries in CSS.
14. Ethan also wrote a bookâŠ
http://abookapart.com/products/responsive-web-design
15. Upon hearing about this
new design technique, IâŠ
1. Felt shock and denial: âWhoa, no way!â
2. Felt guilty for making a ïŹxed-width grid.
3. Bargained: âMaybe itâll just go away?â
4. Felt depressed, over how little I knew.
5. Started looking up:Â âMaybe I can learn?â
6. Reconstructed my way of thinking.
7. Felt acceptance and hope: âI can do this!â
http://www.recover-from-grief.com/7-stages-of-grief.html
16. Yes, those are (very loosely
interpreted) the various
stages of grief. Essentially,
responsive design has both
obliterated, and breathed
new life into, our ïŹeld.
19. Designers âthrowing it over
the wallâ to developers is no
longer an ideal workïŹow.
Nowadays, all of the cool kids
are working collaboratively.
http://ïŹickr.com/photos/camknows/8374910613
21. Venerable tools like Photoshop
still have their place, but other
(equally important) front-end
tools have arisen as wellâŠ
22.
23.
24. Neatly organized *.sass CSS served to browser
http://thingsorganizedneatly.tumblr.com/post/9494864300/submission-the-compulsively-tidy-ursus-wehrli
28. Text editors and IDEâs that support Sass/SCSS syntax
Aptana BBEdit Chocolat Coda
http://aptana.org http://barebones.com/bbedit http://chocolatapp.com http://panic.com/coda
E Text Editor Eclipse Emacs Espresso
http://e-texteditor.com http://eclipse.org http://gnu.org/software/emacs http://macrabbit.com/espresso
GEdit Komodo Netbeans PhpStorm
http://projects.gnome.org/gedit http://activestate.com/komodo-ide http://netbeans.org http://jetbrains.com/phpstorm
PyCharm RubyMine SubEthaEdit Sublime Text
^
http://jetbrains.com/pycharm http://jetbrains.com/ruby http://codingmonkeys.de/subethaedit http://sublimetext.com/dev
TextMate Vim Visual Studio
nd
http://macromates.com http://vim.org http://microsoft.com/visualstudio
We  recomme
http://sass-lang.com/editors.html
29. For the past two years or so, my preferred
approach to rapid prototyping templates
(with Sass & Compass) has been ServeâŠ
http://get-serve.com
30.
31. Continuing the analogy, Serve is likeâŠ
http://hdwallpapers.in/the_avengers-wallpapers.html
32. Since I canât show you NDAâd client stuïŹ
Iâve made using Serve, we are going to
look at one of my personal projects.
http://unsemantic.com
33.
34.
35. I think of wireframes and prototypes like thisâŠ
http://blogs.pennmanor.net/hstsa/nasa/nasa-space-project
36. Ultimately, what weâre aiming to launch is
not a PSD ïŹle or PDF wireframe. Nor is it
the ïŹat HTML, CSS, and JavaScript that
comprise a dynamic prototype.
Everything except the ïŹnal product exists
just to facilitate the launch. Itâs chaïŹ that
burns up, once the real thing takes ïŹight.
To that end, Serve is like the V of Ruby on
Railsâ MVC. It is similar to the âreal thing.â
37. This is the index.html.erb home page âviewâ ïŹle.
38. _layout.html.erb points to application.html.erb
This ïŹle has one code snippetâŠ
<%= render :template =>
"/layouts/application" %>
39. <%= yield %> outputs the view ïŹle (index, etc.)
49. Which is ïŹnally imported
by application.sassâŠ
Seriously, what the?
50.
51. Bear with me. Thereâs a point
to all of this. Weâll get to it.
Dude, thereâd better be.
52.
53. So, after all of that, we end
up with a tightly compiled,
single application.css ïŹle.
Eh? What about all the
@import statements? HTTP
requests, fool. Câmon man!
54.
55. Thatâs the beauty of Sass. If you
@import a *.sass (or *.scss)
ïŹle, it becomes part of the
single, compiled *.css ïŹle.
Rage subsiding? Okay, good.
Still, why all the @import daisy
chaining? Glad you asked! :)
56. â The astute observers
amongst you perhaps
have noticed what looks
like a big compost heap
of compiled CSS ïŹles.
Oh, you saw that? WellâŠ