Skip to main content

Ways Of Driving A Nail Into A Board (ALA)

It's so amazing to observe the evolution of the idea in a creative environment. This is why I love ALA discussions.
There is, I believe, an infinite number of ways for driving a nail into a board - starting from a hammer and working your way up to a microscope - and most of them get the work done. What to use - is entirely up to us.
This article introduce yet another way - great. Even better, it works! Anyone wants to port it to .NET or any other platform - go right ahead, and don't forget to share.
Waste of bandwidth? Hard to fathom without testing under real load; I would say, it might cause some issues in some cases, but this is not the point. The point is - the more ways of skinning the cat we discuss, the larger the world population of the skinned felines will grow.
Ewe.
I meant it in a positive way, actually. Hmm.
Anyway, great work, great concept, and great discussion.
Keep it up.

Sidetrack:
[LazyJim] ...Why not just have images for every letter of the alphabet and replace each letter on your page with a single-character image?...
This is yet another way. And, you don't even need PHP or any other server-side technology to implement it, you can get away with simple JavaScript: take a string of text, split it between characters, loop through the resulting array and write to the page whatever structure you wish to insert "YourArray[i].gif" image for each letter. Assuming that you have all the images pre-made and uploaded to the server.
Here is the sample.
I wasn't entirely happy with this solution, because each line of text would require numerous server trips on the first load (not only that, there was an issue with illegal characters in a file name, like " .gif", "?.gif", "..gif", etc.), so later I revised the script, using single image as a shifting background for the series of floating DIV's and a set of CSS rules to position the background:
www.gerasimenko.com
The next iteration of the script does, in fact, dynamically replace the H1, H2, etc. tags it finds on page onload. I was going to submit a tutorial on this matter to ALA for a while, and finally did earlier this week, inspired by the article we are discussing now (I wonder if this post will be considered a "previous publication" and ALA will dismiss my submission because of that).
Yet another way.

[Stewart] ...Using individual characters would not work, because 1) the kerning of characters would be destroyed and 2) the ALT attributes of each image would be rendered entirely useless, making this technique inaccessible...
The kerning will be affected, yes, but not destroyed, it's just a matter of dynamic positioning of each letter. Kerning in Photoshop is not bulletproof either, and highly typeface-dependable. The ALT attributes will make sense no more, true, but there is also TITLE you may be able to apply to the parent node element to make it up.

[Nevel] ...When using replacing images, you obviously don't think CSS is good enough to serve your needs...
True. It isn't. At least not yet. This is why Stewart developed this technique in a first place.

Popular posts from this blog

WordPress: How to add custom fonts to a twenty seventeen child theme.

Quick help to those who have tried to find some help and failed (as I have so I have to write the code myself). Assuming that you have your virgin child theme configured and activated: here is a function which goes into the functions.php file (of your configured and activated child theme): function childtheme_twentyseventeen_fonts_url() { $replace_original_font = true; // unless you really like Libre Franklin if ($replace_original_font !== true) { $hyph = '-custom-'; } else { $hyph = '-'; }; $font_families = array( //add your Google fonts and weights (400 and 700 are defaults for normal and bold) here: 'Oswald:200,400,700', 'Lato:200,400,700', ); $query_args = array( 'family' => urlencode( implode( '|', $font_families ) ), 'subset' => urlencode( 'latin,latin-ext' ), ); $fonts_url = add_query_arg( $query_args, 'https://fonts.googleapis.com/css' ); wp_enqueue_style( 'twentyseventeen' ....

{position:fixed} in iOS 6

I stumbled upon this oddity when upgrading to iOS 6 while working on a mobile advertising project, and it took me a better part of the day to figure out what is going on: all of a sudden an element {position:fixed} stopped working in a correct manner (which is staying put, while the page is scrolling), and started "sticking" to the scrolling page, moving out of the viewport, and then just "jumping" back to the correct location after the scrolling was finished.If you scroll this page , you will see it—hint: that's the one labeled "broken"—assuming that you have a correct device/browser combination. Mine was iPhone4 and iOS 6.0 (6.0.1-6.1.3 behaves just the same). On the original page, where I first encountered the problem, all of my elements were created dynamically using JavaScript, but at the end of the day (literally) it become clear, that the glitch is in the iOS 6 CSS implementation.Here is what happens: if you have an element {position:fixed} whic...

Have to do something about something

I recently realized, that I haven't been doing any 3D work for month now. I also noticed, that the last movie I made, wasn't all that exciting of a project. For some reason my interests shifted - again - to another area, which is, in turn, split between standard-based web design, and making music with GarageBand. May be, I should concentrate on something; just may be. May be, I will achieve some sort of recognizable and reputable state in that area, whatever that area would be. May be, people will refer to me as an authority on some obscure subject, like cross-browser implementation of unordered lists, or making Apple-compatible loops, I will become famous, and will receive an incredible job offer (this last statement is about as realistic, as me winning a lottery, considering that I never play). Somebody just sent an email to my wife, asking if she still gives art lessons. I couldn't help noticing custom domain name in the email address, so I checked it out: very decent ...