Xenharmonic Wiki talk:Conventions: Difference between revisions

← Older edit Newer edit →

VisualWikitext

@@ Line 6: / Line 6: @@
 :::Nope. The standard list model really is the most reliable. Ever heard of Internet Explorer 6? [[User:PiotrGrochowski|PiotrGrochowski]] ([[User talk:PiotrGrochowski|talk]]) 19:21, 30 September 2018 (UTC)
 : Absolutely yes (to Keenan): I love the "inoffical lists" and hate the <code><nowiki><ul><li></li></ul></nowiki></code> stuff. Why make it so complicated??? Wiki means fast. I don't see anythong faster than placing <code>*</code> at the beginning of the listed items. I'm not aware that this was being discussed somewhere. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 19:03, 30 September 2018 (UTC)
-:: The "FREEZE" thing was just me and Tyler playing with this until we got it to work. We never intended for these conventions to become standardized, it was just the easiest way to parse. [[User:Mike Battaglia|Mike Battaglia]] ([[User talk:Mike Battaglia|talk]]) 19:36, 30 September 2018 (UTC)
 === Informal poll ===
-In favor of Wikitext (*) lists (2): [[User:Keenan Pepper]], [[User:Xenwolf]], [[User:Mike_Battaglia]]
+In favor of Wikitext (*) lists (2): [[User:Keenan Pepper]], [[User:Xenwolf]]
 In favor of HTML-style (<nowiki><ul><li></nowiki>...) lists (1): [[User:PiotrGrochowski]]
@@ Line 16: / Line 15: @@
 In my opinion this would be contra-productive. Every wiki syntax aims to be as simple as possible ''and'' obvious also in the wiki text. You get the idea of markup's purpose easily. Ans it's easy to adapt for people new to the wiki ho to achieve a goal. It's normally not necessary to know HTML tags for editing wiki content. That's why lists should be created the wiki way (using <code>*</code> and <code>#</code>). <br/> --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 19:22, 30 September 2018 (UTC)
-: I will always make lists with the proper, canonical syntax. [[What languages do various users know?]] is my page, therefore it is very clean, using the standard list model. [[User:PiotrGrochowski|PiotrGrochowski]] ([[User talk:PiotrGrochowski|talk]]) 19:25, 30 September 2018 (UTC)
-:: No, we should not imitate "FREEZE artefacts." FREEZE artefacts are just things that I screwed up. We should make it right. [[User:Mike Battaglia|Mike Battaglia]] ([[User talk:Mike Battaglia|talk]]) 20:20, 30 September 2018 (UTC)
-== What is the "Xenharmonic Wiki" Namespace for? ==
+I'm going to agree with [[User:Xenwolf]] here. As a wiki author (as in, I've _written_ one of these), the''point'' of wiki syntax '''at all''' is to permit you to write pages quickly without having to actually write syntactically-valid HTML. If there was no utility to adding wiki markup, it wouldn't have ''been'' added at all, and we'd just be opening edit boxes to paste in HTML. Which we would all have to always get right. Which we mostly would not, and would then spend time dorking with instead of writing about tunings.
-When do we use this instead of making a regular page? [[User:Mike Battaglia|Mike Battaglia]] ([[User talk:Mike Battaglia|talk]]) 19:41, 30 September 2018 (UTC)
+Wiki list markup, which ''is'' implemented in this wiki, is there to allow you to concentrate on providing content. The [[FREEZE]] stuff was introduced because the person who wrote the conversion chose to just inline rendered lists instead of parsing and converting the markup. Insisting on working against the tool, i.e., the wiki,  by forcing HTML markup is counterproductive because it doesn't need to be done, and doing it is slower to write, and harder to update. And updating is the '''''point''''' of using a wiki at all.
-: It's for meta stuff that is not in the Help namespace. Pages that describe the project, pages that are not itself about microtonal or xenharmonic topics. Sometimes it's hard to decide if something is help-only or not. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 19:59, 30 September 2018 (UTC)
+[[FREEZE]] is not a standard. It was a programming shortcut; insisting that it's a reason to hardcode HTML smacks of "I want to do this so I'm finding a reason" not "there is no other way to do this so I've adopted this workaround". There is no need for a workaround. Use the tools. Unless the markup ''cannot be done'' with wiki markup, it should not be there.[[user:joemcmahon]]