After some late nights of programming, wordpresswave V 1 is ready to launch! I have sucessfully implemented posting, reviwing posts, reviewing titles, editing, deleting, and suggesting new blog topics. The only currently known bug is within the suggesting new blog topics. This analysis is very processor heavy and for some reason does not work in regular preview. The results appear on the logging screen, however they are not in the wave. Yet this works in sandbox. This leads me to believe that it will work in preview within the next couple days. It has been an interesting experience working with wave, though, because of time constraints, I am glad its nearing the end. AI / lisp here I come!

The edit feature is finally live! After using the wp:edit command the bot will respond with your selected post. You can change the title and / or post content and click done and the bot will update your blog. Want to make another change? Simply edit the blip comtaining once again or start over by calling wp:edit and then editing that response. Happy editing!

After unsucessfully playing with classes, I am trying a more old fashioned way of allowing a user to select their blog (before it was hard coded to publish to my personal blog which, while useful for me, is not useful for distribution). I have decided to pass log in information durring every blip, however, to prevent a user from entering this information in multiple times they have the opportunity to type in in following wp:configure. This will respond with preformatted blips including their information. You can edit these blips, submit, and then your action has been performed. The key is not deleting your initial wp:configure blip so that you only have to type this information once. This goes without saying that your wave should only contain you and / or the blog collaborators given that personal information will be store within this wave.

I have 7 more invites… let me know if you want one.

For some reason this took much longer than I had expected. The key problem here is that mysql sequentially stores your posts in database, however, if you delete posts then retrieving posts using a simple for loop does not work. Consequently I had to tap into a recentPosts function which finds your most recent published posts and then returns them.

I am sitting by the fire demonstrating the post feature to Lyssie and Katherine.

So it is allowing me to post straight from google wave, though my regexs are not correctly processing the title. It seems as though I ran the regex but never concatenated the text. This also meant that using r.split() was also recognizing the : from the command. I have concatenated the text and changed r.rsplit to r.split. Hopefully it works this time?

This is my first post straight from google wave. I hope it works!