Template talk:User sandbox+

Requested move 5 March 2018

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.

The result of the move request was: Withdrawing this, as it seems that the section below addresses my needs. {{3x|p}}ery (talk) 21:37, 6 March 2018 (UTC)[reply]

Template:create sandbox subpage level → Template:Article page template/library/group
Template:Create sandbox subpage item → Template:Article page template/library/item
Template:Article page template class/Article template library → Template:Article page template/library

– Template organization; these are only used directly on Template:Article page template class/Article template library, which itself is connected to the {{Article page template}} family. {{3x|p}}ery (talk) 00:19, 5 March 2018 (UTC)[reply]

@ManosHacker: {{3x|p}}ery (talk) 00:20, 5 March 2018 (UTC)[reply]

There is coding inside that creates the paths of templates to be called. They are not called directly. As some templates do not seem to be linked to each other, moving them to different names breaks functionality. ManosHacker ^talk 00:32, 5 March 2018 (UTC)[reply]

Could you please explain that further? {{3x|p}}ery (talk) 00:40, 5 March 2018 (UTC)[reply]

The central template is self-adaptive to where it resides (user space or main space, for example) and behaves differently. It behaves differently when the page does not exist yet and also if it has been created in user space or main space, no matter where it currently resides. On top of these, things appear or hide or display different messages or different functionality is enabled. There are nesting limitations in template code that do not allow to do everything programmatically, so I have three different templates that are almost identical: Template:Custom page template (user),Template:Custom_page_template_(program) and Template:Create_sandbox_subpage_item in the fear of crossing the limit. I welcome you to change of naming, I also wish for a more compact code. ManosHacker ^talk 00:58, 5 March 2018 (UTC)[reply]

And this means that these specific templates can't be moved because ... As fair as I can tell, the name of these templates is not determined progamatically. {{3x|p}}ery (talk) 01:18, 5 March 2018 (UTC)[reply]

There is an Editnotice regarding delayed safesubst that is only to appear in Article page templates edits, not assistive templates under the same name. ManosHacker ^talk 02:25, 5 March 2018 (UTC)[reply]

Regarding [Template:Article page template class/Article template library], libraries are being created by declaring them (as classes), and all belong in the same template space. This is "Template:Article page template class" for the time being. A better name for this space is welcome. Please avoid Etitnotice conflict here, too. ManosHacker ^talk 06:36, 5 March 2018 (UTC)[reply]

Editnotice conflict can be avoided by using plural, i.e. "Article page templates" instead of 'Article page template". ManosHacker ^talk 08:07, 5 March 2018 (UTC)[reply]

Sorry, but that defeats the point of this requested move, which is to arrange these internal templates as subpages of their base templa tes, and some having a "s" at the end doesn't do that. {{3x|p}}ery (talk) 15:43, 5 March 2018 (UTC)[reply]

Editnotice conflict has a solution. By wrappping editnotice between

{{#ifeq: {{PAGENAME}} | {{BASEPAGENAME}}
 |

and }}, the templates names proposed above do not get the editnotice. If implemented this way (or any similar way like titleparts), the naming of the two templates proposed (not global library itself move) is fine for me. ManosHacker ^talk 20:23, 5 March 2018 (UTC)[reply]

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.

Re-structure naming

visually edit table


Template	Previous name	Explanation

Assistive
Template:Collapse-mobile		collapsible functionality, original from meta, without show/hide that diplays well in mobiles, even if always expanded
Template:Help-collapsible		collapsible help functionality, supporting nested help levels
Template:Smallbox-mobile	Template:Sandbox smallbox	tiny message box, for inline use, that does not hide in mobile view
Template:Invisible		smallbox-mobile, which is only visible in user space used to display inline messages while the page is still a sandbox, i.e. end of article, so newbies do not modify functional section headers (i.e. References) to use as content section headers.
Template:Delay safesubst		code substitution, in two save steps, which displays and behaves well in user sandbox+ preview

Optical help
Template:Key press
Template:Visual edit
Template:TabButton
Template:BlueButton
Template:WhiteButton
Template:VeButton

Sandbox
Template:User sandbox+		base template that detects space (i.e. main / user / user sub-sandbox), edit mode or not, and page creation origin space, and adapts functionality in central sandbox of user it displays a list of sub-sandboxes of the user and gives the option to click'n'create sub-sandboxes in a user sub-sandbox it gives the option to foolproof click'n'move the sandmoxed page to article space in main (article) space it hides itself if the host pages was originally created in user space it displays in creation messagebox if the page was started directly in main space
Template:User sandbox+/doc		template documentation
Template:User sandbox+/preload		default page content for creation of user's main sandbox
Template:User sandbox+/create page	Template:Create sandbox subpage	handles new page creation centrally embedds help adapts creation mode and functionality according to parameters given
Template:User sandbox+/create page/from library	Template:Create sandbox subpage item , Template:Custom page template (program)	page creation from library of article templates if page template does not exist (is only declared) it prompts for its creation first also prompts for help page creation of article template, to provide support for delayed substitution merge of two templates
Template:User sandbox+/create page/from user palette	Template:Custom page template (user)	page creation from user's palette of page templates if page template does not exist (is only declared) it prompts for its creation first
Template:User sandbox+/create page/new page instructions (useve)	Template:Create sandbox subpage item/New page instructions (useve)	instructions during page creation, for VE
Template:User sandbox+/create page/new page instructions (usece)	Template:Create sandbox subpage item/New page instructions (usece)	instructions during page creation, for CE
Template:User sandbox+/flush page	Template:Flush sub-sandbox	instructions to hide a sub-sandbox form central sandbox list is enabled inside a sub-sandbox it should be replaced by a button that makes the page a redirect, putting text on its top, using prependtext as wiki code editing is not user friendly for newbies or non-computer-literate better yet, if movind a page from other spaces to user space was forbidden for non admins, sandbox (and only sandbox) page delete might be good to be allowed in user space
Template:User sandbox+/move page to article	Template:Move sandbox to article	foolproof move of a user sandbox to main (article) space is enabled inside a sub-sandbox after move, the page is not displayed any more in the user's central sandbox list leaves a redirect behind - moving a page from user space to other spaces should have the option not to leave a redirect behind

