Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Hopelessly large question. Using what you know may be the best option.</p> <p>That said, what I would do is use <a href="http://www.mono-project.com/Main_Page" rel="nofollow noreferrer">Mono</a> (I have done it before).</p> <p>I would use <a href="http://www.asp.net/mvc" rel="nofollow noreferrer">ASP.NET MVC</a> through mod_mono through Apache on Linux for the server side web code and <a href="http://jquery.com/" rel="nofollow noreferrer">JQuery</a> on the client to provide the sex appeal. I would make sure that I used <a href="http://en.wikipedia.org/wiki/Unobtrusive_JavaScript" rel="nofollow noreferrer">unobtrusive JavaScript</a> techniques so that it would work well even when JavaScript was not available.</p> <p>The advantage of using <a href="http://mono-project.com/Main_Page" rel="nofollow noreferrer">Mono</a> (.NET) is that that you could code both the web stuff and the client stuff in the same language (I would use C#) and use the same back-end and DLLs fro both. For the client GUI you could use WPF if it was going to be windows only or either Windows Forms or <a href="http://www.mono-project.com/GtkSharp" rel="nofollow noreferrer">GTK#</a> if you want cross-platform. I would probably use GTK# as that would give me the option of running the desktop client on Linux and Mac as well.</p> <p>ASP.NET MVC is open source and ships (the actual Microsoft code) out of the box in Mono.</p> <p>If you want to build a smart-phone front-end you could use <a href="http://monotouch.net/" rel="nofollow noreferrer">MonoTouch</a> or <a href="http://monodroid.net/" rel="nofollow noreferrer">MonoDroid</a> and reuse your back-end infrastructure as well.</p> <p>For tools, you could use either VisualStudio and friends if you are developing on Windows or MonoDevelop as an IDE if you are writing it on Linux. MonoDevelop also allows you to use Subversion or Git for source control and NUnit for unit testing.</p> <p>For communication with the desktop client, check-out <a href="http://en.wikipedia.org/wiki/Representational_State_Transfer#RESTful_web_services" rel="nofollow noreferrer">REST</a> as an alternative for providing an API to the desktop client while building the website.</p> <p>Of course, there are many other options to choose from.</p> <p><strong>EDIT: I wrote all of this before I knew that the server had been written and that Java had been chosen as the language.</strong></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload