Woo!  Two major accomplishments, both for qrisper and myself.

I finally figured out how to post qrisper answers to Twitter.  Users now have the option to auto-post all of their qrisper answers onto Twitter.  A small step for some but a giant leap for Jungkind.

Also finally figured out the correct MySQL query that displays on your question page your submitted answers plus the answers that your followees submitted.  The key piece that I was missing…parentheses.  Blerg.  Think I need to more schooling on PHP and MySQL.

My next intended major tasks were going to be a qrisper app on Facebook and learning how to use Amazon Web Services.  However, I decided that I had nothing compelling to offer Facebook at the moment.  So that has been pushed back.  As for AWS, I’ve discovered that implementing qrisper in the cloud might be a tad complex for me at the moment.  Going to need a systems engineer to manage that for me.

Here are some additional updates:

• minor tweaks to the follow/do not follow functionality
• added a list of newly suggested questions into the suggest question page (for registered users)
• updated my php version of the sitemap but removed that page althogether and am now using an xml version
• with all of recent redesigns to the current layout, I had neglected the admin pages.  Those pages are now macking the new look
• added a list view for skipped questions (in addition to the current top ten view)

I also fixed the category navigation in the splash page so that clicking on a specific category will keep you in that category question pool.

I had been getting some comments that the color scheme in qrisper was a bit noisy.  It might simply be personal taste (I like loud, bright colors) but I decided to tone it down a notch.  The one thing I cannot back down from is the yellow background.  I’ve tried different colors but so far haven’t been able to find one that maintains the qrisper vibe.  Think the new creamier yellow looks pretty good.

Sheesh, it’s already been almost three weeks since my last post.  Good thing no one reads this thing.

Anyway, a slew of updates for qrisper.com.

• totally redesigned the layout…well, not really.  Just got rid of the image tabs and combined the center columns.  I spent so much time making those tabs though…oh well.  I’ve been meaning to get rid of them…just couldn’t get myself to do it.  I think the site looks cleaner and more open.
• also changed the content, design and navigation of the logged in pages.  The question page contains one question and a bunch of your recently answered questions.  Still trying to add the answers of the people you follow.  I’m basically ripping off Twitter.  But hey, whatever works right?
• added a feedback tab to give it more of a presence.  Hopefully, users will hear the feedback tab beckoning for feedback and do its bidding.
• fixed the user thumbnail uploader.  So you can upload pictures of yourselves into qrisper.  Hooray!  Problem was that I was trying to insert the image path into a mySQL table when I should have been updating the table.  Duh.
• built out the account settings page.  Now you can update your info, password and profile pic.  Still working on the functionality that will autopost your answers to Twitter.
• built out the find and follow people page.
• added the timestamp of when you answered the question.  That was one major pain in the ass.  Could not for the life of me figure out the proper syntax for the mySQL query.
• last but not least, I create profile pages for each user.  Whereas before you could only see your own activity, you can now peruse other users’ answers and questions.  Much easier than I had expected.

With all of that accomplished, I felt pretty good for like a minute.  But there’s still so much that I need to do.  I want to integrate Facebook Connect and create a FB page for qrisper.  Need to get the Twitter post working.  Also need to add a few more navigational features and content.  But I finally feel like I’m getting close to an official launch.  Been thinking long and hard about how to approach that.  Just gotta do it I guess.

Wow, lots of changes this week. First, I decided to remove all ads from qrisper.  Figured I wasn’t going to be making money that way any time soon.  So why clutter up the site?

Removing the ads gave me some room to play around with.  So I changed the content and layout a bit, primarily by removing the leaderboard section.  I also gave search its own tab and removed the searchbar from the page.  And I moved the recent answers into the search tab and added categories to the left column.  After chewing on it for a bit, I think I’m going to bring back the search bar…just need to figure out where to put it.

Had a couple of duh moments.  I was maintaining duplicate files with slightly different content for logged in/not logged in users when I realized that a couple of PHP if statements could swap out the content using the session id.  Yeah, duh.  Doesn’t end there folks!

I was using Simplepie to pull the latest q&a’s from my database.  But then I realized, why the heck am I not pulling the data directly from my database instead of using my own RSS feed?  Umm, beats the heck out of me.  Anyway, changed that.  Progress!  Slow but tangible.

