EQInterface Forums - View Single Post

Decided to update this post since it's the first one anyone sees and the old info was a tad out of date.

The project is in two parts now:
EQIA is a Class Library, more commonly known as a DLL, that assist programmers looking to write their own EQUI tools. It handles reading in EQUI XML files into a set of straight forward classes. The parser has three levels to it: EQUI_Interface for loading an entire interface; EQUI_File for loading a single file; and the individual EQ Interface Definition Language (EQIDL) elements themselves. Each EQIDL class is capable of storing the data for a given element and drawing it on to a sprite batch, which can be used for both drawing to an image and drawing to the monitor.

EQInterfaceArchitect is the actual editing studio. I'll be using this to demonstrate how to work the EQIA Class Library, and as the actual editing studio. My aim is to make this as easy to use as possible while providing minor restrictions to ensure the generated and/or typed XML code will work in EQ.

Progress:

EQIA
- EQIDL
  - All XML related interaction completed !
  - Drawing functions completed for the following: TextureInfo, Ui2DAnimation, Button, Label, Screen, TabBox, Page, WindowDrawTemplate, Gauge, InvSlot, StaticAnimation
  - Unfinished drawing functions: Combobox, Editbox, FinderBox, Listbox, Slider, SpellGem, STMLbox, LayoutBox, Static Elements
- Manager
  - EQUI_File - Complete
  - EQUI_Interface - Complete
EQIA_Core - Partially Complete
EQIA_Debug - Complete
EQIA_Defaults - Partially Complete
EQIA_Xml - Complete

04-06-2007, 11:16 PM	#1
shillingworth A Predatory Creeper Join Date: Dec 2002 Server: Bertoxxulous Posts: 251	EQInterfaceArchitect Decided to update this post since it's the first one anyone sees and the old info was a tad out of date. The project is in two parts now: EQIA is a Class Library, more commonly known as a DLL, that assist programmers looking to write their own EQUI tools. It handles reading in EQUI XML files into a set of straight forward classes. The parser has three levels to it: EQUI_Interface for loading an entire interface; EQUI_File for loading a single file; and the individual EQ Interface Definition Language (EQIDL) elements themselves. Each EQIDL class is capable of storing the data for a given element and drawing it on to a sprite batch, which can be used for both drawing to an image and drawing to the monitor. EQInterfaceArchitect is the actual editing studio. I'll be using this to demonstrate how to work the EQIA Class Library, and as the actual editing studio. My aim is to make this as easy to use as possible while providing minor restrictions to ensure the generated and/or typed XML code will work in EQ. Progress: EQIA EQIDL All XML related interaction completed ! Drawing functions completed for the following: TextureInfo, Ui2DAnimation, Button, Label, Screen, TabBox, Page, WindowDrawTemplate, Gauge, InvSlot, StaticAnimation Unfinished drawing functions: Combobox, Editbox, FinderBox, Listbox, Slider, SpellGem, STMLbox, LayoutBox, Static Elements Manager EQUI_File - Complete EQUI_Interface - Complete EQIA_Core - Partially Complete EQIA_Debug - Complete EQIA_Defaults - Partially Complete EQIA_Xml - Complete __________________ "Computers are like Air Conditioners, they stop working properly when you open Windows."