TrustedUser
2,147
edits
Difference between revisions of "TODO"
Jump to navigation
Jump to search
m
Text replacement - "</source>" to "</syntaxhighlight>"
(Remove iterator handling from the todo list. It is too much of a pitfall for GSoC students.) |
m (Text replacement - "</source>" to "</syntaxhighlight>") |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 38: | Line 38: | ||
== Web sites == | == Web sites == | ||
=== General === | |||
* Move all sites to the new host | |||
* Update outdated software | |||
* Use HTTPS everywhere | |||
* Make a consistent and reusable visual look across all sub-sites | |||
=== Primary website === | === Primary website === | ||
| Line 43: | Line 49: | ||
* Show "Release Date" on download page | * Show "Release Date" on download page | ||
* Change all screenshot filenames to match our rules as described [[Screenshots|here]]. E.g. rename <code>data/screenshots/agos/simon/scummvm_2_4_0.jpg</code> to <code>data/screenshots/agos/simon/simon-0.jpg</code> etc.; also some stuff should maybe be moved to other directories. | * Change all screenshot filenames to match our rules as described [[Screenshots|here]]. E.g. rename <code>data/screenshots/agos/simon/scummvm_2_4_0.jpg</code> to <code>data/screenshots/agos/simon/simon-0.jpg</code> etc.; also some stuff should maybe be moved to other directories. | ||
* Introduce build tools to handle website updates | |||
* Update the template engine | |||
=== [[Buildbot]] === | === [[Buildbot]] === | ||
| Line 52: | Line 60: | ||
* Install the new required dependencies (libpng and libtheora for [[Sword25]]) into the cross compiler environments of all ports that have a chance of supporting [[Sword25]]. | * Install the new required dependencies (libpng and libtheora for [[Sword25]]) into the cross compiler environments of all ports that have a chance of supporting [[Sword25]]. | ||
* Install the new required dependencies (libpng, libfreetype, boost and wx-widgets) into the cross compiler environments of all desktop ports to support building of tools. | * Install the new required dependencies (libpng, libfreetype, boost and wx-widgets) into the cross compiler environments of all desktop ports to support building of tools. | ||
* Fix the console page | |||
=== [[Doxygen]] === | === [[Doxygen]] === | ||
* | * Update the visual theme to better match the site | ||
=== [[Forums]] === | === [[Forums]] === | ||
* Upgrade to phpBB 3 | * Upgrade to phpBB 3 | ||
* Update the theme to phpBB3 | |||
=== [[Planet]] === | === [[Planet]] === | ||
| Line 63: | Line 73: | ||
=== [[Wiki]] === | === [[Wiki]] === | ||
* | * Update the theme to match the updated website | ||
* Update to the latest Wiki version | |||
* Add a ScummVM style guide | |||
* Add content to [[Special:Wantedpages|Wanted Pages]] | * Add content to [[Special:Wantedpages|Wanted Pages]] | ||
* Add some content to [[Help:Editing]], which is shown when editing a page | * Add some content to [[Help:Editing]], which is shown when editing a page | ||
| Line 88: | Line 100: | ||
is valid for which event type. Implementation wise, we might want to use | is valid for which event type. Implementation wise, we might want to use | ||
the classic union-of-structs trick. It goes roughly like this: | the classic union-of-structs trick. It goes roughly like this: | ||
< | <syntaxhighlight lang="cpp"> | ||
struct BasicEvent { | struct BasicEvent { | ||
EventType type; | EventType type; | ||
| Line 109: | Line 121: | ||
... | ... | ||
}; | }; | ||
</ | </syntaxhighlight> | ||
However, this approach is contrary to classic OO paradigms. Indeed, its | However, this approach is contrary to classic OO paradigms. Indeed, its | ||
| Line 120: | Line 132: | ||
casting in code using events. The passing around of pointers could be | casting in code using events. The passing around of pointers could be | ||
mitigated by using | mitigated by using | ||
< | <syntaxhighlight lang="cpp"> | ||
typedef Common::SharedPtr<BasicEvent> Event | typedef Common::SharedPtr<BasicEvent> Event | ||
</ | </syntaxhighlight> | ||
or something like that. Yet this would mean increased overhead in all | or something like that. Yet this would mean increased overhead in all | ||
our code, yet the gain is unclear. In conclusion, we probably are best | our code, yet the gain is unclear. In conclusion, we probably are best | ||