best documented layout?

[chumii]

Hey there,

i rly love using oUF and i think its time to try to make an own layout.

since im not that good at lua, i have to use tutorials and such, so i wondered if there is a layout with good documentation in the .lua file which i can use as orientation. (maybe one where the author describes sth like "now player frame" "now de/buffs" "now grp" and so on..)

//edit: or is there sth like a oUF layout tutorial out there? that would be the easiest way

[Orane]

Originally Posted by chumii Hey there, i rly love using oUF and i think its time to try to make an own layout. since im not that good at lua, i have to use tutorials and such, so i wondered if there is a layout with good documentation in the .lua file which i can use as orientation. (maybe one where the author describes sth like "now player frame" "now de/buffs" "now grp" and so on..) //edit: or is there sth like a oUF layout tutorial out there? that would be the easiest way

I would like this as well. I have been spending time making textures and artwork and now I can't use them haha

[chumii]

edit: nothin =)

[Dawn]

Just download some and look at the code?!

[ravagernl]

If we really need to tell what this code is: self.Health = CreateFrame('Statusbar', nil, self) then you are better of using pitbull or shadowed unit frames

Just do what Dawn says. If you don't understand a method, like texture:SetTexCoords, look it up on wowwiki. That's how I learned

[yj589794]

oUF_Lily is the layout made by Haste as a simple reference design. Try starting with that and ask questions about any parts you do not understand.

[zork]

The problem is: Lily is not how layouts should be actually made of. haste implemented a style system and does not show to use it. Its one of the best things of oUF imo.

I try to comment most of my layouts and I wrote a oUF template file some time ago.

http://code.google.com/p/rothui/sour...F_Template.lua

Other than that. What Dawn wrote is correct. Take a layout you like. Look at the code and try to understand what it does. Try/error it out by editing code.

[Unkn]

Most of the layouts are really well commented because people that are using oUF are doing so because they like the customization and generally are capable of going and tweaking their favs.

Like posters have said above me. Once you look at a layout you like and look at the code its very very simple. My suggestion is start with one that just lua no xml unless you are comfortable with that.

Most of it is very easy to understand

Example :

  	-- Healthbar
   local hp = CreateFrame("StatusBar", nil, self)
   hp:SetStatusBarTexture("Interface\\AddOns\\oUF_Text\\StatusBar\\Empty")
   hp:SetHeight(hp_height)
   hp:SetWidth(width-border_size)
   hp:SetPoint("TOPLEFT", self, "TOPLEFT", 2*border_size, -2*border_size)
   hp:SetPoint("TOPRIGHT", self, "TOPRIGHT", -2*border_size, -2*border_size)
   hp:SetPoint("BOTTOM", self, "CENTER", -2*border_size, 2*border_size)
   hp:SetStatusBarColor(0.45, 0.45, 0.45)
   hp:SetBackdrop(backdrop)
   hp:SetBackdropColor(1,0,0, .55)
   hp.colorDisconnected = true
   hp.colorClass = false
   hp.colorClassPet = false
   hp.frequentUpdates = true
   self.Health = hp

The result of above code + rest of layout...


A bit more complicated one

 -- Healthbar
   local hp = CreateFrame("StatusBar", nil, self)
   hp:SetStatusBarTexture(statusbartexture)
   hp:SetHeight(hp_height)
   if unit == "player" then
        hp:SetOrientation("VERTICAL")
        hp:SetWidth(((width)/3)-(2*border_size))
        hp:SetPoint("TOPLEFT", oUF.units.player, "TOPLEFT", 2*border_size, -2*border_size)
        hp:SetPoint("BOTTOMLEFT", oUF.units.player, "BOTTOMLEFT", 2*border_size, 2*border_size)
        hp:SetPoint("RIGHT", oUF.units.player, "RIGHT", -7*width/9, 0)
        hp:SetPoint("LEFT", self, "LEFT", 2*border_size, 0)
        hp:SetStatusBarColor(0.45, 0.45, 0.45)
        hp:SetBackdrop({bgFile="Interface\\AddOns\\oUF_Geared\\StatusBar\\DarkBottom"})
        hp:SetBackdropColor(1,0,0, .6)
    elseif unit == "target" then
        hp:SetOrientation("VERTICAL")
        hp:SetWidth(((width)/3)-(2*border_size))
        hp:SetPoint("TOPRIGHT", oUF.units.target, "TOPRIGHT", -2*border_size, -2*border_size)
        hp:SetPoint("BOTTOMRIGHT", oUF.units.target, "BOTTOMRIGHT", -2*border_size, 2*border_size)
        hp:SetPoint("LEFT", oUF.units.target, "LEFT", 7*width/9, 0)
        hp:SetPoint("RIGHT", self, "RIGHT", -2*border_size, 0)
        hp:SetStatusBarColor(0.45, 0.45, 0.45)
        hp:SetBackdrop({bgFile="Interface\\AddOns\\oUF_Geared\\StatusBar\\DarkBottom", edgeFile = "", edgeSize = 4, insets = {left = 3, right = 3, top = o, bottom = 0},})
        hp:SetBackdropColor(1,0,0, .6)
    else
        hp:SetWidth(width-border_size)
        hp:SetPoint("TOPLEFT", self, "TOPLEFT", border_size, -border_size)
        hp:SetPoint("TOPRIGHT", self, "TOPRIGHT", -border_size, 0)
        hp:SetStatusBarColor(0.45, 0.45, 0.45)
    end
   hp.colorDisconnected = true
   hp.colorClass = false
   hp.colorClassPet = false
   hp.frequentUpdates = true
   self.Health = hp

Try messing around with it. You'll find once you start its fun and a great learning tool.



BTW don't use my code as an example... its sloppy as all get out and I don't care

[chumii]

Originally Posted by zork I try to comment most of my layouts and I wrote a oUF template file some time ago. http://code.google.com/p/rothui/sour...F_Template.lua Other than that. What Dawn wrote is correct. Take a layout you like. Look at the code and try to understand what it does. Try/error it out by editing code.

That is what i needed, thx very much.

i know that reading more and more code is the best way to learn, but i needed a good point to start at.

[Dawn]

Originally Posted by zork The problem is: Lily is not how layouts should be actually made of. haste implemented a style system and does not show to use it. Its one of the best things of oUF imo.

Could you point out the major advantages and disadvantages between the way you do it (several small functions for everything) compared to the "one large style function" thing, please?

I just want to understand what's the difference, after all. Just curious.

[zork]

- You can call any of the small functions with different variables set inside the small style function for each unit.
- You can access units (even special units) on the style activate per spawn. Thus you know exactly what unit you have in your style function because its the specific style function for that unit (no match needed etc.)
- If you want to edit the healthbar you go to the healthbar function and change your stuff, you don't have to read through one giant piece of code.
- Each style function can call specific functions depending on style. No conditions needed. If the function call is there it gets called otherwise not.
- Its much more readable/editable.

But thats my way of programming. There are many trees in a forrest, not just one.

[Dawn]

Thank's, I'll try that. Maybe it works for me, too.

[wurmfood]

I've been working on creating a new layout for my rogue and have adopted a mixed style (only one style is called, but the individual elements are put together by their own function) and it is definitely making it easier for me to read and update. It's very clear where one block starts and another ends.

I'll get to the full modularized approach at some point as I work on it.