This is style issue. Everybody has its own style. I prefer to have different forms in different .c files. That results in more clear structure and debugging more easy. However, dialog boxes are put in separate .c file but in same .c with the form triggering it.
Here is my preferred arrangement: 1. main.c (program entry point and application event loop) 2. routine.c (shared program routines usable by modules) 2. [module1].c 3. [module2].c . . . where module1, module2, ... is name describing what the form is doing. On desktop, Delphi is my usual tools and I get used to using object-oriented approach too. So I'm going to use POL but it may take some time to study it at first. "Steven Fisher" <[EMAIL PROTECTED]> �b�l�� news:[EMAIL PROTECTED] �� ���g... > > A coworker and I are having a bit of an argument over whether or not > multiple forms should be handled by a single source file. I'm a big fan > of considering .c files to be objects, and trying to use an > object-oriented approach to developing forms. However, he's right that > handling related forms with a single .c file takes a lot less source > code (though I'm not really convinced it's that much less object code). > > So, I thought I'd ask here: What are the advantages/disadvantages to > each approach? Have you regretted one extreme or the other? Is some > comfortable middle ground (like related forms in a single .c) a better > approach than either extreme? > > I'm willing to be convinced either way. Please let me know what you > think. :) > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
