Tickets? We dont need no steenkin tickets!

Winds of Change

Good news!

Paradox over at TrinityCore is taking a look at the changes I requested. Hopefully, he will approve them and add them to patchqueue. Once they are accepted, develoment of the ticket system in TrinityAdmin will continue.

r5 committed, hilarity ensues

Just committed r5, after almost 12 hours of work on TA today. Here's what got done:
- Miscellaneous bug fixes (nothing major)
- Commenced restructuring of the code in a more modular arrangement
- Moved GOb buttons to GOb tab
- Fixed grid navigate. Now that it works properly, I will keep it.
- Fixed model rotate bug
- found and fixed a LOT of non-localised strings. Everything will be localised.

Notes:
TrinityAdmin's code had got to be quite a mess. It was getting difficult and very time consuming to find a partiular section of code to work on it. Adding new functions was dreaded because it took so... damned... long...
So, I decided this morning to re-structure the source code files in a more logical fashion.
TrinityAdmin.lua - Will contain only code for making the app as a whole function
Locales/xxXX.lua - Will still be the localisation for particular languages
Frames/MangFrames_TabName.lua - Still contains code for drawing the controls
Commands/Commands_TabName.lua - Contains the functions needed by all controls on that tab
FunctionInit.lua - Now contains all the code relating to the tabs that needs to be executed at startup

So, what does this mean? Well, it make it EASY to add commands to TA now - Add 1 line to FunctionInit, add 1 function to the appropriate Commands file, add necessary strings to the localisation file(s), and draw the approipriate controls in the Frames. Well.. it *is* actually easier than it was before, believe me.

Once this restructing is complete, I hope to have some cooperation from the trinity devs (still nothing so far from Machiavelli), and I'll get Tickets pushed out the door.

Future: There will be more tabs:
WHO, a scrolling list of who is online with appropriate buttons for goname, namego, etc.
RPG, imagine wow's macros on steroids
PvP - A tab for controlling Arenas & BGs
EVENT - A tab for controlling game events

There will be more functions:
Currently, we have about 40% of the GM commands implemented. Naturally the goal is 100%.

Tell me what you want!

Grid Navigator

Thinking about getting rid of the Grid Navigator on the Main/GM tab. I never use it... do you? Does anyone care if I get rid of it, or do you use it?

Progress

Today, we have set in motion some requests to the Trinity Core Dev team for some alterations to the outputs of a couple of commands. These changes will enable TrinityAdmin to capture ticket info properly and will also support an upcoming *surprise* feature.

If the devs approve the changes and implement them, I can make the ticket system work as intended. Of course YOUR ability to use the ticket system would require you to be on a server produced after the changes are implemented *or* have access to your server's database to do a few SQL updates (to make an older core compatible). All but one of the changes I requested are SQL changes, so this would work. The other change relates to the command .go ticket #ticketnum, which currently seems to be broken (at least on my core it is). So in other words, if they fix the command and implement the SQL changes, those of you on older cores would be able to use all of the ticket system (by updating SQL) but not be able to .go ticket #ticketnum

Questions? Comments?

Workaround for non-enUS users?

Namida, over at the TrinityCore forums, has posted a workaround for non-enUS users:

If you have the game in non-usUS localization, you can use it in English :
-Choice English language for wow
-Or use it with your client, but you have to modify some files in TrinityAdmin : For example with French client

• \TrinityAdmin.toc : delete the line concerning your localization (for French example : delete Locales\frFR.lua
• \TrinityAdmin.lua : delete the 3 lineS concerning your localisation (Locale:RegisterTranslations("frFR", function() return Return_frFR() [line 140] end) AND Strings:RegisterTranslations("frFR", function() return ReturnStrings_frFR() end) [line 158] and {"French","frFR"}, [line 2846])
• In \Locales\ : delete your localisation file (frFr.lua)

And now you can use trinityadmin with your French client (but it will be in English)
The third way is to translate all the files...good luck


iotech : thanks for your tool ;)

__________________

Default Sig, click here to change your sig if you are logged in

Thanks, Namida!!! Please note: I have no idea if this works or not, and if you do the above workaround, it *may* break the addon even worse! 

Welcome to the new TrinityAdmin Blog!

Well, the move is comlete. All the source code is at the new Google Code site, the discussion groups are up (although I am not impressed with them) and the blog is.. well, it's right here.

Hang on, the fun starts now.