Post Fri May 10, 2013 5:08 pm

TIBWIDGET - UNDERSTANDING TIB MENU STRUCTURE

Aka How to make TIB modules and skins - Part 1


TIB - OVERVIEW
TIB - UNDERSTANDING TIB MENU STRUCTURE
TIB - INSTALLATION AND CONFIGURATION GUIDE

___________________________

In order to make TIB universal and able to load other modules built by other users, we need to define some standards.
So, let's take a look at TIB structure and its functional design.


\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\ TIBWIDGET Menu \\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

Image
TIB Light MCP



TEMPLATES
________________

If we use our own Custom Template, every aspect of the design can be costumized. So, we're free to build it as we like using any button positions and sizes.

If we use the default TIB Templates, we should use the next image as reference. We'll be designing over a 4x9 grid with 34x34 button size.

TIBSKIN-Original size is 136x350px.
TIBSKIN-Light size is 136x316px.


ImageImage



BUTTON SETS
________________

The MCP has a main 31 Button Set (TIBWIDGET).

(This is where we should keep things uniform)

It's dividec into GSlot and MCPGlobal.


GSlot

GSlot is a group composed by the first 12 Buttons. GSlot will be loaded with the active GPage.

A GPage is a 12 Button Set (It can be your action Bar, for example). Our GPages are TIB-GK1, TIB-GK2, TIB-GK3, TIB-GK4 and TIB-GK9.


MCP Global Buttons

(This is mandatory to be considered TIB official)

Top row has 2 buttons: GPage UP/DOWN. They MUST be Button 13 and 14 of TIBWIDGET Button Set.
Button 31 is the Logo Button (ISBoxer and TIB). It also captues a screenshot.

(I really like to keep the following purposes on the next ones)

Buttons 15 and 17 are Bank Up/Down.
Button 19 loads the Matrix, Button 20 loads the Action Rack.

All the other 12 buttons (16,18, 21..24, 25, 26, 27..30) are free. We can program them to do whatever we want.


Image
TIB V1.1 comes with more buttons with new styles



HOTKEY SETS
________________

Hotkeys are set in the TIBWIDGET Hotkey Set.

If you want a specific GPage to a have different hotkeys, you need to create a Hotkey Set to that page and load it along with the Button Set (in the GPages Roller Mapped Key, inside TIBWIDGET Key Map).



\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\ TIB-MATRIX Menu \\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

Image


Matrix structures is very simple. Is a 5x6 grid menu. Each Matrix column is a Behaviour Set.

TIB-MATRIX Menu loads 2 Button Sets (WHO1 and WHO2) by default.

WHO1 is a Button Set with 3 Behaviours (WhoAOE, WhoSkull and WhoCC).
WHO2 is a Button Set with 2 Behaviours (WhoIWT and WhoFollow).

Matrix don't use hotkeys!



\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\ TIB-RACK Menu \\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

Image

TIB-Rack is a Menu with 29 (12+16+1) buttons.

It loads 2 Button Sets: TIB-COMBAT and TIB-EXTRA, with 12 and 17 buttons respectively.

TIB-COMBAT holds your Combat-DPS buttons.
TIB-EXTRA holds your other combat actions and utilities.

Button 17 of Extra Button Set is a special button named the EYE. It switches AOE/SingleTarget modes.

We set hotkeys to our Action Rack at TIB-COMBAT and TIB-EXTRA Hotkey Sets.


Important:

If a TIB custom module implements actions with Mapped Keys that are not part of the Default IB41 configuration, those Mapped Keys should be put inside the TIBWIDGET Key Map. Same with Macro Sets...

If the refered standards are met, I may consider to include user custom modules as part of the future releases of TIB.


\m/ TRoNDaNeflin \m/