Max: It sure does work on an iPod... the location awareness stuff is dependent on GPS (or WIFI assisted GPS which the iPod can do if your range has WIFI and you've submitted their location), but everything else works seamlessly.
legi0n: Good call, not sure how I overlooked that... thanks.
knockturna: From my latest comparisons with JBL, JBall, GEBC and few other online ballistic engines, iSnipe computes results closer to the major names than Ballistic does. Ballistic took the GEBC open-source engine and modified it so that he wouldn't have to continue to offer his code as open-source.
Derek Yates, the guy actually wrote GEBC, created our exclusive ballistics engine which is an updated version of the original GEBC... now written in C++ and was designed from the get go to run on a mobile device. It computes only the usable distance for a bullet (stops computing when the bullet is falling down faster than it is traveling forward) so as not to waste computing cycles on your device.
Also, in v2.0 I've included more factory ammo profiles than Ballistic and several features that Ballistic just plain doesn't have. (HUD)
That being said, Ballistic has a range-log feature that I have not included in iSnipe on purpose. if you feel this an important feature for you, please let me know. As of now, I have received only one request for this feature and that one didn't come in until yesterday. If I find that people are looking for this feature, I will definitely add it to iSnipe in the next couple of version.
Sakoboy: The reason SnipeBerry doesn't exist yet is that RIM chooses to use Java exclusively for their programming language of choice. iSnipe (and indeed most of the ballistic apps around) uses a modified open-source ballistic engine written entirely in C and C++. Java doesn't play well with others, not even C, so it means sitting down and writing from scratch not just iSnipe, but it's underlying ballistic math as well.
That's not to say we haven't been thinking about this, but it will require a whole lot more work than most realize. The other major issue is that from the quick look I've had at their dev site, RIM's SDK is lacking many of the navigation controller paradigms that make iSnipe so easy to use on the iPhone.
Also, FYI, as of February of this year RIM had sold a total of 50 million blackberry devices, and as of June Apple has sold over 40 million iPhones/iPod Touches... so it's getting to the point where RIM isn't the majority player anymore.
Obtunded: I was initially going to go back to all the forum posts I had mentioned iSnipe before (in conversation) and mention the update, but I figured that users would appreciated one centralized thread instead of 10 different spammy updates... I was/am fully prepared to take down the thread though, in the case that one of the admins didn't approve.
legi0n: Good call, not sure how I overlooked that... thanks.
knockturna: From my latest comparisons with JBL, JBall, GEBC and few other online ballistic engines, iSnipe computes results closer to the major names than Ballistic does. Ballistic took the GEBC open-source engine and modified it so that he wouldn't have to continue to offer his code as open-source.
Derek Yates, the guy actually wrote GEBC, created our exclusive ballistics engine which is an updated version of the original GEBC... now written in C++ and was designed from the get go to run on a mobile device. It computes only the usable distance for a bullet (stops computing when the bullet is falling down faster than it is traveling forward) so as not to waste computing cycles on your device.
Also, in v2.0 I've included more factory ammo profiles than Ballistic and several features that Ballistic just plain doesn't have. (HUD)
That being said, Ballistic has a range-log feature that I have not included in iSnipe on purpose. if you feel this an important feature for you, please let me know. As of now, I have received only one request for this feature and that one didn't come in until yesterday. If I find that people are looking for this feature, I will definitely add it to iSnipe in the next couple of version.
Sakoboy: The reason SnipeBerry doesn't exist yet is that RIM chooses to use Java exclusively for their programming language of choice. iSnipe (and indeed most of the ballistic apps around) uses a modified open-source ballistic engine written entirely in C and C++. Java doesn't play well with others, not even C, so it means sitting down and writing from scratch not just iSnipe, but it's underlying ballistic math as well.
That's not to say we haven't been thinking about this, but it will require a whole lot more work than most realize. The other major issue is that from the quick look I've had at their dev site, RIM's SDK is lacking many of the navigation controller paradigms that make iSnipe so easy to use on the iPhone.
Also, FYI, as of February of this year RIM had sold a total of 50 million blackberry devices, and as of June Apple has sold over 40 million iPhones/iPod Touches... so it's getting to the point where RIM isn't the majority player anymore.
Obtunded: I was initially going to go back to all the forum posts I had mentioned iSnipe before (in conversation) and mention the update, but I figured that users would appreciated one centralized thread instead of 10 different spammy updates... I was/am fully prepared to take down the thread though, in the case that one of the admins didn't approve.
