v50 Steam/Premium information for editors
  • v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
  • Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.

Editing Talk:Main Page/archive2

Jump to navigation Jump to search

Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.


The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 122: Line 122:
 
::::2) We've discussed user names on [[User_Talk:Teres_Draconis#Naming Conventions|my talks page]]. (Also, <nowiki>~~~</nowiki> still puts "jaz"... why bother with the link when it's just a P.S.?)  
 
::::2) We've discussed user names on [[User_Talk:Teres_Draconis#Naming Conventions|my talks page]]. (Also, <nowiki>~~~</nowiki> still puts "jaz"... why bother with the link when it's just a P.S.?)  
 
::::3) I'm sorry. I was (apparently) trained wrong, and that was a /long/ time ago. I was taught (20 years ago) that when responding, to do so in-line, so that people can tell what the response is actually relating to. (Like an actual conversation, except with a time warp. You say something, I respond, someone else adds, we all move on to the next topic.) It supposedly adds clarity. The style and curtesy rules of such things has changed. I can see I'll need to update myself. Thank you for pointing that out. =)
 
::::3) I'm sorry. I was (apparently) trained wrong, and that was a /long/ time ago. I was taught (20 years ago) that when responding, to do so in-line, so that people can tell what the response is actually relating to. (Like an actual conversation, except with a time warp. You say something, I respond, someone else adds, we all move on to the next topic.) It supposedly adds clarity. The style and curtesy rules of such things has changed. I can see I'll need to update myself. Thank you for pointing that out. =)
::::4) I was hasty. I had to have meatspace people explain to me why, as wiki-''writers'', you would not want so much detail on a page. Especially when, with every new game release, any given page on the wiki might need an over haul. I was only looking at it from the end-user perspective of "If I'm looking for information, I don't want a page that just tells me to go look at the three pages I've already looked at. I want a page that reduces the noise of the irrelevant, and distills to just that specific (sub-)topic." I /don't/ see the point of six pages that are identacle except for title, and all only three lines long. If it's got it's own page, it should have it's own page. If it just links back to the three pages that linked to it, and they all link to each other already, what's the point? If the only thing Chalk has going for it is that it's flux, why not just make a note on the [[Stone]] page reading, "These three rocks can be used as flux" and link to the flux page from there? Why should chalk have it's own page, if it's not going to be richly detailed and, you know, informative?  - [[User:Teres Draconis|jaz]] 18:59, 22 May 2009 (UTC)
+
::::4) I was hasty. I had to have meatspace people explain to me why, as wiki-''writers'', you would not want so much detail on a page. Especially when, with every new game release, any given page on the wiki might need an over haul. I was only looking at it from the end-user perspective of "If I'm looking for information, I don't want a page that just tells me to go look at the three pages I've already looked at. I want a page that reduces the noise of the irrelevant, and distills to just that specific (sub-)topic." I /don't/ see the point of six pages that are identacle except for title, and all only [http://argosycasinokansascities.com/ Argosy casino kansas city]
 +
three lines long. If it's got it's own page, it should have it's own page. If it just links back to the three pages that linked to it, and they all link to each other already, what's the point? If the only thing Chalk has going for it is that it's flux, why not just make a note on the [[Stone]] page reading, "These three rocks can be used as flux" and link to the flux page from there? Why should chalk have it's own page, if it's not going to be richly detailed and, you know, informative?  - [[User:Teres Draconis|jaz]] 18:59, 22 May 2009 (UTC)
  
 
::::The templates are there because they are pretty, detailed, and condensed ways to display some key information. Rather than expanding existing information so that it takes up more space, it's more productive to add things that you think are lacking. [[User:VengefulDonut|VengefulDonut]] 12:15, 21 May 2009 (UTC)
 
::::The templates are there because they are pretty, detailed, and condensed ways to display some key information. Rather than expanding existing information so that it takes up more space, it's more productive to add things that you think are lacking. [[User:VengefulDonut|VengefulDonut]] 12:15, 21 May 2009 (UTC)
Line 132: Line 133:
 
:::I agree! But I have no idea how to write it. Most of what I know about geology I learned from looking at the raws. Everything else is "OMG, is that a ''rock''?! I've heard of those!" - [[User:Teres Draconis|jaz]] 18:59, 22 May 2009 (UTC)
 
:::I agree! But I have no idea how to write it. Most of what I know about geology I learned from looking at the raws. Everything else is "OMG, is that a ''rock''?! I've heard of those!" - [[User:Teres Draconis|jaz]] 18:59, 22 May 2009 (UTC)
  
