Since my last few posts have been fluffy meme-age, I wanted to take a few minutes and talk about something real I've been working on: the next version of Journey
( Read more... )
Interested in working on merging into the Brassy's Database? Right now, the DB is great for player and character tracking and plots, but could use a good flexible player questionnaire functionality. (You saw what we have since Lullaby of Broadway uses the Brassy's DB).
Possibly. If I recall correctly, the Brassy's database is written in PHP, right? Journey (and the Festival site) are written in Ruby on Rails, which means they couldn't easily become one app.
But that's probably not relevant anyway. I'm not planning on merging Journey and the Festival site into a single application; I'm planning on exposing an API (using REST or XML-RPC or SOAP or something) for other apps to hook into Journey with. That means you could likely use it from Brassy's just the same way I'm going to be using it from Festival.
Actually, I've been informed that I'm wrong and it's actually written in Perl. Either way, hooking it up to Journey should be relatively easy given an API.
Comments 5
Reply
But that's probably not relevant anyway. I'm not planning on merging Journey and the Festival site into a single application; I'm planning on exposing an API (using REST or XML-RPC or SOAP or something) for other apps to hook into Journey with. That means you could likely use it from Brassy's just the same way I'm going to be using it from Festival.
Reply
Reply
Reply
That said, Journey could become a marketable product if that's what you wanted from it.
Reply
Leave a comment