Φ wowmods - xFont @ ?
[ addon updates | search | RSS | Google: subscribed link (?); Gadget | Twitter ]
[ login | register ] [ contact ]
search addons:

 • details
addon: xFont
listed author: phrozenassid   [list all addons]
latest version: v1.1.0
date last updated: Mon, 08 Feb 2010 02:56:55 +0000
date added: Sat, 23 Jan 2010 22:50:06 +0000
 
wowinterface.com: http://www.wowinterface.com/downloads/info15778-v1.1.0.html

 • about + changelog
Change Log:






v 1.1.0

-- Re-wrote some of the SetFont function.

-- Re-wrote the way Zone Fonts are now handled. (Use the same syntax as the rest of the code).

-- Added some commenting so users with less LUA experience could more easily configure the code and cleaned up the code.



v 1.0.1

-- Original Release



Description:






xFont

Complete LUA based font reskin at < 5kb of memory!



There is NO GUI configuration as GUIs use excess memory. There is some LUA commenting now to help users out who are generally unfamiliar with LUA.



Description: So I used to be a big ClearFont2 user and decided that I wanted an updated way to configure my fonts. Basically it is a VERY stripped down version of ClearFont2 with added in features from tekticles and aZoneText with all the GUIs and in-game configs completely removed. I know there are lots of similar addons but I kinda just decided to release it because there is no other addon that does EXACTLY what this does for as small a memory footprint.



Description shortened. It's just a self-contained LUA based font changer, nothing more, nothing less.





Future Updates:

For 99% of usable purposes this addon has no problems and works as it should. I have been using it for months now. That said I really don't see a whole lot of need to ever update it unless there is a SEVERE error that occurs (which I really don't forsee). It works and is simple and I see no reason to clutter up the code.





Known Issues:

The one error about the territory text showing up as not the zone text style, but using the font specified as "standard" I am aware of. It just simply requires alot of code to fix one minor problem that only occasionally even occurs. For the time being I have no plans to write in code to fix this for every PVP territory in the game. This would just increase the size and memory consumption of the addon and I find that this code is ultimately counter-productive.

 
Hint: see addon details for related searches in Google: use the Google Subscribed Links service.