For some reason, the application works when i’m on my development server. but it fails after I compile it! So, it runs, but it doesn’t work after I compiled it. I’m stupid enough to not test it even once!

I changed the link into a giant (super huge) button

I’ve gotten IE to work. Building off what I did to get Opera to work. (BTW. Safari is just like firefox, so no real problems there)

It really wasn’t as hard as one might imagine. I created a browser sniffing thing to use VMLRenderer for IE and SVGRenderer for everything else. I tested it out. IE worked fine…. except one small thing. The shapes appeared 200px away from where I drew them! Oh Noes! After some experimentation, i discovered that it only works when the canvas is absolutely positioned. But when I do that, my awesome centering doesn’t work! So, i made some more browser-sniffing code to detect if it’s IE and set positioning to absolute, and make left: 5% so it’s not too terribly off-center.

Also, I got rid of some globals, and the canvas size is no longer hard-coded.

If you have Opera 9.5 it already should work. But Opera 2.5 (the current stable version) had issues. The createUUID function uses the Array.map() function. This comes native in Opera 9.5 and Firefox, but not in Opera 9.25. After figuring that out, I made a version of the function that didn’t use Array.map. Now it’s fine.

It still renders the shapes a bit awkward (again, 9.5 is fine).

…Now to get killed by IE

i have almost fully integrated  the ajax animator toolbox with onlypaths. In the last post, i talked (briefly) about how i integrated the color management system. The rest was just as easy. For simple reasons, i rewrote the user statistics section of the toolbox (it took up too much room and used a switch(), so i replaced it with matching with an associative array, which is evidentally much more elegant). I also replaced the evil evals with friendlier parseFloats.

There were tons of things that I fixed that may improve speed (ever so slightly). For some reason the application relied highly on the xyinput div. So many DOM operations obviously isn’t too good when you could store all of this in a simple variable. This was a relatively minor problem.

This solved almost everything. you could switch tools, draw squares, rectangles, ellipses, circles, paths, etc. But Select failed miserably.

Still, there was a problem with the select box, so i made a quick hack. SVGRenderer apparently does direct dom operations to the page. Eventually, i’ll have to track down every one of those dom operations and replace them with something scripted. But i decided to copy over the html from onlypaths html and put it inside a ext windows object. Show it, and hide it. That’s why after you press "enable onlypaths" you may see a little box pop up and vanish  almost instantly. Now select almost works. it kept nagging about no document.forms[0].code. So I commented out all those lines.

I implemented a select() function to the tools. so I can dynamically select them. It used to be a sort of read-only system with the tools. The user could input to the toolbox, and that’d alter the display and change the tool (for onlypaths). but you couldn’t script it to change the display. So, now it by default automatically selects the Rectangle tool when you press the magical link.

I actually don’t know why I made the whole enable onlypaths thing sort of opt-in. I guess it is because its currently the least-stable part of the application. So, this prevents the app from crashing on startup (hopefully).

The colors (fill and line) and linewidth are integrated into onlypaths.

You see a nice little UI for where where the drawing canvas will look like. It is basically a clone of the Flash UI, but I like it :P.

Today, i just added a new theme. "Orange"