History: Immediate Wiki Tasklist

• «
• »

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

{maketoc}
!!Simple tasks right now
Snippets are slowly being added to the ((Cookbook)) structure.
The overall structure of the ((Snippets)) '''area''' has been created, and the sections up to and including Geometry has been '''filled up''' with articles.
''Rendering'' is next.
Simply add pages to the structure according to the ((Snippets)) page.
Like:
{CODE(wrap="1")}
Rendering
    * 2D Sprite Manager: A class for rendering 2D sprites, ie: the DirectDraw? way. 
    * Drawing Lines in 3D
    * Drawing lines in 3D revisited: Example of dynamic buffers code.
    * Drawing Circles in 3D
    * Displaying 2D Backgrounds
    * Displaying a Lens Flare Effect
    * HDR Effects Without Using Full Floating Point Textures
    * Billboard-style Text in 3D: MovableText 
    * A More In-Depth Version of the 2D Sprite Manager
    * Oriented Bounding Box 
{CODE}
A good idea to work with two browser windows visible, the Snippets page and the structure layout page. (:wink:)
!!Keep up with the Ogre Wiki
Right now there is 10 days of changes to port over.
Not a lot of work, but needs to be done.
See {ALINK(aname="Keep up with the Ogre Wiki status")}Keep up with the Ogre Wiki status{ALINK}

!!Put pages into structures
((Development|Development)) and ((Tutorials|Tutorials)) are underway.

((Addons|Addons)) and ((Cookbook|Cookbook)) are not even started.

See {ALINK(aname="Addons Sketch")}Addons Sketch{ALINK} and {ALINK(aname="Cookbook Sketch")}Cookbook Sketch{ALINK}

!!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.
!!Port MediaWiki markup to Tiki markup

Ported: 464 Remaining: 908 (Total: 1372).

{CHART(id=>1, type=>PieChartGraphic, format=>, orientation=>, label=>B1:A1, value=>B2:A2, color=>"green,red", style=>, width=>240, height=>200)}Ported Pages{CHART}

{ATTACH(id=>10, image=>1)} {ATTACH}

See ((Porting from MediaWiki))
!!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.

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.

---

!!Work Area

!!!Keep up with the Ogre Wiki status

This wiki is based on a wiki dump from November 29th 2009.

Currently we have about 14 days worth of 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)
#13 December 2009 (1 page with changes)
#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%

__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:)


!!!Addons Sketch

Just a suggestion:
{CODE(wrap="1")}Addons
    Libraries
    Ports
        Mogre
        Ogre4J
        PythonOgre
    Rest of the addons - the tags will make it easy to find an addon, and the addons tracker as well.
    Assembling a toolset, and related articles.
{CODE}
!!!Cookbook Sketch

This one is difficult.

There's over 300 pages in this category..
So we need a good way to organise those.

{CODE(wrap="1")}Cookbook
    Snippets
    Codebank
    Experiences{CODE}

Tried to replicate the structure of the 'old' snippets overview page, but I think that maybe we'll get too many levels of pages.
Probably a good idea to refactor.
See ((Cookbook|The Toc for Cookbook))