Utility: Official release of the unofficial Dominions 3 Wiki

[momfreeek]

Originally Posted by Soyweiser

Without scripts it would not be able to edit them.

Oops, this does not make sense.

Originally Posted by Soyweiser

http://www.unnecessaryquotes.com And http://owl.english.purdue.edu/owl/resource/577/01/

Oh dear, why the unnecessary capitalization?

Perhaps this will help:
http://www.wikihow.com/Be-a-Grammar-Nazi


ok, I'm just being an *******, sry

[brxbrx]

Originally Posted by momfreeek

Oops, this does not make sense.

What he means is that the way a wiki works is that anyone can edit it, and if it were just text, this would not be possible.

On a wiki, you can edit an article and add your own information. You can create internal links to other articles and transclude certain pages onto others.

Take a look at how Wikipedia works, and please leave the 90's for the 21st century.

[lch]

Originally Posted by JonBrave

Here's what I don't get/is sad. Your Wiki is, or should be, 99.9% static text. No offence intended, but as I recall it's just clicking on links to other pages (little if any interaction)

Like others already wrote, far from it. It's probably pretty close to the other way around. Almost everything, including in most parts the graphics, is dynamically generated. There are caching mechanism in place, especially for the graphics, so that it doesn't have to be generated completely if there is a hit, of course. But what is stored in the MySQL database is something called Wikitext, which is being rendered into what you see on your screen. The Wikitext is just some very sleek text with Wiki-specific markup which aims to be very readable even when you edit the source code in the editor, instead of HTML for example, where your actual text can get lost in all the tags and markup it carries. And unlike HTML, that Wikitext has to be parsed by the server, not only on your side by your browser. That whole Wikitext runs through the MediaWiki parser before you see it, and MediaWiki, the Wiki software, has some very wicked Templating mechanism built-in, too. It's a very complex Turing-complete language, if you want, which differentiates it from a WYSIWYG Content Management System where you use a finite set of tools. Oh, and the MediaWiki software itself with the included parser is programmed in PHP, which is an interpreted language that has to run through a PHP parser at runtime before it is being executed, too. So there are a couple of parsers simultaneously at work at the server on different levels whenever the Wiki has to spit something out on your screen.

Of course, the aim is to keep the actual rendering low as much as possible. Which is why I am using something called APC, Advanced Parser Cache, to always keep the things which are used the most in memory. And theoretically, all the rendering should only be necessary if somebody makes a change to one of the pages. But there's just not enough memory to keep all the thousands of pages in memory at once, which is why you do have those load times (and sometimes it seems to get stuck at some point, I don't know why). When I wrote that the Wiki is probably slow either because of my net connection (I doubt it) or the server hardware (quite possible), I forgot one other thing: It might very much be slowed down by the design, too. I am using extensions, like SMW, Semantic MediaWiki, which could probably be used better. I'm using Templates that could probably be optimized. A couple of pages could probably be formatted in a better way, and most of all: The unit pages, which I'm guessing are being accessed the most, are using a design which is maybe not very cache-friendly. It accesses an internal MySQL database of stats and values quite similar to Edi's Dom3DB which I separated from the MediaWiki articles so that I'd have it easy to update those stats and values when a new update to Dom3 changes them. Back when the Wiki was developed, there were more or less regular updates every half year, and quite a lot of little data changes could happen in a patch. Populating that data into the Wikitext from the unit articles would be painful manual labor, or I'd have to write my own parser/robot to find and change that information, so I wrote a MediaWiki extension which grabs that data from another internal database instead. Nowadays Dom3 is pretty much final and there haven't been any major patches to the content lately, so such a setup is not as necessary as it seemed to be at first, and I could probably lose that design. I didn't knew about the power of Semantic MediaWiki when I started this design, too, and I probably could have dismissed this strange design from the start. Like I wrote in my opening post, I think there's probably a lot more powerful stuff to be harnessed from SMW, but I lack the knowledge and the time to learn it outside of a paid work experience myself now.

I'm still hoping that a SMW wizard might come by at some point, weave his magic wand and suddenly everything will just be beautiful and lightning fast... In the meantime, you'll have to live with things the way they are now. Not ideal, but you'll have to cope.

[momfreeek]

Originally Posted by brxbrx

What he means is that the way a wiki works is that anyone can edit it, and if it were just text, this would not be possible.

yeah, I knew what he meant, I was just being a counter-grammar-nazi.

[Soyweiser]

Originally Posted by momfreeek

Oops, this does not make sense.

Oh dear, why the unnecessary capitalization?

Perhaps this will help:
http://www.wikihow.com/Be-a-Grammar-Nazi


ok, I'm just being an *******, sry

Thank you for pointing out the mistakes. I would edit them, but sadly the forum doesn't allow me to edit posts past a certain time frame.

[Soyweiser]

Originally Posted by momfreeek

yeah, I knew what he meant, I was just being a counter-grammar-nazi.

Brxbrx has correctly inferred the meaning of my badly written text.

Momfreeek, would you say you are just trolling here now?

[momfreeek]

no, there was a point. Not on topic but thats in keeping with your own "advice".

Perhaps this will help:
http://www.wikihow.com/Be-a-Grammar-Nazi

I thought steps 2, 5 and 7 seemed relevant.

Just a little forum riposte, I don't mean to be belligerant.

[JonBrave]

Originally Posted by Soyweiser

"stop" "misusing" "quotation" "marks"

And you are wrong. 99% of the good sites out there are not just static pages. Without scripts it would not be able to edit them.

@Soy
I use quotes (among other things) if the word I'm using is not exactly right. When I say "scripts", I know it might be scripts, or programs, or transformers, or whatever. I don't know if his site is really "down", maybe it's running fine but not available. Seems like standard English usage to me as long as I can remember. You're probably pleased that "Waterstone's" got renamed (or perhaps you'd prefer Waterstone's).

@Elsewhere
As for the points about the (Dom3) Wiki content. Yes, I do realise (especially e.g. with Wordpress) that most stuff is delivered dynamically --- and so much the worse for delivery speed and processing usage. My point was that, as an information source with loads of text and little if any interaction, the content is static in nature. When I read the pages that's what I'm accessing.

At times you ask questions here with no intention other than an innocent & polite query for information and you get shouted at.

[Admiral_Aorta]

little if any interaction

except for that whole users can edit pages thing

[brxbrx]

Originally Posted by Admiral_Aorta

except for that whole users can edit pages thing

He doesn't seem to understand what a wiki is.

"A wiki is a website which allows its users to add, modify, or delete its content via a web browser using a simplified markup language or a rich-text editor. Wikis are powered by wiki software. Most are created collaboratively."