'First rule: don't compare SDKs, that's apples to oranges. So here I go breaking my first rule. My first app with NSB was a rewrite of a VB6 program. I copied code directly from it to NSB, made a few syntactical changes, used the SDK to create the controls (similar to VB6) and that was it. It ran. I have since then gone back to many routines developed in VB6 and reused them in NSB, again after making some changes to syntax. I was trying to avoid rethinking the logic I used to create these routines and that was a success. This is one reason I chose NSB, I could not do this in Java Script, even if I was proficient, the time to convert and debug, no thanks. And then a few weeks ago I had some time on my hands and went back to a program in VB6. Did I like the quick response, advanced syntax checking, and debugging on my PC, yes, you bet I did? But then I kept finding myself highlighting groups of code and trying to right click to block comment. No way, damn why couldn't VB6 have this great capability like NSB? Thank you 'Just for Fun' for this suggestion and the NSB team for listening. But it really is still apples and oranges.
Serial means a unique number or code which identifies the license of the software as being valid. All retail software uses a serial number or key of some form. A serial number can also be referred to as an Activation Code or CD Key. When you search for Nsb Appstudio Serial, you may sometimes find the word 'serial' in the results. Deploying the project to the nsb site worked out pretty well and was quite efficient. Going from idea to final product only took a few weeks working on it sporadically.' The judges say: This is a great app for small devices. It lets investigators do on the scene analysis. The UI is well put together - the app is already very useful. NSB/AppStudio is designed to be an easy to use WebKit based tool to create web apps. It is a simple yet powerful language that can be used to write programs for almost any application. There is a file named Readme.htm included with the release which contains late-breaking information about NSB/AppStudio, including updates to the Handbook.
Second rule: 'If you can't be with the one you love, love the one you're with'. I have never used an SDK that had everything I wanted. My first Basic compiler couldn't do drop down menus so I bought an add-in. It couldn't handle keyboard entry the way I wanted so I wrote a machine language routine. VB6 has many things missing but there are a plethora of DLLs, VBXs and OCXs that make up for this. And the same applies to NSB. I recently wrote an app that had to convert an html text file to pdf format and then save it to the device drive for printing with a separate device driver to a Brother printer. Solution, a java script add-in for the conversion and phonegap to save the file. Oh, and don't forget the best 'add-in' of all: this forum (thanks Less for that great procedure to ease building dual portrait/landscape apps).
Third something or other: 'monogamy is best but polygamy can work, just not as well'. My second app with NSB was a lot more aggressive. I wanted it to be an 'everything/everywhere' app. It connected to my server, exchanged data, sent email both from the app and the server, allowed for internal correspondence (social networking?), maintained a database (SQL on both the server and the app), used local storage in place of cookies, had a 'coded' splash screen form which of course worked on iOS, and much much more. But most important it had to run everywhere, on anything: PCs, Macs, Android and Apple devices. And all with different screen sizes. Oh, and it had to look good, with either a full picture image background stretched to fit or tiled to fit, and all controls were re-sized and centered. Now I cannot afford to buy every device out there and I don't even own a Mac, but whenever I am near someone with a device I like to do a little test. So far everything I tired worked, some better than others. But it sure is a lot easier if you only need to develop for one device and screen size.
So for me, NSB gets a thumbs up, and I am sure that in the future it will change to a big thumbs up as the GUI/Editor/documentation issues are resolved. ' -- John Calhoun