tecreations library

{$LEADING} This is the topic content as well as any relevant data to guide the conversation.

{$NAME_CLASHING} TColor is a carrier for Color. Naming TColor, Color, as in java.awt.Color, causes name clashing, therefore if you use that style for naming, you must also specify all of the AWT classes that you need to import, one by one. By naming my color class TColor, one can simply use import --> ca.tecreations.* and java.awt.*. Note that using ca.tecreations.File requires the listing of all java.io.??? classes, since both File classes cause ambiguity. You can specify that you want the ca.tecreations or java.io .File classes individually, but that is kind of a hassle also. I suppose that TFile would be a solution for that, however I prefer the naming for File as File, not TFile. The same rule applies for Keystore and KeyStore. Note that java.security names a keystore class as KeyStore whereas tecreations uses Keystore to denote the actual object of the KeyStore on the file system and IIRC in Server and Client it is KeyStore[Path] and TrustStore[Path], to denote the path to the objects' file and keyStore and trustStore for the variable names which are the instances of the "java.security.KeyStore" or "ca.tecreations.security.Keystore". Using a basic IDE will usually identify the specific classes within packages of your project. I prefer to mostly distinguish between the differences to provide clarity for debugging.