Customization versus Modification
We have tried to provide the ability to alter every aspect and element of the pages created by our product. So, the term "customization" in our perspective implies changes to the appearance of 20/20 DataShed's content on your web site via the HTML templates or CSS. While the term "modification" implies changes to the basic architecture, source-code, or inner-workings of the product.
By this terminology, "customization" is allowed and encouraged but "modification" is not. As a general rule, the *.asp, *.mdb, *.js, and *.xml files should never be opened, edited, or modified in any way. Other files, such as the HTML templates, CSS, and languages.xml file, can be edited as necessary to suit your needs (provided that your customizations respect the information provided in this documentation and you do not make "breaking" changes to those files).
In other words, we want to provide you with the ability to adapt our product for your web site and integrate the product smoothly into your own design. To this end we have focused heavily while developing this product on features that allow customers to customize the presentation layer of the product. At the same time however, we have to set some limitations and be clear to our customers exactly what kind of customization we will support and when modifcations aren't acceptable by our license agreement or technical support obligations.
In discussing the architecture of 20/20 DataShed we can roughly separate our source code into the following three layers:
- Presentation Layer
- This layer includes:
- We invite you to customize these files as you please!
- Customizing these files will not result in irreparable damage to the source code or data within 20/20 DataShed on your web site. As such, we encourage our customers to take full advantage of the flexibility that this layer and it's associated files provides.
- This layer creates the cosmetic design and layout of the data. This is the layer which displays the information passed to it from the "business logic" layer.
- The flexibility provided by the HTML templates and other files listed above enables you to make 20/20 DataShed look however you wish. Do so at your own risk; we deny all responsibility for any and all loss or harm you may encounter as a result of your customizations.
- Business Logic Layer
- This layer includes the *.asp, *.inc, *.js, *.gif, *.jpg, *.xml files (except languages.xml) included in or associated with the product. These files perform the "business" of the product: it's subroutines, functions, classes, documents, text, and other elements which perform the logic and action required to serve content to the presentation layer.
- This layer provides the basic functionality of 20/20 DataShed and is one of the elements include in 20/20 DataShed's "CORE" packages.
- Modifying these files may result in irreparable damage to the source code or data within 20/20 DataShed on your web site.
- Any direct alteration or modification of these files is forbidden. Do so at your own risk; we deny all responsibility for any and all loss or harm you may encounter as a result of your modifications.
- Data Layer
- This layer includes:
- Modifying these files may result in irreparable damage to the source code or data within 20/20 DataShed on your web site.
- This layer is used to store raw or formatted data for use with 20/20 DataShed.
- Any direct alteration or modification of these files is forbidden. Do so at your own risk; we deny all responsibility for any and all loss or harm you may encounter as a result of your modifications.
What DO we support, and what do we NOT support?
Basically, we are committed to helping you get our product up and running on your web site and devoted to solving problems or correcting errors in our product.
This does not mean that we will install the product for you (although we do offer that service for a fee). Instead it means that we are available to answer questions you may have about configuration and setup. It means that we want to help and understand that we are obligated (to a point) to assist our customers to ensure they have a positive experience with our product. And it means we enjoy working with customers who are genuinely interested in getting the most out of our product and contribute to the betterment of the product.
We will do our best to answer your questions but we have a basic expectation that our customers will Search the Knowledge Base on our web site, read this documentation and/or investigate online resources first! In some cases where our own documentation is lacking important information, we'll gladly answer your questions. In other cases where the answers are readily available on our web site or in our documentation then we may simply point you towards the relevant resources. However, we simply cannot be expected to perform work or provide tutoring services free of charge.
We will always support what we CAN support. By this we mean that if the problem or error is ours then we'll explain it and/or fix it. However, if the root of the problem resides with your web server, your HTML editor, or other entity, then we simply cannot fix it but can instead point you towards a more appropriate resource.
But, I really like to tinker, and I absolutely/positively have to...
- ...add another field to the database.
- ...change that Javascript function.
- ...change the file name.
- ...link this database to my own.
- ...import content from other databases.
- ...use a SQL/mySQL/Oracle/FoxPro database.
- ...use Netscape/Opera/Explorer version 3! or other web browser with less than 2% market share.
- ...etc. etc.
Well, go on and tinker then!
We simply recommend that you:
- Ask yourself why? or ask yourself "Is there another way?". Perhaps there are features (already available in the product) that provide the functionality you desire. Are your source-code modifications absolutely necessary? 20/20 DataShed's core source code allows a tremendous amount of flexibility -- for example, our web site at www.2020applications.com uses 20/20 DataShed at its core and all the functionality of the web site is created without any modification to 20/20 DataShed's source code!
- Be smart. Don't "tinker" on a live web site. It's best to play in a sandbox where no harm is done.
- Take sensible risks. If you've never seen VBScript before, then you probably have no business making changes to the source code of the *.asp files. And please do not trust that Visual Studio, FrontPage, or Macromedia DreamWeaver or any other WYSIWYG editor will do the job for you. Often those products do as much harm as good.
- Be careful. Always backup the files before making and testing any changes.
- Go slow! We highly recommend against making broad changes to a file and then testing it. Make ONE change...then test it. Make a second change...then test it. This way, if you encounter an error you will have a better understanding of where or how the error occurs.
- And if you get stuck or something is broken, don't expect our help. You may ask for our help...and we may help you, or we may ask you to take a long walk, hike, or to never bother us again. In such cases, it's best perhaps to just implement the original files and source code and either start again or stop tinkering.
Send Feedback
().jpg.html){kind=link}