Changes between Version 18 and Version 19 of WikiTodo


Ignore:
Timestamp:
Aug 4, 2007, 1:12:22 PM (17 years ago)
Author:
Nicolas
Comment:

Major organization and many added things.

Legend:

Unmodified
Added
Removed
Modified

  • WikiTodo

    v18 v19  
    55{{{
    66#!comment
    7 Add new items at the end of this page. Please keep the bulleted list format. Note that you must have a space before the asterisk!
     7Add new items at the end of the appropriate section. If you don't know what section is best, just add it at the end of the page. Please keep the bulleted list format. Note that you must have a space before the asterisk!
     8
     9To add a comment to an existing item, add it below, using two spaces before the asterisk instead of one.
    810}}}
    911
    10  * PythonMysql had been converted from [/install_python_mysqldb.txt the original .txt]. I recently "wikified" the page, since it was just plaintext copied verbatim. It probably needs some cleanup, and checking if the information on it is still correct. ''Answer: With recent distributions you won't need this page anymore. I always used the stable packages (usually: python-mysqldb) provided by each distro and got no problems. ChristianB''
    11  * UpdateVersions mentions adding an <app_dir> tag to config.xml, but it's not listed in [ProjectOptions#HostsdirectoriesandURLs ProjectOptions] (does the tag still exist?).
     12== Missing information (or requests for documentation) == #missing
     13 * UpdateVersions mentions adding an <app_dir> tag to config.xml, but it's not listed in [ProjectOptions#HostsdirectoriesandURLs ProjectOptions] '''(does the tag still exist?)'''.
    1214 * Where is the format of `global_prefs.xml`? I want to link it from ClientSim#input_sim_prefs. I see many pages with related info, I don't know which one is right or correct: PrefsImpl, GlobalPrefs (doesn't show XML format), PrefsOverride, and bottom of ClientFiles.
    13  * PrefsOverride is out of date.
     15 * It may be useful to have a new page (MigratingServers) explaining how to migrate a BOINC project to a new server.
     16
     17== Out of date information == #out-of-date
     18 * PrefsOverride is out of date, as it says on the page itself. Somebody should go check the code for what the current prefs format is...
     19 * Implementation notes are most '''very''' outdated.
     20  * An updated ClientApp may help create a library to allow [JavaApps Java applications] on BOINC; basically porting the BOINC API to Java.
     21
     22== Minor corrections == #minor
    1423 * ManagerAdvanced could have some new screenshots. Current ones show glitches on the rendering of menus. Also it's probably better to keep the screenshots as attachments to that page, instead of stored somewhere else on BOINC server, that way contributors can change them.
     24 * AlphaInstructions has missing links at the very bottom. It says "see here and here" but words aren't linked.
    1525 * ~~JobIn needs similar work to BackendState: reformatting using headings instead of that table mess~~. I reformatted JobIn using [WikiFormatting#DefinitionLists definition lists]. I think it looks better than with [WikiFormatting#Headings headings], but we can't link to individual attributes...
    16  * AlphaInstructions has missing links at the very bottom. It says "see here and here" but words aren't linked.
    17  * minor correction on page: http://boinc.berkeley.edu/projects.php about date of LHC first turn-up - according to: http://press.web.cern.ch/press/PressReleases/Releases2007/PR06.07E.html the machine will not "see" first-light (see where i'm coming from;) until May of next year.
     26 * minor correction [http://boinc.berkeley.edu/projects.php project list] about date of LHC first turn-up - according to [http://press.web.cern.ch/press/PressReleases/Releases2007/PR06.07E.html this press release] the machine will not "see" first-light until May of next year.
     27  * This isn't part of the Wiki.
     28
     29== Misc == #misc
     30
     31 * PythonMysql had been converted from [/install_python_mysqldb.txt the original .txt]. I recently "wikified" the page, since it was just plaintext copied verbatim. It probably needs some cleanup, and checking if the information on it is still correct.
     32  * ''Answer: With recent distributions you won't need this page anymore. I always used the stable packages (usually: python-mysqldb) provided by each distro and got no problems. ChristianB''
     33  * Other pages need to be updated to say Python DB can just be installed that way.
     34 * Would it make sense to move DevProjects stuff into Trac tickets marked as 'Task'?