::"More useful" to some, but I agree it would be a great addition. Also, the more I think about it, the more I like what MrDG did with the table in Other Stone - tables could condense any and all small, individual articles into single pages w/ (sortable?) tables where all these various similar objects could be compared/contrasted at a glance.  Templates are perfect when there is a lot of various info, but if the different topics (semi-generic stones, animals, finished goods) all differ only in one or two details, and there is just not that many variables to begin with, a Table would be (imo) preferable. ''(And imo that table now covers such stones as Olivine well, to get back to the original example that sparked this discussion.)''
+
::"More useful" to some, but I agree it would be a great addition. Also, the more I think about it, the more I like what MrDG did with the table in Other Stone - tables could condense any and all small, individual articles into single pages w/ (sortable?) tables where all these [http://bicycle-casinos.com/ Bicycle casino]
 +
various similar objects could be compared/contrasted at a glance.  Templates are perfect when there is a lot of various info, but if the different topics (semi-generic stones, animals, finished goods) all differ only in one or two details, and there is just not that many variables to begin with, a Table would be (imo) preferable. ''(And imo that table now covers such stones as Olivine well, to get back to the original example that sparked this discussion.)''
  
::As an additional example of how current stub-articles could be combined into a simple table, I've made this page - [[Example - some fish]] - which could be a model for such.  (A page/table with all the "Sea-creatures" would be more likely approp, but this was faster for now.)  It would replace every stub-article on related "generic" items, but any truly noteworthy items would still have their own full articles for expanded information and commentary (here, "carp").  It still has 100% of the prev information, but also allows immediate comparison and contrast, and, if sortable, allows a User to more easily compare relations between similar aspects (like "biome", in this example.)--[[User:Albedo|Albedo]] 00:13, 22 May 2009 (UTC)
+
::As an additional example of how current stub-articles could be combined into a simple table, I've made this page - [[Example - some fish]] - which could be a model for such.  (A page/table with all the "Sea-creatures" would be more likely approp, but this was faster for now.)  It would replace every stub-article on related "generic" items, but any truly noteworthy items would still have their own full articles for expanded information and commentary (here, "carp").  It still has 100% of the prev information, but also allows immediate comparison and contrast [http://bluechipcasinos.net/ Blue chip casino]
 +
, and, if sortable, allows a User to more easily compare relations between similar aspects (like "biome", in this example.)--[[User:Albedo|Albedo]] 00:13, 22 May 2009 (UTC)
  
::: Is it possible to put the expandable version of the raw ("game object data (show)" seen at the bottom of the [[carp]] page) inside the table, instead of the whole thing? Or does the one preclude the other?  - [[User:Teres Draconis|jaz]] 18:59, 22 May 2009 (UTC)
+
::: Is it possible to put the expandable version of the raw ("game object data (show)" seen at the bottom of the [[carp]] page) inside the table, [http://bodog-casinos.com/ Bodog casino]
 +
instead of the whole thing? Or does the one preclude the other?  - [[User:Teres Draconis|jaz]] 18:59, 22 May 2009 (UTC)
  
 
:::Actually, if someone finds it easy to extract that information from the .RAWs, I would find that an improvement on what [[Creatures]] currently has. [[User:Decius|Decius]] 17:52, 22 May 2009 (UTC)
 
:::Actually, if someone finds it easy to extract that information from the .RAWs, I would find that an improvement on what [[Creatures]] currently has. [[User:Decius|Decius]] 17:52, 22 May 2009 (UTC)
Line 142: Line 146:
 
::::If someone here knows PHP they may be able to write a new wiki hook that pulls information from raw entries. That would make many things much easier. [[User:VengefulDonut|VengefulDonut]] 22:22, 22 May 2009 (UTC)
 
::::If someone here knows PHP they may be able to write a new wiki hook that pulls information from raw entries. That would make many things much easier. [[User:VengefulDonut|VengefulDonut]] 22:22, 22 May 2009 (UTC)
  
:::Which information do you want extracted? I can probably do it for you, but you may have heard, I'm in the doghouse for not paying attention to style and formating rules. =/  Show me what there is, and one example of what you want, and I can probably do it for you with a minimum of stupid questions. ... ''Probably.''  - [[User:Teres Draconis|jaz]] 18:59, 22 May 2009 (UTC)
+
:::Which information do you want extracted? I can probably do it for you, but you may have heard, I'm in the doghouse for not paying attention to style and formating rules [http://casino-del-sol.net/ casino del sol]
 +
. =/  Show me what there is, and one example of what you want, and I can probably do it for you with a minimum of stupid questions. ... ''Probably.''  - [[User:Teres Draconis|jaz]] 18:59, 22 May 2009 (UTC)
  
 
::::@ jaz, Dec - Did either of you look at this sample table? [[Example - some fish]]  Does that cover what you were envisioning?  It's just a rough idea - but it could work the same way that the table on the [[stone]] page currently does, to cover all the generic, almost-identical objects. Same w/ finished goods, weapon traps, probably many other sim categories of like items.--[[User:Albedo|Albedo]] 22:52, 22 May 2009 (UTC)
 
::::@ jaz, Dec - Did either of you look at this sample table? [[Example - some fish]]  Does that cover what you were envisioning?  It's just a rough idea - but it could work the same way that the table on the [[stone]] page currently does, to cover all the generic, almost-identical objects. Same w/ finished goods, weapon traps, probably many other sim categories of like items.--[[User:Albedo|Albedo]] 22:52, 22 May 2009 (UTC)
I've read this sort of. My view is, wikis add value to the game far more for noobs than they do to legends who have been around since when the z-axis was just an idea. With this in mind, I reckon if everything with a name in the game had an article that would be *A Good Thing* (tm). Just my own opinion, feel free to disagree. Ideally, articles for things like stones should contain a template constructed from the raws, with prose/dialogue manually added.
+
I've read this sort of. My view is, wikis add value to the game far more for noobs than they do to legends who have been around since when the z-axis was just an idea. With this in mind, I reckon if everything with a name in the game had an article that would be *A Good Thing* (tm). Just my own opinion, feel free to disagree [http://casino-royale-lasvegas.com/ casino royale las vegas]
 +
. Ideally, articles for things like stones should contain a template constructed from the raws, with prose/dialogue manually added.
 
Even things like [[screw pump]] could have a template driven section, advising what the components are / who makes it etc. Maybe <nowiki>{{building|Building Name|Component 1:Component 1 name|Component X| component X name|Constructed by|trade}}</nowiki> or similar.[[User:GarrieIrons|GarrieIrons]] 08:45, 30 May 2009 (UTC)
 
Even things like [[screw pump]] could have a template driven section, advising what the components are / who makes it etc. Maybe <nowiki>{{building|Building Name|Component 1:Component 1 name|Component X| component X name|Constructed by|trade}}</nowiki> or similar.[[User:GarrieIrons|GarrieIrons]] 08:45, 30 May 2009 (UTC)
  
 
:I agree, probably, although that sounds like a lot of work. I think the stone templates and articles could do with a bit of a cleanup and more in-game information. I mostly use the articles to see if there's anything notable about a particular stone and then check out the wikipedia page. Some of the wikipedia links are broken or indirect now because disambiguity pages have been added since. Also, the wikipedia links are right at the bottom of very long boxes listing ores and gems and the like - I suggest adding drop down boxes to the templates that contain all that information but which are minimized by default. Or changing the template so that the wikipedia link wraps around the stone name at the top. --[[User:Harmonica|Harmonica]] 01:36, 2 July 2009 (UTC)
 
:I agree, probably, although that sounds like a lot of work. I think the stone templates and articles could do with a bit of a cleanup and more in-game information. I mostly use the articles to see if there's anything notable about a particular stone and then check out the wikipedia page. Some of the wikipedia links are broken or indirect now because disambiguity pages have been added since. Also, the wikipedia links are right at the bottom of very long boxes listing ores and gems and the like - I suggest adding drop down boxes to the templates that contain all that information but which are minimized by default. Or changing the template so that the wikipedia link wraps around the stone name at the top. --[[User:Harmonica|Harmonica]] 01:36, 2 July 2009 (UTC)
  
Way late to this party, apologies. Tables are no good (to me) if they aren't sortable. The World Ends With You (a Nintendo DS game) Wikia portal/wiki thing has an ''awesome'' method for adding sortable tables. Some gadget called [http://en.wikipedia.org/wiki/Semantic_MediaWiki Semantic MediaWiki] that hooks into the Wiki to automatically pull data out as you request it, then display it in easy-to-read and use sortable tables. The TWEWY Wikia has [http://twewy.wikia.com/wiki/The_World_Ends_With_You:Semantic_MediaWiki a page on it] for their editors, giving a few examples of how powerful it is. Their use of the tool is to easily pull information from a table of 304 items, each containing 30 attributes, to generate lists comparing and compiling various items. Hugely powerful, extremely flexible.
+
Way late to this party, apologies [http://clams-casino.net/ clams casino]
 +
. Tables are no good (to me) if they aren't sortable. The World Ends With You (a Nintendo DS game) Wikia portal/wiki thing has an ''awesome'' method for adding sortable tables. Some gadget called [http://en.wikipedia.org/wiki/Semantic_MediaWiki Semantic MediaWiki] that hooks into the Wiki to automatically pull data out as you request it, then display it in easy-to-read and use sortable tables. The TWEWY Wikia has [http://twewy.wikia.com/wiki/The_World_Ends_With_You:Semantic_MediaWiki a page on it] for their editors, giving a few examples of how powerful it is. Their use of the tool is to easily pull information from a table of 304 items, each containing 30 attributes, to generate lists comparing and compiling various items. Hugely powerful, extremely flexible.
  
This type of tool would work wonderfully with a PHP RAW parser, or even simple dumps of the RAWs to the Wiki. Think of how easy it would be to update the entire Wiki across the board when new versions come out. New critters? Changes to existing critters? Update the information in one spot and it trickles down through the entire Wiki! That's in addition, of course, to being able to, say, generate tables listing how many bones each creature drops when killed, then sort to see which one drops the most. Pretty sweet stuff.
+
This type of tool would work wonderfully with a PHP RAW parser [http://clearwatercasinos.com/ clear water casino]
 +
, or even simple dumps of the RAWs to the Wiki. Think of how easy it would be to update the entire Wiki across the board when new versions come out. New critters? Changes to existing critters? Update the information in one spot and it trickles down through the entire Wiki! That's in addition, of course, to being able to, say, generate tables listing how many bones each creature drops when killed, then sort to see which one drops the most. Pretty sweet stuff.
  
 
With some sort of system in place for wading through all the data on the wiki, one wouldn't have to worry about having too much information, right? -- [[User:Blank|Blank]] 04:44, 3 July 2009 (UTC)
 
With some sort of system in place for wading through all the data on the wiki, one wouldn't have to worry about having too much information, right? -- [[User:Blank|Blank]] 04:44, 3 July 2009 (UTC)
Line 158: Line 166:
  
 
Particularly for stone, I think that it would be a good idea to describe each individual stone relative to other, similar stones.  Let's use [[sandstone]] as an example.  Suppose that I read (either in its own article, or in a table) something along the lines of "Sandstone is a [[sedimentary]] layer.  Unlike most sedimentary layers, it may contain [[aquifers]] or veins of [[native copper]]."  If I already know what a sedimentary layer is (and how it differs from other types of layers), this information will be much easier to process and much more useful than a full list of everything that appears in sandstone.  If I have no idea what a sedimentary layer is, this will tell me that there are several sedimentary layers and that they all have many things in common, which is again more useful than a list of everything that appears in sandstone. --[[User:LaVacaMorada|LaVacaMorada]] 08:56, 2 October 2009 (UTC)
 
Particularly for stone, I think that it would be a good idea to describe each individual stone relative to other, similar stones.  Let's use [[sandstone]] as an example.  Suppose that I read (either in its own article, or in a table) something along the lines of "Sandstone is a [[sedimentary]] layer.  Unlike most sedimentary layers, it may contain [[aquifers]] or veins of [[native copper]]."  If I already know what a sedimentary layer is (and how it differs from other types of layers), this information will be much easier to process and much more useful than a full list of everything that appears in sandstone.  If I have no idea what a sedimentary layer is, this will tell me that there are several sedimentary layers and that they all have many things in common, which is again more useful than a list of everything that appears in sandstone. --[[User:LaVacaMorada|LaVacaMorada]] 08:56, 2 October 2009 (UTC)
:That's not the way this (any?) wiki is set up.  The idea is that a lesser concept (here, "sandstone") need not include redundant info from a larger, parent concept (here, "sedimentary layer").  If you don't know what a sed'y layer is (or an aquifer or a vein or whatever) you click that link.  If, then, you don't know what a "layer" is, you click that link.  Sounds good at first, but if every lesser article included an explanation, even a quick synopsis, of the info for all relevant articles on broader, umbrella concepts, the articles, and this wiki as a whole, would explode beyond usefulness. --[[User:Albedo|Albedo]] 23:43, 2 October 2009 (UTC)
+
:That's not the way this (any?) wiki is set up.  The idea is that a lesser concept (here, "sandstone") need not include redundant info from a larger, parent concept (here, "sedimentary layer").  If you don't know what a sed'y layer is (or an aquifer or a vein or whatever) you click that link.  If, then, you don't know what a "layer" is, you click that link [http://commerce-casino.com/ commerce casino]
::Thanks for making my point for me.  If you look at the current sandstone article, it lists everything contained in sandstone.  Looking at just the ores and non-generic stones, we have:  Native copper, Hematite, Limonite, Magnetite, Native platinum, Tetrahedrite, Bituminous coal, Lignite, Bauxite.  All of these except for native copper appear in every sedimentary layer.  That's not even counting all of the generic stone (especially gypsum with its five other types of generic stone contained in it) and (mostly low-value) gems.  95% of the text in this article is redundant, and could easily be summarized by "This layer is exactly like every other sedimentary layer except for these two differences". --[[User:LaVacaMorada|LaVacaMorada]] 09:06, 6 October 2009 (UTC)
+
.  Sounds good at first, but if every lesser article included an explanation, even a quick synopsis, of the info for all relevant articles on broader, umbrella concepts, the articles, and this wiki as a whole, would explode beyond usefulness. --[[User:Albedo|Albedo]] 23:43, 2 October 2009 (UTC)
 +
::Thanks for making my point for me.  If you look at the current sandstone article, it lists everything contained in sandstone.  Looking at just the ores and non-generic stones, we have:  Native copper, Hematite, Limonite, Magnetite, Native platinum, Tetrahedrite, Bituminous coal, Lignite, Bauxite.  All of these except for native copper appear in every sedimentary layer.  That's not even counting all of the generic stone (especially gypsum with its five other types of generic stone contained in it) and (mostly low-value) gems.  95% of the text in this article is redundant, [http://desplainescasinos.net/ DES PLAINES CASINO]
 +
and could easily be summarized by "This layer is exactly like every other sedimentary layer except for these two differences". --[[User:LaVacaMorada|LaVacaMorada]] 09:06, 6 October 2009 (UTC)
 
:::Ah - ''that's'' your point. (When you said "describe", I thought you were advocating a narrative commentary on and verbal expansion of the info included in the sidebar.) When I was talking about not having redundant info, I was talking text - which is quite terse in this case, exactly because of the point you make.  Those sidebars were designed to encapsulate the key info, an "at a glance" sort of thing, to avoid exactly what you're talking about in narrative form. Are the sidebars redundant? Often, yes.  But they are the style this wiki has adopted for ''all'' stone.  So you're talking not just about changing sed'y layers, but the style approach to all stone, since they would not then be consistent across the board. (Not how I would have personally designed the layout, but it's there and it works, and well. Any stone, same layout, same info in the same place, bam got it.)  And when discussing presentation and usability issues, any article has to be taken both individually and in the context of others "like" it - here, any "stone" article is the same layout, the same info at a glance, which (for now) trumps whatever redundancies exist.  Perhaps a quick line such as you're stating would go well, since there is, indeed, very little unique to say about any one sub-type of sedimentary layer, and that is info in and of itself. (Take a look at any [[igneous extrusive]] except obsidian for something similar.)--[[User:Albedo|Albedo]] 16:46, 6 October 2009 (UTC)
 
:::Ah - ''that's'' your point. (When you said "describe", I thought you were advocating a narrative commentary on and verbal expansion of the info included in the sidebar.) When I was talking about not having redundant info, I was talking text - which is quite terse in this case, exactly because of the point you make.  Those sidebars were designed to encapsulate the key info, an "at a glance" sort of thing, to avoid exactly what you're talking about in narrative form. Are the sidebars redundant? Often, yes.  But they are the style this wiki has adopted for ''all'' stone.  So you're talking not just about changing sed'y layers, but the style approach to all stone, since they would not then be consistent across the board. (Not how I would have personally designed the layout, but it's there and it works, and well. Any stone, same layout, same info in the same place, bam got it.)  And when discussing presentation and usability issues, any article has to be taken both individually and in the context of others "like" it - here, any "stone" article is the same layout, the same info at a glance, which (for now) trumps whatever redundancies exist.  Perhaps a quick line such as you're stating would go well, since there is, indeed, very little unique to say about any one sub-type of sedimentary layer, and that is info in and of itself. (Take a look at any [[igneous extrusive]] except obsidian for something similar.)--[[User:Albedo|Albedo]] 16:46, 6 October 2009 (UTC)
  

Please note that all contributions to Dwarf Fortress Wiki are considered to be released under the GFDL & MIT (see Dwarf Fortress Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Please sign comments with ~~~~

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)