=========================================
DL Components Version 5.00 - Licence
=========================================


License Information
===================

The DLComponents are provided as freeware, and as such, there are minimal 
license requirements. You should quickly read through these conditions.
Usage of the components indicates your acceptance of the conditions.


Copyright
---------

The DL components are Copyright (c) 1997-2002 by David Leeding,
the "Author".


Licence
-------

You may:

 1. Install and use the components on as many machines as you wish; and,

 2. Copy the components and documentation for the purposes of backup; and,

 3. Give a copy of the components to another user, provided that all files
    are included in their original state and with the full documentation, 
    and that no fee is charged; and,

 4. Link the software into a program through the Delphi interface to create 
    a program for your own use, the use of a client with a specific application
    need, or for a limited market. Such programs may be distributed royalty free. 

You may NOT:

 1. Sell the components to another user, or attempt to make profit from them.

 2. Incorporate the components into a suite of components for sale, or for free
    distribution, without the express permission of the Author.

 3. Use, copy, modify, or transfer this software or its documentation,
    or any modified copy, in whole or in part, except as expressly provided above.

 4. Link the software into a program through the Delphi interface for the purpose
    of creating "commercial" software. Commercial software is defined as that which
    will be sold through a retail distribution network, or publicly advertised for 
    sale.


Limited Warranty
----------------

This software is provided "as is" without warranty of any kind, either
expressed or implied, including, but not limited to the implied warranties
of merchantability and fitness for a particular purpose. The entire risk
as to the quality and performance of the program is with you. Should the
software prove defective, you (and not the author) assume the entire cost
for any servicing, repair or correction.

The Author warrants any diskette(s) on which he as personally furnished the
program, to be free from defects in materials or workmanship under normal 
use for a period of ninety (30) days from the date of delivery as evidenced 
by a copy of your receipt.

Limitation of Remedies
----------------------

The Author's entire liability and your exclusive remedy shall be the 
replacement of any defective diskette(s) not meeting the abovementioned 
"Limited Warranty".

In no event will the author be liable to you for any damages, including
any lost profits, lost savings or other incidental or consequential damages
arising out of the use, misuse or inability to use such software even if
the author has been advised of such damages, or for any claim by any other 
party.

General
-------

You assume responsibility for the selection of this software
to achieve your intended results, as well as for the installation,
use and results from the programs. 

Although the DateEdit components themselves are considered to be Year 2000 Ready,
using these components DOES NOT guarantee that your application itself is
capable of dealing with all so-called "Year 2000 Issues". You, the developer, 
must assume full responsibility for an application's Year 2000 compliance status. 
The DateEdit components are designed to make your job of building a compliant 
system easier. However, you are responsible for testing your application for 
Year 2000 issues, particularly if you manipulate date values internally within the 
applications you write.

You MAY NOT remove or modify any copyright or version information, either 
within DCU, DFM, RES, BPL or DCP file, or within source code.

You MAY NOT sublicense, assign or transfer the license or software except
as expressly provided in this Agreement. Any attempt otherwise to sublicense,
assign or transfer any of the rights, duties or obligations hereunder is void.

This agreement is governed by the laws of the State of Victoria, Australia.

Questions concerning this Agreement should be Directed in writing to
David Leeding, 13 Treherne Court, Carrum Downs 3201, Australia.

You acknowledge that you have read this agreement, understand it and agree to 
be bound by its terms and conditions. You further agree that it is the complete 
and exclusive agreement between us, which supersedes any proposal or prior arrangement,
oral or written, and any other communications between us relating to the subject matter
of this agreement.


Questions & Answers about the License in Plain English
------------------------------------------------------

Q: Can I modify the components and use this in my applications?
A: Yes. You can either derive a new component from the existing
   one or, if you have registered the Source Code edition, modify 
   the source code directly. As long as you distribute the modified
   component as an integrated part of your application, you can do 
   so without payment of a royalty.

Q: Can I distribute my modified versions of the components to
   other developers?
A: Yes, provided that you also distribute the original version, and 
   make it clear to the recipient(s) which is the original, and which
   are modified. Further, you should document exactly what you have
   changed and why.

Q: Can I sell my modified versions of the components?
A: No. But if you're willing to offer the author a royalty, we can talk!

Q: I have a contract with a client that states that I must hand-over
   all source code when the development project is complete. Can I give them
   a copy of the DCU, DCR, RES and DFM files so that the client can recompile
   my program, or have another developer take over development?
A: Yes. Please ensure that you provide the client with the original (complete)
   distribution files with full documentation.  

Q: I have modified the components to add a new property; can I give
   this source code to my client as part of a Source Code Hand-over?
A: Yes, provided that your client also has a license for the 
   unmodified version of the DL components source code. If your
   code uses inheritance to modify a DL component, and does NOT require 
   the source code for the DL Components, you may pass on your own source code
   without restriction.

Q: I work for MegaSoft and we want to use your components in an application that
   will revolutionise the world, and will be installed on every computer in the 
   galaxy. Do we have to pay a royalty?
A: Yes. Please. Thankyou. I'm sure we can negotiate a small royalty based on unit
   sales. You software is clearly commercial, and I've done some (albeit a small 
   amount) of work for you. It's only fair.

Q: How can I tell if what I've developed is considered "commercial" or not? I 
   have written something for a client that the client is going to install in about 
   1,200 company sites world wide. 
A: The distinction can be viewed like this: if you are paid for your development of 
   an application by a client (at say an hourly rate, or an agreed contract price),
   then what you have developed is probably not commercial software, regardless of
   how many copies are distributed. If, however, you develop something (either for 
   a client or for yourself) and you or your client are going to sell that software
   publicly, then it is classed as commercial software.

   For example, if you are contracted by "Bunnings Hardware" to develop a 
   point-of-sale system, and you use the source code in it, you are not required to
   pay a royalty for each installation of the system. But say you develop a communications
   package that uses the components, and then sell it in shrink-wrapped packages in
   stores throughout the US. In this case you have created commercial software, and a 
   small (very small) royalty is only fair.

Q: What about distribution of components in shareware?
A: That really depends on what your product is and how much you charge for the registered 
   product. For low cost or low distribution products, it is likely that a royalty will 
   be waived. Contact the author with the appropriate details.
   
   
   
