Previous Entry Share Next Entry
The Poker Rosetta Stone
jducoeur wrote in querki_project
Those of you who read my personal blog probably came across me burbling about the Poker DB last week. For those who didn't, the summary is that the first "normal" Querki Space -- my Poker Variants Encyclopedia -- is now up and running. It's pretty simplistic, but it's a fine example of the sort of problem Querki should excel at.

That previous post contains the high-concept burblage; here, I wanted to talk about details. And it's for that reason that I spent a day or so implementing the _code() method.

_code is a new method whose sole purpose is explaining Querki code. You can use it in a lot of different ways. You can pass some text into it:
[[""Hello there"" -> _code]]
You can put some text in a parameter:
[[_code(""Hello there"")]]
You can tell it to display the literal, unprocessed contents of a Property on the current Thing:
[[_code(My Property)]]
Or on some other Thing:
[[_code(Other Thing.My Property)]]
Or you can simply specify a block of code:
[[_code(My List -> _join("", ""))]]
It tries very hard to do the right thing with its parameters, displaying what it finds as an unprocessed, XML-neutered inset code block.

The *reason* I spent all that time on this was so that I could implement the first How It Works page. "How It Works" is a convention I'm planning to encourage: if a Space has a page with this name, then it should be a tutorial, not on how to *use* the Space, but on how it is *built*. I figure that, since Querki is very much designed for tinkerers, we want to encourage a Maker ethos, and we might as well start now.

Anyway, y'all are encouraged to take a read through that page. It isn't short, because it goes into *considerable* detail about how the Poker Space works. But it is, in a sense, the Rosetta Stone to Querki. While I'm going to be adding tons and tons of features, we've now got the most critical ones implemented, and they are front-and-center in the Poker Space. Once you understand how this one is put together, you pretty much have the tools you need to build lots of basic-but-functional systems in Querki. (I'll specifically note that we now have pretty much all the functionality I had in ProWiki, and I used that heavily for ten years, building a bunch of ferociously complex LARPs in it.)

Questions encouraged -- this is dense stuff, and I'm happy to talk about it. For the time being, ask here, since we don't have discussion capability natively in Querki yet. (But it's coming...)

  • 1
This is very exciting-looking. I'd like to try to translate our course descriptions into it. May I do some alpha-testing?

Sure, happy for you to do so. I don't have the invite system written yet, but hopefully that (and therefore, the ability for people other than me to log in) will get done in the next month or so. I'd be happy to put you on the initial invite list, and get your impression of what does and doesn't work for you.

(Indeed, this is a reminder that I should set up a tiny Space to start actually tracking who I mean to invite...)

  • 1

Log in

No account? Create an account