So I am not much for talk right now so straight to the points:
I started Pymetheus originally to create a platform for a near real time web based multi-user dungeon… but I wasn’t satisfied with what was available as far as feature complete frameworks and toolsets. I wanted to create a VERY rich web application that used as much of the newer possibilities being rolled out by HTML 5. Specifically web sockets, local & session storage, and then branch out to using the Canvas tag and whatever else I could pull off. So a normal bread & butter html
Change of plans:
I’ve had more rewarding of an experience making the platform then I have making the game. Of course I can’t make the game until the platform is stable, but with few exceptions, when is a platform ever completely stable when it involves the internet?
Client side is a rich web application that relies completely on dynamically injected/loaded content and logic to function. On the initial load, there is nothing but a blank blue page and about half a dozen scripts src’d in.
From authentication, modules, mini-app like bundles, are bootstrapped into the client by means of dynamically injecting new script tag’s with src links to corresponding logic. If any of the modules depends on external content like images or extensive HTML markup, that logic is dynamically loaded in as well.
While all of this is happening, the service side is merely instantiating classes called handlers to provide the business logic and hold some of the more important parts of the module’s state. One trick about these handlers is that they don’t have to belong to the platform but instead can come from any package available on the Python import path. The closest comparable design to this would be a WSGI based application, where a WSGI app can include other WSGI apps according to the URL path.
Anyway, I have the platform up and running and the three parts I feel need to be hammered out some more are
- Working example of a Model system
- Cleanup the user management system, it’s functional but has some weak points in it’s design
- Implement a multiplexing message system that won’t encumber the platform, specifically for passing non-control messages between users.