Moving hosts - some downtime expected.
Monday, January 12. 2009
Because of how troublesome this blog software has been in the past when moving from one host to another, I expect to have some difficulties and downtime. I'm not as concerned with this portion of my hosting being up as I am with other domains under the same plan, so I'll probably move everything over, make sure they all work, then come back and take a look at this.
I know, it's not professional, but since it's my personal blog, it doesn't have to be. :) I'll be moving hosts sometime before Saturday morning.
I know, it's not professional, but since it's my personal blog, it doesn't have to be. :) I'll be moving hosts sometime before Saturday morning.
Yay for hiatus.
Wednesday, January 7. 2009
So, after an interruption of work, first with attempting to fix a core bug with CakePHP to help fix a bug with my own application on our staff site (and failing miserably to create a unit test case so it's not yet fixed), and then being asked to create a Tri-fold pamphlet for a series that our library was putting on (with no knowledge of the series itself other than its name, and the 6 programs), I've been a little busy - oh, and holidays, traveling, and more traveling. (Gonna be out in Arizona for a week starting on the 17th.) Fun times, fun times. I am back to reading up on more stuff about Adobe Air. Our library just got the O'Reilly "Adobe AIR 1.5 Cookbook" and it does have some pretty good examples. Unfortunately, even though extremely confusing and too technically written, I think the official Adobe Help documentation is probably a more thorough resource for me. IT'S SO DRY.
Either way, skimming through the cookbook, I already found a few notes to jot down, such as how to access information about the current monitor's resolution in order to set the location for my application (when using AIRAliases.js with HTML/JS creation):
...and there was a nice and easy example of how to use custom "chrome" with HTML/JS minimize and close buttons:
I've got the internal SQLite chapter bookmarked and may take a quick look at it later if I ultimately decide to deal with network failure to the production DB store or not.
Either way, skimming through the cookbook, I already found a few notes to jot down, such as how to access information about the current monitor's resolution in order to set the location for my application (when using AIRAliases.js with HTML/JS creation):
air.Screen.mainScreen.visibleBounds.width air.Screen.mainScreen.bounds.height
...and there was a nice and easy example of how to use custom "chrome" with HTML/JS minimize and close buttons:
onClick="window.nativeWindow.minimize()" onClick="window.nativeWindow.close()"
I've got the internal SQLite chapter bookmarked and may take a quick look at it later if I ultimately decide to deal with network failure to the production DB store or not.
