What are the best practices for multiple programmers to program in a single MDI application?
Should a large project be divided up into multiple MDI programs where only related functionality is in a particular MDI exe?
Should each potential window or formset have only the gui code in the MDI app and the functionality, validation, io etc come from a DLL?
Dumb question. Can there be more than one resource file per exe? I've not seen it so I assumed it was impossible.
What steps do different shops go through to test each part by different programmers without affecting the whole?
I'm trying to take our main application away from 420 small exe's that are tied to one multi-tiered menu. The upside to this approach is that every unique functionality is in one exe, hence all a programmer has to do is check it out and no one else can mess with it until it's finished. We use test areas, and different directories for TEST BAS'S TEST INC'S, the REVIEWED directories, then our stable beta area and finally code repository for what the customer's actually have.
One man shops don't have this problem, but I have to control and simplify the efforts of six programmers with standard includes and wrappers for common functionality that we use through our app.
Also, it's become a management priority to become either MDI or multi-windowed architecture.
I've thought about using #IF %DEF/ENDIF conditional compiles that would allow an INCLUDE FILE TO be run and tested independently.
In other words, if a certain equate is true don't compile repetitive code, but if it's not compile it all.
Also every generalized include for dialog and control creation would have the same conditional compile.
What is the best track for a team of programmers to use with PowerBasic.
Bob Mechler
Should a large project be divided up into multiple MDI programs where only related functionality is in a particular MDI exe?
Should each potential window or formset have only the gui code in the MDI app and the functionality, validation, io etc come from a DLL?
Dumb question. Can there be more than one resource file per exe? I've not seen it so I assumed it was impossible.
What steps do different shops go through to test each part by different programmers without affecting the whole?
I'm trying to take our main application away from 420 small exe's that are tied to one multi-tiered menu. The upside to this approach is that every unique functionality is in one exe, hence all a programmer has to do is check it out and no one else can mess with it until it's finished. We use test areas, and different directories for TEST BAS'S TEST INC'S, the REVIEWED directories, then our stable beta area and finally code repository for what the customer's actually have.
One man shops don't have this problem, but I have to control and simplify the efforts of six programmers with standard includes and wrappers for common functionality that we use through our app.
Also, it's become a management priority to become either MDI or multi-windowed architecture.
I've thought about using #IF %DEF/ENDIF conditional compiles that would allow an INCLUDE FILE TO be run and tested independently.
In other words, if a certain equate is true don't compile repetitive code, but if it's not compile it all.
Code:
Something like: #ID NOT %DEF(%PRG_PROGM1) THEN FUNCTION PBMAIN AS LONG #ELSE FUNCTION PRG_PROGM1(PRM1,PRM2....) #ENDIF
What is the best track for a team of programmers to use with PowerBasic.
Bob Mechler
Comment