Most of the recent programming sessions were spent ironing out the invitation and registration system used by the application both from the main site and the FB portal.
FB has a very particular system of application invitation which attempts to prevent abuse. As an avid Facebook user, I can state from first-hand experience that the invitation system needs work as I have been deluged with invitation requests not only for application but for friends and events.
I have a invitation system in general which will limit who can join the game. This will prevent people from adding the application until its ready. For now, I will setup custom invitation codes by hand for a select group of alpha testers.
A big consideration in releasing any system is the readiness of that system and whether any users will be turned off from trying the beta once they have been burned by an alpha system.
Tuesday, September 2, 2008
Friday, August 15, 2008
Rendering
Most of today's programming session was centered on CSS. Certain styles were embedded directly into HTML elements using the style attribute. I worked at removing these, organizing styles into classes, and altering the rendering to appear similar cross-browser. I am still having difficulties with IE however.
I also added a history pane, which shows the game history in terms of hands played.
I also added a history pane, which shows the game history in terms of hands played.
Saturday, July 12, 2008
Consolidation
The original web app was written in an include-driven method, which has not translated well to Facebook integration. I have therefore consolidated most application code into a new global application class which handles processing. The includes merely call these application-level methods to perform processing.
In this way, I can derive a Facebook application class from a parent and override certain key virtual methods which control rendering, which Facebook is very particular about. Facebook only accepts a certain subset of HTML and javascript in its integrated applications.
In this way, I can derive a Facebook application class from a parent and override certain key virtual methods which control rendering, which Facebook is very particular about. Facebook only accepts a certain subset of HTML and javascript in its integrated applications.
Thursday, July 10, 2008
First Things First
After recreating the former schema and ironing out some more of the setup issues and before beginning the integration, I decided that I would need to add a much requested feature--AI.
I decided to work on two levels of AI, one really dirt simple bot, and another more advanced one. The simple AI took several programming sessions to implement.
It involved developing routines to generate all possible moves given a player's hand, and rewriting the code to allow retrieving the appropriate hand from an AI Player subclass of the general player class.
The second level of AI has been less straightforward and is only 60% complete thus far, despite certain assumptions I have made to ease the task.
I decided to work on two levels of AI, one really dirt simple bot, and another more advanced one. The simple AI took several programming sessions to implement.
It involved developing routines to generate all possible moves given a player's hand, and rewriting the code to allow retrieving the appropriate hand from an AI Player subclass of the general player class.
The second level of AI has been less straightforward and is only 60% complete thus far, despite certain assumptions I have made to ease the task.
Thursday, June 26, 2008
Revival
I had been working on a few Facebook applications when I remembered that I already had a working web game I had written in college. It was a simple game based on the card game Thirteen, which some people call Control. I decided to try to find the original code for this game, recreate the MySQL database backend and schema, and adapt it for Facebook.
Subscribe to:
Posts (Atom)