Search the Community
Showing results for tags 'database'.
Found 3 results
Data informs our decisions it helps us keep track of what we have and what we may want to get. Some people are creating database apps for managing their collections but these rely on outside data providers. I want to add an extra game provider section to Telllico my collection database app of choice as it already can manage everything from movies to book or your own custom collection. I am wondering are there any mostly complete databases of Atari 2600 games that can be downloaded and used? If not are there any open APIs for querying any existing databases that can be used in an Open Source database app? Any information or experience is appreciated.
I've been working on a way to use a remote SQL database from the A8 via FujiNet. I originally wanted to use cubeSQL since its free, and offers SQLite wrapped in a server. However I need full JSON to and from to make it work, and thats still WIP on the outbound side. In the mean time, I've been writing my own SQLite wrapper in the form of a proxy using Perl. I wanted to use SQLite because the db's are small and it doesn't have any running process requirements. I chose Perl because its readily available, and has easy integration with both IP and DBI. Since SQLite doesn't have user authentication compiled in (by default), and I want to keep it simple, so I added some basic authentication into the proxy itself (you'll maintain this DB directly with SQLite admin tools). The proxy will listen for connections, accept commands, and return responses. Right now, it will open and close a database, and handles user authorization successfully. I'm working on the add/delete/update and query functions now. The first 3 should be fairly easy to implement, with delete/update also having a user perm tied to them. Select will be a little more complex in how it returns larger datasets back to the A8, and I need to think through that a bit more. My initial thought is to allow up to three 4K chunks to be returned - the first result would have only two (current 4K, and next 4K), once progressed to next 4K then there would be three (previous 4K, current 4K, and next 4K). Chunk sized could be changed depending on program requirements/memory restrictions on the A8. The other thought is to just return some # of results which could be asked through calls to the proxy, which would free up a lot of storage memory on the A8. Here is a shot of the proxy server running, and a simulation client showing how the calls would be made. Just the basics right now.
Hello, everyone. I've found myself, more often than not, needing to pull a manual for a VCS game, to read it... After the 4,623,136,126,842nd time of doing so, I thought, "Gee, isn't there an EASIER way to deal with this?" Now, before I start sounding like a fucking Ronco commercial, I'll just get right to the point: I've created an Android App, which I am currently feeding every VCS game manual that I can get my hands on, for the purpose of being able to quickly find the game, flip through it, and read it. This first version of the app, has these features, and a small subset of the total # of games which will be available, when it's finished (I intend to go from A-Z, finding as many, as I can.). You can: * Select the manual from the list * flip through content * pinch-zoom and pan dirt simple. An upcoming release will add the ability to take photos of high-scores to attach to a game, for record-keeping. That'll be about it. There will be no full text search. Why? The manuals are on average 4 to 12 pages long...With an average of 350 words a page, lots of pictures. This isn't an index of law journals, nor is it an engineering cross reference of airplane engine block internals, nor is it even a historical text in the typical sense. I do not see the point, and it would drastically increase the complexity of the program, for no real benefit. What do you need? * An Android tablet. While it will work on phone, it was ultimately designed for a tablet. Feel free to share your experiences anyway, if you only have a phone. * Android 4.0 absolute minimum (Ice Cream Sammich) * 0.1GB of space. The final will need approximately 0.6GB of space. The manuals are stored on device, inside resources, so they do not clutter up your gallery. No on-line connection needed to use the app in its present state. You can get it here: https://drive.google.com/open?id=0BxBzWnEPRL2Hd1FMSWViZF84ZFk Please let me know what you think. This is for my own use, but I always try, even with things for my own use, to apply the same standards as for something I do for commercial work. Since this contains copyrighted material, it will NOT go into the Android Play store, ever. It will be available from a site. Will there be an iOS version? Yes, at some point, BUT, it will require UDID registration, as it will never go into the Apple App store. -Thom