Return to Digital Photography Articles
JPEGsnoop - Source Code
JPEGsnoop is released as Open Source!
JPEGsnoop is now Open Source!
I'm happy to announce that I have now released JPEGsnoop source code to the open source community. I am hoping that this will enable others to add value in the project in new ways, in addition to helping those who are learning to write their own JPEG decoders
After researching many of the options pertaining to how the source code was released, here are the details:
- Source code hosted on SourceForge.net
- Source code repository via SVN for revision control
- License agreement is GPL v2 (although I may consider LGPL if sufficient interest)
- JPEGsnoop Sourceforge Project
NOTE: Source code for version 1.7.5 has now been posted
- JPEGsnoop Source Code SVN Repository (online source browser)
- JPEGsnoop Feature Requests (add new request)
- JPEGsnoop Bug Reports (add new bug)
- JPEGsnoop Discussion Forums
Considerations for Open Source
After analyzing digital images for years and developing JPEGsnoop in my spare time, I decided to explore the possibility of releasing the source code to the Open Source community for further development. I was looking to my readers to provide their input in how to best approach this transition.
There are many wonderful application developers out there who are more than capable of improving upon the features and user interface, and I'd like to give everyone the opportunity.
The Source Code
- JPEGsnoop is written in Visual C++
- JPEGsnoop uses Windows MFC framework
- No 3rd party libraries are required: All image decode/display, EXIF decode, etc. are written independently.
- An extensive database of camera signatures is also included with the source code.
Are you interested in improving JPEGsnoop?
Please let me know if you are a programmer with ideas that you'd like to roll into future releases of JPEGsnoop.
Porting JPEGsnoop to Mac and/or LINUX
Quite frequently, I have been receiving requests to port JPEGsnoop to other operating systems. In most cases, the User Interface code has been reasonably well separated from the primary analysis code, so a port should be relatively easy.