Knowledgebase
Anatomy of a DMXReady Application
Posted by Graham Strong on 12 June 2008 03:12 PM

Anatomy of a DMXReady Application

DMXReady created a standardized system of files and folders right from the beginning to make all DMXReady applications 100% compatible with each other. This, as you will find out, is a great help to the DMXReady SDK user. Although some applications are more complex and therefore have more associated files, the basic structure remains the same.

 

Folders

Most DMXReady applications have this basic folder structure:

 

/admin or /admin_area

/applications

/assets*

/Connections

/css*

/databases

 

(*added in later apps)

 

Files

DMXReady applications usually consist of a main “display” file (visible to your website visitors), a main “admin” file (visible only in the Admin Pages), a connection file that connects your application to its database, and the database itself. All other files included with an application are designed to support these files in some way.

 

The display file always follows this naming convention: inc_appname.asp.

 

For example, the main display page for the Secure Login Manager is found at: /applications/SecureLoginManager/inc_secureloginmanager.asp.

 

Admin files usually are named “list.asp” and are found in their respective folders. For example, the main admin page for the Secure Login Manager is:

/admin/SecureLoginManager/list.asp

 

The connections file, which connects your application to its corresponding database (included in the top line of the display file), is found in the Connections folder and follows this naming convention: appname.asp

 

For example, the connection file for the Secure Login Manager is:

/Connections/secureloginmanager.asp

 

The database is found in the /databases folder, and follows a similar naming convention. For example, the database for the Secure Login Manager is:

/databases/SecureLoginManager.mdb

 

From here, it is easy to discover what each file in an application does. Try this yourself: start with your main display page (i.e. inc_secureloginmanager.asp) and list all the include files you see. Open those files, list the include files you see again, and so forth. Eventually, you can create a whole chart showing how each file interconnects with the others.

 

Congratulations! Now that you have created the application map, you have taken your first step towards understanding how DMXReady applications work.

(527 vote(s))
This article was helpful
This article was not helpful

Comments (0)
Help Desk Software by Kayako dmxready.helpserve.com