Recent Posts

Pages: 1 ... 8 9 [10]
91
General Discussion / Re: Hypothetical : New gamebook platform requirements
« Last post by Chris on October 23, 2013, 12:21:26 PM »
Speaking from experience, the best way to come up with an architecture for a gamebook platform is to use that architecture to build a gamebook.  ;)
92
General Discussion / Re: Hypothetical : New gamebook platform requirements
« Last post by Villain Mastermind on October 22, 2013, 03:39:56 PM »
Here is an extremely brief overview of my favorite permutation of the web-components idea:

PixelBook - The root element of the application
  • Displays the designated "Page" element
  • Acts as the primary controller, handling the specifics of basic functions like "Page Turning" and most other logic
  • Stores various elements invisibly in storage-divs walled off from the user by hiding them in element's "Shadow DOM" (e.g. Page, ?VarData?, Pix, and Passage/Snippet elements not residing in a Page element)
  • Contains and manages a "Log" component that can be displayed for debugging purposes
Log - A normally hidden element that is activated when the application is running in debug-mode so it can store various "LogEntry" elements

LogEntry - Text messages that record debuging data like events, state changes, and error messages

Page - Primary display container for templated application content

Passage - A semantic extension of the "p" element (?additional funtionality?)... Can either exist directly in a Page element or be stored invisibly in the root element for dynamic insertion
 
Snippet - Serves a function analogous to the Passage element, but extends the "span" method instead for containing short chunks of inline text... Can also exist directly in a Page or be stored for dynamic insertion
I have about a dozen different ideas about how to implement variables... Still batting around the best way to do it. Suggestions and brainstorming is appreciated

Pix - An extension of the "img" element with addional functionality?
 
Tbox - A special extension to the "div" element for additional layout options along with extra functionality like a type-writer effect... Would be useful for "Visual Novel" applications or ones that need that old-school feel.  (Might make that also available on passages)
I dunno... Still playing around with different schemes.
 
Suggestions and/or Ideas, anyone?

* A Note on the state of the available polyfills *
X-Tags appears to be a partial implementation at best
Polymer requires a web-server, so a purely client-side web-app (which is exactly what I want at this stage) is impossible to build with it
93
General Discussion / Re: Hypothetical : New gamebook platform requirements
« Last post by Villain Mastermind on October 21, 2013, 09:15:37 PM »
After dreaming up several dozen different ideas and plans, I've settled on one that does exactly what I want in a way that isn't a tangled mess. Actually, it is so simple that I'm almost ashamed and humbled that it didn't occur to me sooner.

Web components! The only way to achieve what I want without a horrendous mess of divs and javascript hacks.

But there is a catch...

The technology is quite literally experimental, which makes prototyping a giant pain in the ass. The latest versions of Chrome Canary have the needed features after tweaking the application flags, but it still acts a bit oddly. There are polyfills and shims, but they are ugly as hell, but I may have to suck it up and use them even to get a proof-of-concept prototype up and running.

Oh, well... *sigh*

I originally started coding it in TypeScript, but the web component angle was such a delicious alternative that I dropped it on the spot.
94
General Discussion / Re: Hypothetical : New gamebook platform requirements
« Last post by Villain Mastermind on October 12, 2013, 07:57:26 AM »
I'm in the initial design stages, more or less.
My dayjob being a corporate slave and minor related life-events have been delaying progress, not to mention time spent researching and throwing out overly-complicated designs. The simpler the system, the easier it will be to learn, use, mantain, and modify to the user's needs.
Gonna use the "Chaos Model" for this particular project... I found it in one of my research missions and instantly fell in love with the idea.
I'll post more as my life permits.
95
Noticeably, interactive text doesn't have many of these problems. One good quote:

Quote
And emotion is carried fairly effectively through movement, too, which is why Bioware Face - the name I have for two characters standing stock still, facing each other, maintaining eye contact and making occasional gestures that are completely unrelated to what they're saying - seems so wooden and jarring.
96
General Discussion / Re: Hypothetical : New gamebook platform requirements
« Last post by Chris on September 30, 2013, 03:04:12 PM »
Well it's a good idea to define some stakeholders here:

  • Writers (probably want something easy to write with, with easy ways to manage standard gamebook logic/inventory/choices, as well as publishing options)
  • Programmers (probably want something extensible and easy to modify)
  • Readers (probably want something that looks good)

Are you building something?
97
General Discussion / Re: Hypothetical : New gamebook platform requirements
« Last post by Villain Mastermind on September 28, 2013, 09:10:34 AM »
Off to a good start... A little confusion as to which set of project stakeholders I wanted to gather requirements from, but I was going to ask for Dev-centric requirements next anyway.

No matter... Maybe I should have just asked for requirements for the Devs in the first place. Alls well that ends well...

Currently, I am researching software/API's similar to what I have in mind to take a survey of how they tackled various problems.
98
General Discussion / Re: Hypothetical : New gamebook platform requirements
« Last post by HarmlessTrouble on September 22, 2013, 08:14:48 PM »
Lightweight core.  But robust API for more specific requirements.

Requirement: Extensible through API.
Description:
API for both the authoring tools and story engine.
Want to make a dungeon crawler? grab the quest tools.
Find the verb?  grab the parser module.
Old media / CYOA?  Pick a format generator.
Feature doesn't exist? Write it!
Priority: High

Which language should the Api use? meh... What's trending right now?  Python?
99
General Discussion / Re: Hypothetical : New gamebook platform requirements
« Last post by Chris on September 20, 2013, 12:51:47 AM »
My instinctive response is 1) Choices, 2) Inventory, 3) Logic

We should pass this on to more people - perhaps I'll send out an email!
100
General Discussion / Adventures in the Game Industry
« Last post by Villain Mastermind on September 19, 2013, 07:19:24 PM »
I was wondering how many of you out there have worked for a big gaming company (or even a small one) and what your experiences were...

The company I worked for was, and still is, one of the largest in the world... Among other things, they are well known for their ridiculously popular sport games, particularly a game named after a certain coach and color-commentator. I was a QA tester and had only been there for a few weeks, and since I wasn't a part of any cliques and/or suck up to any Team-leads or managers, no one could remember my name... but that wasn't uncommon in the case of new QA testers because we were hired in large batches and considered disposable.

I was going to tell the entirety of my story, which was woefully short, but I'm kinda tired of retelling it in full. So I'll just skip to the almost comical way it ended.

1) Manager whom I have never met or seen before calls me into a meeting: "Hey, you... We need to have a talk."

2) I am lectured on how my attendance and performance are not up to par, which I found odd considering that I was always on time and hard at work when everyone else was talking about sports.

3) Then I am addressed by a name that is not even remotely mine and handed a non-disclosure agreement (company secrets and such) to sign that had that same erroneous name on it.

4) After informing the manager and team leads present that the name is not mine and belongs to the gentleman that sits beside me, I am left alone for at least a half-hour to wait. Seeing as this all appears to be a bureaucratic mistake, I feel secure in the knowledge that I have dodged a bullet meant for someone else.

5) Eventually, a single team-lead wordlessly comes in with a non-disclosure agreement with my correct name on it... I am forced to sign it by security before I am escorted out of the building. In the parking lot, I see my former neighbor with a box containing his things.

6) On the drive home, my state of shock and confusion fades and I piece together what had just transpired. They had fired me just so they wouldn't have to admit they'd made a mistake. I then pull over and proceed to scream obscenities and the most vile of curses into my closed-face motorcycle helmet.

Does anyone else have any stories, good or bad?
Pages: 1 ... 8 9 [10]