TexasCHLforum.com

This idea is for Linux, *BSD, ect, but I also want input from from windows and mac users. There are plenty of software programs for Windows users to track their firearms collections, and some of these packages work on Linux/*BSD if you run them under wine, and there is at least one Java application that works on just about every operating out there, The problem is they are not open source, they do not always play nice when running in wine, or they do not have the features I want. My solution is to write my own, this is not going to be an overnight project and I am still researching and planning. This project will stretch my rusted up programming skills and prove to be a significant challenge, but it wouldn't be any fun if it didn't. Some features I am already planning around are:

It will be licensed under an Open Source Software License.
Gnome/GTK interface
Tracking of an unlimited number of firearms.
Option to track changes to records.
Ability to track ammo and accessories (accessories will be able to be associated with multiple firearms).
Ability to check accessories and ammo stock from the firearm's record.
Ability to track multiple (Unlimited?) calibers on a firearm (357/38spec, 45colt/.410 [judge], .22LR/L/S/Magnum [revolver w/ interchangeable cyls], ect.)
Unlimited images.
Image Scanner support
Tracking of almost every imaginable detail regarding purchase and/or sale.
and more.

But I would like to know what features others would be interested in seeing, especially users of Linux and the various BSD variants. At this time I am leaning towards using existing database applications for Linux/*BSD like MySQL and PostgreSQL but I am open to other suggestions. One thing that has been suggested is that I develop it so that a dealer might get a variance from the ATF to use it in place of a bound book. So please give me some feed back regardless of what OS you use.

G.A. Heath wrote:This idea is for Linux, *BSD, ect, but I also want input from from windows and mac users. There are plenty of software programs for Windows users to track their firearms collections, and some of these packages work on Linux/*BSD if you run them under wine, and there is at least one Java application that works on just about every operating out there, The problem is they are not open source, they do not always play nice when running in wine, or they do not have the features I want. My solution is to write my own, this is not going to be an overnight project and I am still researching and planning. This project will stretch my rusted up programming skills and prove to be a significant challenge, but it wouldn't be any fun if it didn't. Some features I am already planning around are:

It will be licensed under an Open Source Software License.
Gnome/GTK interface
Tracking of an unlimited number of firearms.
Option to track changes to records.
Ability to track ammo and accessories (accessories will be able to be associated with multiple firearms).
Ability to check accessories and ammo stock from the firearm's record.
Ability to track multiple (Unlimited?) calibers on a firearm (357/38spec, 45colt/.410 [judge], .22LR/L/S/Magnum [revolver w/ interchangeable cyls], ect.)
Unlimited images.
Image Scanner support
Tracking of almost every imaginable detail regarding purchase and/or sale.
and more.

But I would like to know what features others would be interested in seeing, especially users of Linux and the various BSD variants. At this time I am leaning towards using existing database applications for Linux/*BSD like MySQL and PostgreSQL but I am open to other suggestions. One thing that has been suggested is that I develop it so that a dealer might get a variance from the ATF to use it in place of a bound book. So please give me some feed back regardless of what OS you use.

Why not do it in OpenOffice.org Base? Then it would run on just about any operating system..

I'd like to see a database with a desktop application that would synch with a blackberry.

MrsFosforos wrote:I'd like to see a database with a desktop application that would synch with a blackberry.

Web based, mobile device capable is definately a plus.

If you REALLY want to go all out, mobile device application that allows you to add, modify, etc records, and import pictures directly from the device camera :)

Liberty: I will look into the OpenOffice.org API and consider supporting it as a DB backend. My plan really calls for modular support for Database Servers so that I can support multiple DBs out of the box, and add additional support later.

Russell: I am initially targeting Individual users, but want to also support dealers who wish to use an electronic bound book, I have no plans to even try to do an E-4473 application or support at this time (not even sure the ATF would approve an OSS product for that application).

dicion: A web based interface may come about later (maybe something done with Ruby), currently there are issues that would prohibit a php based interface but those issues should be resolved around the end of October or so. A web interface may not play nice with OOo base support, but it maybe possible for those users to backup their data, reinstall/reconfigure, and restore to move to a new database. I may even write in a function to allow moving the database over (I had not considered this). See my response to MrsFosforos regarding the PDA idea.

MrsFosforos: Smart Phone and/or PDA support would have to be done by another party, as I do not have the time or tools to develop it. However, With my goal being to create an open source project it would take little effort to coordinate my work with someone developing such an application. I may look to see if there is someone working on such an application and if they could be talked in to working to gather in order to develop a more complete package.

Ideally I plan to finish the Design and Research planning stage by the end of next week and begin coding the generic DB interface (PostgreSQL, MySQL, and maybe OOo base), and the basic code to add, edit, delete, and do more to entries. To test this portion of the code I will write a text interface. The next step once I am happy with the database and manipulate entries I will start to work on a Graphical User Interface. Once that is working I will probably make a public release and then start adding stuff like Camera and Scanner support. I plan to support backing up the data (not the images) by writing it to an XML file, then that file and the images will be compressed into either a tar.bz2 or zip file. This will make changing/upgrading database entries and such easier for the non-geeks. Another consideration for non-geeks is allowing the initial setup to even configure their database server for them if needed.

Everybody: All great ideas, and I really appreciate them. I would like to hear more also. Also Windows support maybe possible, but I am not willing to commit to it just yet, MacOS support is also a possibility but I lack the hardware and software to make that happen,

On a Side note, I feel Open Source Software (OSS) and the second amendment movement are both closely related. OSS is not about non-cost, its about freedom. The Freedom to look at your software source code, the freedom to modify it, the freedom to say "This is good software, here's a copy to try and its 100% legal for you to use", ect. Now I do not see a need to explain why the second amendment movement is about freedom, atleast not here.

The software I use also allows me to track the information about where/when the firearm was purchased as well as information on selling the firearm if I ever sell them. Also, it allows me to upload pictures of my firearms to display on the firearm information page.

One thing I'd like is the ability to scan in certain documentation, such as receipt, insurance policy information, anything. That way I have a one-stop shop for all information/documentation regarding the firearm if anything should happen to it.

Kythas wrote:The software I use also allows me to track the information about where/when the firearm was purchased as well as information on selling the firearm if I ever sell them. Also, it allows me to upload pictures of my firearms to display on the firearm information page.

One thing I'd like is the ability to scan in certain documentation, such as receipt, insurance policy information, anything. That way I have a one-stop shop for all information/documentation regarding the firearm if anything should happen to it.

I have actually planned for those features from the start, as it will use SANE (the Linux/*BSD scanner service/API) scanner access will be available. I am also researching the gphoto2 API so it can pull images directly from a camera. For Acquisition and Disposition I am planning to allow users to track every possible detail regarding a private party and/or FFL. As for images I am planning to support an unlimited number of images for acquisition, disposition, and of the firearm and anything related.


Yesterday I started to do a little coding on minor aspects of the program (to get the rust off of my skills), that however was interrupted by my carport getting itself some flight abilities.