C#

• Can nodes be re-used (ie serve as end points for multiple beams)?
  
  
  • Should join strength be a variable or ideal?
  • Is there a common joint, or are one connected to side of other?
• Can you have multiple load vectors on each beam?
• What types of load do you want to model (of the five classic)?
• Do you want to distinguish between, for want of a better term, primary (entered by user) and secondary (calculated and distributed over the structure) loads?

Orjan Westin wrote:

For instance, I'd probably keep nodes, members and primary and secondary loads separate in a relational database, and let the loads have a relationship to a member, which has a relationship to two nodes. So that's four tables of data to start you with.

Jacob Barton wrote:

My biggest question is how should I store all of the program data the user
enters

Gerry Schmitz wrote:

I would consider using Windows Presentation Foundation (WPF) instead of WinForms; I think you'll have better results and better resources.

jschell wrote:

What you should do however is create a persistence layer. That layer is ENTIRELY responsible for taking your data and storing it and retrieving it.

WebBrowser.Navigate(string.Format("facenama.com/{0}", "user_name");

WebBrowser.Navigate(string.Format("facenama.com/{0}", user_name);

public class MyClass {
  private const string SettingKey = "SomeSettingKey";
  private static readonly System.String SettingValue = 
        System.Configuration.ConfigurationManager.AppSettings[SettingKey];
}

public class MyClass {
  private readonly System.String SettingValue;  // readonly if it never changes during the "life" of this instance
  public MyClass() {
         const string SettingKey = "SomeSettingKey";
         this.SettingValue = System.Configuration.ConfigurationManager.AppSettings[SettingKey];
  }
}