Tiny nitpick: IMO the call to action styles doesn't belong (seems a bit to specific for a generic boilerplate). Other than that, nice job.
Edit: I also like that this is more lightweight than Bootstrap - which I hadn't seen before.
479 karma · joined July 16, 2010
kayla.rose.martin@gmail.com http://twitter.com/_kaylarose
Tiny nitpick: IMO the call to action styles doesn't belong (seems a bit to specific for a generic boilerplate). Other than that, nice job.
Edit: I also like that this is more lightweight than Bootstrap - which I hadn't seen before.
//Overly simplified example $.get('tooltips.php?id=tooltip-id',function(data){$('#tt').text(data);});
I read this article[1] and it changed my life.
In a single universal field you have instant: app launcher, calculator, dictionary, file search, email search, contact search.
My single best tip for Mac power-users: learn what you can do with Spotlight.
Edit: grammar
This is the major thing that turned me off about Kohana. I loved the original concept - "PHP5 fork of CodeIgniter" - and we actually have it backing our two largest web apps. But I would never recommend Kohana again for a commercial project that is under active development.
Between minor versions there was major API breakage, that wasn't really documented - and was going on in parallel with 3.0 development (think Rails 2 -> 3 with no documentation). For a long time the "Unofficial Kohana 3 Wiki" was actually the only source of documentation for KO3 (even after release).
It seems like the PHP community keeps fragmenting into new PHP frameworks to replace old stodgy (cough PHP4) frameworks (good), with modern design practices (good), but then totally ignoring the community aspect of OS software, documentation, and maintenance.
So yes - IKEA newbs do not take the shortcut paths!
[1] Blog Post: https://github.com/blog/817-behold-image-view-modes
[2] Demo: https://github.com/cameronmcefee/Image-Diff-View-Modes/commi...
Coupled with Kaleidascope on the desktop: http://www.kaleidoscopeapp.com/
I think the problem is introducing the IDEA of version control to designers. Once they grok the idea, they usually like it. But with the exception of web designers, most designers aren't introduced to the concept.
*I was a designer before I was a developer
However I agree about the contrast, I checked on my external dev monitor (vs. my super bright MBP screen) and the contrast could definitely use some work.
That said, I've actually been pretty pleased performance-wise, I expected worse.
Also, I am not a man. But thanks!
I wanted to see how close I could get using CSS3 without any images.
I recommend using a Webkit browser [you can also see an alternate implementation using Firefox 4]
http://en.wikipedia.org/wiki/HTTP_Live_Streaming
Edit: Spelling
Yes, people always bitch about how easy it is to just set up Apache, but they fail to realize the departmentalization of apps is great for development. Currently in my dev environment I have a virtual host for every app/site/lib. It is rare that most PHP devs even do that. Far too often they just do FTP straight to the production server. This would curtail that.
$ cd your/app
$ php -s
That said, I think the recent trend of lightweight servers for PHP is awesome. I think any additions to PHP that introduce real professional practices to the PHP community is a great thing. In the past few years we have seen the wider adoption of Unit tests, better frameworks, and somewhat better packaging.PHP devs always complain about how people rag on PHP, but it's because the professional programmers that actually know what they are doing don't spread their knowledge to amateur programmers - which leads to more crappy PHP code. Just like any other language embracing and evangelizing good standards will better the community as a whole.
[1] http://news.ycombinator.com/item?id=2281724 (source link is down at the moment)
2. No idea. If I had to guess it wouldn't be harder than the original jailbreak, and potentially much easier.
3. You can use your iPhone/iPod touch's Remote app to control the ATV (the remote it comes with is a pain for text input) [No jailbreak required]
<ul class="main-nav inline-list">
<li><a href="">...</a></li>
</ul>
To style/highlight my example the above:
//This will not have to be modified if we want to add more nav instances
.main-nav.inline-list li{float:left;} $('.main-nav.inline-list a.selected').highlight();
To style/highlight your example the above (at top and bottom of page): //Each time you add another instance, you have to add its new id/selector (not very DRY)
#navigation.inline-list li,
#navigation_b.inline-list li{float:left;}
$('#navigation.inline-list a.selected, #navigation_b.inline-list a.selected').highlight();
Again, it's personal style, but I've never found myself saying "boy I wish I used an ID instead of an adding another class" where many times you regret the use of ID because when you ultimately need to duplicate that element, you are effecting the dryness of your CSS and Javascript. Plus, with modern selector engines the performance of ID vs class based selectors is not really going to have that big of an impact.The times I use ID in my markup is more for sub-navigation through the page rather that styling-specific reasons.
<h2 id="chapter_two">Two</h2>
<a href="#chapter_two">Got to Ch. 2</a>2. Only use the minimal selectors you need: div#features ul.feature_list li.feature a{color:red;} could be DRYed up to be .feature_list .feature a{color:red;} which will be far easier to override later.
3. Avoid !important at all costs (sometimes you can't, but try).
4. This is personal taste, but I also usually avoid IDs for styling.
5. Grid frameworks (Blueprint, etc.) are usually overkill, but syntax frameworks (LESS CSS, Compass) are fantastic.
It really boils down to experience, and knowing what you DON'T need - most people add in a ton of extra cruft and end up with hard to extend and debug spaghetti.
For a website: callouts, user quote styles, tables styles [zebra stripes, etc.], feature lists, intro paragraph styles, Flash/message styles, common control styles, etc.
Edit: Oh, and XBMC just gets added as another menu item, so you can still use the regular AppleTV ui too.
It's actually pretty easy to make better jQuery themes.
http://gemdash.tumblr.com/post/3941893390/cupertino-a-jquery...
It's not great but I think it came out pretty good.