• Welcome to the new COTI server. We've moved the Citizens to a new server. Please let us know in the COTI Website issue forum if you find any problems.
  • We, the systems administration staff, apologize for this unexpected outage of the boards. We have resolved the root cause of the problem and there should be no further disruptions.

Traveller on Digital Devices Discussion

Yes, I know that. The main question I asked was, "Which SINGLE smart phone OS is in use by more people than laptops?" as this has to do with mktg & allocation of resources.

Please read the post above completely. ALL smartphones support WEBINTERFACES through a BROWSER. So use a TOMCAT or JETTY(1) server to run a JAVA Webapplication on any box from good (SOLARIS) to bad (penguin os) and simply connect the WEBBROWSER. Problem solved.

And by writing the server in JAVA you also solve the other problems of portability


(1) Actually JETTY and using it's ability to run as part of the application instead of as a full server would be the best ways.
 
Please read the post above completely. ALL smartphones support WEBINTERFACES through a BROWSER. So use a TOMCAT or JETTY(1) server to run a JAVA Webapplication on any box from good (SOLARIS) to bad (penguin os) and simply connect the WEBBROWSER. Problem solved.

Cool, I didn't know that Tomcat ran on the new smart phone O/Ss
 
Cool, I didn't know that Tomcat ran on the new smart phone O/Ss

Please stop putting words in my mouth, from the context it should be clear that I did not intend a smartphone as the Server base but rather a normal box.

But YES a Jetty or Tomcat should run on quite a few of the new Tablet/Smartphone systems. Dalvik/Android is JAVA SE based and the MAEMO/MEEGO platforms have IIRC an OpenJDK running and that should work.
 
Please stop putting words in my mouth, from the context it should be clear that I did not intend a smartphone as the Server base but rather a normal box.

Um, it wasn't clear at all since we were discussing what runs on a smart phone and P2P s/w using one side as the server.

But, as I was saying, I'm not looking at anything but a stand alone & P2P. No, "cloud" crap. Not interested in being tethered to a "service". Academic anyway since no company is going to 1st roll out a tethered browser only cloud app.
 
Last edited:
No cloud needed. Simply a small standalone JAVA app on the GM's home server (or if he uses Laptops even there) and you are done. Jetty is a small Webserver that can run as part of a JAVA app, add embedded database and all you have to deliver is the program, a small batch to start it and done. After all we are not talking Fantasy gamers as a target audience

At this point you either use DynamicDNS or the AdHoc mode of WLAN cards and that's it. No P2P but the RPG tools don't need that anyway with the sole exception of possibly a Ship-Combat system. MGT Chargen is "group-orientet", Imperial Encyclopedia works fine server-based, Trading often is multi-character etc.

OTOH writing for say Google App Engine and having the GM register an account(free) and download the app there (free) and run from there should also work. The limits for the free accounts are high enough for casual use. Again no need for the Publisher to provide the infrastructure

Besides: Companies HAVE rolled out cloud apps in Roleplaying for quite some time. WoW, Everquest, ...
 
Spreadsheets would work for the elder chargen systems without livepath and group options quite well. Problem with the MGT system is the Livepath/Event part. It is complex coding that in an easily expanded/maintained way and may not work with spreadsheets.

MGT ship "building" system is easy. Lack of detail means easy of coding in a spreadsheet. TNE or MT would be more complex
 
This is really pretty simple.

If you're targeting desktops, you should use Java. It's the only environment well ported to all of the major desktops, and it works surprisingly well to the 90-95 percentile. You can create perfectly usable GUIs and have access to a rich graphics rendering framework. It also can drive printers reasonably well, and portably.

As long as you're not trying to create the latest McGreatest action 3D shooter, it's more than adequate. The complaint about downloading the JRE is a red herring, as it's pretty much painless to install on all of the platforms, including Linux. And once the JRE is installed, publishing for the major platform is mostly automated at this point (using simple packaging utilities), and with WebStart, it's even more simple, and cross platform.

Java lacks specifically in being a "perfect citizen" with all of the desktop environments. Out of the box, generic Swing works well enough though that the benefits far outweigh the downsides.

If you're targeting a hosted solution, you can use whatever you're happy with and target the modern, rich Web experience. Modern browsers are still bleeding edge, even with the cross browser libraries. Arguably, the cross browser stuff is more of a pain to manage and debug than Java is to work with. But if you want to target the browser, that's simply the truth of it.

You could almost safely target a single browser, Firefox, since it runs everywhere and is certainly a leading browser. That can save the pain of worrying about cross browser details. Some will decry its lame to target a single browser, but they're not the ones writing and hosting software for a niche environment.

However, if you want to target mobile, then Firefox is not necessarily the best development browser, as most of the mobile browsers are based on WebKit (save for Windows, of course...). In that case you're better developing in Safari or Chrome.

Also, all of the new browsers do support the concept of the "off-line" application. Where the bulk of the resources are cached locally on the mobile device or desktop computer. You can have local databases, etc. with these applications, and they don't need network connectivity to run. This area is a bit bleeding edge right now, but it's possible.

If you're writing a hosted app, then the backed environment that is most popular is simply PHP. The major benefit is that it's dirt cheap to host, and performs reasonably well on cheap hosting servers. Most hosts have real good support for PHP above pretty much anything else. You can still use CGI and other scripting languages (Perl, Python, etc.), and some host will support them well (with mod_perl, etc.), but PHP is by far the most dominant in this domain.

Another alternative is the Google App Engine. Here you can develop in Java or Python, and the hosting is effectively free, but it's definitely a different development model that most folks are unaccustomed too, so it takes some getting used to. But it offers some nice advantages.

If you want to target mobile directly, then you have to be specific and simply pick one. The modern mobile space is similar to the old school world of Commodores, Apples, Ataris and nascent IBM PCs with old school CP/M machines. This world is rocketing forward and has yet to stabilize. Obviously, Apples iOS and Android are the heavy hitters here, with Android likely grabbing more overall market share, but, at the same time, with a wide mix of platforms and devices as well. Android is certainly easier for the casual developer since you can publish your own code (i.e. you don't have to use the official app store for Android) and you can develop on anything you want (PC, Mac, Linux).
 
Back
Top