History: Immediate Wiki Tasklist

• «
• »

            See also the ((Public Tasks|Wiki Todo List))

{maketoc}
!!Fix anchor links
{MONO()}~np~((pagename##anchor|text))~/np~{MONO}
should be:
{MONO()}~np~((pagename|#anchor|text))~/np~{MONO}
I.e. the double '{MONO()}__~np~##~/np~__{MONO}' is replaced by '{MONO()}__~np~|#~/np~__{MONO}'

!!Port MediaWiki Section Links
MediaWiki:
{MONO()}~np~((#SdkTrayListener|SdkTrayListener))~/np~{MONO}
Tiki:
{MONO()}~np~{ALINK(aname="SdkTrayListener")}SdkTrayListener{ALINK}~/np~{MONO}

Needs to be done.
Low priority, though.

Just click the {IMG(src="pics/icons/world_link.png")}{IMG} icon on the edit toolbar to set an alink.

Alternatively, using the pagename, you can avoid the ALINK edit plugin:
{MONO()}~np~((pagename|#alink|click me))~/np~{MONO}

Actually, the latter is the easiest. :)
Just prepend __{MONO()}pagename|{MONO}__ and you've fixed it.
{MONO()}~np~((#SdkTrayListener|SdkTrayListener))~/np~{MONO} __~np~->~/np~__ {MONO()}~np~((OgreBites|#SdkTrayListener|SdkTrayListener))~/np~{MONO}

If you spot a link which doesn't work and look like the first one above, you know how to fix it.. (:wink:)

!!Port MediaWiki markup to Tiki markup

Ported: 1390 Remaining: 0 (Total: 1390).

Yes, we're done! :D

See ((Porting from MediaWiki))

!!Keep up with the Ogre Wiki
This wiki is based on a wiki dump from November 29th 2009.

This is the list of '''outstanding''' changes:
#30 December 2009 (3 pages with changes)
#29 December 2009 (2 pages with changes)
#28 December 2009 (1 page with changes)
#27 December 2009 (1 page with changes)
#26 December 2009 (1 page with changes)
#25 December 2009 (1 page with changes)
#24 December 2009 (2 pages with changes)
#23 December 2009 (1 page with changes)
#22 December 2009 (6 pages with changes)
#21 December 2009 (2 pages with changes)
#20 December 2009 (6 pages with changes)
#19 December 2009 (Lots and lots of changes!)
#18 December 2009 (3 pages with changes so far)
#16 December 2009 (6 pages with changes) %done%
#13 December 2009 (1 page with changes) %done%
#10 December 2009 (1 page with changes)
#9 December 2009 (4 pages with changes)
#8 December 2009 (3 pages with changes)
#7 December 2009 (6 pages with changes)
#4 December 2009 (2 pages with changes)
#3 December 2009 (7 pages with changes)
#1 December 2009 (5 pages with changes)
#30 November 2009 (2 pages with changes) %done%

Pages done (as of December 31st):
((Hardware))
((Glow))
((Minimal Ogre Collision))
((CodeSnippets))
((Projects using MOGRE))
[Building_From_Source_(for_iPhone)]
((CMake Quick Start Guide))
((CurrentOgreFeatures))


__Q:__ How to port the changes?
__A:__ Pick a day, then take each page with changes and do diff between November 29th and the latest version.
Yes, this means that you will port changes over for the whole period, but then it becomes easier down the list. Not a bad thing. (:wink:)

!!Add Addons to the Addons Tracker
Take for instance an addon like ((Octopus)) - it does not show up on the list on the ((Addons)) page, and it does not have a pretty info header/box like ((Ogitor)) and ((ETM)).
What we need to do is enter it into the Addons Tracker and put this tag at the ((Octopus)) page:
{CODE(wrap="1")}{TRACKERLIST(trackerId=1, view=page, max=-1, wiki="addons tpl") /}{CODE}
This is not done overnight, but it wouldn't hurt to do one by one - eventually we'll have them all in the tracker.
The template can be changed.
Current template: ((addons tpl))
Possible template: ((ogregallery tpl))
It's also possible to use both, just swap '''addons tpl''' with '''ogregallery tpl''' in the tag.

Using the tracker and the templates ensures a consistent look, and it's easier to update the information.
Besides, they show up in the list at the ((Addons)) page, making it easy to find them.

!!Give each page a description
Fairly important, but can't be done 'overnight'.
Descriptions are used for link descriptions and shown on the page itself.
Saves typing and manual labour later.

To track progress, use the TOC pages of the structures:
((TOC Tutorials))
((TOC Community))
((TOC Addons))
((TOC Pipelines))
((TOC Development))
((TOC Community))

There are two Tables of Contents on those pages:
One '''normal''', without descriptions, and one using descriptions.
Both are numbered.
Should be obvious if a page has a description or not.
The goal is to '''fill out''' the second TOC. :)

'''How do I find the description?'''
Take a look at the page, or maybe some '''overview''' page, like this one: ((Snippets))
The names given to the links (using a different name than the article actually linked to) would be good candidates for a description field.
Just make it short, and - well - descriptive. :)

See ((Ogre Wiki Help|#give a page a description?|How do I give a page a description?))

!!New Ogre Wiki theme
Betajaen is working on it. :)
See [http://www.ogre3d.org/forums/viewtopic.php?f=1&t=54256&start=0|Proposal: New Ogre Wiki] in the Ogre Forums.

!!Tag pages
This is a minor thing, but let's start tagging pages.

Tags are basically a much better way of categorising pages than using categories.
Besides it being easier to throw some tags on a page than having to create a new category and then assign that category to a page, it's also much easier to use tags for finding stuff.
Categories are used mainly for administrative purposes due to the fact that permissions can be assigned to categories.

!!Simple tasks right now
none yet! :)