I didn’t forget about the non-existent logged in users out there!  The right column will become the exclusive domain for the logged in user.  Added some stats (questions answered, skipped, remaining, etc) so that users can keep track of their progress.  Gonna be adding a lot more exciting stuff so stay tuned!

Furthermore, the main questions page was modified to  focus is more on the users answers.  I came to the conclusion that I need build two very different qrispers – one for folks seeking answers, another for folks seeking questions.  And with that, qrisper just became a lot more complex.

I’ve been meaning to write a few thought pieces on where qrisper is headed.  Read a couple of interesting blog posts that I plan to respond to.  Hopefully some time next week.

Well, I succeeded in removing four images from the index page. But I replace those with a couple of hundred lines of javascript. Meh, what’re you gonna do. Went a little nuts with jQuery. I changed the forgot password link to do a little switchToggle animation. I also replaced the original qrisper leaderboard ad, which used to be a simple onclick/onmouseover event, with a snazzy sliding panel.  I think it gets the message across, don’t you?

But I didn’t stop there with the javascriptin.  I wasn’t happy with just having the recent answers in the left column.  So I added a cool accordion function, this time using prototype/scriptaculous.  I saw another version using jquery but I liked this one better.  I think it’s pretty neat.  Except I couldn’t figure out how to set the max height for the content (that’s why the recent answers heading isn’t sitting flush against the bottom).  I decided to leave it as is since it doesn’t look that bad.

The problem with the accordion function, however, is that as soon as the user clicks on on of the recent answers links, the page will load and the recent answers column will reset back to the bottom.  Not very user-friendly.  So I figured I’d add a dash of ajax and make the recent answers links load on the screen without a page refresh.  I found another handy tutorial on Nettuts that did just that.  But the source code appears to have gone through a number of revisions, with the final version incompatible with the current versions of IE7 and Safari.  Looks great on Firefox though!

All of these javascript functions were weight my site down.  So I looked into ways to optimize the handling of my source codes.  Initially, I was using Google’s Minify to minfiy my code.  But then I discovered that Google also hosts most of the popular javascript libraries.  So instead of attaching a copy of those files, you can link to Google hosted copies.  Those are already minified and could potentially provide a speed boost if your users already have a cached copy of the library, which most people probably do.  You can find all of the details at Google’s AJAX libraries API.

With the addition of all of the new fancy effects, I also decided that qrisper would no longer support IE6.  So I created a redirect page for those poor souls still using that wretched browser.  I’ve been using IETester to test qrisper on IE6.  Worked pretty well.

Decided to take a breather on the php to focus on the interface.  Actually, the php issue was interface related so I guess what I really mean is focus on making qrisper a bit flashier looking.

The landing page was getting a little noisy so I decided to put the registration into a modal window. I used jquery and followed a tutorial from yensdesign.com.  Implementation was pretty straightforward. One thing I want to tinker with is the location of the window.  It looks a bit off-center…I noticed that on the tutorial as well.  If anyone can see the reason why, please holler (code below).

function centerPopup(){

        var windowWidth = document.documentElement.clientWidth;
	var windowHeight = document.documentElement.clientHeight;
	var popupHeight = $j("#popupSignup").height();
	var popupWidth = $j("#popupSignup").width();

	$j("#popupSignup").css({
		"position": "absolute",
		"top": windowHeight/2-popupHeight/2,
		"left": windowWidth/2-popupWidth/2
	});
}

I’m using jquery with prototype so I needed to make sure that I included jquery’s noconflict clause and change the $ variable for all jquery scripts (hence the $j).  There’s so much information out there about jquery that it’s hard not to use it.  But now that I have the power, I need to be responsible and practice restraint.  qrisper’s getting a little large around the waist from overindulging on all of those image files. Found this site on web optimization, telling me that qrisper needs to go on a  diet.

Also added a little feedback button…meh…looks alright.  The button made me realize that I’m digging myself into a trap.  I am maintaining slightly different versions of the same page.  Which version the users see depends on whether or not they’re logged in.  Decided that I could probably use a php if statement to swap out includes depending on whether or not a session id exists.

Wanting to trim the fat further, I went to clean up my css files and optimize them with a few new tricks I learned.  Big mistake that was.  Spent a few hours fixing all of the damage I caused.  I found the tips from David’s old blog.  Actually found a number of good resources…a few of which I used to fix a few issue that had been bugging me.