Article page templates
Template:Article page templates/display/group	Template:Create sandbox subpage level
Template:Article page templates/user custom/host page matrix	Template:Custom page templates/User hostpage matrix
Template:Article page templates/user custom/display available	Template:Custom page templates/existing
Template:Article page templates/create/matrix	Template:Article page templates matrix
Template:Article page templates/create/talkpage matrix	Template:Article page templates talkpage matrix
Template:Article page templates/empty page	Template:Article page template/empty page
Template:Article page templates/generic article	Template:Article page template/generic article
Template:Article page templates/generic article (codeedit)	Template:Article page template/generic article (codeedit)
Template talk:Article page templates/empty page	Template talk:Article page template/empty page
Template talk:Article page templates/generic article	Template talk:Article page template/generic article
Template talk:Article page templates/generic article (codeedit)	Template talk:Article page template/generic article (codeedit)
Template:Article page templates/libraries/create/matrix	Template:Article page template class/preload
Template:Article page templates/libraries/Article template library	Template:Article page template class/Article template library

Group template editnotice
Template:Editnotices/Group/Template:Article page templates	Template:Editnotices/Group/Template:Article page template
Template:Article page templates	Template:Article page template

How about this structure? Is plural more accurate? Files are the same (renamed) and two of them are merged into one. ManosHacker ^talk 17:40, 6 March 2018 (UTC)[reply]

It's not clear to me what corresponds to what in the format you've provided. {{3x|p}}ery (talk) 21:36, 6 March 2018 (UTC)[reply]

A few initial comments (more to come in a couple hours). 1: You should expand "useve" and "usece"/"codeedit" into "Visual editor" and "Wikitext editor", and mention the editor in all cases where there are separate templates for both editors. 2: Many of the template names you suggested in the {{Article page templates}} family technichally meet G8, as {{Article page templates/display}}, {{article page templates/libraries}} and {{Article page templates/libraries}} don't exist. {{3x|p}}ery (talk) 12:39, 7 March 2018 (UTC)[reply]

Hello Pppery, thank you for your reply, I will be able to fully respond in 7-8 hours from now. 1 is a technical issue as I am trying to narrow down the number of if statements inside the template code, so I am using the Inputbox parameter name itself. This anorthodox approach is a hack and annoys me too. If I have to use it now, to overcome template restrictions, it sure has to be noted to change after porting to real (non-template) code. The other thing is I have used plural (templates instead of template), so the links are red, but we can go back to singular as I do not have a strong preference on this. I will study more and reply later on.46.198.215.34 (talk) 13:09, 7 March 2018 (UTC)[reply]

You misunderstood my point 2 about singular versus plural. {{Article page template/display}} won't exist either. (I, in fact, prefer plural). {{3x|p}}ery (talk) 19:57, 7 March 2018 (UTC)[reply]

{{User sandbox+/create page/from library}} should be part of the {{Article page templates}} family, because it is used on what will be {{Article page templates/libraries/Article template library}}.

{{Article page templates/libraries/Article template library}} is the most tautological name I have ever seen. Prune it to {{Article page templates/libraries/main}} at least, likewise moving up {{Article page templates/libraries/create/matrix}} up one level to {{Article page templates/libraries/preload}} ("preload" name for consistency with all the other templates with similar purpose)

{{Article page templates/user custom/display available}} should be moved up one level to {{Template:Article page templates/list}}, because it also lists the standard templates. {{3x|p}}ery (talk) 20:15, 7 March 2018 (UTC)[reply]

Yes, I was in a hurry this morning and I missed point 2.

I can overcome tautology by using a special label I need to show for main library, instead of the last part of the page name, which is to be used for the rest of the libraries.
G8 issue derives from Editnotice issue, as the solution I proposed was to add one more part to the name of the page, to be excluded from editnotice. But this is one more hack. As editnotice is meant to be only for page templates, Is there an acceptable way to exclude the rest of the pages from receiving it on their edit?
Matrix is indeed funny, I will switch back to preload.

Thanks once again Pppery. ManosHacker ^talk 21:33, 7 March 2018 (UTC)[reply]

Redo the subst method; discard the editnotices and replace {{safesubst:...}} with {{«name here»|...}}, using a template that I just created in {{X1}}, which expands to a substitution of itself in template namespace and in all other namespaces expands to a substitution of the template specified in its arguments in other namespaces. {{3x|p}}ery (talk) 22:04, 7 March 2018 (UTC)[reply]
Other templates, like {{Submit an edit request/preload}} have subst in preload without needing to manually escape it every time. {{3x|p}}ery (talk) 22:34, 7 March 2018 (UTC)[reply]

A mother template (matrix) generates other preloads (article page templates) for creating articles. In mother templates  is used to preserve the code and is asked to be removed while saving an article page template based on it, starting a delayed safesubst. I will give the proposed code a try to see its behavior. ManosHacker ^talk 12:44, 8 March 2018 (UTC)[reply]

Pppery your last proposal is a saver, it works fantastic. Delay safesubst is not needed, nor the editnotices. I begin restructure. ManosHacker ^talk 13:10, 8 March 2018 (UTC)[reply]

Nor the "template talk" pages. {{3x|p}}ery (talk) 15:58, 8 March 2018 (UTC)[reply]