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

Who is running MacAddict forums?

I normally hate to complain, but, being a happy subscriber to the magazine for some time now, feel like I do need to express a concern about my recent experience with MacAddict forums section of the web site. Due to some server misbehavior, I had to re-register, my old profile disappeared, while I was updating it. My new profile was assign a label "n00b" (None Of Our Business, if I am not mistaken. This is some way to welcome a new member to the MacAddict community). It could've been cute, but it isn't. And I don't think, it was intended to be: from the post of "Scott": "...using tables for layout...is for lame-ass n00bs..." I have read several more posts in the "Web Design and Development" forum, which, for some reason, was for a couple of days named "George" (the name is back to normal now; but here is how forum moderator "Gipetto" reacted when he was asked about this oddity: "...poop, it blew me away tha...

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

May 1st Reboot 2016

My main site gets a facelift (about half-a-decade overdue). Due to a chronic caching issues with iPage, I have to model everything on CodePen , and then FTP files to iPage, where, for some mysterious reason, html gets updated instantly, but CSS and Javascripts marinate somewhere for at least half an hour, before starting to render, which makes it impossible to model anything in real time. Annoying. Oh, well. At least I finally got to re-doing the site. I still do not have a concept for the galleries, though, and a main navigation menu is really primitive, but the new site is HTML5, CSS3 and what not, and I am not ashamed to refer people to it anymore. Yay. P.S. Resolved the cache issue with .htaccess file: FileETag None Header unset ETag Header set Cache-Control "max-age=0, no-cache, no-store, must-revalidate" Header set Pragma "no-cache" Header set Expires "Wed, 11 Jan 1984 05:00:00 GMT"  everything now works a lot livelier. P.P.S. Why is Blo...