This page is currently the admin contact page. Click my email link and let me help.

Most of you don't know me.  But I am sure you know someone who knows someone, who knows someone I know 

I've been building websites 2000 and programming since the 70s. 

One of the first considerations when building a project like a  member management, content management system is, maintenance of the website. External dependencies to various resources can strike a crippling blow to a website, sometimes requiring hours - sometimes days of work to repair. I always plan to have as few dependencies on external resources as possible.  External resources tend to evolve and sometimes require updating. Google Maps is a good example. Here I've incorporated the google maps API and hopefully, it will not require updating for a few years…  

The Image uploader is maybe going to evolve. Using the image uploader allows for you to decide whether you want the image to be tall or wide. It's a little tricky. I made every little bit of it the gauges are just images I move around.

Now is the time for all  good men to come to  the aid of their country . . . 
This page is currently the admin contact page. Click my email link and let me help.
I need a list of all the different mediums. all of them. :)

This below is just some of the notes I will put in the help pages. This page will be updated with new stuff all the time.

The Gallery Help shows what the image manager looks like when you load an image into your browser.  Along with the upload button,, you see a text box with the name of the image in it. You can change the name but not the extension on the image. In this case, test.jpg could be changed to anything.jpg you could do this in order to not overwrite the existing file which you see is there in the file exist upload to overwrite notice.
When you open the image manager will find two buttons in the upper left-hand corner. These two buttons select for either the uploader or the image library. When you browse for an image on your computer, keep in mind that we have some fairly strict uploading image size requirements.  I've offered a series of controls that allow your browser to resize the image as you select it from your computer. This will allow us to upload around 100k bytes on each upload, this number varies not necessarily on the dimensions of the image, but a combination of the content of the image and dimensions. Encoding offers us two advantages. 1 as the first step in the process we can have future offerings to the image, such as a watermark or other image overlay. And this is being done in your browser instead of using Server CPU Time.   2. Achieving heightened security, uploaded images are encoded helping us remain secure. The downside to encoding, it adds a little bit of size to the image.   I could force the size of the image easily with the software we have and use. And the watermark and overlay that I was talking about simply using the GD library. But we get much more flexibility for now and in the future using the javascript canvas in your browser., And that added bit of security in the encoding process. And... Lower Server CPU Time.