13,208
edits
Template talk:Repo link: Difference between revisions
Jump to navigation
Jump to search
→Todo list: Horribly late reply
m (→Supporting different protocols: no longer specific to just SCM links) |
(→Todo list: Horribly late reply) |
||
| Line 181: | Line 181: | ||
:: Regards, | :: Regards, | ||
:: [[User:Red_Leader|<span style="color:red">'''''Red Leader'''''</span>]] ([[User_talk:Red_Leader|Talk]], [[Special:Contributions/Red_Leader|contribs]]) 06:03, 31 May 2015 (EDT) | :: [[User:Red_Leader|<span style="color:red">'''''Red Leader'''''</span>]] ([[User_talk:Red_Leader|Talk]], [[Special:Contributions/Red_Leader|contribs]]) 06:03, 31 May 2015 (EDT) | ||
::: Sorry for the even later reply. | |||
:::; Often used parameters and name suggestions | |||
:::: I think that ''site'' and ''path'' parameters would be superfluous, also how about using ''file'' instead of ''repo''. Instead of pointing to the whole of the repo usually will point to a specific file or directory within a repo. As you say the ''commit'' parameter would only be used sparsely, though I think it might be good to have at times. | |||
::::In essence I am suggesting {{obr}}'''flightgear file'''{{!}}''path''{{!}}''commit''{{cbr}}, {{obr}}'''simgear file'''{{!}}''path''{{!}}''commit''{{cbr}} and {{obr}}'''fgdata file'''{{!}}''path''{{!}}''commit''{{cbr}} for links to source files (and directories). The ''path'' parameter would be what follow after <code>flightgear/src/</code>, <code>simgear/simgear/</code> or <code>fgdata/</code>. | |||
:::; Defaulting | |||
:::: Yep, it is definitively better to default than trow an error. | |||
:::; Aircraft URL templates | |||
:::: Good point about automatic downloading. I did not think of that. Better link to the info pages. | |||
:::; Link styling | |||
:::: Interesting problem. I have considered both something resembling the path in a local file system or some abbreviated variant, like <code>flightgear/src/Time/TimeManager.cxx</code>, <code>simgear/simgear/magvar/coremag.cxx</code> and <code>fgdata/Nasal/view.nas</code>, or <code>flightgear/Time/TimeManager.cxx</code>, <code>simgear/magvar/coremag.cxx</code> and <code>fgdata/Nasal/view.nas</code>. The advantage with having them look like a file path is to help those using Git to find the file in their local clone faster. Then there is also the issues of whether only the ''path'' parameter should be used for the link to the file while there could be an explanatory link preceding it, for example like [[SimGear]]/[http://sourceforge.net/p/flightgear/simgear/ci/next/tree/simgear/magvar/coremag.cxx magvar/coremag.cxx], and whether or not to use mostly lowercase the file path like label or the case used sometimes otherwise, in essence flightgear, fgdata and simgear, or FlightGear, FGData and SimGear. | |||
:::: I am going to suggest abbreviated paths but camel case repo names, like [http://sourceforge.net/p/flightgear/simgear/ci/next/tree/simgear/magvar/coremag.cxx SimGear/magvar/coremag.cxx], though I am not convinced it is the best way. | |||
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 17:34, 10 September 2015 (EDT) | |||