YATCO
Posted: Thu Dec 27, 2012 3:29 pm
YATCO is still a working product, but has been replaced by EMCO viewtopic.php?f=6&t=22797 in terms of receiving improved functionality and updates. YATCO will still place a tabbed chat in the corner of your choice, but EMCO provides further styling options, better embedding in existing Geyser UIs, and the added bonus of future updates.
YATCO has been updated to 2.5
Please report issues on GitHub
You should head over to YATCO's github page HERE for more information on YATCO.
Quick Start, for version 2.5
Install base config package.
2.5 adds Map display options. demonnic.chat.config.Maptab defaults to "", if you set it to the same name as one of the tabs in your tablist, it will create a Geyser mapper object in that tab. Leave it as "" in order ignore this functionality.
I also added demonnic.chat.useContainer , which you set to the Geyser container you want YATCO to be contained in. So if you have a container you created with
OLDER INFO KEPT BELOW
UPDATE: Bumped to 2.4. New download link HERE
Also, you should be able to install using the following in your mudlet inputbar:
I am starting a new thread, since this version is significantly different from the one I posted to this forum last and the redirection at the top of the last post points to an outside forum. If you're using one of the versions of tabbed chat I wrote which makes use of geyser (all the 2.x ones) then using this should be about the same. If you're on 2.2, the only real changes are I added an alias to fix the blackbox issue on the chats, and I stripped out some leftover kruft from Lusternia, did not need any GMCP handlers in a mud agnostic tabbed chat widget. Scroll to the bottom for the configuration options, but since it's really just a copy/paste job from the configuration options in the script package itself, you almost may as well just go edit it. =)
You can download the xml HERE
I provided an example trigger to send something to the "Org" tab. Simply call demonnic.chat:append("Tabname") to send the line you've triggered upon to the Tabname tab. This is case sensitive, "tabname" is not the same as "Tabname"
There are currently 2 aliases provided with this.
dblink:
turns the blinking on or off. Temporary toggle, to make permanent change the configuration option in the script editor.
fixchat:
In 2.0test5 through 7 there is a slight issue with miniconsoles. If you are using one of the predefined locations for the chat tabs (topright, topleft, bottomright, bottomleft) then running this alias sets the tabbed chat to the opposite corner, redraws the it, then sets it back to where it was before and redraws it again. In my experience this removes the blackbox over the top of the chat console every time. There is a fix for this in git but not yet released. Once it is released this alias will no longer be necessary.
YATCO has been updated to 2.5
Please report issues on GitHub
You should head over to YATCO's github page HERE for more information on YATCO.
Quick Start, for version 2.5
Install base config package.
once you've installed this, go over the configuration options and set the name of the tabs, etc. Then once you're ready to start up YATCO itself, install the code package. This is for 2.5.
This will startup the actual tabbed chat using the configs you edited. From this point forward you should be able to just uninstall YATCO and install the new version to pick up any code fixes, etc. I will add additional packages for bringing yourself up to date with configuration options which are added post 2.5.
2.5 adds Map display options. demonnic.chat.config.Maptab defaults to "", if you set it to the same name as one of the tabs in your tablist, it will create a Geyser mapper object in that tab. Leave it as "" in order ignore this functionality.
I also added demonnic.chat.useContainer , which you set to the Geyser container you want YATCO to be contained in. So if you have a container you created with
Then you would do
Leave it set to false if you don't want to add YATCO to some other container. This way YATCO will be easier to incorporate into other UI projects. It should be noted that if you stuff YATCO into another container, it will be at x=0, y=0 and both height and width will be 100% of this container. Then to hide or show all of YATCO you can hide or show the container. In the example, uiRight:hide() and uiRight:show(). This also means that the height and width of the chat boxes will be determined by the container you place them in, and not YATCO. This could mean you'll need to adjust your demonnic.chat.config.width until the text wraps properly. I intend to make this autodetect and work itself out in the future, but haven't gotten it in place yet.
OLDER INFO KEPT BELOW
UPDATE: Bumped to 2.4. New download link HERE
Also, you should be able to install using the following in your mudlet inputbar:
Please report issues on GitHub
I am starting a new thread, since this version is significantly different from the one I posted to this forum last and the redirection at the top of the last post points to an outside forum. If you're using one of the versions of tabbed chat I wrote which makes use of geyser (all the 2.x ones) then using this should be about the same. If you're on 2.2, the only real changes are I added an alias to fix the blackbox issue on the chats, and I stripped out some leftover kruft from Lusternia, did not need any GMCP handlers in a mud agnostic tabbed chat widget. Scroll to the bottom for the configuration options, but since it's really just a copy/paste job from the configuration options in the script package itself, you almost may as well just go edit it. =)
You can download the xml HERE
I provided an example trigger to send something to the "Org" tab. Simply call demonnic.chat:append("Tabname") to send the line you've triggered upon to the Tabname tab. This is case sensitive, "tabname" is not the same as "Tabname"
There are currently 2 aliases provided with this.
dblink:
turns the blinking on or off. Temporary toggle, to make permanent change the configuration option in the script editor.
fixchat:
In 2.0test5 through 7 there is a slight issue with miniconsoles. If you are using one of the predefined locations for the chat tabs (topright, topleft, bottomright, bottomleft) then running this alias sets the tabbed chat to the opposite corner, redraws the it, then sets it back to where it was before and redraws it again. In my experience this removes the blackbox over the top of the chat console every time. There is a fix for this in git but not yet released. Once it is released this alias will no longer be necessary.
To show the difference between preserveBackground true/false... top is false, bottom is true.