Code & Downloads

Details for code base along with downloads of ours and various WYSIWYG editors.

Core Deployment Package

Includes all folders for templates, PHP Functions, installation to set SQL tables, category edits, and WYSIWYG support pages. Please note, this does NOT include the actual WYSIWYG tools themselves. You will need to download them directly from their respective home pages. Depending on which one you would like to use TinyMCE, CKeditor or WYMeditor.

eComDelta_core.zip (rev 0.001, pending...)

The Code Base:
Made up of primarily two included files that are intended to used in most if not all PHP files used on this site, these two files provide most of the variable definitions, database access and programing logic used to display this site. A list of these files and the folder layout is as follows:

Folder: /inc/ "the includes folder"

common_functions_class.php
This single file contains most of the functions used in the code base.  The programing code is writtin as FUNCTION which are subsquently called when needed. It was decided to avoid the use classes at the point in the code base's development in or to improve readability for begining PHP programmers.

constants.php
Contains most of the site's primary definitions. The database login values, site name as well as several default value settings for page descriptions and key words. It is also the file you will need to edit once the WYSIWYG editor of your choosing is installed.

Folder: /sniplet/ "the template folder"

00_00_full_template_800.html (example /sniplet/00_00_full_template_800.html)
This is the current default template file, the folder contains various files and this changes frequently. The contents of that folder will, no doubt be different from the time of this writting, to when you are reading. In part the name sniplet was used since the original implementation of the methodology used multipule HTML code segments to build any given page. It was common for us to use multiple sniplets to build a particular type of table type, for example to display invoice or shipping data. 

While the use of multiple sniplets has some practical advantages, it is more work to understand how each piece is used to build a give page. Since it is our itent to make this easy to understand, the current implementation uses a single template. The naming convention is designed to support a sequence of files and subversions there of. 

Additionaly, the numbering convention has some advantages under PHP when using shared memory resources. While presently not in the code base, it is our intent read all the sniplet files into shared memory to reduce file I/O. The same methodology will be implemented to cache fully rendered page output to reduce database I/O, but that is another topic.

 Other files and folders that are less significant and will no doubt be changed by anyone who edits their own template are as follows:

/i/ (main reused template images & site logo)
/i/clipart/ (images used on a per page basis)
/css/ (style sheet folder)
/js/ (javascript folder)