The Big Programming Thread - Page 74

luanet.load_assembly("Paessler.Billingtool")
invoice = GetInvoice()

if SensorChannel(1) ~= nil then
freeVolumeGB = 15
costPerGB = 50
currency = "$"
sumGB = math.ceil((SensorChannel(1):GetRawSum()/1024/1024/1024))
calculateGB = sumGB - freeVolumeGB
if calculateGB <= 0 then
calculateGB = 0
end

invoice:AddItem(SensorChannel(1).Name , sumGB .. "GB");
invoice:AddItem("Free volume" , freeVolumeGB);
invoice:AddItem("Each GB over " .. freeVolumeGB, costPerGB .. currency);
invoice:AddItem(calculateGB .. "GB to pay", calculateGB*costPerGB .. currency);
invoice:SetTotal("Total", calculateGB*costPerGB .. currency);
else
invoice:AddItem("Error: " , "Channel 1 not available in this type of sensor");
end

luanet.load_assembly("Paessler.Billingtool")
invoice = GetInvoice()

if GetPercentile() ~= nil then
percentile = math.ceil(GetPercentile()/1000*8)
costPerKbit = 1.50
currency = "$"
totalCost = percentile * costPerKbit

invoice:AddItem("Percentile", percentile .. "kbit/s");
invoice:AddItem("Charge per kbit/s", costPerKbit .. currency);
invoice:SetTotal("Total", totalCost .. currency);
else
invoice:AddItem("No percentile available", "");
end

I'm not sure why you would want to do this. For events, it seems like a bad idea to release control of your events. If you really need to, you can pass an Action object via lambda with () => MyEvent(...), which saves a lot of typing. I agree it would be nice to have access to the property getters and setters, but this is only useful in the context of reflection anyway, and it doesn't take all that much to get the MethodInfo for the property's getter and setter.



The threading pool examples all serve very different problems that overlap only tangentially. The XML parsers make more sense in the context of mobile platforms and Silverlight where they aren't all available simultaneously.



I'm confused. It can do all of those things.

public int Blah()
{
    return 5;
}

public void Blarg()
{
    var a = Blah(); // works fine, a is type int
}

There is the readonly keyword, which is perfectly suitable if your data is truly immutable.

PRTG Billing Tool Scripting Documentation
2011

To customize the billing calculations and output it is necessary to edit or write
scripts in the Lua scripting language (see Lua documentation:
http://www.lua.org/docs.html).

There are already some example scripts in the “\scripts” folder as well as example
templates in the “\templates” folder. The Billing Tool executes the script to
assign data to the template placeholders. The templates will be rendered as HTML
and PDF files afterwards.


Load Lua assembly
-----------------
To access the Billing Tool functions and data in Lua scripts, the Lua assembly
needs to be loaded:

luanet.load_assembly("Paessler.Billingtool")


Available Lua functions
-----------------------

After this step the following functions are available:

SensorChannel([channel_ID]):GetRawSum()
- Return the total bytes of the selected sensor channel for the specified
period.
- The [channel_ID] can to be found in the PRTG web interface under the
channels tab in the sensor details view.

SensorChannel([channel_ID]).Name
- Return the name of the selected sensor channel.

SensorChannel([channel_ID]).Id
- Return the ID of the selected sensor channel.

GetPercentile()
- Return the calculated percentile value for the spcified period if
available.

invoice = GetInvoice()
- Save the invoice object in the invoice variable to access invoice
functions later.

invoice:AddItem([name], [value])
- Add an item to the <#itemtable> placeholder in the template.
- With style sheets it is possible to customize the layout. Each item is
seperated into 2 columns (<td> tags).
- The columns are accessible via the CSS class "itemkey" for [name] and
"itemvalue" for [value].

invoice:SetTotal([totaltext], [totalvalue])
- Add the total value to the <#itemtable> placeholder in the template.
- The <tr> tag in the generated HTML file is accessible via the CSS ID
"total".
- Via the CSS class "totalvalue" it is possible to style the <span> tag
where the [value] will be visible.


Itemtable HTML
--------------

The following HTML is generated for the <#itemtable> placeholder:

<tr>
<td class="itemkey">
[name]
</td>
<td class="itemvalue">
[value]
</td>
</tr>
<tr id="total">
<td class="itemkey" >
[totaltext]
</td>
<td class="itemvalue">
<span class="totalvalue">[totalvalue]</span>
</td>
</tr>