In the line of search engines Brandon pointed out, I am liking the koders.com search engine. You can search for code in all different kinds of languages. They have a firefox plugin as well as code to embedd the search on your site. Enter a snippet of code, or a function and try it out:
Currently in Beta and soon to be released is a search engine available for programmers and coders.
Unlike conventional search engines, Krugle is designed to locate code. Krugle supports code search by crawling, parsing and indexing code found in all open source repositories, as well as code that exists in archives, mailing lists, blogs, and web pages.
According to their page you can search repositories, pages and resources that offer relevent code. You can even add comments to code, save and share the query’s. It also will deliver basic “basic API information about highlighted portions of code”.
By the sound of it, it looks like a stand alone ap.
You can signup for it at thier site to get a copy as soon as it’s live. I’m definately looking forward to it! I wish I had seen this sooner. I would love to have seen this Beta.
I’m in the process of creating some new pages and am trying to learn how to use CSS ‘properly’. I was coding right along and my page was looking real slick. Then I opened it in IE. What a mess!
One thing I came across the hard way was that IE likes to use their own CSS standards. I won’t get into what I think about this – that’s an entirely different post.
How does this affect a browser? Tons! To begin with I found out I needed to know what the CSS Box Model is. You can just google it up. Here is a nice visual presentation at hicksdesign. And a nice interactive version can be found at redmelon.net.
I would suggest reading the ilovejackdaniels.com explanation of how IE Vs. Firefox/Mozilla browsers interpret the CSS box model.
I could have hacked up my stylesheet to get what I needed out of IE. There are many hacks out there to force IE to doing what you want to. After reading up on it, it’s my opinion that this is a bad idea. For starters, it’s really a pain to have 2 different styles within your stylesheet. It’s really difficult to read after a while (and it’s uglyto the eye). Even more so, it’s difficult to make changes to it. I found a solution. I must say that it wasn’t on my own completely. I had some great help from IRC EFnet channel #css.
The Solution: Conditional Comments.
Conditional comments allow you to maintain 2 different stylesheets for your page. 1 for Firefox/Mozilla, the other for IE. Here’s how it looks Read more…
According to zdnet Firefox has passed a 20% marketshare in Europe.
Personally I’ve used Firefox for the last year or so and I really like it. I’ve recently tried Opera. It seems to run much lighter. However, I’ve been told by some css “gurus” that Opera isn’t that good.
I’m unsure why or what the exact complaints are against the Opera browser, and I’m unsure of my source’s credentials. I would really like to get feedback from anyone on their preferred browser and why. Please feel free to leave a comment.
I’ve also been using IE7. I’m quite frankly not pleased with it. In general the options really don’t offer anything more exciting than the firefox or the opera. Not only does it have the M$ signature giant footprint, but as usual it does NOT render css very well.
Today I fought what I thought was some kind of permissions error. I was learning how to create a database table in mySQL with php.
After 3 hours I figured out my error was due to syntax.
“AUTO-INCREMENT” is not the same as “AUTO_INCREMENT”
I looked over that line at least a thousand times thinking – thats right.
When you are trouble shooting code:
Break down the elements.
Print out the variables print_r();
Put in escape messages while you are creating:
if($this_is_true){
print("Its all good<br />");
} else {
print("Houston, we've got a problem");
}
or print all the elements getting $_POSTED:
print_r($_POST);
or print all the elements in an array:
print_r($myArray);
…it only takes a few seconds to code that temporarily in to your code to help find problems.