Template talk:Expedition

From Geohashing
Revision as of 20:23, 18 June 2015 by imported>Eldin

I almost never use the image at the top of the page, and I usually make the expedition page before I have photos, so I commented out the image at the top to elide the empty image tag that subst:Expedition always leaves. -- Jevanyn 15:10, 5 June 2009 (UTC)

__NOTOC__ ?

why does this default to no toc? my personal opinion is that the toc makes sense in some cases (multiple people reporting) and is not a detraction otherwise. just wondering what the reasoning was. --mykaDragonBlue [- i have no sig -] 12:27, 11 August 2009 (UTC)

Improved Expedition template

I've created an improved version of this template (currently found at User:Eldin/template/Expedition) which allows you to specify the contents of various page sections in the template, or omit page sections entirely. My version should be completely compatible with the existing version, by which I mean any template usage which works in the currently existing version should produce identical results in either the existing or my modified version. I would like to eventually replace the existing version with my modified version, but I didn't want to make major changes to such a widely used template without at least having some discussion about it first. --Eldin (talk) 13:52, 27 July 2013 (EDT)

Looks reasonable to me, but I've got a couple of suggestions
  • Making the image at the top of the page (sort of) required isn't good, as the template (should) often get used long before the pictures are uploaded.
  • The "help" message is very dense, making it hard for me to read. I'd suggest adding a blank line before and after each pair of "turn this section on/off" and "use this text for that section" params to make it more readable.
Other than that, seems good to me. Jiml (talk) 22:28, 28 July 2013 (EDT)
I suppose I could add a flag to turn off the image at the top. I'd rather have it include or not based on whether or not a value for 'image' was provided, but that breaks the strict backwards compatibility I was shooting for in the first version. I did make the changes you suggested to the format of the help message. --Eldin (talk) 04:22, 29 July 2013 (EDT)
Thanks for putting the work in to improve the template. However, I'm wondering if many of the options will be used much. It would take some time to fill in all the fields or set the flags, and might be rather quicker to just use the basic template and then cut out the unwanted sections while editing the report. I suppose the most useful way of using the new template would be for people to keep a note of their 'default' expedition report settings, and to copy-and-paste that when setting up a new expedition page. Is that how you'd intended it to be used? — Benjw  {talk} 13:44, 29 July 2013 (EDT)
I imagine that at least some of the new options will almost never be used and were only included for completeness because it was trivial to add them at the same time as the more useful ones. Others are things I've personally wished for in the past. Keeping a copy of personal default options is certainly one way to use it. I was also considering the idea of having an app or a web-form that someone could fill in that would build an expedition page from the template without the need for figuring out how to edit the wiki. And of course, it still covers all of the use cases which the existing template does, as all of the new options will default to current behavior if you don't specify otherwise. As a note though, it only behaves properly if you use the {{subst:template}} syntax. If you just use the {{template}} syntax, the way I currently have the conditional logic built doesn't work right. But I don't think that's a big deal to users of the existing template, since it isn't very useful with just the {{template}} syntax anyway. --Eldin (talk) 17:05, 29 July 2013 (EDT)
Given that people can just leave out all of the new options and get the old behavior, and some of the new options might be useful for people, is there any objection to me replacing the existing template with my extended one? --Eldin (talk) 12:14, 18 June 2015 (EDT)
As long as it is fully backwards compatible I don't see a problem in replacing it--Eupeodes (talk) 12:22, 18 June 2015 (EDT)
It is designed such that someone who uses it in a manner which is useful with the existing template should get exactly the same results with mine as the existing one. I have not yet found any case where it doesn't work as intended, but if anyone does I'll consider that a bug and try to fix it.--Eldin (talk) 16:23, 18 June 2015 (EDT)