Check out the full tutorial at net.tutsplus.com.
HTML5 is the future of the web, but building the future is hard work and so it’s always great to get a bit of help with that. Some of that help comes in the form of HTML5 Boilerplate from the minds of Paul Irish and Divya Mani, who have teamed up to bring us “the professional badass’s base HTML/CSS/JS template for a fast, robust and future-proof site”. Boilerplate is basically a bunch of files, the exact kinds of files you would create as you start working on a new website, except that these already contain the basic starting code and include all the best practices baked in. Things like reset styles, pngfix, HTML5 markup and more. I went over most of it line by line and after a few adjustments based on my own personal preferences I’m going to start using it as the base for all websites I work on. Read more »
If you work with Joomla 1.5 and like me, find the right alignment of toolbar icons counterproductive (in the default admin theme), then you can fix it with just a few CSS tweaks. Here’s what I mean.
To do this, in Joomla’s root folder go to administrator/templates/khepri/css. In file rounded.css find the style for div.m and add position:relative to it. That’s it for that file. Now open the file general.css and that’s where you’ll need to make several changes. Read more »
I wanted to have an AddThis share button that would fit better with the site’s design, and if you’re reading this post on its own page you can scroll down and see what I mean. While AddThis provides plenty of ways to customize their buttons, there is no way to assign your own image to the icon, which means doing it the hard way… well, relatively speaking of course.
Read more »
So the new look for the IliaDraznin.com is up. There were some teething pains (categories disappeared there for half a day or so), but it all seems to be working out now. Biggest addition, other than the new design, is the Syntax Highlighter script, to make all those code chunks look nice.
There are still a few features missing but I’ll be adding those in the upcoming weeks. Anyway, it’s back to our regular scheduled programming now.
Well, it’s been a while since my last post but I’m back and I’ll make sure to start posting more often.
Right now I’m finalizing an all new (and original) design for the blog; it’s gonna be minimalistic and dark. In the meantime I’m also redoing categories, cleaning up the tags and modifying small things here and there, as part of the preparations for the new design.
Update: I have created a better version of this script that, among other improvements, supports password fields, unlike the code below.
Placeholder is a very useful attribute of the
<input> tag that is specified in the HTML5 spec. It provides a text that goes into the field, by default, and is used as a kind of a quick tip for the user about what they should type into the field, such as “type to search”, or “type in username”. The nice thing about “placeholder”, as oppose to, for example, simply setting some value for the field, is that it automatically disappears when the user starts typing something in, but it reappears if the user ends up leaving the field empty. Unfortunately this attribute, and its functionality, is actually not supported by most browsers, including Firefox 3.6 and IE8, it is however supported by Chrome 4, and possibly Safari 4 though I can’t vouch for the latter.
If you’ve been following apple related news you’ve heard that they recently started coming really hard after any applications that could be considered “sexy” or “suggestive” — whether its by virtue of having girls in bikinis in their screenshots, or suggestive text in the description — and removing them from the app store. You can read about it in more detail on this techcrunch and ars technica posts.
I’m not going to argue about fairness to developers who have invested time and money into, in many cases, perfectly legitimate apps, only to see them pulled down without any warning despite being approved in the first place. I’m not going to discuss the fact that there seems to be no clear guidelines or rules as to what constitutes an “offending” app, meaning that these can change at any moment to accommodate apple’s every whim. I’m not even going to mention that not a few months ago apple introduced the 17+ rating which is used to prevent the purchase of “adult” apps by kids, and which could be easily used to also filter out those apps from even showing up on the store pages unless age was verified. (Why Apple would not do that in the first place is beyond me, you’d think they have amateurs working there.) Read more »