Ok, it's been some time since I revisted this handy lil' script, but since I've been in an overhaul'n kind of mood lately, I thought I would give this one another crack. If your not familiar with Cj Html Parser, it's my nice little function that converts an HTML encoded string to ASCII text.
Check out Cj Html Parser over on the projects page.
Well guys, I've been working on one of my projects for the past couple of days trying to make improvements and I just had one of those Ahhhh-Ha moments. Seriously, this thing has been eating away at the back of my brain for days. I was having dreams about it at night and right now, I'm all giddy with excitement.
Unfortunately, your going to wait a day or two until I post it. It needs to be cleaned up and comments need to be added. Also, I think I can add a couple of new functions.... it's pretty frick'n cool. You guys are going to love it.
I'll have it online as soon as I can!
About 6 months ago, I came across an online tool called JSLint. It's a JavaScript program that looks for problems in JavaScript code. I began using it to check most of my scripts to see if I had any errors in them (I know, I know... you thought I was perfect). Well as it turns out, I had a lot of little mistakes, like using a function or object before it was defined or little formating issues. But one error I kept receiving made no sense to me and I honestly didn't understand why I was getting it.
Expected '===' and instead saw '=='. Expected '!==' and instead saw '!='.
Granted, it wasn't like I didn't understand how to fix the issue, but JSLint wasn't very forthcoming on why I needed to make these changes. So, without fully understanding what wasgoing on, I began using "===" and "!==" whenever I needed to make a logical comparision. And I've been doing this for the past 6 months, without a clue as to "why".