You are currently browsing the monthly archive for March 2007.

Where do I start. I have actually pulled out hair over this issue. I have been designing my sites using; Bluefish Web Dev, IglooFTP and viewing in Swiftfox (Firefox  Now, after initial creation of the site, everything looked just fine. All of my divs,etc were in the right place. Now after the first version of the site, I wanted to do some maintaince and refine a little. Well, I made all of the revisions. Then I ran into a problem. Internet Explorer 6/7 decided it would be a great idea to not display certain boxes (divs) in the correct locations.

So after exploring my options, I found a nice solution. It does not make your CSS2 Validate. But, it does the trick. Let’s say you have a div that the width exceeded what it should of in IE.

CSS2 Compliant.

.mydiv { width: 20px }


* html .mydiv { width: 15.5px }

Worked great for a number of IE related problems. Width, Font Sizes, Etc.

Well, I am not much of a Flash fan. Probley, becauase I have been using linux for awhile and the support for Flash hasn’t been great to any degree. (We just got flash 9 not to long ago). But FJAX is a great idea.

Fjax is an open, lightweight, cross-browser methodology for Ajax-style web 2.0 development
Fjax is a technique focused on drastically streamlining the XML handling layer of web 2.0 applications. Picture Ajax’s XML parsing and handling with less than 65 lines of code! It’s not a replacement for toolsets that provide presentation-layer visual gizmos. Think of it as a new engine to put under the hood of all the great widgets that are already out there.
Our goal in sharing this with the web building community is to open some doors of possibility by introducing a much more nimble way of getting things done. Call it web 2.1. And not only can Fjax make development faster, but we hope to see its simplicity make it possible for everyone to get to play. Want the straight poop? Read the Fjax Overview.

Check it out. Worth a shot.

March 2007

Blog Stats

  • 9,047 hits