Difference between revisions of "User:Atari2600tim"

From Mudlet
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
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.
 
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)
 
;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.
 
: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==
 
==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>
 
<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>
 +
 +
 +
==construction==
 +
<div class="version-block"><span class="version-image">👷</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.
 
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.
+
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.  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.   
+
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.   
  
  
−
==debugc==
+
==debugc with fake new arg colored==
 
;debugc(content<span class="version-label" style="color:red">, stdout</span>)
 
;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.
 
: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 78: Line 84:
  
 
{{note}} Basic idea of color coding for adding functionality to existing content
 
{{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>
 +
 +
 +
 +
 +
 +
==debugc with fake new arg and tagged additions==
 +
;debugc(content <span class="version-label" style="border-style:solid;border-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.
 +
 +
* stdout<span class="version-label" style="border-style:solid;border-color:red">👷 currently only in [[Main Page|Public Test Build]].</span>
 +
:if true then the error message will also be dumped to standard output
 +
 +
: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.  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">

Latest revision as of 16:54, 21 March 2023

Tim works on The Eternal Fantasy and 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 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.
See also: Errors View
Mudlet VersionAvailable in Mudlet1.0+

Note 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. 

debugc(" Trigger successful!")
-- Text will be shown in errors view, not to main window.

redInRed

Mudlet VersionAvailable in Mudlet Public Test Build


redBox

Mudlet VersionAvailable in Mudlet Public Test Build


redText

Mudlet VersionAvailable in Mudlet Public Test Build

PTBicon

Mudlet VersionAvailable in Mudlet Public Test Build

link

Mudlet VersionAvailable in Mudlet Public Test Build

explain

Mudlet VersionThis will be introduced in a future release of Mudlet and is currently in the Public Test Build

explain2

Mudlet VersionThis is currently under development, help out by using the Public Test Build

explain3

Mudlet VersionThis is currently under development, feedback welcome on the Public Test Build

explain4

Mudlet VersionThis is in the Public Test Build, feedback is wanted prior to upcoming release.


construction

👷This is in the Public Test Build, feedback is wanted prior to upcoming release.


Other ideas

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. 👷

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.


debugc with fake new arg colored

debugc(content, stdout)
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.
  • stdout
if true then the error message will also be dumped to standard output
See also: Errors View
Mudlet VersionAvailable in Mudlet1.0+
Mudlet VersionSome parts only available in Mudlet Public Test Build

Note Note: Basic idea of color coding for adding functionality to existing content 

debugc(" Trigger successful!")
-- Text will be shown in errors view, not to main window.



debugc with fake new arg and tagged additions

debugc(content 👷, stdout)
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.
if true then the error message will also be dumped to standard output
See also: Errors View
Mudlet VersionAvailable in Mudlet1.0+
Mudlet VersionSome parts only available in Mudlet Public Test Build

Note 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. 

debugc(" Trigger successful!")
-- Text will be shown in errors view, not to main window.



sample with text lighter color

debugc(content , stdout)
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.
  • stdout Mudlet Version Not in current release; only available in Mudlet Public Test Build
if true then the error message will also be dumped to standard output
See also: Errors View
Mudlet VersionAvailable in Mudlet1.0+

Note Note: Basic concept of just color. The gray would turn black upon release. 

debugc(" Trigger successful!")
-- Text will be shown in errors view, not to main window.
Retrieved from "https://wiki.mudlet.org/index.php?title=User:Atari2600tim&oldid=20390"