So I have been toying with the Fancybox overlay lightbox clone. (personally I prefer shadowbox but it performs less than stellar on a mobile device right now)
I updated to the newest version for a little tweaking I am doing on my store site. I always try new stuff in a temp folder just in case. I copy and pasted the code exactly how they tell you to off the website. It looks the same as the old version save for one folder in the paths and the version number. However IT WOULD NOT WORK! No matter what I tried. It worked fine with the old version. (I say old it's 2.0.3 to 2.0.5)
Finally after getting some donuts from that crazy Cambodian place and an hour of wanting to stab my monitor with a pizza cutter I thought "Hey let's delete this backslash (/) in front of the paths because I am out of options and sanity". Guess what. IT FUCKING WORKED AFTER THAT!
The old version it worked fine with the "/" in front of the path. That is exactly what they show on the examples on the website AND the instructions. However as soon as it got on my server all logic went out the damn window.
What possible functionality BS change is this? I don't get it at all. Just don't get me started on the easing in animation. I needed extra code to make that work.
Hey Developers: when you "improve" something it's supposed to be an IMPROVEMENT!
I'm gonna eat more jungle donuts now...
Friday, April 13, 2012
Wednesday, March 14, 2012
HTML Fuuuuuuuuuuuuu......
Does anyone else think it's ridiculous you have to have THREE video formats to get html5 to work on everything. Two of the formats are nothing you have heard of (unless you have had to deal with it already) and the third, which is .h264, you better hope you encode it right or else IE will just laugh at you.
Miro converter is suggested to make an .mp4 that will work as a flash fallback but hey guess what... it doesn't seem to.
It's all so damn frustrating.
Miro converter is suggested to make an .mp4 that will work as a flash fallback but hey guess what... it doesn't seem to.
It's all so damn frustrating.
Monday, February 27, 2012
Tuesday, February 21, 2012
Doing lines...
I find it so very odd that hours of frustration can pass without notice in the pursuit of that one tiny string of alphanumeric bliss.
One tiny thing can be out of place and NOTHING works. It then takes an hour or more to realize... that's not a semi-colon. Damn.
Today's frustration is brought to you by the letter .PNG click thru transparency and the letter ARRRRGH!!!
Closed captioning provided by fluid layouts are not for artistic sites.
One tiny thing can be out of place and NOTHING works. It then takes an hour or more to realize... that's not a semi-colon. Damn.
Today's frustration is brought to you by the letter .PNG click thru transparency and the letter ARRRRGH!!!
Closed captioning provided by fluid layouts are not for artistic sites.
Wednesday, February 8, 2012
This week on antiques roadshow...
In an earlier post I commented about a "center" tag causing a problem in IE. My friend pointed out center is a "deprecated" tag.
I understand deprecated is a technology term and it means something has come along that works the same in a different way or is just better. HOWEVER, I believe that as long as it still works use it! (unless it fucks up your layout of course)
There are times when I just can't get div align to play nice with anything so I use center because I am lazy. CSS has made things easier in many ways but there are a few things that can be a pain to implement from time to time. Anyone remember "hspace" and "vspace"? They still work so fuck W3 and their gestapo BS.
It's like prop making. It might look like shit on the inside but as long as it works and looks good on the outside, who cares!? So use those tags labeled old and dated until they are phased out entirely. (However, you should still know the other stuff too. I'm not saying to ignore it entirely.)
Standards be damned.
I understand deprecated is a technology term and it means something has come along that works the same in a different way or is just better. HOWEVER, I believe that as long as it still works use it! (unless it fucks up your layout of course)
There are times when I just can't get div align to play nice with anything so I use center because I am lazy. CSS has made things easier in many ways but there are a few things that can be a pain to implement from time to time. Anyone remember "hspace" and "vspace"? They still work so fuck W3 and their gestapo BS.
It's like prop making. It might look like shit on the inside but as long as it works and looks good on the outside, who cares!? So use those tags labeled old and dated until they are phased out entirely. (However, you should still know the other stuff too. I'm not saying to ignore it entirely.)
Standards be damned.
Sunday, February 5, 2012
In the jungle, the mighty jungle...
Safari is such a bad browser.
It's like the IE of Mac computers. When compared to the other browsers out there it's no wonder I downloaded the icab browser on my touch. There is basic functionality that is severely missing. Ever tried to view the source of a webpage? It's like trying to decipher something in notepad.
HTML5? Sure.. maybe. It might work.
I don't hate it as much as I do IE. I'd say I'm more disappointed in what they are lacking. So for those of you who try to look at webpages on Safari that I make (including on mobile devices) if something doesn't work... sorry.
Get to a real computer.
It's like the IE of Mac computers. When compared to the other browsers out there it's no wonder I downloaded the icab browser on my touch. There is basic functionality that is severely missing. Ever tried to view the source of a webpage? It's like trying to decipher something in notepad.
HTML5? Sure.. maybe. It might work.
I don't hate it as much as I do IE. I'd say I'm more disappointed in what they are lacking. So for those of you who try to look at webpages on Safari that I make (including on mobile devices) if something doesn't work... sorry.
Get to a real computer.
Wednesday, February 1, 2012
Like a cajun scream....
Anytime I design a website I dread... let me repeat that, DREAD looking at it in Internet Explorer. Why you ask? Simple. IE does not play well with others.
I don't know what Microsoft's problem is but I'm guessing it's that they think they are right and everyone else is crazy. There are functions and behaviors in IE that make NO sense. As an example, tonight I saw something that I have never seen before. Two DIV layers were created when there was only code for one. Why is this you ask? Because I had a "center" tag before the DIV layer. HUNH!? Exactly. Makes no sense to me either but it only took me an hour or so to figure out that little bit of lunacy.
Here is the problem: While everything works fine on every other browser I have, IE plays by it's own rules. So much so that they had to create a piece of HTML known as "If IE". What it does is tells the webpage that if you are looking at that page in IE to use a certain set of rules. The fact this piece of code even HAS to exist is insane.
IE has plagued web designers since day one. When other people looked at the shortcomings of that browser they decided to take matters into their own hands and now you have a handful of browsers to choose from. (mind you they all tend to work the same way... more or less. I'm looking at you Safari.)
I am all for having proprietary ideas. trying to standardize something with a militant fist is not the answer either (hear that W3?). However while IE was working on a way to make your text scroll and annoy people who come to your website, everyone else was trying to devise functions that were useful... ok well maybe not Netscape but I digress.
Thankfully people are wising up. The newer versions of IE have finally caught up to everyone else in some respects and are implementing CSS3 tactics... but not as many as they could. I refuse to switch because so many still have IE8 and I need to make sure stuff will work as best it can.
Except for those still using IE 6. You can suffer.
I don't know what Microsoft's problem is but I'm guessing it's that they think they are right and everyone else is crazy. There are functions and behaviors in IE that make NO sense. As an example, tonight I saw something that I have never seen before. Two DIV layers were created when there was only code for one. Why is this you ask? Because I had a "center" tag before the DIV layer. HUNH!? Exactly. Makes no sense to me either but it only took me an hour or so to figure out that little bit of lunacy.
Here is the problem: While everything works fine on every other browser I have, IE plays by it's own rules. So much so that they had to create a piece of HTML known as "If IE". What it does is tells the webpage that if you are looking at that page in IE to use a certain set of rules. The fact this piece of code even HAS to exist is insane.
IE has plagued web designers since day one. When other people looked at the shortcomings of that browser they decided to take matters into their own hands and now you have a handful of browsers to choose from. (mind you they all tend to work the same way... more or less. I'm looking at you Safari.)
I am all for having proprietary ideas. trying to standardize something with a militant fist is not the answer either (hear that W3?). However while IE was working on a way to make your text scroll and annoy people who come to your website, everyone else was trying to devise functions that were useful... ok well maybe not Netscape but I digress.
Thankfully people are wising up. The newer versions of IE have finally caught up to everyone else in some respects and are implementing CSS3 tactics... but not as many as they could. I refuse to switch because so many still have IE8 and I need to make sure stuff will work as best it can.
Except for those still using IE 6. You can suffer.
Subscribe to:
Posts (Atom)