Like I said, I’m ok with making the full table, or at least making the draft.
1 Like
Oh no, I’m not saying there’s no reason to make this, I’m saying we can save a lot of time looking for the names of every device by using the TUGTED’s.
1 Like
Plus, I am pretty sure there are more devices than back then.
Only a few more. TUGTED 3 is pretty recent.
Ok, I drafted a list. Fundamental devices are 1 Letter, and all others are 2.
I just realized both Text and Trigger are T, text is supposed to be Te.
2 Likes
Draft is above.
This is starting to become a repeat of the other notation systems…
1 Like
Teleporter is te, so text might be tx?
How about you can do some sort of check. Find and replace? See if there is more than one for abr. So if you are looking for T, do find “- T” like that.
And then make it so First letter is caps, second is caps.
I’m sure it is, but this time, it’ll be more organized. We’ve already got an idea of the direction we’re headed with the rows and columns.
Did nobody read my posts?
Is there a symbol for Run on channel ____ and broadcast on?
If not, I put forth
(!-> = "Channel")
For run on channel ___ and
(->! = “Channel”)
For broadcast on channel ___
A trigger loop would then look like this.
T ((!-> = “update”)(->! = “update”))
1 Like
Hey I got pinged
So because im too lazy to read 100 replies what’s the summary of what you guys have so far?
1 Like
How about
Device(settings) - connection type -
[Device(connected settings)],
[Device(connected settings)],
[Device(connected settings)]
Nothing solid at all.
Nothing much. We were trying to come up with abbreviations for all devices and then going to work from there but it kinda died off.
No text should be txt. Many systems already abbreviate text as txt. For example a text file. Txt would be the most obvious choice.