Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I come from the web application development and I try to make a small desktop application. I am looking for a good way to build the skeleton of my desktop application.

From the web design, the skeleton is mainly handled by the web browser combined with the web server which manage application states (each page could be compared to a state) which in some way "wrap" the whole application and give you access to the basic informations like the post and get variables (and many others). Finally you can wrap the whole web application in a MVC design.

I am wondering how I can do the same (or something similiar) in a desktop application? How can (or should) I properly wrap my application? Should I go with a state machine design combined with a MVC or is there something better?

Thanks for your time

share|improve this question
up vote 1 down vote accepted

Most desktop applications are event driven, so learn that paradigm. Most higher level RAD-style IDE's do that for you automatically.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.