We're about to design am enterprise Windows app. Since it will have lots of
modules, we're thinking about a listbar (like Outlook) on the left with menu
bar across the top, and status bar at the bottom. Each "module" would then
take up the space that's remaining. So, it looks like we're wanting some
sort of master form where the module forms show up inside it. Should we
have user controls for each of the modules? I was hoping there would be a
better way to structure the app.

I would appreciate any design guidance.

Thanks,
Ron

Hi,

You should think a little about the design of the "core" that is the part of
the app that will support all the modules and the interaction among them.

For example you should implement a plugin interface to allow modules (or
command) to be added to the toolbars.

Take a look at this article about plugin:
http://www.codeproject.com/csharp/C_...chitecture.asp

Also take a look at how to implement a Command pattern (there was such an
article in MSDN magazine a time ago)

The book of Design patterns is also a good reading as they explain the
design of a text processor.



--
Ignacio Machin
machin AT laceupsolutions com

"Ronald S. Cook" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> We're about to design am enterprise Windows app. Since it will have lots
> of modules, we're thinking about a listbar (like Outlook) on the left with
> menu bar across the top, and status bar at the bottom. Each "module"
> would then take up the space that's remaining. So, it looks like we're
> wanting some sort of master form where the module forms show up inside it.
> Should we have user controls for each of the modules? I was hoping there
> would be a better way to structure the app.
>
> I would appreciate any design guidance.
>
> Thanks,
> Ron
>
>
>

Ronald, you should definitely check out the Composite UI Application
Block (CAB) and the Smart Client Software Factory (SCSF).

On Dec 21, 8:30 am, "Ronald S. Cook" <r...@westinis.com> wrote:
> We're about to design am enterprise Windows app. Since it will have lots of
> modules, we're thinking about a listbar (like Outlook) on the left with menu
> bar across the top, and status bar at the bottom. Each "module" would then
> take up the space that's remaining. So, it looks like we're wanting some
> sort of master form where the module forms show up inside it. Should we
> have user controls for each of the modules? I was hoping there would be a
> better way to structure the app.
>
> I would appreciate any design guidance.
>
> Thanks,
> Ron

I'll re iterate the
Composite UI Application
Block (CAB)


"Ronald S. Cook" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> We're about to design am enterprise Windows app. Since it will have lots
of
> modules, we're thinking about a listbar (like Outlook) on the left with
menu
> bar across the top, and status bar at the bottom. Each "module" would
then
> take up the space that's remaining. So, it looks like we're wanting some
> sort of master form where the module forms show up inside it. Should we
> have user controls for each of the modules? I was hoping there would be a
> better way to structure the app.
>
> I would appreciate any design guidance.
>
> Thanks,
> Ron
>
>
>

Is Composite Application UI Block (CAB) old and now part of Windows
Presentation Foundation (WPF), or is it something totally separate? -thx


"sloan" <(E-Mail Removed)> wrote in message
news:%237N$(E-Mail Removed)...
> I'll re iterate the
> Composite UI Application
> Block (CAB)
>
>
> "Ronald S. Cook" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> We're about to design am enterprise Windows app. Since it will have lots
> of
>> modules, we're thinking about a listbar (like Outlook) on the left with
> menu
>> bar across the top, and status bar at the bottom. Each "module" would
> then
>> take up the space that's remaining. So, it looks like we're wanting some
>> sort of master form where the module forms show up inside it. Should we
>> have user controls for each of the modules? I was hoping there would be
>> a
>> better way to structure the app.
>>
>> I would appreciate any design guidance.
>>
>> Thanks,
>> Ron
>>
>>
>>
>
>