Meanwhile I'm working on a completely new template for my blog, I made the decision to temporarily rever the blog's template to something very simplistic. This will give me the flexibility to be able to add richer content without having to worry about the constraints of the previous blog template, and start looking forward to the eventual implementation of the new one.
I did run into one snag: Since WordPress's own default theme is really formatted for a fixed width 800x600 screen, it doesn't jive with my new design & content areas. I looked around and found this theme, which is a 1024 adaptation of the original WordPress template. You can download this template here:
I still can't find what's wrong with AJAXed WordPress. After a few back & forth on the author's forum here, he offered a few things that I could look into, but nothing I did or could look into solved the problem. The only thing either of us can point to seems to be some weird error thrown by the newest version of WordPress:
Warning: htmlspecialchars_decode() expects parameter 1 to be string, NULL given in /home2
/pixelpu1/public_html/blog/wp-includes/compat.php on line 105
I can't figure out what that means... there are nothing in the configuration that even points to that directory. Comparing the old "compat.php" in WP 2.7 and WP 2.7.1 revealed that the new compat.php file is incredibly huge compared to the old one, seemingly with a lot more error checking routine than before.
The only thing I can do for now, is revert back to WP 2.7. I'm also considering a new blog layout that will probably make AJAxed WordPress unnecessary anyway.... Things to ponder...
AJAXed WP is still broken, but I've reactivated it in hopes that the author can come take a look and try to figure out what's going on. I've tried several things, including:
Disabling all addons other than AJAXed WP.
Re-uploading all the files from WP 2.7.1.
Re-uploading AJAXed WP files manually.
Changing back to default theme.
Nothing's worked so far... I'm gonna try a database repair or something next.
Update:
Performed some database maintenance routines... optimizing and removing overhead. It's not having any effects.
I upgraded to WP 2.7.1 today, and it broke some functionality in the "AJAXed Wordpress" plugin. So if you click all the "click to continue reading..." links, they won't work. I'm too lazy to deactivate the plugin right now, since it'll make my "wall of text" look even more daunting than ever. You can still read the full blog post by clicking on the title.
Hope they fix it soon.
Update: Temporarily disabled the addon and inserted old school ---more--- tags on the more recent posts.
QuickSilver, for those who are unfamiliar, is one of the greatest software utility on Mac. On its most basic level, it is a text-based application launcher. With some experience with its more intricate features, you can select and copy multiple files from different locations, append text into files, create drawers for multiple copy and paste as well as storing text clippings. Some people would go as far as getting rid of OS X's dock altogether and base their entire workflow on just QuickSilver alone.
In the past year though, the development of QuickSilver came to a grinding halt. It was put into the open source community but received very little attention since. The original developer of QuickSilver now works for Google's Mac division, and has been focused on other projects. So imagine my excitement when I came across the article on Smoking Apples Blog that the same developer has unveiled his latest project, Google Quick Search for the Mac.
I've been using Firefox 3 beta for a while now, and it's a definite improvement in memory usage and speed over Firefox 2. As expected, it's taking some of the addon developers quite a while to write new versions of their addon that's compatible with Firefox 3.
Granted, I don't use a whole lot of Firefox addons, but there is one addon I couldn't live without: The bookmarking addon from del.icio.us. Since I work on multiple computers at work and home, del.ici.ous has became a valuable tool to keep all of my bookmark in one place. It's also much more flexible than Google Bookmarks.
Now there is a beta version of the del.icio.us addon for Firefox 3, available here:
Just follow the link and install the new version of the addon, so far it's been working great. With the availability of this addon, my switch over to Firefox 3 is complete.
I can't take credit for the title of this post, it's really just a part of the discussion on one of the TWIT podcast this past week (or was it the week before? I can't remember). Last week Google announced an astonishingly underwhelming software platform. I mean, it's not horrible or anything, it's just disappointing that a lot of people were expecting Google to throw their hat in a complete consumer product, rather than a half-assed promise to deliver some sort of product nine months from now which may or may not be any good.
Well, Google released the Android SDK today. The SDK was pretty impressive, giving us a good preview of the the OS user interface (via Engadget). However, one can't help notice how much the "mockup" looks like a Palm Centro, or any myriad of Palm or Windows Mobile device that's been available so far. One also can't help but notice how the UI takes many lessons from iPhone's UI. Imitation is the sincerest form of flattery, I suppose, but didn't everyone expect a *lot* more from Google than just another software platform that looks just like any other software platform?
I listen to podcasts when I bike to work every morning (my form of reading the newspaper while having breakfast?), and one of the panelist on TWIT made a lot of sense, although I can't recall it verbatim (and I'm too lazy to listen through a one-hour long podcast to find the exact quote). Whenever Google can't conquer a market, they fragment.
Take for example, the "OpenSocial" initiative that Google just started. Google had their own social networking property (www.orkut.com), which was almost completely forgotten as a footnote to all their other services. Facebook became the monstrosity that overtook MySpace, which long before had overtaken Friendster. Orkut, however, was nowhere in anyone's distant memory. By introducing OpenSocial, Google is undoing Facebook's dominance in building web applets specifically for their service. In away, it seems like a move that benefits every developer, who can now develop for every social networking site (other than Facebook) and support many "platforms" at once. Of course, the "side" benefit is that Google has planted the seed that could possibly unseat Facebook from its dominance at the top, and also insert themselves as the tour-de-force of any social networking site that may eventually take the throne.
Taking a look at what they've done with Android, they've essentially fragmented any previous mobile Linux development, again inserted themselves at the helm of the movement. Furthermore, they've even fragmented the Java development community as well. CNet's Crave blog has a great post on this, which touches on some of the issues with Android's SDK and overall Java development. Of course this isn't all bad, since Java in itself is a platform that has failed to satisfy anyone. However, once again it shows Google as a very shrewd company at being able to project themselves as a kind, gentle company that can do no evil; and at the same time, position themselves as the titan that is able to undermine an entire industry in one fell swoop.
Who does that sound like? You know it, it's on the tip of your tongue, you know exactly who I'm talking about.
Google's Open Handset Alliance is exciting, because geeky programmers around the world just all simultaneously orgasmed and are now struggling to hold their drool inside what is presumed, to be their oral cavity. To be frank, that was not my first response to the announcement. I had a really, really busy day at work when Google hit the press; so my first impression was, "Oh, there are some new info on the Googlephone, great!"
It was another day of soul-searching later, that I said to myself, "Wait, is that all there is to this news? That's it? Really? You mean, I didn't miss anything? I mean.. I combed through my RSS reader for hours and hours looking for more detailed information, something more exciting, something with actual substance.... and... really? That's it?" For at least a few hours, I thought I was caught in some sort of temporal anomaly and was missing vital information that Google has apparently announced to the entire world minus little ol' me.
The truth is rather, disappointing? Underwhelming? Indeed, the news outlets were positive on Day 1, and almost all universally speculative and introspective on Day 2. How many times have we been promised a "mobile phone OS based on Linux & open-source"? This harkens back to the Linux PDA days, and we all know how that went. The only difference between Google's announcement and all the other dozen open-source mobile OS initiative, is that Google has a lot of money. Shitloads of money. Certainly a lot more money than open source Linux companies that's been trying to figure out how to make any money at all by doing, anything and everything?
Of course you'll see an impressive list of partners, it's Google for god's sake! Everyone jump in the pool! The question is, how many of those partners really have any product development plans? How many of those partners will be looking for their own competitive advantage once the SDK is out? How many of those partners will actually, actively contribute to the initiative once they realized that they are at very high risk to put themselves out of business?
The answer for now is, "It's Google, they'll make it work." We'll see what develops in the coming months. I see it as Google just throwing a piece of SDK out there, and allowing the sharks to battle it out for supremacy. After all, taking this strategy really means they have very little stake in any particular company. It's a smart way to position themselves, as a software platform provider that doesn't really care which hardware wins out. If Sony Ericsson develops something great and put HTC out of business, so be it. If Nokia collapse (well, they haven't made a commitment to the consortium at all yet, probably a smart move at this point for them), it really doesn't matter to Google either.
I'm starting to see a bunch of executives & software engineers from companies gather at a coliseum built in Google's backyard (or maybe by naval airbase or something), and someone from Google is sitting atop in the Emperor's seat and just giggling at the bloodshed that's about to happen.
There's nothing fundamentally wrong with the way that Google is going about this. In fact, it's probably the smartest thing they could do to get into the mobile device arena without actually becoming involved in it. The style just disagrees with me on a personal level. I like companies that design end-to-end solutions that satisfies consumer needs. For example, Tivo is a great company that threw themselves into the heat of the battle, and forever changed the way we interact with televisions.
That kind of a company earns my respect. Google's Open Handset initiative makes me wonder, "Is this just going to be a Linux version of Windows Mobile?"
It took me a few hours to upgrade to WordPress 2.3 last night. I don't have the coding prowess of some out there, so it wasn't exactly unexpected that it would've been a painful undertaking. However, upgrading to WP 2.3 was even more difficult than I had expected due to the new tagging mechanism built into WP 2.3 (which I had known about beforehand, but wasn't expecting any issues).
Upon installing WP 2.3, I immediately was being fed errors due to the use of Simple Tagging plugin that I had before to manage tags. I had to disable Simple Tagging, then import the tags into WP's new format. The import process was pretty easy and smooth. However I immediately found that there are no tag management UI built into WP 2.3 at all. Good thing that someone had already wrote a plugin to help manage tags, but it's perplexing that you would have a blog that supports tags without any UI that help manage tags.
Furthermore, the tag cloud display that shipped with WP has no options whatsoever. It just displays a cloud, it doesn't give you any customization capabilities. You can't display a list view that I had before (although arguably I may stick with the cloud view anyway). Although there are a few early plugins that can help you customize the tag cloud display just a little bit, none of them had the flexibility of the Simple Tagging Widget.
Of course, retaining Simple Tagging isn't possible, because the database structure that Simple Tagging used before is completely invalid with WP 2.3. So even though now there's an "official" tagging structure in place, overall it is much less effective and usable than previous third party implementations. Over time, there will be third party enhancments to the built-in tagging mechanism for WP 2.3, but I'm really disappointed in how bad the out-of-the-box experience is.
Despite of how much I love the iPhone, I still don't believe in signing a two year contract for AT&T/Cingular. I've been a customer with Cingular back since when they were PacBell PCS, I have no reason to be locked down to a contract to prove my loyalty to a carrier. Especially since the iPhone isn't subsidized at all. If signing a contract meant I can save a few hundred dollars, then at least the value proposition is existent. There is absolutely no reason to a sign a contract for a phone that will inevitably be unlocked (and probably be available at the same price).
Service issues aside, the iPhone itself is simply one of the most brilliant consumer product ever made. It is a device that will completely reshape the mobile phone market. The problem is, the other phone manufacturers seem to be thinking, "Wow, the iPhone has a touchscreen, we must all move to touchscreen-only phones as well." I'm not saying that iPhone's touchscreen isn't brilliant, but it isn't the end-all solution to the woes of the mobile phone design we've seen in the past decade.
There are already several manufacturers that's decided to manufacture their own versions of a touchscreen phone. Some of which has been offering touchscreen capability for years (for example, most of HTC's Windows Mobile based phones). The problem with these phones isn't whether or not your buttons are placed on a screen or engraved into a rubber nub, the problem is the underlying unresponsive, inadequate, and sometimes down-right ugly software.
It's easy to credit an obvious invention (even though touchscreen has always been around, the type that iPhone uses, basically a type of clear laptop touchpad, is completely new to the market) for the success of a hardware product; ultimately it isn't just the hardware design, but how the hardware design interact, melds and works with the underlying software. I don't find the buttons on my Razr hard to press, I don't find the features on my HTC Windows Mobile phone to be so hard to access or inadequate; but I also don't understand why everything I do on either of these phones seems to take place 3 seconds after I've executed a command, clicked a button, or even just scrolling through the address book.
Years and years ago, there was this great, ambitious operating system called BeOS. It was built from the ground up to be a multi-threaded, multi-CPU operating system. The most impressive aspect of BeOS, was how responsive it was at handling tasks that were extremely taxing to other operating system at the time. You can run multiple windows of videos, move them around the screen, resize them and still have lightning fast response. Mind you, this was the age when most users were still living with Windows 3.1 (maybe some on Windows 95?). The software engineers of BeOS were able to achieve this, because they were very aware that the outward responsiveness of an OS is just as important to its interaction with the user as the underlying operations.
For example, while another OS will prioritize the task of writing files to the disk, BeOS prioritized the playback of that file being written, saved, copied. The writing of the file can still be finished up in the background, but the immediate feedback of that file being worked on is the most important thing to the user, and delivered a level of interactivity that was far more appreciable. The OS was instantaneously more robust because it made sure that you knew what it is doing, what you've done, then went ahead and finished up all those tasks in the background where it wouldn't bother you.
That is in essence one of the most important aspect about the iPhone. On the first week of iPhone's release, CNet even performed a real-life, side-by-side test of iPhone's UI speed against what Apple were showing in the commercial. There were all sorts of accusation that Apple had fussed with the footage, sped up some parts, edited out the lag time in between. Well, the CNet guys found that almost second by second, they can do everything that was done in the commercial with their iPhone. Sure, the touchscreen UI is slick and intuitive, but it is also the amazing responsiveness of the UI, the underlying robustness of the software, that really sets the iPhone apart from any phone that you've ever used before.
Another company named Pasen put out this video on Youtube recently:
Sure, it's a touchscreen device that completely rips off the iPhone. Look at the video, watch the number of times you had to click, double-click, drag fingers around, try to see if the device is responding. Wait, what is it doing now? Did I just select that? Is that playing now? How do I.. wait, let me click on that again.
I hope the rest of the consumer electronics industry doesn't follow suit. It's not just about the touchscreen.
