Template Layouts
From Wine-Wiki
Contents |
Information
<center><pre> <Your Wine Verison> 111111111</pre></center>
Wine 20041201
Used the above when posting what wine verison and linux you used to create the guide.
Game Posting Information
The box to the right with the information will be used when posting about games. I will make the "Buy It Now" links to support Wine-Wiki.org
| Guild Wars | |
| Full Title: | Guild Wars |
| Developer: | NC Interactive |
| Publisher: | Interplay |
| Released: | 2005 |
| Operating System: | Windows NT / XP / 2000 |
| Genre(s): | Role-Playing |
| Multiplayer: | MMORPG |
| System Requirements: | N/A |
| Recommended System Spec: | N/A |
| Buy It Now: | From Amazon |
Box Code
<strong>Title or preview</strong>
<pre> $ sudo emerge moo </pre>
Emerging Moo
# sudo emerge moo
Use this when posting code or console information.
Wikify
{{wikify}}
and Posting Guidelines
Use this on a poorly wikied page.
HOWTOs
{{Wine HOWTO Index}}
| Installing Wine • Business • Games • Internet • Multimedia • System and Utilities |
| • Education • Other |
Use these at the top of any HOWTOs.
Categorys
[[Category:Wine]]
[[Category:Cedega]]
[[Category:CodeWeavers]]
Use this in any HOWTO, TIP, or others.
Configuration Postings
{{config|<Your Wine Type> Configuration|
<pre>Your Config Here</pre>}}
| Configuration: Wine Configuration |
[wine] "GraphicsDriver" = "x11drv"; (x11drv, ttydrv) ;"ShowDotFiles" = "1" # [wineconf] [Version] ; Windows version to imitate (win95,win98,winme,nt351,nt40,win2k,winxp,win2k3,win20,win30,win31) ; Set version to win98 is recommended. "Windows" = "win98" ; DOS version to imitate ; Only effect when "Windows" = "win31" ;"DOS" = "6.22" ; Be careful here, wrong DllOverrides settings have the potential ; to pretty much kill your setup. |
Use this when posting your Wine Configuration.
Displaying screen output
If you want to show a predictable output of a command, you can use {{Screen_output}}
How to use it :
{{Screen_output| Some Text }}
Example :
Display Coin
$ echo Coin
| |
|
Coin |
Links to the Application Databases
When making a link to the Wine Application Database you can use this template: {{Appdbmain}}
How to use it:Check the link for the Application Database which lists the number for the application at the end of the link. Add those numbers to the template. In this example it is number 12, for the main MS Access listing which lists all versions of Access and add the name afterward.
- http://appdb.winehq.org/objectManager.php?sClass=application&iId=12):
- {{Appdbmain|12}} MS Access
- This then looks like this:
This Software is listed in the Official Wine Application Database
Winehq Main AppDB entry MS Access
The template for the software version is much the same, but is used the the application version. grab the number off the end of the link.
{{Appdb}}
And the same for Codeweavers application Database:
{{Codedb}}
Links to the Wine Bugzilla Entry
{{Winebug}}
How to use it:Check the link for the bug found in bugzilla and look the number for the bug at the end of the link. Add those numbers to the template. In this example it is number 9484, for a bug with copy protection and Wine
- http://bugs.winehq.org/show_bug.cgi?id=9484
- {{Winebug|9484}}
- This then is expanded to look like this:
- Winehq Bugzilla entry 9484
Maintainer Required
Sometimes an application listed in the Wine application database desperately needs a maintainer, or it might just need more maintainers to lend a hand. You can add this to the page. You can use {{Maintainer}}
Example :
- Can you add your results to the Official Wine Appdb? Submitting your results for this software under Wine will help the many other users who run Wine.
| |
Regularly Submitting results for installing and running on the latest version of Wine makes a big difference for others considering using Wine. By looking at how well the software runs others can be encouraged to try it themselves and together you can make progress in finding workarounds. By testing the software you will also notice when something breaks and when you make a bug report, the bugzilla team will often point it out to the person who broke it. If you are slightly more technically minded, you are able to regularly compile wine and test it before each fortnightly release then you will catch breakages before each wine release.
Official Information Unofficial Information A big advantage of being a maintainer is that as you quickly become familiar with installing and using wine with your software, you can have a direct hand in improving wine and your software. Many times you will find very handy tips posted by others and by posting a summary many benefit from your work. When you are asked a question you don't know, simply post in the wine-users forum and perhaps someone can help. Just by being there, you make a difference. A maintainer quickly tests each monthly release of wine, and adds to the application database a rating of how good it runs.. gold/silver/bronze or garbage. Wine is constantly being improved, and occasionally something breaks. When you do spot a breakage, file a bug in bugzilla and if you want to try and fix it you can then post to the wine-devel mailing list for advice. However, if you have a little spare time (usually about 2 hours, in between doing other things) regression testing allows you to identify which patch caused the break. By filling out a bugzilla report, posting the name of the software, and the patch which broke it to the wine-devel mailing list, the developer who broke it can have a look at fixing it.
Further Help to Wine |
Links
Want to add some handy links to help a visitor investigate running their software on Linux and Wine. By adding {{Links}} to the page they may find some handy reading.
