hmmm, a new user, unaware, or uncertain, or moreover, better than most, ..., un-dis-advantaged. Tim.
So, I guess the most important thing about the library product is to understand how I've organized the classes.
The most "GLOBAL" and "accessible" features are in the Default package -- package; or rather, its' equivalent within a Java namespace.
Essentially, the "Default Package" is where I typically store files the project depends on, aside from .jars. Those I keep in the <ProjectPath/jars/> directory.
Typically, for Spring Projects, I will store the tec_xml.pom file in the "default package directory", or the root of the project.
It doesn't yet, but I'll continue in that direction.
$USER_HOME$$$TEC_SEP##$DOCS$$$TEC_SEP##$SECURITY_PATH$$$TEC_SEP##
To Comply with Tecreations standards, please place your properties within: "USER.DOCUMENTS_PATH + "tecreations" + File.separator".
To automatically exclude any directory, just put the word 'security' within its' contents and I will attempt to exclude it. Secure by default.
Please refer to Deploy.doInitialSetup() && Exclusions: '*security*' in 'ca.tecreations.apps.deploy.Process'.
A future version may have a $SECURITY_PATH$ to redact.
After that, the package ca.tecreations would be the next most important to learn.
Finally, the packages ca.tecreations.* would be the next critical section and then the packages that are offshoots of the directory
level organization, ie: ca.tecreations.apps.*... && ca.tecreations.wip.*..., etc. Additionally, one should review the non-tecreations
directories, so for example, contrib.mail... && a.*, b.*, etc., for the relevant code sections. There is a JNA and JNI example implementation within,
and the notes for how to do the JNI compilation are either in: /ca/tecreations/apps/Notes.php or /ca/tecreations/tracy.php : content contents.
I try to make it all a 'minimalistic' approach. There isn't too much 'fluff' in my code, but you're free to decide. It isn't good for some things.
If I had to weigh in? ca.tecreations.??? VS. java.awt.??? I try to make my code mine and a carrier + xtra's. No, not intuitive that much...
I think for the classes from similar packages, you should examine what is going on. So ca.tecreations && java.awt??? , ca.tecreations.? && java.util.* >>>-> Please refer to ca.tecreations.time.
If I could speak securely? You must. Gen from airgapped, copy dayta there. Sign. Release signed public key. I'll watch it.
fill
.