Phazm Webdesign

This article is the fourth in a continuing series of DIY tutorials, which aims to make things as simple as possible.

To be honest, I wasn't planning on writing this article, but it would seem that there are quite a few people that want to know - what does the server-side code for the Ajax article look like?

In the previous Ajax article I outlined how to make a simple voting script, and a simple 'shoutbox' using Ajax. If you didn't read that post, I recommend doing so now, before reading this one.

It's always a bit harder to post server-side code, because there are a lot of ways you can do a something, and many people think their way is the better than any other. So let me just say that while there may be other ways to do things, this way works just fine. Anyway, back to your regularly scheduled program.

In this session, you are going to learn how to work the backend (in this case, PHP) for Ajax requests.

NO MORE Internet Explorer 6!

Update: For a select few

IE6 is being phased out with a mandatory push from Microsoft, requiring all computers to upgrade to IE7.

The article from Microsoft mentions several ways you can disable the WGA-free update, so the war might not be over. But in my opinion, this is a major step forward.

This post is the third in a continuing series of DIY tutorials, which aims to make things as simple as possible.

The [Easy as Pie] series focuses on tasks that most people consider too challenging and presents it in a way that is easy (as pie!) to understand.

Introduction

In this post, you are going to have a fantastic time learning:

• How to create a MySQL Database
• How to create a table in a MySQL Database
• How to add data to a MySQL Database
• How to get data from a MySQL Database
• How to create a random quote generator

The good stuff

If you're like me, you learn really well from example. For this reason, I include the download for the random quote generator right here. Enjoy!

Download the Random Quote Generator source code

Let's get started!

It seems that using Alexa's redirect URL to game your rank is no longer an option.

UPDATE

On about 4:00PM on Thursday, January 10th, I clicked one of the comment author's names, which I assumed lead to their blog. Instead of their page, however, I got:

The requested URL /redirect was not found on this server.

I glanced at the address bar, and saw this:

http://redirect.Alexa.com/redirect?myblog.com

That's not good for business...

This post is the second in a continuing series of DIY tutorials, which aims to make things as simple as possible.

Ajax. Some would say that it is simply an over-used buzzword, but I disagree. Ajax (formerly known as AJAX) is a fantastic way to enhance websites and improve user interactivity. However, like all things, it should be used in moderation, and has the potential to be used improperly (I'm looking at you, flash.)

But I don't want to get off-topic so early on. In this tutorial, you will:

• Learn how to use Ajax in the simplest way I could think of
• Create an addictive voting script
• Create a simple shoutbox
• Download source and create your own within minutes!

This post is the first in a continuing series of DIY tutorials, which aims to make things as simple as possible. I will also monitor the comments on the 'Easy as Pie' posts more carefully so I can address any questions anyone has.

While it pains me to do so, the following warning is needed:

This entry best viewed in Firefox 3

Since Mozilla released the Firefox 3 Beta (Code Name: Minefield) there have been a rash of blog posts regarding the many new features, increased security, and enhanced UI. However, one thing I have yet to see is what I am really need to know: how does this affect web developers?

I am speaking to Nik Ainley, a UK based designer with a passion for producing awe-inspiring art and illustrations. You'll see what I mean in a few minutes.

I have recently been getting mildly irritated at all of the "Just don't code for Internet Explorer 6 and people will stop using it" blog entries I've been seeing lately. I consider it a huge problem in the mentality of a designer when they disregard a large portion of visitors and/or customers. No disrespect to Nick La, but simply "giving up" on IE6 is not (at this time) a viable solution, especially because IE6 still has the largest user base.

The fact is, IE6 is not that hard to code for, as long as you have a good understanding of Semantic XHTML, you shouldn't have much of a problem. In this post, I'm going to outline some of the steps you can take to reduce the time it takes to develop your pages for Internet Explorer 6.