Should I split up Gtk+ code?

[silllykone]

I'm starting to do Gtk+ programming. One thing I find when doing a project is that my main() method (I'm using C++) is getting really bogged down--not necessarily with running time, but with code. Would it be good practice to set up the code in different functions like this:

*GtkWidget addMenubar()
{
// Create a menubar and return a pointer.
}

*GtkWidget addTextfield()
{
//Create a text field and return a pointer
}
int main()
{
  GtkWidget *menubar = addMenubar();
  GtkWidget *textField = addTextfield();
  //...Do some other stuff...
  // Add all the elements to the window and show.
}

Or would it not even be worth it?

[giulix]

For OO languages, it is common practice to organize files by class, grouping classes that have a common purpose in namespaces (packages in Java). Your current approach looks as if you're planning to use standard GTK+ libs and a procedural approach. Look into gtkmm instead: That will guide you towards a more object-oriented approach...