This wiki has been automatically closed because there have been no edits or log actions made within the last 60 days. If you are a user (who is not the bureaucrat) that wishes for this wiki to be reopened, please request that at Requests for reopening wikis. If this wiki is not reopened within 6 months it may be deleted. Note: If you are a bureaucrat on this wiki, you can go to Special:ManageWiki and uncheck the "Closed" box to reopen it.DynamicPageList3 Manual talk:Feedback: Difference between revisions
DynamicPageList3 Manual talk:Feedback (view source)
Revision as of 13:45, 16 April 2022
, 2 years agono edit summary
imported>FrozenPlum m (Fix my typos because my writing is really bad today.) |
No edit summary |
||
Line 54:
:* Could shorter references from the code, with a citation and link to the full code on GitHub, be a feasible alternative to copying larger chunks of the extension's code (I have no idea if this is sufficient, I'm just wondering if it needs duplicating, or if perhaps function names, citations with links, and line number(s) could be an alternative if the MH licenses are incompatible, since I've seen that sort of approach elsewhere)?
:* Would the code sections need to be updated between different versions (if I understand correctly, though I probably don't, the code sections may change between versions)?
: [[User:FrozenPlum|FrozenPlum]]
<dl><dd><dl><dd>Sorry for the late I have not known this wiki was re-opened to the public as notifications didn't work.
<blockquote>Would a "Key changes" and/or "Migration guide" page (or something along those lines), in addition to the normal in-line (brief) mentions of, and links to changes, sound appropriate to you? --I'm pretty excited by the idea. :)</blockquote>
It sounds great to me and I even didn't know that the readme does not include that information, unlike the PortableInfobox.
<blockquote>I'd also propose not doing DPL extension code in-line, on the existing pages,</blockquote>
I can't understand this sentence. Does 'DPL' mean the original DPL for Wikinews? Wikitext code or PHP code? I think we should not show end users the PHP code at all. Do you mean administrators of wikis and the installation guide?
<blockquote>Would large extension code blocks be necessary (for the average user) to see, to migrate successfully from one version of DPL3 to the other?</blockquote>
Same, I am not sure what 'extension code blocks' means. PHP code? What I tried to write in my last post is the documentation of the code, not the code itself. I Apologies if I confused you. [https://github.com/Universal-Omega/DynamicPageList3/blob/master/README.md#configuration README.md#configuration] provides many resources and we expect it to be always up-to-date and it is why I thought we should carry it to the wiki. Another example is something like below comment from [https://github.com/Universal-Omega/DynamicPageList3/blob/da27636f6b294f64e379c1fca96cbee0bbd83bc9/includes/ParametersData.php#L232-L241 here]:
<syntaxhighlight lang="php" line="1" start="232">
/**
* category= Cat11 | Cat12 | ...
* category= Cat21 | Cat22 | ...
* ...
* [Special value] catX='' (empty string without quotes) means pseudo-categoy of Uncategorized pages
* Means pages have to be in category (Cat11 OR (inclusive) Cat2 OR...) AND (Cat21 OR Cat22 OR...) AND...
* If '+' prefixes the list of categories (e.g. category=+ Cat1 | Cat 2 ...), only these categories can be used as headings in the DPL. See 'headingmode' param.
* If '-' prefixes the list of categories (e.g. category=- Cat1 | Cat 2 ...), these categories will not appear as headings in the DPL. See 'headingmode' param.
* Magic words allowed.
*/
</syntaxhighlight>
Reusing the documentation would reduce efforts to start from scratch and the possibility of the wrong description, but with license concerns. (I don't mean we should to include code in this way, we should remove <code>/**</code> etc and use normal paragraphs)
[[User:Lens0021|Lens0021]] ([[User talk:Lens0021|talk]]) 13:45, 16 April 2022 (UTC)
</dd></dl></dd></dl>
| |||