Disqus - Latest Comments for dsande

Re: Making of: Prioritab, a Chrome Extension - bitsandbites

dsande — Fri, 19 Jan 2018 12:55:57 -0000

Any chance you guys are considering adding a 'This Year' list to the app?

Re: Stop Arguing So Much with Your Mixins

dsande — Wed, 09 Mar 2016 15:37:45 -0000

I can say that is an alternative, but I can't agree it's better. There are issues with that use that don't fit the problem I set out to solve as the genesis of this article.

If it works for you ... #winning

Re: How to Use Sass to Build One Project With Multiple Themes

dsande — Fri, 17 Oct 2014 14:21:01 -0000

http://anotheruiguy.gitbook...

Chapter 5 is dedicated to file management.

Re: Why I Choose Stylus (And You Should Too)

dsande — Sat, 22 Feb 2014 16:32:58 -0000

This is a great article and you put a lot of thought into the comparisons. But your reasons for choosing Stylus over Sass (Sass is spelled with lowercase letters, only the SCSS syntax is with all caps), are short sighted. Yes, the original Sass is written in Ruby and requires the Ruby language to be installed, but there is NOT a requirement for Rails at all.

It's the new kid on the block, but your research glosses over the Sass port written in C/C++ called libsass. This version is ultimately universal allowing for any other language to create native wrappers that fit it's architecture the best.

Already there are Node, Python and .NET wrappers.

While Stylus is cool written as JavaScript, there is something even more powerful about being able to use libsass in a native application language for local development and deployment purposes.

Here is an example project for setting up Node-Sass with a Node.js project
https://github.com/anotheru...

Re: Use lengths, not strings

dsande — Mon, 16 Sep 2013 12:36:09 -0000

Agreeing with all of this, I too have an aversion to tutorials that either convert a value into a string or use interpolation to chain a value to a unit of measurement.

Along the lines of what Jacob did, I too have a preference to using more common values and using the power of Sass to convert.

Using a simple `value to em` converting function, I can accomplish the same output, but input a value that more closely represents a `pixel` size given from a designer or comp.

$font-size: 12

@function em($target, $context: $font_size)
@return $target / $context * 1em

$value: 160.44
$length: em($value)

whatever
padding-top: round($length)

Re: Joining LinkedIn

dsande — Mon, 22 Apr 2013 10:55:19 -0000

HA! When I read this, all I could think of was the conversation we had on SassCast on this very topic.

Re: Joining LinkedIn

dsande — Mon, 22 Apr 2013 10:54:19 -0000

Dreamjob achieved! Best of luck with the new gig.

Re: How to structure a Sass project

dsande — Mon, 08 Apr 2013 01:38:27 -0000

I guess it all depends on how you are structuring your framework. Are you using local variables or global? Are you wanting to keep your variables close to your mixins or in a global config file?

As John points out, taking a modulare approach really helps to keep things isolated and manageable.

If you are saying that you have a general `_vars` and `_mixins` file, you may get some additional insight from my article on cleaning out your Sass junk drawer(http://gist.io/4436524).

Re: How to structure a Sass project

dsande — Fri, 05 Apr 2013 14:56:20 -0000

Great article John! Thanks for the props at the end.

Re: Announcing! New Learning Adventures (Try Them for Free)

dsande — Fri, 18 Jan 2013 13:00:08 -0000

The 'try Sass' link posted is a good start, but if want to play with all the features of Sass and the different libraries, SassMeister.com is something you have to check out.

It also has support for importing and exporting Gists from GitHub.

Re: Announcing! New Learning Adventures (Try Them for Free)

dsande — Fri, 18 Jan 2013 12:56:58 -0000

Are you talking about code hinting? Most newer editors are starting to support Sass natively, but if you need additional support look here http://sass-lang.com/editor...

Re: Source Maps with Chrome Canary and Rails — Codeography

dsande — Sat, 15 Dec 2012 21:28:10 -0000

You can go to http://toadstool-app.heroku... and inspect. The rendered CSS from that project is in the debug state.

Re: 30 Amazing Resources for Sass Lovers

dsande — Tue, 27 Nov 2012 22:20:56 -0000

I would be remissed if I didn't talk about Toadstool, a Style Guide framework. Concepts are simple, build in the abstract and apply to the semantic.
https://github.com/Anotheru...

Re: Front-end Maintainability with Sass and Style Guides

dsande — Fri, 27 Jul 2012 19:14:52 -0000

Wow, this is a great problem to solve. One that I don't think is best served in this forum. Do you G+? If you do, please follow me at http://goo.gl/Knh49 and I'd love to have a conversation about this.

Re: Front-end Maintainability with Sass and Style Guides

dsande — Fri, 27 Jul 2012 15:58:50 -0000

You are not alone. Compass' version of blueprint is a great development framework, but not a style guide framework. To fill this gap I started creating a project called Toadstool. Your team is welcome to take all or some of the code if that helps to speed up the process.

It is my goal to have this as a fully functional style guide framework that people can spin up, edit and make awesome happen fast.

https://github.com/Anotheru...

Re: How Sass Can Shape The Future Of CSS - Articles

dsande — Mon, 21 Nov 2011 10:57:25 -0000

Peter, this is a great article.

I am glad to see that concepts introduced in SASS are being taken into consideration, but these proposals fall a bit short? That variable is pretty ridiculous.

I am somewhat taken back by the fact that Webkit tried to move the ball forward to only be slapped by the W3C? WTH?

Personally I am sick of these arguments as of late. Between the W3C trying to assert leadership when they clearly do not, and the insane assertions of others that things like vendor prefixes are killing CSS and that CSS processors are the devil's work.

As Wikipedia so well puts it, "A style sheet language, or style language, is a computer language that expresses the presentation of structured documents." CSS is a programming language, not a paint brush. And with all languages, it must evolve and improve in order to meet it's user's needs.

This garbage that handcrafted CSS is an art and 'no machine will ever process my code' is laughable. Last time I checked, a browser is processing your code. The people who get it are trying to move the ball forward and create a language that will embrace the growing needs and increasing complexity of websites versus these luddites.

CSS in it's current form is dead. I am talking dinosaure dead. Are you on the train, cause it's leaving the station with you or without!

Re: The Strake - To Photoshop or Not To Photoshop

dsande — Thu, 05 Jun 2008 11:43:32 -0000

100% agree. I too read Jason's post and felt that there was a left field thing going on here.

Either building web apps or web sites, there is a design concept that needs to be considered. I have meet other designers that share this 'no PSD' thought and go straight to HTML/CSS, but oddly enough, all their projects look the same? There is no opportunity to creatively approach an idea. With this process you are locked into a pattern that is hard to escape.

But yes, once you have defined the UI and design of a project, a mature designer will compose a UI guideline with all the creative elements assembled. From there on out, any new screens are best created either as wireframes or HTML mock ups to simply communicate the idea.

I will agree that photoshop is a very involved process and it is not collaborative either. All designers will hold that PSD close to their heart. So, tools like OmniGraffle or using HTML is a great, cheep way to execute UI and allow for collaboration.