image upstreaming test Now I'm checking to see if the images get referenced from the correct place. 6:57:11 PM comments () trackback [] |
home again home again jiggity jig Okay, I'm home and I figured out why I was losing directives. Let's see if this fixes things. 5:54:52 PM comments () trackback [] |
okay, I give up now Okay, I'm giving up now until I get home.
I hate this. Murphy laughs when you announce a release. |
really, this is just an excuse to test Boy, the difference between the PowerBook I had on loan and the one that I just purchased is striking. The one I had on loan was of the first generation of TiBooks, and the current one is the latest generation, and the fit and finish is even better. The first TiBook didn't like to be on unsteady surfaces, like my lap. It had a nasty habit of losing power when I needed it the most. I got used to seeing the system date set to some time in 1969. And the DVD drive made me a little nuts -- if a disk was spun up and I rested my hand over it (which is standard operating procedure if you want to type on the keyboard), the case would flex just enough to make contact with the spinning disc, resulting in a very scary sound. It never seemed to damage the discs, but it was disturbing none the less. The new TiBook is solid as a rock, and the SuperDrive uses a completely different mechanism for loading and holding the disc. I have yet to feel as if I was in danger of destroying the disc while it was spun up. The increase in screen resolution between the two is interesting. The original TiBook had a resultion of 1152x768, and felt roomy, but I still liked the extra real estate gained by hiding the dock. The new TiBook is 1280x854, and the extra space gives me just enough room to keep the dock unhidden, without feeling like I'm wasting space. It's just nice. I've mentioned before how much I like Apple's industrial design, and the new TiBook just confirms it.
All this just so I could see if the #imageAlign "left" directive works
correctly. |
something strange is going on Something strange is going on, and it's looking like directive parsing is getting some things wrong. It also looks like the images are getting doubly uploaded; once to the /images/mailEdit/... directory, which is where they are supposedto be going, and another time to just the /images/ directory, which would be bad, because we could end up with a potential filename collision (which is why I was putting them in a date-oriented subdirectory to begin with).
Dig dig dig. |
even more testing More testing. I want to see what happens when more than one image is attached, and I've specified the imageAlign directive. I'm curious to see if they will be displayed next to each other or above one another. I'm actually hoping they will be above one another.
I'm fairly certain that this testing stuff is kind of boring. |
isn't it always like that? Great. I just sent out an invitation to the Radio-Dev list for testers, and I realize that I've got a minor bug. Last night, at the request of a friend, I added the "imageAlign" directive, which allows you to place your images to the left or right, and have text wrap around them. Which it does quite well. However, if you try to #get that post for editting, you'll notice that the "imageAlign" directive is not returned correctly. As a work around, you'll just have to supply the imageAlign directive again. At least until I get back home to fix it.
This is going to bug me all day. I guess I need a version of MailEdit
for remote code editing. |
burning in It's exciting to get to this point in the development cycle. The initial feature set is complete, the bugs are getting squashed, and now I'm just letting the software burn in for a while before I make the announcement that it's time to ship. Actually, it's not -quite- time to ship. I want more people to give it a try, and use it in ways that I haven't anticipated, to try and shake out more bugs. I'm fairly proud of the preferences pages I've set up for the tool. They catch some common errors, and I hope they do a pretty good at explaining what each setting does. The best part is the future potential. I've laid the groundwork for a general mimetype handling system, although right now it's just for images. I want to be able to handle pretty much any attachment type, and I've got a table that maps mimetypes to actions (actually, right now it just maps mimetypes to file extensions so I know what to point the image link at).
So, to sum up, expect a general Beta announcement soon, and perhaps I
can go gold this weekend. |