3DGC:Design

3D Game Comparison - Game vs. game. No hype; just facts.™

Revision as of 20:52, 4 August 2007 by Eep² (t|c)
Jump to: navigation, search

Originally designed for a database, conversion to MediaWiki presents some problems:

This page is MediaWiki-specific but see http://tnlc.com/eep/compare/database.html for general design ideas.

Contents

Classification

There are different ways of designing this "database"'s classification system using MediaWiki.

Categories

The most obvious is with categories. Unfortunately, these can quickly clutter up the bottom of pages if there are too many. Categories could be named like namespaces (i.e. Game:Tomb Raider) but why not just use namespaces then to reduce having to type the link (:Category:Game:Tomb Raider vs. Game:Tomb Raider)?

Namespaces

Perhaps the next most obvious is with namespaces for games (game:), companies (company:), engines (engine:), characters (character:), effects (effect:), etc.

Subpages

Less obvious is using subpages (games/Tomb Raider) but they may be easier to manage than namespaces, although I'm not sure how DPL (see next section) can handle them. Additionally, subpages are automatically transcludable via template calls ({{/Tomb Raider}}).

Wiki markup comparison

System Markup Adavantages Disadavantages
Category Default classification system with auto-generated lists
  • Mixing same-named articles and categories causes redundancy (redirect to categories only?)
  • Games with simple names (like Rune, Dirt, etc) can conflict with object names (like a "rune") or surface types (like "dirt"); engine names like Steam and Source can conflict with the "steam" effect and "source" of something (though rare; or short for "source code"). Lowercase names can help alleviate most of these conflicts but not these:
  • bow action -> bow weapon
  • Camera pan (view pan, camera pan?) -> object pan (pans?)
  • sprite (computer graphics) -> sprite (fantasy creature)
Namespace

Game:Games

Effect:Effects

Name conflicts less likely Must use extension to generate lists
Subpage

game

effect

Name conflicts less likely Must use extension to generate lists

Extensions

Note: DPL and SMW appear to cause pages to load slower (lots of server calls, flashing the web browser statusbar like mad most of the time).

Dynamic Page List (DPL)

Using DPL, lists of pages linking to other pages (as well as pages in categories and namespaces) are possible. This may be the best option that will allow all classification schemes to be included/used.

Semantic MediaWiki (SMW)

This extension is similar to DPL in outputting lists of pages in categories and namespaces, but also allows more complex relationships between things. Unfortunately, it's a lot more complicated to use (even moreso than DPL), which makes it a last resort. Programmers still code for programmers, apparently...even if they claim to be "semantic"--try being "intuitive" and "user-friendly" instead.

Comparison table

So far I've tried 2 extensions for the comparison table. One (TemplateTable) is easy-to-use but very limited and the other (DPL) is more difficult to use but more customizable (yet still not enough for my needs).

Personal tools