dentin (dentin) wrote,
dentin
dentin

Long term number 2

Since the last post, the only real item I can remove from my list is the xml layer. There's been a lot of other stuff done since then, but none of it really applies to other list items. It also occurs to me that the list items need to be more specific, so that they can either be marked off or changed from update to update. For example, the 'learn javascript and html5' thing can probably stay, since once I complete it I can break it up into multiple pieces. The 'work on core server libraries, general' item however should go, since it's never completed. Things like general library maintenance should also only happen as a means to an end, not an end in and of themselves.

A good question to ask when doing something is, 'what do I intend to do with the result of this work?'

Old list:

1) learn enough javascript and html5 to make a web client

2) work on core server libraries - socket/ssl layer

3) work on core server libraries - binary packet layer

4) get together an interim dclient release

5) server code - daily autogenerated quests

6) server code - start work on druid class

New items:

7) I just bought the 'blindsoftware.com' domain name, and need to put up a placeholder web page. It would also be a good idea to figure out what exactly I'm going to do with it; I certainly have the ability and tools to create blind-specific apps, I'd just have to sit down and do it.

8) Try to create new player introduction areas for mage and cleric classes (necromancer was an experiment, and appears to be a hit.)

9) Dclient http downloader, so I can replace wxHTTP (which crashes on a lot of builds.)

I also really want to start work on a separate server, but I have a problem: cross game accounts. Ideally, I should be able to set up an account server which handles all the credit stuff, email addresses, and character names (to prevent cross-game douchebaggery.) The down side is that I really don't have a good way of doing this, and I don't at all trust databases. A database is honestly probably the best option, but I'm really not sure how I feel about it and I don't know much about them. I'm also not used to having use request/response style apis; most of the things I have done are single threaded, and either happen instantly, or are at least synchronous/memory resident.
  • Post a new comment

    Error

    default userpic
  • 0 comments