BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Edgewall Software//NONSGML Trac 0.11.2.1//EN
METHOD:PUBLISH
X-WR-CALNAME:Snarkydog - Roadmap
BEGIN:VEVENT
UID:</milestone/FargoChat 2.2@trac.snarkydog.com>
DTSTAMP:20090501T050000Z
DTSTART;VALUE=DATE:20090501
SUMMARY:Milestone FargoChat 2.2
URL:http://trac.snarkydog.com/milestone/FargoChat 2.2
DESCRIPTION:This release will deal with everything that didn't make it into
  the 2.1 release :o). Hopefully the 2.2 release will deal more with adding
  fun things and features into the chat as 2.1 was mostly dealing with bug 
 fixes and interface tweaks.\n=== Things that could make their way into 2.2
  include: ===\n * better rooms and world layout\n * theme support\n * expa
 nd on user achievements idea. Perhaps there are certain commands or places
  user can go after a certain achievement. Have a special client window pop
  up when achievement is accomplished\n * interactive forms that are dynami
 cally generated\n * Ability to pickup and use items\n * NPC or some other 
 Artificial Intelligence system\n * Look at using active rendering for core
  animation within chat applet. Look at several examples\, the best might b
 e from the threerings development kit\, called nenya[[BR]]\n=== Other Pie 
 in the Sky Ideas: ===\n * Look at connecting to IM (using Jabber client) o
 r IRC channels? We still would need our own server to proxy messages to th
 e IM/IRC channel. This might tie in best with extending the Room object. C
 reate a special "remote" room object that extends the base and allows for 
 sending/receiving messages remotely. Each remoteRoom would probably have t
 o be a separate thread? In addition we would probably have to move all mes
 saging functions from the player to the room\, at least the definition of 
 the function\, the player object would just proxy the function call to the
  room/channel.\n * Look at Html/Javascript client. This would allow us get
  rid of the java/swing client\, which though it works\, is a pain in butt 
 to work with. Look at the AJAX/Comet technology. We should be able to supp
 ort of all of the current efx on client in add some new/better ones fairly
  easily using some of the javascript libs out there like prototype or mooe
 fx.\n * OR we could still use java for the client connections and then use
  html/javascript for the display using live connect. Not sure if this work
 s on all browsers??\n * I would probably have to change this version to 3.
 0 if I did all this!!
END:VEVENT
BEGIN:VEVENT
UID:</milestone/Mute Server 1.0@trac.snarkydog.com>
DTSTAMP:20090630T050000Z
DTSTART;VALUE=DATE:20090630
SUMMARY:Milestone Mute Server 1.0
URL:http://trac.snarkydog.com/milestone/Mute Server 1.0
DESCRIPTION:Really this release should be the final release unless any hard
  to find bugs are found. '''OR''' if I find a better way to do things\, in
  which case I will just rewrite everything from scratch for the 5th time. 
 Maybe this should be called version 5.0? Most of the work left really has 
 more to do with fleshing out the javadoc and any help files that need to b
 e created.\nA few of the things I need to finish off:\n * Improve the JMX 
 handling of internal objects? \n * Better examples\, perhaps a simple HTTP
  server.\n * Make more use of annotations for XML parsing.\n * Flesh out j
 avadoc and help files
END:VEVENT
END:VCALENDAR
