Talk:GWBBCode

Um, content? &mdash; Skuld 03:17, 21 October 2006 (CDT)

For more content, the next step is to transfer the tutorial to this article.

Extension
Discusion about this page and about the extension if annyone is interested: http://gwshack.us/forums_small/viewtopic.php?t=310 .--Phoenix 17:49, 23 October 2006 (CDT)

About deleting
I am against it. You are wright that is for forums, websites, but it's verry used almost the entire comunity usses it including GuildWars.com uses a similar version. Also an extension for MW exists as well. An thats way there is this category. And this is about the game in the end like GWFreaks, The Edge, GW Team Builder, GW Manager --Phoenix 02:49, 25 October 2006 (CDT)


 * The end product is not something you use in the game, it's something you use to make your site look better. --Karlos 03:52, 25 October 2006 (CDT)


 * Wrong! the end product you use in game. After the build maker makes the build it postes it on the forum for the next gvg battle, or TA, or wathever then the memmbers can specify if they can play it or not and what position as well make modification. So you see it is used.--Phoenix [[Image:Phoenix_Benu.png]] 04:52, 25 October 2006 (CDT)


 * Ummm, this is not a build maker, is it? As I understand, it's just code to allow you to display skill info on a web page, no? --Karlos 05:06, 25 October 2006 (CDT)


 * Yes it's a build maker as a code to be displayed on a forum. Take a look on http://gwshack.us/ at the build library section.--Phoenix [[Image:Phoenix_Benu.png]] 06:49, 25 October 2006 (CDT)


 * I'm not sure yet whether I should agree or disagree with a delete. It is right, we do have articles about 3rd party software, but this is not a 3rd party software used with the game, but rather a 3rd party software for fansites about the game. It was agreed that we do not want articles about fansites on the wiki. However, from a different point of view: Does it hurt in any way, to keep this article? It may not be directly connected to the game, but it is closely related. --84-175 (talk) 06:29, 25 October 2006 (CDT)


 * I have made a Mediawiki extension to support gwBBCode on wiki, so I think this page has a place in the wiki (see here). Even if the extension is not used by Guild Wiki, it is a software which has a relationship with Guild Wars.--Ouroboros 07:13, 25 October 2006 (CDT)


 * If this articles claim that ANet uses this on their homepage is true, that is a good argument against deletion. --Xeeron 09:23, 25 October 2006 (CDT)
 * If you view the source code, then it's obvious that GuildWars.com is using a Java markup that's entirely different than the markup used by the french wiki site. From that, I believe that the guildwars.com code is not based on gwBBcode.
 * As for deletion, I support it. We do not document mediawiki, php, mySQL, or the hardware on which the fansite runs.  We are not an encyclopedia, we document the game.  If we documented individual fansites or software used by fansites, then I could see keeping this.  But, we do neither.
 * I believe that gwBBCode deserves a topic of discussion in the talk page for the Community Portal, to discuss its use on this site. But, I do not believe that it merits its own article. --- Barek (talk • contribs) - 09:41, 25 October 2006 (CDT)


 * I am completely against deleting, This is not a fansite article (the article is about GwBBcode not Gwshack), it is a tool just like Gwfreaks (which you have an article). It is not only for sites to look "pretty", it also helps incredible to party formation (see pickup function on tutorial). While you are ingame, I use gwBBcode more than gwfreaks actually looking for the posted builds that have neat information. I even beleave wiki should install it, having to open 5 windows to understand an uncommon posted build is annoying, which would be great if you have all the skill info in a little pop-up window. --Coran Ironclaw.

