unifiedarearect defines the left, top, right and bottom position of a window(widgets such as buttons, lists, etc. are classes, derived of the window class).
The relative value ranges from 0 to 1 with 0 beeing 0px and 1 beeing the width or height of the render window. Offsets are pixel values.
Name:
Anonymous2006-11-23 17:06
>>3
im not a big fan of xml but i have to admit, it realy is great for this. I wouldnt have cared if it was c like scripting language though. Which is also possible with lua bindings.
Name:
Anonymous2006-11-23 18:25
>>6
You're the best programmer ever, you're beautiful!
Name:
Anonymous2006-11-24 6:14
>>3
Exactly! That's how managers and retards who take decisions think.
XML is just the next buzz born from the ashes of previous "ML" buzzes, like a Phoenix. It's by no means optimal (waste of space; braces instead of close tags would have been better), powerful (very limited grammar anyways; standard grammar parsing and navigation tools would have been better), backwards-compatible (because it doesn't allow any grammar; it's not even compatible with HTML), or magic (doesn't do shit, actually, but managers will never realize this).
Manager thinking: Hey, I know how to solve the language barrier forever! Let's all talk XML! <?xml version="1.0" encoding="utf-8"?><message>Hi, I'm being universally understood!!!!! OMG BUSINESS PROFITS CASH FLOW CUSTOMERS FAP FAP FAP FAP</message>
>>11
exactly. Some people do have a clue with XML. However, most just go "EXECUTABLE XML, LESS CODE LAWL" and shift the code into 4 times more XML in addition to the zillion libraries needed to support the parsing of their poorly reinvented wheel.
Reminds me of a project where we wanted to regularly import various data from one ERP system into another. The consultant for the remote ERP system came up with this design that involved web services, XML, .NET - all the 'cool' stuff that actually completely overcomplicated the problem. His actual analysis of the problem was laughable.
We looked at the problem on our side and found that the simplest solution was to purchase some software that gave us an ODBC-ODBC bridge, and use that to transfer the data from the remote ERP system into ours. We used the native data transformation and scheduling services of MS SQL Server to grab the data and put it in.
It's usually more wise to work with the tools and concepts that you are familiar with and know that will do the job, than to jump on something else entirely because it's flashy and new.