Template talk:Development

From RepRap
Jump to: navigation, search

more metatags

This Infobox needs to be added to to include metatags for software, electronics, and extruder ends.--Buback 05:07, 25 October 2010 (UTC)

Are you literally asking for someone to add "software" etc. to the Template: Development template something like this?:
|categories = xzk
|cadModel = 
|software = 
|electronics = 
|hotend = 
|coldend = 
|url = 
What about adding them to the Template: Machine template? --DavidCary (talk) 09:32, 23 April 2014 (PDT)

category tag

Hey Issac, could you fix the category tag so that you just have to enter in the plaintext, comma seperated, and it will generate a link to the proper category and add the category tag to the page? it's a annoying to have to type:


And i don't expect most users to bother doing it properly. --Buback 20:10, 25 October 2010 (UTC)

That would be a handy feature. While I'm not exactly sure how to do that I think I'll give it a go! Something else we need to figure out is how to make some infobox fields optional so they don't show up by default if you don't require them. For example if someone didn't have an external url. Of course we still would want some fields to always show up like description and author and so-fourth. --Isaac Olson 00:57, 26 October 2010 (UTC)
If When we get it to work right this type of functionality should be extended to Author/Contributors so multiple users could be bundled up with no []'s. --Isaac Olson 01:02, 26 October 2010 (UTC)
Yes, I agree that would be a handy feature.
Ideally an editor would only have to type "toolheads" in the appropriate place in the template, and it would Do the Right Thing.
But alas, I don't know how to do that.
However, I can get pretty close -- I only need to type "{{tag|toolheads}}".
See template:tag for details. --DavidCary 21:31, 1 December 2010 (UTC)
See Repic[1] for an example of using the "tag" template inside this "development" template. --DavidCary 21:42, 1 December 2010 (UTC)
I have struggled with this as well. However I do not use the shortform tag at this time as the use of {{tag|toolheads}} instead of [[:Category:Toolheads|Toolheads]][[Category:Toolheads]] is not quite equivalent. Certainly if there was something that would format the bulk of the link data with simple user fields or perhaps even some kind of pop-up for pre-existing category names it would be wonderful. The two formal [] links do allow for alternate uses that are pretty rarely (but sometimes) required such as shorter names for the info-box and/or an altered sort order in the category listing these options are not available in the short from {} tag style. If a template or the short tag style becomes standard there might still be justification for being able to override the effects (I have a suspicion that putting the formal [] links after the development header or {} tag would achieve this but it would be good to test). KalleP (talk) 13:58, 21 April 2014 (PDT)
Huh? Using {{tag|Toolheads}} is exactly equivalent to using [[:Category:Toolheads|Toolheads]][[Category:Toolheads]]. --DavidCary (talk) 09:32, 23 April 2014 (PDT)

optional fields

User:Buback wrote: Something else we need to figure out is how to make some infobox fields optional so they don't show up by default if you don't require them.

How this should work is described here: [2], i.e. using #if: and #ifeq: and thelike. I tried in a sandbox, but stuff didn't work out, not even with the sample code copy&pasted. --Traumflug 22:45, 4 June 2011 (UTC)

#if:, #ifeq: and the like require the ParserFunctions extension to be installed, which has to be done by an admin. Is that installed? --Cincodenada (talk) 09:44, 11 July 2015 (PDT)

multiple authors

What should I put in the "author=" section of this template, on a page about some new RepRap developed by two people? Currently several pages name both authors in that section, with a comma between them -- Cyclone PCB Factory, TinyCut/fr, Eiffel, etc. But that makes a single big redlink to a nonexistent username -- all those names mashed together into one name. Is there some way to make two separate bluelinks, one to each person? --DavidCary (talk) 06:21, 23 April 2014 (PDT)

status recognition

The RP9 page currently has "status = production", which is currently not recognized by this "development" template.

Should we change the template:development to recognize "production" as a valid status? Or should we change the RP9 page to "status = working" so its status is recognized by this template? --DavidCary (talk) 08:19, 16 March 2016 (PDT)

Word Breaks

There was a common issue where if the amount text in the template went over a very small threshold, the text would overflow out of the box. I have resolved this by putting each section of text into a new <div> and setting the style to word-break: break-word. I also fixed the inside border so that the radii match up better. This somehow took me two hours and since the preview does not apply changes to the template, I had to keep saving the changes and making small adjustments. I'm so sorry for spamming the edit history but I had no other way to see my edits to the template. NinthDimension (talk) 21:09, 2 December 2018 (EST)

Fix some empty field

Use some {{#if: use in the template to fix wrong issue then no value in author field for example. See RUMBA+ page for example. Phd0 (talk) 18:27, 25 April 2020 (EDT)