CSE499 Project: vBulletin Calendar API

vBulletin is a commercial Internet forum software produced by Jelsoft Enterprises Ltd. It is written in PHP using a MySQL database server. Even though it’s not a open source product, I am planning to extend its Calendar feature for my CSE499 project, research course in our university, NSU. What my initial plan is to use vBulletin Calendar system for developing an instant notification system. So, my and my teammates’ (Tanzil and Suzana) task would be to develop an API which will act as a remote agent for client applications. Such a client application may look like this figure: And its rough SRS (Software Requirement Specification) can be: There should be two GUI (Graphical User Interface)

1. Login Form

There should be two textboxes for username and password. Application should be able to check user input validity and prompt accordingly. On successful login, this login form should be set to hidden and then main frame should popup. If login attempt fails, should give error messages.

2. Main Frame
   1. When user clicks an item in calendar list, the event category list should update itself.
   2. When user clicks an item in event category list, the event list should update itself.
   3. When user clicks an item in event list, the event description panel should update itself.
   4. Left click on an event item, will popup options:
   5. Notify event:
      1. Should ask for time before event reminder and send request to API.
      2. After getting positive response from API, should put a FLAG icon before it.
   6. Do not notify event:
      1. Send request to API.
      2. After getting positive response from API, should remove FLAG icon.
   7. mark as read:
      1. Mark event as read.
      2. If already marked as read, this item should be disabled.
      3. This is a local feature.
   8. mark as unread:
      1. Mark event as unread.
      2. If already marked as unread, this item should be disabled.
      3. This is a local feature.

Auto Notification Feature:

• As long as the application is running, it should check for updates automatically. User should be able to update interval in minute (Min value: 5, Max Value: 60)
• A popup in taskbar should show up as soon as there is a new event post.
• Until user has a new message for reading, corresponding calendar and event category should turn RED.

As the interface design states, there should be four scrollpanes. These are for Calendar List, Event Category List, Event List and Event description. After login the application should populate the lists. Once again, we are not going to develop client applications but the API, which might be useful for developing such applications. The diagram, shown above, gives you the idea how and where the events would be available. A subscriber does not have to browse forum or check for regular updates oneself; the updates will ring the alarm wherever you are: firefox sidebar, facebook application, opera widget, desktop application, IRC (Internet Relay Chat) and your mobile in your pocket! Even a commercial industry can use this for another SMS service. So….. what do you think?