this tool, is not intended primarly to make sites look better, is intended to provide an understendable way to look at builds, or build discussion in a forum, also GW official page have now something similar, you can see it here http://www.gwshack.us/forums/viewtopic.php?t=322, althoug its not directly related to the game, its related the same way as Gw freaks or any other third party software, its only the channel on which you use it what changed, in this case PHPbb forums (and various others) Apoguita 09:58, 25 October 2006 (CDT)
 * As I said above, the official site does not appear to be using gwBBCode, they are using their own Java code. We do not have articles for any of the software used by this site: mediawiki, php, mySQL, nor any of the other add-ins used such as ParserFunctions, ceSetup and wfSetupParserFunctions.  Even if added to GuildWiki (which I agree that we should seriously consider, as I like the tool), I still see no reason to document it in its own article.  We do not document fansites, we do not document software used by fansites, and we are not an encyclopedia.  --- Barek (talk • contribs) - 10:17, 25 October 2006 (CDT)


 * Agree w/deletion for much the same reasons that Barek lists. Next thing we'll need a page for The Internet (3rd party network that the game is played on).  --Rainith 11:06, 25 October 2006 (CDT)
 * I disagree on treating GWBBcode as a Fansite discussion /article, this article is NOT about http://www.gwshack.us the SITE but GWbbcode THE TOOL, and i stand my ground on saying that its a TOOL such as GWFreaks, The Edge, GW Team Builder, GW Manager or others third party programs that you have articles on wiki, its just that the media on wich is distributed differs on popular third party programs in this case its in PHPbb forums and not stand alone applications.Apoguita 12:40, 25 October 2006 (CDT)


 * The arguments I gave above for deletion was based on the tool, not the site. Please re-read it.  It is fundamentally different than GWFreaks or any other third party tool currently documented on this site, so not a parallel of those examples.  The tool is much more closely related to tools such as the ParserFunction extensions which is currently in use on the skill articles within this site, but that tool also does not get its own article.
 * I agree that we should seriously consider implementing the tool for this site. But, it does not deserve its own article.  --- Barek (talk • contribs) - 12:54, 25 October 2006 (CDT)


 * I think the comparison on gwbbcode with php, mysql or mediawiki is completely wrong. Because the other softwares are Generic ones, and (as you claim) can be found on a Generic Encyclopedia or wikipedia. But if we want to look for gwbbcode on wikipedia, guess what? We can't find it!, why? Because it is Exclusively for Guild Wars, then it shouldn't be documented on a Generic Encyclopedia or wikipedia but on a Guild Wars Wiki-pedia. -Coran Ironclaw
 * The argument for it being in Wikipedia or not are 100% irrellevant and unrelated to if it belongs in GuildWiki. --- Barek (talk • contribs) - 13:09, 25 October 2006 (CDT)
 * The argument being a tool exclusively for Guild Wars is relevant. -Coran Ironclaw
 * It's a tool for fansites. We do not document fansites, their site tools, or their site software. --- Barek (talk • contribs) - 13:44, 25 October 2006 (CDT)
 * If a tool for fansites is exclusively for Guild Wars sites, you should start considering document them. Furthermore, if Guild Wiki in a near future decide to apply this code to thier pages, you will need an article explaining how to use it, since it is not part of mediawiki. -Coran Ironclaw
 * There is no reason to document tools for fansites unless we also documented fansites - which is something that was debated previously and decided against.
 * As for documenting its use, we have instructions in our style and formatting articles on how to do many mediawiki formatting tasks, yet we have no mediawiki article. If we implement this tool, I see no reason to change the precedent of just documenting use of the tools in a style and formatting article.  I also suspect that to simplify its use, we would embed much of the function by modifying existing site templates. --- Barek (talk • contribs) - 13:58, 25 October 2006 (CDT)
 * "There is no reason to document tools for fansites unless we also documented fansites" <- I disagree with this particular rational, without taking a side in the issue yet. The tool isn't just used by particular fansites, but is a general fansite tool.  Thus the issue of documentation of this general tool should not be related to the decisions of whether to document specific fansites.  Additionally, we do have a general article on fansite.  Thus the quoted argument against a general fansite tool, in my opinion, is flawed reasoning.  On the other hand, I agree that whether GuildWiki uses this tool or not (either in its original form or a modified form) has no bearing on whether we should document it or not. - 14:54, 25 October 2006 (CDT)


 * (resetting margin)
 * There are two arguments being presented for why we should keep this article:
 * It is a useful tool used on Guild Wars sites to help make builds more readable.
 * It is a tool "exclusive" to Guild Wars sites unlike mySQL.
 * The first argument is irrelevant. We honestly do not care to document anything about sites and how they work, including Guildwars.com.
 * The second argument is misleading because the author customized existing JavaScript code (or something else) to help with the specific task of displaying skill icons with info overlayed on it. This is not really exclusive to GW. Someone else can write a similar module for their site (as ANet did for theirs and as Fyren did for us). So, to say that the CONCEPT is used on many sites is a reason to document a SPECIFIC instance is misleading. --Karlos 14:36, 25 October 2006 (CDT)


 * If the specific instance happens to be the (or one of the) most prominent implementation of abovementioned concept for GuildWars fansites (I do not know whether that is true or not, just throwing the IFs around for consideration), would you consider that to be of sufficient merit for documentation? I'm still reading the various arguments and weighing them before taking a stance on this issue. - 14:49, 25 October 2006 (CDT)


 * No, as I said in the first point, it's really irrelevant how GW sites choose to document the game and I do not think we should go about recording that. Another point to consider is that this is a tool used by site admins/webmasters to make the information presentation better. the average user could not possibly care any less about how that cute little hovering feature is implemented. We do not have ANY content here on the wiki that is just for site admins/curious programmers/and so forth. Anything we document is something that users (all users) would be intersted in. why would the average user care how something behind the scenes is implemented? All those other tools are things the user can pick up and use himself while he is playing. If I pick up this tool tomorrow, what can I do with it while playing the game? --Karlos 15:01, 25 October 2006 (CDT)


 * Your argument is completely false and it is the main argument to be documented. This tool is not used only by admins/webmasters to put information on their sites.  But It is used by Any Forum User which wants to put a build or talk about a skill on any forum with this code implemented. By instance, look at this site, and how every user uses the code to make their points extremely more readable than without it. -Coran Ironclaw. http://gwshack.us/forums/viewtopic.php?t=36 and if you want a link outside the official site here is an example http://foro.cronicasderiddick.com/viewtopic.php?t=262&postdays=0&postorder=asc&start=0 and i have many more examples (sorry for the spanish on last one)


 * You just made Karlos' point for him. By your own admission: "any forum with this code implemented".  It MUST be implemented by site admins/webmasters to even be relevant.  If we do implement it here, that would still not automatically mean than an article should exist on it.  As I pointed out, the style and formatting articles cover all code instruction for us now, and should continue to do so with or without this code.  It is merely an extra add-on/extension to the site code base. --- Barek (talk • contribs) - 15:25, 25 October 2006 (CDT)


 * Ironclaw, You are missing the point. The users on that thread (by the way, none of the icons showed anything for me, but I assume it works) posted their builds. I don't see the code they used, but I am assuming they just put minimal code arround the skill name to have it displayed in that manner (kinda like Fyren is doing with the whole toggle thingie). The user should not "program" to get this to work (and if this is how it works now, then it sucks), so as far as the user is concerned, they do something like we do here (e.g., and then some backend renders that into a pretty icon with a cool hover. am I correct in this assumption or does it require them to write actual code?
 * So, assuming that this is how it works, it's still not "used" by the average user, it benefits the average user. Do you follow? --Karlos 15:33, 25 October 2006 (CDT)

how Gwfreaks differs from gwBBcode? or for this matters, any third program Gw software differs from this?, BBcode is an utility to post builds in a public channel, gw freaks is for making builds in a privete channel, but to me is still the same, both are aids for players to manage thing from the game outside the game.Apoguita 15:43, 25 October 2006 (CDT)


 * A user can download GWFreaks, and they have a tool that they can use immediately. A user who downloads gwBBcode does not unless they also happen to have a forum or wiki on which to install it.  gwBBCode is only relevant if a site admin downloads and installs the code.  It's an add-on the forum or wiki software.  We don't document any other wiki or forum add-on, this should not be treated any differently than other add-ons. --- Barek (talk • contribs) - 15:53, 25 October 2006 (CDT)
 * gwfreaks can only be used with framework 1.1 installed we can make an analogy of framework and a forum though its obviously not the same, but to prove the point that you need another application in order to run it. presonally, i dont use gwfreaks because of the framework wich i dont have.