oUF dLx

Since this is a plugin for oUF, you absolutely NEED to get oUF.
Frames support moving through oUF_MoveableFrames.

Introduction
I play a rogue and keep the minimap to the left of the unit frames and a bunch of buttons below the player frame so I can easily see the cooldowns. Here's a link to show you how it looks. :P
What isn't shown here is that above the player and target frames, a Quartz bar pops up with the corresponding cast timer.

Please note that this oUF style does NOT contain any action bars. The screenshots have plenty of buttons visible, all placed there by the Dominos addon. Have a look in vars.lua if you wish to make changes to how this style looks.

Frames

Player

Pet / vehicle

Target

Target of target

Focus

(Party if you enable in vars.lua)

Features
Race abbreviation, creature type display, difficulty coloring, raid group number (yum!) and probably a whole lot more I just can't remember. Most of this is scavenged from the now discontinued Discord Unit Frames addon! <3
Limited user control! (read the following section)

vars.lua
vars.lua contains a number of settings you can change to make these unit frames slightly more personal.
All the settings have a comment to explain just what it does. If you make changes and there's an update, you have two options. A) Remake those changes in the new vars.lua or B) Don't overwrite your vars.lua, but make sure all new options are added to your own one, either with standard values or your preferred values. The A-method is a lot safer.

If you have any ideas, bugs to report or requests to make, post a comment.
Thank you.

2010-01-01
- TOC bump
- Added support for oUF_MoveableFrames (install and use /mvf)

2009-01-26
- Power bar background is lightly coloured by class
- Seems to work just fine with oUF 1.3.3

2009-01-20
- Added a pet happiness icon

2009-01-01
- Added combatGlow to vars.lua - Check it out!

2008-12-26
- Should work fine with the new oUF framework (1.3.1) now

2008-12-17
- All unit frames now have their own coordinates in vars.lua
- healthCritical added to vars.lua
- Added frame names. You can now move the frames with addons such as "Visor2" or "MoveAnything"
- Removed xpos, ypos and xOffset from vars.lua

All I can say is that I've witnessed similar behavior in PerfectRaid which I used as a party frame replacement for a bit. It did the same thing you describe when I was in arenas. It also set a couple of units to display my own info rather than the unit they SHOULD display, making it utterly useful.

However, this does not help you, and I'm afraid I can't either as I'm quite happy using Grid for party frames now. I'm sorry.

There is something weird going on with the party frames. I haven't been using them until now and I'm now noticing some strange stuff.

Let me preface this with the fact that I removed all addons and deleted my wtf folder... then loaded ouf_core and ouf_dLx. No other addons were loaded during this test and I'm seeing the same results.

1. If I'm in a raid, one of my party members is shown, but all of the others are not shown. I'm not sure if the party unit frames are supposed to be shown in a raid or not... but the fact that only one person in my party is shown can't be right. I typically turn off party frames (set to false) during raids so I don't see this anomaly.

2. The reason I started using the party frames was because I just started doing arenas and I want to use them to view my partner. For some reason my partner (party frame) disappears when we step into the arena.

I'm guessing that there is some conflict with the blizzard unit frames or at least it appears that way.

Is anyone else using these party frames having the same issues? I'm trying to isolate the problem and have hit a dead end. I'm not that familiar with Lua code or how it interfaces with the game client, so any help would be greatly appreciated.

I love these unit frames, so I would hate to ditch them for this little glitch.

Great Addon... the best oUF Layout IMO! Very easy to configure for someone who doesn't know how to program .lua

The code is simple and easy to understand. All of the base information is there (pvp icon, player name, level, mob type, buff, debuffs, etc); all I had to do was move and resize some items to fit my needs/preferences.

The only thing... strictly cosmetic... is there is no background for the party unit frames... but really... it doesn't even matter... everything works and looks great... with very little memory usage.

Originally posted by p3lim Just a suggestion:
Use a savedvariable database instead of a huge amount of global vars, along with a good handler.
That way people can still have their settings saved when they update the addon, new settings are added (as default values) and they can also change the settings ingame.

Sometime in the beginning of next year im gonna make a GUI based layout, with alot of configs that are changed ingame.
This might make oUF more approachable to new users, and make it a more famous addon, in some way.

Early statement though, dont get your hopes up, as im not designing it for myself, and it will get a low priority on my list of tasks.

Global or local variables, as you should know, makes absolutely no difference. Using "savedvariables" only stores them in another location, so not only can that be safely disregarded, what you're suggesting would only add needless complexity in my opinion. In addition, it's stored under the dLx table, and further more under an oUF table in that, and only a specific subset of values at that, albeit a subset that increases as users make requests. Bottom line; it's far from a "huge amount", and the risk for collision virtually is non-existent if that was your main concern. I'd love to localize them, but I'd have to stick them in the main lua file, and that would complicate things for users.

As for a config UI, you should realize (and you probably do) that an oUF config UI is pretty global to begin with. Frames are accessible via oUF.units and so forth, you know that, so positioning through a stand-alone config addon is definitely possible, and furthermore it's something most layouts would benefit from. I was writing a config addon for this purpose, but stopped because quite frankly I don't have any use for it whatsoever.

Anyway, I'm not REALLY doing this addon for the broad masses, I only add variables to my vars.lua semi-hack because people ask for it, and even so I only do it when it's not too much hassle and I'm already mucking around with other stuff anyway.

I certainly hope the users are content with this solution, I know it works just fine for me. Actually checking for missing variables also adds both workload for me and adds "weight" to the addon. I do not believe the tradeoff is worth it.

Just a suggestion:
Use a savedvariable database instead of a huge amount of global vars, along with a good handler.
That way people can still have their settings saved when they update the addon, new settings are added (as default values) and they can also change the settings ingame.

Sometime in the beginning of next year im gonna make a GUI based layout, with alot of configs that are changed ingame.
This might make oUF more approachable to new users, and make it a more famous addon, in some way.

Early statement though, dont get your hopes up, as im not designing it for myself, and it will get a low priority on my list of tasks.

Originally posted by Rintrah Is there any simple way to modify the vars file to add a yOffset, so that I can put the target frame under my player frame? (Rather than to the right)

I'd also be interested in removing the black space for buff/debuff under the target frame (like the option you added in vars to do so to the player frame).

Its a great UF, I'm just having trouble setting it up the way I like!

For now the black spaces are probably the easiest things to modify. :P
At the very end of layout.lua there's a block of lines where the frames are spawned. Look up a bit till you find "local tBG = addBG(target, 57)"
That number is what you want to change. If you remove the number entirely so the line reads "local tBG = addBG(target)" it will default to the minimum height required to fit the target frame, much like you see if you look at the totBG and focusBG lines.

Grimman, p3lim wasn't trying order you to do something. I thought the same as you initially did. He is simply being professional about his suggestion. His statement below should be re-read with that in mind.

As a wow player, that doesn't happen often enough to be an easily recognizable trait in text.

He is himself an oUF Layout designer, and I'm sure his suggestion was purely to help you build a better addon.

Originally posted by grimman The background boxes? They slipped my mind.
Now, as for you, there are ways of asking for things (AND including details! *gasp*) without giving direct orders. I kindly suggest you find a way to do so.

Im not giving orders, im suggesting.
Neither am I asking, as im not using this plugin.