Revision history for FBWikiFaq


Revision [22128]

Last edited on 2018-02-03 09:01:54 by JeffMarshall [Fix page link]
Additions:
The overall style for your tutorial is up to you. There are no specific rules for how you //must// format it, but you may want to look at other tutorials of pages in the FreeBASIC manual for some ideas. The [[FBWikiFormatting|formatting codes]] used are the same as any other page in the wiki. We only ask that all sample code be enclosed between tags where ##**""%""""%""( freebasic )**## is the starting tag and ##**""%""""%""**## is the ending tag so it is recognized by our document converters.
Deletions:
The overall style for your tutorial is up to you. There are no specific rules for how you //must// format it, but you may want to look at other tutorials of pages in the FreeBASIC manual for some ideas. The [[FBWikiFormattingRules|formatting codes]] used are the same as any other page in the wiki. We only ask that all sample code be enclosed between tags where ##**""%""""%""( freebasic )**## is the starting tag and ##**""%""""%""**## is the ending tag so it is recognized by our document converters.


Revision [22127]

Edited on 2018-02-03 08:30:31 by JeffMarshall [wiki registration is disable - add link to "Wiki signups" in forum]
Additions:
- Login into your Wiki account. ++Use same name and password as in the forum++. **Note: currently, Login/Register form is disabled** due to spam attacks in the past. To create an account for this wiki, visit [[https://www.freebasic.net/forum/viewtopic.php?f=9&t=25849|Wiki signups]] in the forum.
The overall style for your tutorial is up to you. There are no specific rules for how you //must// format it, but you may want to look at other tutorials of pages in the FreeBASIC manual for some ideas. The [[FBWikiFormattingRules|formatting codes]] used are the same as any other page in the wiki. We only ask that all sample code be enclosed between tags where ##**""%""""%""( freebasic )**## is the starting tag and ##**""%""""%""**## is the ending tag so it is recognized by our document converters.
Deletions:
- Login into your Wiki account. Note: use same name and password as in the forum, you can't register into the Wiki, the Login/Register form is disabled for registering.
The overall style for your tutorial is up to you. There are no specific rules for how you //must// format it, but you may want to look at other tutorials of pages in the FreeBASIC manual for some ideas. The [[FormattingRules|formatting codes]] used are the same as any other page in the wiki. We only ask that all sample code be enclosed between tags where ##**""%""""%""( freebasic )**## is the starting tag and ##**""%""""%""**## is the ending tag so it is recognized by our document converters.


Revision [20809]

Edited on 2016-03-12 14:18:39 by fxm [Formatting]
Additions:


Revision [20017]

Edited on 2016-02-10 15:52:47 by DkLwikki [Update link format]
Additions:
- [[DocToc|FreeBASIC Manual - Table of Contents]] - All of the content here is used to make downloadable versions of the FreeBASIC manual.
- [[CommunityTutorials|Community Tutorials]] - Programming tips, information, and tutorials provided by the community.
- [[FBWikiHelp|FB Wiki - Help]] - Help about the wiki itself, styles, formatting, and this FAQ.
We would prefer that if an error or omission is found in the wiki that you either leave a comment on the page where it was found, or help improve the wiki by updating the page yourself. The FreeBASIC documentation is a community effort and is only improved by its members. If it is something you think should be discussed first, you can make a post about it on the [[http://www.freebasic.net|FreeBASIC forums]], or as a last resort, contact one of the [[http://sourceforge.net/project/memberlist.php?group_id=122342|FreeBASIC developers]].
- Go to the [[CommunityTutorials|Community Tutorials]] page
The overall style for your tutorial is up to you. There are no specific rules for how you //must// format it, but you may want to look at other tutorials of pages in the FreeBASIC manual for some ideas. The [[FormattingRules|formatting codes]] used are the same as any other page in the wiki. We only ask that all sample code be enclosed between tags where ##**""%""""%""( freebasic )**## is the starting tag and ##**""%""""%""**## is the ending tag so it is recognized by our document converters.
Recognition for the community tutorials is on the [[CommunityTutorials|Community Tutorials]] page. Please remember to credit yourself by putting your name or handle next to your link on the community tutorials page.
If you know that you have contributed significantly to the overall improvement of the wiki and wish to be recognized, please add yourself to the [[ContributorList|Major Contributors List]].
The keyword reference pages which should begin with ""KeyPg"", are for compiler keywords and runtime library functions. Anything and everything about how the keyword or function is used should be documented. The only thing that shouldn't go in here is any personal comment on if the keyword is "good" or "bad". It's OK to describe the alternatives, but not OK to pass any judgment on the choices. If it's a valid keyword or construct in the language, it should be up to the programmer to choose to use it or not. For example, [[KeyPgEnum|Enum]], [[KeyPgConst|Const]], [[KeyPgPpdefine|#define]]. are all valid ways for introducing constants in to a source program, and each have their strengths and weaknesses.
The programmer's guide pages which should begin with ""ProPg"", are for concepts, ideas, and general information on how to use different aspects of the language. For example, a single page could describe how to use [[KeyPgEnum|Enum]], [[KeyPgConst|Const]], [[KeyPgPpdefine|#define]]. This would be the perfect place to describe the pros and cons, tips and traps, for using one over the other with links to each of the keyword pages for more information. The programmer's guide should not only provide information on how to make use of the language to write programs but also offer advice on best practices.
Deletions:
- [[DocToc FreeBASIC Manual - Table of Contents]] - All of the content here is used to make downloadable versions of the FreeBASIC manual.
- [[CommunityTutorials Community Tutorials]] - Programming tips, information, and tutorials provided by the community.
- [[FBWikiHelp FB Wiki - Help]] - Help about the wiki itself, styles, formatting, and this FAQ.
We would prefer that if an error or omission is found in the wiki that you either leave a comment on the page where it was found, or help improve the wiki by updating the page yourself. The FreeBASIC documentation is a community effort and is only improved by its members. If it is something you think should be discussed first, you can make a post about it on the [[http://www.freebasic.net FreeBASIC forums]], or as a last resort, contact one of the [[http://sourceforge.net/project/memberlist.php?group_id=122342 FreeBASIC developers]].
- Go to the [[CommunityTutorials Community Tutorials]] page
The overall style for your tutorial is up to you. There are no specific rules for how you //must// format it, but you may want to look at other tutorials of pages in the FreeBASIC manual for some ideas. The [[FormattingRules formatting codes]] used are the same as any other page in the wiki. We only ask that all sample code be enclosed between tags where ##**""%""""%""( freebasic )**## is the starting tag and ##**""%""""%""**## is the ending tag so it is recognized by our document converters.
Recognition for the community tutorials is on the [[CommunityTutorials Community Tutorials]] page. Please remember to credit yourself by putting your name or handle next to your link on the community tutorials page.
If you know that you have contributed significantly to the overall improvement of the wiki and wish to be recognized, please add yourself to the [[ContributorList Major Contributors List]].
The keyword reference pages which should begin with ""KeyPg"", are for compiler keywords and runtime library functions. Anything and everything about how the keyword or function is used should be documented. The only thing that shouldn't go in here is any personal comment on if the keyword is "good" or "bad". It's OK to describe the alternatives, but not OK to pass any judgment on the choices. If it's a valid keyword or construct in the language, it should be up to the programmer to choose to use it or not. For example, [[KeyPgEnum Enum]], [[KeyPgConst Const]], [[KeyPgPpdefine #define]]. are all valid ways for introducing constants in to a source program, and each have their strengths and weaknesses.
The programmer's guide pages which should begin with ""ProPg"", are for concepts, ideas, and general information on how to use different aspects of the language. For example, a single page could describe how to use [[KeyPgEnum Enum]], [[KeyPgConst Const]], [[KeyPgPpdefine #define]]. This would be the perfect place to describe the pros and cons, tips and traps, for using one over the other with links to each of the keyword pages for more information. The programmer's guide should not only provide information on how to make use of the language to write programs but also offer advice on best practices.


Revision [14798]

Edited on 2010-08-21 04:44:14 by GaLeon [Changed run-time to runtime]
Additions:
The keyword reference pages which should begin with ""KeyPg"", are for compiler keywords and runtime library functions. Anything and everything about how the keyword or function is used should be documented. The only thing that shouldn't go in here is any personal comment on if the keyword is "good" or "bad". It's OK to describe the alternatives, but not OK to pass any judgment on the choices. If it's a valid keyword or construct in the language, it should be up to the programmer to choose to use it or not. For example, [[KeyPgEnum Enum]], [[KeyPgConst Const]], [[KeyPgPpdefine #define]]. are all valid ways for introducing constants in to a source program, and each have their strengths and weaknesses.
Deletions:
The keyword reference pages which should begin with ""KeyPg"", are for compiler keywords and run-time library functions. Anything and everything about how the keyword or function is used should be documented. The only thing that shouldn't go in here is any personal comment on if the keyword is "good" or "bad". It's OK to describe the alternatives, but not OK to pass any judgment on the choices. If it's a valid keyword or construct in the language, it should be up to the programmer to choose to use it or not. For example, [[KeyPgEnum Enum]], [[KeyPgConst Const]], [[KeyPgPpdefine #define]]. are all valid ways for introducing constants in to a source program, and each have their strengths and weaknesses.


Revision [12698]

The oldest known version of this page was created on 2008-03-08 21:35:14 by DoS386 [Changed run-time to runtime]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki



sf.net phatcode