Tags: css, ie, japan, theme, updates, wordpress.
Categores: Blogging Advice, Culture, Opinion, Site Updates.
Nanyate?! has a new theme! This layout is titled “Yukata 浴衣 Summer”. For those who are unfamiliar with Japanese culture, yukata is the summer version of a kimono 着物. The flower in the background is inspired from a yukata featured in last year’s issue of JJ Magazine. Yes, I drew it. And yes, it took forever. I haven’t actually illustrated anything complicated for a while, so I was quite antsy when I drew the flower.
The layout is currently in beta mode. The background is incomplete. I wanted to add a couple more embellishments but I haven’t received my brushes from Seishido as of yet. And of course, there are bugs to kill and the layout doesn’t work on IE 6 at all. Most bugs will be fixed by tomorrow. IE6 compatibility will have to wait. Busting out my old Sony Vaio to re-code half the site is just…argh.
I’ve been at this for 2 days. 1 day for drawing the background. 1 day for designing + coding. I haven’t slept for 20 hours. So, pardon this rough post and rough layout.
I’m exhausted. Off to bed.
UPDATE!:I received my brushes! Here’s the new background! Most bugs for the Mac Firefox, Safari and Opera are squashed. I’d expect that their Windows would react the same way. Now all that’s left is that nasty IE6, which I don’t have access to - not even from my old Sony VAIO! IE NetEenderer isn’t powerful enough for me to refresh every 5 seconds, so coding for IE will have to wait until I go to my school’s library.
Sorry, IE6 users. On the other hand… you really shouldn’t be using IE6. Microsoft is already developing IE8 and even had a beta release! I can’t imagine what kinda security flaws you IE6 users have to deal with. 
The browser’s free for goodness’ sakes; all it takes to upgrade is some free time. Think about it this way: just 10 minutes less of porn, infinite increase in security. Time for a upgrade, people.
Tags: css, ie.
Categores: Opinion, Site Updates.
After digging out my old Sony Vaio sinking under dust bunnies, and many freaking hours of trial and error with the footer, I finally fixed the freaking footer for the foul Internet Explorer. I re-coded the whole layout twice thinking that it’s a float error, only to find out that it was a measly padding problem that plagued my precious footer. (Alliteration, much?)
Seriously, Microsoft, it’s impossible for a Mac user to code for Internet Explorer since you stopped producing IE for the Mac. Yes, I know there is a nifty tool called IE NetRenderer, which job is to enable Mac users to view screenshots of their sites rendered through Windows IE. But honestly, a screenshot is no match for the real page. I can’t freaking see how the footer ends even on a page with no content.
If you think by halting IE production for the Mac, you will lure Mac web designers into using RAM-eating Windows Vista, you are dead wrong, my friend. In the end, we will get fed up enough to stop coding for IE altogether and your troublesome browser will lose all of what little the browser market share you have left.
In case you haven’t noticed, the number of IE users in the past few years have been exponentially decreasing. 99% of my visitors in my old sites have been surfed and served via IE. Now 4 years later, it’s dropped to a mere 29%. Hmm, I wonder why? Oh yeah! IE-less Mac users have increased exponentially; Firefox, Opera and Safari can read code more efficiently and compliantly. So, if you want to stay in the game, please, please, bring back IE to the Mac, and improve on its code rendering.
Do you, designers, find cross-browser coding a pain too?
Special thanks to Iva, for pointing out the footer problem on IE.