On our last post, we mentioned that the goal of our yet-to-be-named project is to provide documentation for a certain application. To do this, we insert screenshots of that app, determine the areas where information is contained, stick annotations to them, and link those annotations to lessons which would give the user information about that part of the app. But then after a week, we thought of this and that, and asked how about this? and that? then we realized, why not use something more than a screenshot?

When we had a meeting with the big bosses, one of them stated that it would be a nice feature to make the screenshots as real as possible. What that meant was, if the actual app had a link to another part of the program, and if that certain link in the screenshot is clicked, it should be able to do the same thing. We all agreed that the idea was good, however, how to do it? Then one of our faculty interns gave an incredible suggestion (credits to sir eugene): why not incorporate the actual application itself!  After much talk and arguments, we came up with a final decision: scrap the screenshots, we're going live!

Now comes the hardest part, how? The only solution we had in mind was to use, (chedeng!) html iframes -- inline frames. This means, instead of inserting a screenshot, we get the url of the app, put it in one of the iframes, and there we have the live application, as if the user is browsing the real application (which is actually what the user is doing). This is definitely more powerful and cooler than using screenshots but it comes with great price, it's definitely harder to handle. And what's more, this is only a part of our yet-to-be-named project, and there's much much more details to consider and think about. On the positive side, it may be very difficult but it's a start. A start that has an end, hopefully. Good luck to us!