Composer

Nice work.
Do you have any plans in integrating with composer? And, maybe deploying on packagist?
Another question, I'm wondering why you choose to name the class in lowercase?

Regards,
Robert.

I currently do not have any plans for composer or deploying on any package repository. Aside from PHP, there are no dependencies.

If another developer wants to extend it, or use it in a derivative work, they are free to do so under the conditions of the GPL license.

As far as lowercase naming conventions...

I am from the old school thinking on naming files or folders. There was a time in internet history when you actually had to type in the url for any resource you wanted. Unix based operating systems where case sensitive, so it just made sense that everything should be lowercase. It was a real pain to try and remember where a resource was located and then to have to remember which characters where capitalized made it nearly impossible.

Of course, everything in the wide world web is hyper-linked now, so it is not that big of an issue, however the convention stuck with me.

You would be surprised how long it took me to actually use file names longer than 8 characters even after extended names became the standard. For anyone not aware, there was a time that file names could not be longer than 8 characters and extensions no longer than 3.

Dave

Any package in PHP Classes can be installed with Composer. Just go on the package download page and click on the Install with Composer to find the necessary instructions.

phpclasses.org/package/9527-PHP-Con ...

Hi Dave,

Thank you very much for taking the time to reply. All makes sense now.

I remember a bit about naming conventions when I used MS-DOS 6 or Win 95.

Recently, I had an argue with a colleague about not reformatting the filename of an uploaded file to convert the space with an underscore. He was really surprised of my reaction. I ended up urlencoded the file path so that it will work as a web link.

Robert.

Thanks Manuel.
I didn't know that.

Now, I'm wondering how it will know what version to download?
I'm seeing "phpclasses/giflayer": ">=1.0" , but I don't see the version number anywhere.

The site only keeps one version of the package as it works also with packages that were not imported from version control repositories.

Anyway, the current version is on the left of the information tab of the package page.

The site automatically bumps the package version when the author updates any files, so composer knows that the package was updated.