oUF_ScriptableText

[starlon]

I'm considering writing these oUF modules for WidgetBar, WidgetHistogram, WidgetIcon, etc... I don't use oUF though. If someone wants to give it a go, don't hesitate.

local parent, ns = ...
local oUF = oUF
local LibCore = assert(LibStub("LibScriptableLCDCoreLite-1.0"))
local WidgetText = assert(LibStub("LibScriptableWidgetText-1.0"))
local core = LibCore:New({}, "oUF_ScriptableText")

local Update = function(self)
	local fontstring = self.fontstring
	fontstring:SetText(self.widget.buffer)
end

local Enable = function(self, unit)
        -- note that row, col, and layer don't mean anything to us here.
	self.widget = self.widget or WidgetText:New(core, self.name, {
		value=self.value, -- the Lua script to run.
		update=self.update, -- How fast the widget will update.
		speed=self.speed, -- How fast marquee text will scroll.
		direction=self.direction, -- Left or right, 1 or 2.
		align=self.align, -- ALIGN_LEFT, ALIGN_CENTER, ALIGN_RIGHT, ALIGN_MARQUEE, ALIGN_AUTOMATIC, ALIGN_PINGPONG = 1, 2, 3, 4, 5, 6
		cols=self.cols, -- How many columns wide the text should be. This is optional, and really only matters in marquees.
		prefix=self.prefix, -- A lua script for text prefix.
		postfix=self.postfix -- A Lua script for text postfix.
                -- WidgetText does its own updating, but that's optional as you can simply call widget:Update() in your own time.
		}, row, col, layer, errorLevel, Update, self)
	self.widget.environment.unit = unit -- This will be the 'unit' variable within the run environment.
	self.widget:Start()
	return true
end

local Disable = function(self)
	self.widget:Stop()
	return true
end

oUF:AddElement('ScriptableText', nil, Enable, Disable)

Sorry for the dry code.

[starlon]

Here's oUF_ScriptableText's home for now.
https://github.com/Starlon/oUF_ScriptableText

Here's a marquee of your mana.

        local hp = CreateFrame("StatusBar", nil, self)
        -- do stuff to your health bar
        local fs = hp:CreateFontString()
        fs:SetFontObject(GameTooltipTextSmall)
        fs:SetPoint("BOTTOM", hp, "TOP", 0, 15)
        fs.value = "return Power(unit)"
        fs.speed = 100
        fs.update = 100
        fs.repeating = true
        fs.align = oUF.ALIGN_PINGPONG
        fs.cols = 20
        self.ScriptableText = fs
        self.core = LibCore:New({}, "oUF_Arl", 2)

[starlon]

Here's for status bars.
https://github.com/Starlon/oUF_ScriptableBar

Each WidgetBar object will keep track of two bars, although this isn't fully implemented in oUF_ScriptableBar currently. In LCD4Linux design you could specify half the bar keep track of one cpu profiling aspect, and have the bottom half tell some other information.

In terms of LCD4Linux character display bars, the program used "special characters" provided by the LCD firmware which you can draw on. LCD4Linux calls them icons in another widget. They're 8x8 pixels large. LCDs typically come with 8 special characters you could store your bitmap in. Then you just print to the LCD the ascii value, which represents the special character memory space. Some have the special characters at the start of the ascii alphabet. I only tinkered with CrystalFontz and Pertelian, which both have their first special character pointed to by ASCII#0.

Character display bars could use half the special character for one widget bar, and use the top half of the special character for the widget's other bar. I'm not sure if LibScriptable's bar widget really needs two bars. Any thoughts?

One thing to keep in mind though is that DriverCharacter can draw its own fonts, so the "special character for bars" design can apply to DriverCharacter's own special character data. D; DriverCharacter is a simulation of a character display. Of course this would require LibCore instead of LibCoreLite, and it would have transitions, so you could display some bit of information for a few seconds, then scroll to a different widget face.

The only thing about this is it's a memory horse. You're going to use some memory. Any suggestions on how to trim away memory space are much appreciated. I'm going to make it so you can install LibScriptable in bits and pieces to create a bunch of addons for individual internal libraries, such as PluginLuaTexts, or WidgetBar.

Here's a WidgetBar provided by oUF_ScriptableBar. Note that some things like status bar texture, min and max values, color, length, height... it all updates at each refresh.

That's one thing I should mention. At the moment everything's just refreshed by a timer based on WoW UI animation groups. Any suggestions regarding how to update based on events would likely get some balls rolling. heh

        local mybar = CreateFrame("StatusBar", nil, self)
        mybar.expression = "return random() * 100"
        mybar.min = "return 0"
        mybar.max = "return 100"
        mybar.color1 = "return random(), random(), random(), 1"
        mybar.length = 100
        mybar.height = 15
        mybar.direction = WidgetBar.DIR_EAST
        mybar.orientation = WidgetBar.ORIENTATION_VERTICAL
        mybar.update = 200
        mybar.texture = cfg.tex
        mybar:SetPoint("BOTTOM", fs, "TOP")
        mybar:SetMinMaxValues(0, 100)
        mybar:SetStatusBarTexture(mybar.texture)
        mybar:SetValue(50)
        mybar:SetHeight(mybar.height)
        mybar:SetWidth(mybar.length)
        mybar:GetStatusBarTexture():SetHorizTile(true)
        self.ScriptableBar = mybar

[starlon]

I guess I should point people to LibScriptable's home.

https://github.com/Starlon/LibScriptable-1.0

I recommend getting it straight from git. What's at Wowace may go away.

[starlon]

Fixed a nasty bug (not really a bug, and not really a fix). But every widget needs a unique name. The examples I've shown here didn't give them a name. I was giving them all the name of ScriptableBar and ScriptableText. It'll go for ("ScriptableText" .. random()) now if nothing else is provided.

[starlon]

You should be able to set events now.

mybar.events = {UNIT_POWER = true}

[haste]

Originally Posted by starlon Fixed a nasty bug (not really a bug, and not really a fix). But every widget needs a unique name. The examples I've shown here didn't give them a name. I was giving them all the name of ScriptableBar and ScriptableText. It'll go for ("ScriptableText" .. random()) now if nothing else is provided.

Wouldn't it be better to use the name of the parent add-on combined with a internal counter? That way you are sure you won't get any conflicts. Using random() seems to beg for hard to reproduce bugs.