User:Atari2600tim - Revision history

Atari2600tim: /* Other ideas */

2023-03-21T16:54:59Z

Other ideas

Atari2600tim at 16:50, 21 March 2023

2023-03-21T16:50:29Z

Atari2600tim: /* Other ideas */

2023-03-21T16:39:31Z

Other ideas

Atari2600tim: /* Other ideas */

2023-03-21T14:46:33Z

Other ideas

Atari2600tim: /* Other ideas */

2023-03-21T14:37:11Z

Other ideas

Atari2600tim at 14:33, 21 March 2023

2023-03-21T14:33:29Z

Atari2600tim: Initial personal page

2020-10-12T18:26:08Z

Initial personal page

New page

Tim works on [https://www.eternalfantasy.org The Eternal Fantasy] and [https://www.timmud.com TimMUD] and lurks on the Discord, offering help on things that he barely knows anything about but has seen discussion of.

@@ Line 62: / Line 62: @@
 Construction hat or something like that might be more obvious. 👷
-I picked an existing link for demo but would be good to have a page like [[Public Test Build]] with [[PTB]] being a redirect alias to it, and the page would have explanation of how you can do conditions in your UI, how to do if X then X() end or use mudletOlderThan and so on.
+I picked an existing link for demo but would be good to have a page like [[Public Test Build]] with [[PTB]] being a redirect alias to it, and the page would have explanation of how you can do conditions in your UI, how to do if X then X() end or use mudletOlderThan and so on.  It would explain basic concept that it is the current development branch and built daily.
 On the Discord there was idea of dimming the text itself.  I have not yet searched for examples of how to accomplish it properly with templates.  Everything here is spans for the moment.

← Older revision		Revision as of 16:50, 21 March 2023
Line 111:		Line 111:

	{{note}} Basic idea of color coding for adding functionality to existing content. This example I tagged parts and had a general note, probably would want to pick one or the other instead of having both. Maybe one template for the main line that disappears upon release, and separate template for the "currently only..." one, which turns into version tag.		{{note}} Basic idea of color coding for adding functionality to existing content. This example I tagged parts and had a general note, probably would want to pick one or the other instead of having both. Maybe one template for the main line that disappears upon release, and separate template for the "currently only..." one, which turns into version tag.
		+
		+	<syntaxhighlight lang="lua">
		+	debugc(" Trigger successful!")
		+	-- Text will be shown in errors view, not to main window.
		+	</syntaxhighlight>
		+
		+
		+
		+
		+	==sample with text lighter color==
		+	;debugc(content <span class="version-label" style="color:gray">, stdout</span>)
		+	:Again this will not send anything to anywhere. It will however print not to the main window, but only to the errors view. You need to open that window to see the message.
		+
		+	;Parameters
		+	* ''content''
		+	:Message to print.
		+
		+	* <span style="color:gray">stdout</span> <span class="version-label" style="color:gray;border-style:solid;border-color:gray;">[[File:Mudlet PTB 1024px.png\|18px\|Mudlet Version\|link=]] Not in current release; only available in Mudlet Public Test Build</span>
		+	:<span style="color:gray">if true then the error message will also be dumped to standard output</span>
		+
		+	:See also: [[Manual:Introduction#Runtime_errors_aka_Errors_View\|Errors View]]
		+
		+	{{MudletVersion\|1.0}}
		+
		+	{{note}} Basic concept of just color. The gray would turn black upon release.

	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">

@@ Line 7: / Line 7: @@
 This section is to show off some ideas regarding version tags.  Currently we move things from Area 51 to the target page on release day.  This means that release day has lots of edits.  Copy from Area 51, paste to target destination.  If you're updating an existing function, then you need to incorporate any edits that were made to the canon page that happened after the fork to Area 51.  Seems like it'll be easier to have things go onto the canonical page once they are accepted into the Public Test Builds.  Release day, changing every instance of MudletPTB to MudletVersion|1.0 would be simpler plus allow PTB users to look at documentation without it all being on Area51.
-==debugc==
+==debugc original==
 ;debugc(content)
 :Again this will not send anything to anywhere. It will however print not to the main window, but only to the errors view. You need to open that window to see the message.
@@ Line 51: / Line 51: @@
 ==explain4==
 <div class="version-block"><span class="version-image">[[File:Mudlet PTB 1024px.png|18px|Mudlet Version|link=]]</span><span class="version-label">This is in the [https://make.mudlet.org/snapshots/?platform=all&source=ptb Public Test Build], [https://github.com/Mudlet/Mudlet/issues/new feedback is wanted] prior to upcoming release.</span></div>
@@ Line 56: / Line 60: @@
 The colors I did so far look like dangerous warnings.  Maybe a color themed with the PTB icon would be better.
-Construction hat or something like that might be more obvious.
+Construction hat or something like that might be more obvious. 👷
 I picked an existing link for demo but would be good to have a page like [[Public Test Build]] with [[PTB]] being a redirect alias to it, and the page would have explanation of how you can do conditions in your UI, how to do if X then X() end or use mudletOlderThan and so on.
@@ Line 63: / Line 67: @@
-==debugc==
+==debugc with fake new arg colored==
 ;debugc(content<span class="version-label" style="color:red">, stdout</span>)
 :Again this will not send anything to anywhere. It will however print not to the main window, but only to the errors view. You need to open that window to see the message.
@@ Line 80: / Line 84: @@
 {{note}} Basic idea of color coding for adding functionality to existing content
 <syntaxhighlight lang="lua">

@@ Line 55: / Line 55: @@
 =Other ideas=
 The colors I did so far look like dangerous warnings.  Maybe a color themed with the PTB icon would be better.
 I picked an existing link for demo but would be good to have a page like [[Public Test Build]] with [[PTB]] being a redirect alias to it, and the page would have explanation of how you can do conditions in your UI, how to do if X then X() end or use mudletOlderThan and so on.

← Older revision		Revision as of 14:37, 21 March 2023
Line 58:		Line 58:
	I picked an existing link for demo but would be good to have a page like [[Public Test Build]] with [[PTB]] being a redirect alias to it, and the page would have explanation of how you can do conditions in your UI, how to do if X then X() end or use mudletOlderThan and so on.		I picked an existing link for demo but would be good to have a page like [[Public Test Build]] with [[PTB]] being a redirect alias to it, and the page would have explanation of how you can do conditions in your UI, how to do if X then X() end or use mudletOlderThan and so on.

−	On the Discord there was idea of dimming the text itself. I have not yet searched for examples of how to accomplish it.	+	On the Discord there was idea of dimming the text itself. I have not yet searched for examples of how to accomplish it properly with templates. Everything here is spans for the moment.

← Older revision		Revision as of 14:33, 21 March 2023
Line 1:		Line 1:
−	Tim works on [https://www.eternalfantasy.org The Eternal Fantasy] and [https://www.timmud.com TimMUD] and lurks on the Discord, offering help on things that he barely knows anything about but has seen discussion of.	+	Tim works on [https://www.eternalfantasy.org The Eternal Fantasy] and [https://www.timmud.com TimMUD] and lurks on the Discord, offering help on things that he barely knows anything about but has at least seen discussion of. In spite of his answers coming from searches of earlier discussion, he often can pass for a human.
		+
		+
		+
		+
		+	= Public Test Build tags =
		+	This section is to show off some ideas regarding version tags. Currently we move things from Area 51 to the target page on release day. This means that release day has lots of edits. Copy from Area 51, paste to target destination. If you're updating an existing function, then you need to incorporate any edits that were made to the canon page that happened after the fork to Area 51. Seems like it'll be easier to have things go onto the canonical page once they are accepted into the Public Test Builds. Release day, changing every instance of MudletPTB to MudletVersion\|1.0 would be simpler plus allow PTB users to look at documentation without it all being on Area51.
		+
		+	==debugc==
		+	;debugc(content)
		+	:Again this will not send anything to anywhere. It will however print not to the main window, but only to the errors view. You need to open that window to see the message.
		+
		+	:See also: [[Manual:Introduction#Runtime_errors_aka_Errors_View\|Errors View]]
		+
		+	{{MudletVersion\|1.0}}
		+
		+	{{note}} I just copied and pasted this... the "Again" stuff... I think this came from a tutorial and wasn't adjusted for wiki. Come back to this later, for now I just am showing example of tag for something that is currently in program.
		+
		+	<syntaxhighlight lang="lua">
		+	debugc(" Trigger successful!")
		+	-- Text will be shown in errors view, not to main window.
		+	</syntaxhighlight>
		+
		+	==redInRed==
		+	<div class="version-block"><span class="version-image">[[File:MudletIcon_256px.png\|18px\|Mudlet Version\|link=]]</span><span class="version-label" style="color:red;border-style:solid;border-color:red;background-color:lightred;">Available in Mudlet Public Test Build</span></div>
		+
		+
		+	==redBox==
		+	<div class="version-block"><span class="version-image">[[File:MudletIcon_256px.png\|18px\|Mudlet Version\|link=]]</span><span class="version-label" style="border-style:solid;border-color:red;background-color:lightred;">Available in Mudlet Public Test Build</span></div>
		+
		+
		+
		+	==redText==
		+	<div class="version-block"><span class="version-image">[[File:MudletIcon_256px.png\|18px\|Mudlet Version\|link=]]</span><span class="version-label" style="color:red;background-color:lightred;">Available in Mudlet Public Test Build</span></div>
		+
		+	==PTBicon==
		+	<div class="version-block"><span class="version-image">[[File:Mudlet PTB 1024px.png\|18px\|Mudlet Version\|link=]]</span><span class="version-label">Available in Mudlet Public Test Build</span></div>
		+
		+	==link==
		+	<div class="version-block"><span class="version-image">[[File:Mudlet PTB 1024px.png\|18px\|Mudlet Version\|link=]]</span><span class="version-label">Available in Mudlet [[Main Page\|Public Test Build]]</span></div>
		+
		+	==explain==
		+	<div class="version-block"><span class="version-image">[[File:Mudlet PTB 1024px.png\|18px\|Mudlet Version\|link=]]</span><span class="version-label">This will be introduced in a future release of Mudlet and is currently in the [[Main Page\|Public Test Build]]</span></div>
		+
		+	==explain2==
		+	<div class="version-block"><span class="version-image">[[File:Mudlet PTB 1024px.png\|18px\|Mudlet Version\|link=]]</span><span class="version-label">This is currently under development, help out by using the [https://make.mudlet.org/snapshots/?platform=all&source=ptb Public Test Build]</span></div>
		+
		+	==explain3==
		+	<div class="version-block"><span class="version-image">[[File:Mudlet PTB 1024px.png\|18px\|Mudlet Version\|link=]]</span><span class="version-label">This is currently under development, [https://github.com/Mudlet/Mudlet/issues/new feedback welcome] on the [https://make.mudlet.org/snapshots/?platform=all&source=ptb Public Test Build]</span></div>
		+
		+	==explain4==
		+	<div class="version-block"><span class="version-image">[[File:Mudlet PTB 1024px.png\|18px\|Mudlet Version\|link=]]</span><span class="version-label">This is in the [https://make.mudlet.org/snapshots/?platform=all&source=ptb Public Test Build], [https://github.com/Mudlet/Mudlet/issues/new feedback is wanted] prior to upcoming release.</span></div>
		+
		+
		+	=Other ideas=
		+	The colors I did so far look like dangerous warnings. Maybe a color themed with the PTB icon would be better.
		+
		+	I picked an existing link for demo but would be good to have a page like [[Public Test Build]] with [[PTB]] being a redirect alias to it, and the page would have explanation of how you can do conditions in your UI, how to do if X then X() end or use mudletOlderThan and so on.
		+
		+	On the Discord there was idea of dimming the text itself. I have not yet searched for examples of how to accomplish it.
		+
		+
		+	==debugc==
		+	;debugc(content<span class="version-label" style="color:red">, stdout</span>)
		+	:Again this will not send anything to anywhere. It will however print not to the main window, but only to the errors view. You need to open that window to see the message.
		+
		+	;Parameters
		+	* ''content''
		+	:Message to print.
		+
		+	* <span class="version-label" style="color:red">stdout</span>
		+	:<span class="version-label" style="color:red">if true then the error message will also be dumped to standard output</span>
		+
		+	:See also: [[Manual:Introduction#Runtime_errors_aka_Errors_View\|Errors View]]
		+
		+	{{MudletVersion\|1.0}}
		+	<div class="version-block"><span class="version-image">[[File:Mudlet PTB 1024px.png\|18px\|Mudlet Version\|link=]]</span><span class="version-label" style="color:red;background-color:lightred;">Some parts only available in Mudlet Public Test Build</span></div>
		+
		+	{{note}} Basic idea of color coding for adding functionality to existing content
		+
		+	<syntaxhighlight lang="lua">
		+	debugc(" Trigger successful!")
		+	-- Text will be shown in errors view, not to main window.
		+	</syntaxhighlight>