Skip to main content

Update

I have abandoned the blog for a while... Due to many legitimate reasons, of course, being out of job (but not work, that's good), for one.
Short recollection of events, which took place during last couple of weeks:
I have completed a small, but reasonably priced project, working with a PHP programmer I have never seen before (we spoke on the phone once or twice).
I have almost finished a client-side JavaScript application for a small NYC production of Valiant; the application is designed to provide "typographic assistance" for the main character during stage performance ("Sally" doesn't speak, she types on her laptop, and the monitor contents are projected on screen - an unusual concept and a lot to type... so, I have come up with a script, which types hard-coded text string letter by letter into the page's HTML on each keystroke the actress makes - no misspeling or missing punctuation...). Being annoyed by the warning sound, which IE|Win makes on every keystroke, if the focus is not on an element, which is supposed to receive text input, decided to provide a dummy input field to take whatever the user types, thus eliminating the sound. Only worked, while the page was short, then I ran into a problem: the browsers try to scrol the document to display the element in focus, and all of them do such thing in a different way. What a surprize. IE|Win will scroll toward an input field, which receives focus, but just enough to display it; Firefox|Mac behaves the same way. Safari tries to display the field as close to the middle of the window, as it can, and IE|Mac puts the field at the top of the viewport, which would be ideal, if not for the fact, that it is painfully slow, which pretty much makes the whole thing useless. Ended up dismissing the idea of using element.focus() to automatically scroll to the desired location, and instructed the actress to turn off the sound. Oh, the everlasting joy of web design.
On the other front of my recent activities: I've discovered a new weekly jam session, where the traditional blues repertoire often diluted (or should I say "spiced up"?) with a hearty amount of funk, and even jazz. The place is called House of Swing, the jam is there every Thursday, hosted by Reid Project; 11:30 pm - 1:00 am or so.
My musical exersizes, posted at MacJams.com, seem to hold up rather well, to my surprize. I am on the first page of the "Jazz" genre if listed by "Ratings".
So far, so good.

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' ....

How to Make a Website Everyone Has

On The Endless Wonders Of Internet Explorer

May be somebody will stumble upon this post and save some time for him/herself. Apparently—it only become apparent after several hours of trial, cursing and error, as it usually goes with IE—, Internet Explorer (up to version 7) throws a runtime error, if you try to modify innerHTML of the dynamically created element under certain conditions. The conditions, as it always go with IE, are significantly lacking consistent logic. For starters, if you assign innerHTML to the element before you insert it into a DOM tree, the error may not come up at all, but will surface later, when you try to modify it. So far it looks like the error mostly comes up, if you change innerHTML of the block element inserted into inline element (which is not kosher in standard-compliant HTML, so it makes sense), and some nested block elements (like DIVs inside Ps—why is that considered wrong, too?—for instance). So, if one really-really need to insert a division into a paragraph, and w...