05-19-2005, 09:21 PM
Yeah, that wiki script while easily extendable is pretty restrict with names, you must registry following its CapitalCapital convention, so your nick can become a reference and a page too.
The {{fbdoc}} is just to make parsing easier later to convert to other formats (wiki->xml->anything else), they will mark whem one section starts and they don't have to come in some predefined order (but we must follow one, course), and are optional.
All page names must follow the CapCap style, so the keywords tag is a bit more complex, the value field must contain the real page (KwDefine for example) and the keyword name (#DEFINE), separated by a | (yeah, too much PHP :P).
Access to pages can be controlled with that wiki script, so i could add only who is part of the doc team to have write access to them if people start to vandalize pages. They could only post comments then.
FB functions can be used as statements (if you were talking about say SCREEN as statement, not about the compound ones, for example) and some statements like OPEN/GET can be uses as functions, i don't know if putting them in different sections would be better.. or if we should do like the QB quick help, listing everything on a single section, but separated by category.
No, i didn't write anything in any language, translating would be even more difficult and i hate to write comments in portuguese, they are always too long ;).
If the format is okay, i will write the script to load that wiki with Nex's docs - that's what i've atm. You can then transfer what was done in XML or CHM, and updating what is missing.
New sections can be created then, sorted alphabetically, and so on, KeywordsList will be pretty much the gfxlib/Nex format, everything else can follow their own formatting.
The {{fbdoc}} is just to make parsing easier later to convert to other formats (wiki->xml->anything else), they will mark whem one section starts and they don't have to come in some predefined order (but we must follow one, course), and are optional.
All page names must follow the CapCap style, so the keywords tag is a bit more complex, the value field must contain the real page (KwDefine for example) and the keyword name (#DEFINE), separated by a | (yeah, too much PHP :P).
Access to pages can be controlled with that wiki script, so i could add only who is part of the doc team to have write access to them if people start to vandalize pages. They could only post comments then.
FB functions can be used as statements (if you were talking about say SCREEN as statement, not about the compound ones, for example) and some statements like OPEN/GET can be uses as functions, i don't know if putting them in different sections would be better.. or if we should do like the QB quick help, listing everything on a single section, but separated by category.
No, i didn't write anything in any language, translating would be even more difficult and i hate to write comments in portuguese, they are always too long ;).
If the format is okay, i will write the script to load that wiki with Nex's docs - that's what i've atm. You can then transfer what was done in XML or CHM, and updating what is missing.
New sections can be created then, sorted alphabetically, and so on, KeywordsList will be pretty much the gfxlib/Nex format, everything else can follow their own formatting.
ew FreeBASIC forums: http://www.freebasic.net/forum/index.php