UserInterfaceProcess AB and CompositeUI AB

[hB]

Hi,

(I do not know which is the exact newsgroup for this post)

I am doing application based on SOA.
My client app is winforms and we are targeting it as smart client.

I know about MVC in general. And I am puzzled how to go with MVC in my
this Smart Client User Interface (winform based) app.

First I see UIP AB and then CompositeUI AB.
UIP AB looks additional complicated for smart client app considering
Model part and interaction of model with other in MVC. While I like
WindowsFormControlView because we do not have interfaces like series of
Form instead one Form.

Note I want to work striclty on Dot Net 1.1.

Desc:
I have an MDI app client side ui, which is a smart client that it only
talks to server thru Web Svc (the most fundamental part of smart client
apart from rest).

SOA is already there.
I want my Client UI MVC driven.

1) Dot Net + MVC = UIP AB (app block)
2) Dot Net + Smart Client + WinForms = CompositeUI AB (CAB)

For 1) I can have separate controller for separate view (winform or
user control) or one for all or ...
Model is Web Svc. Or like on smart client there is only view and
controller and model thing is web svc which is on server.

Fro 2) I can have my UI as (user controls plus winforms) as smart
widgets and achieve my objective through CAB.

Now what you ppl suggest?
Please advice.

(Plus If I cannot use CAB can I make it source work on dot net 1.1 or
at least can i see its Class Diagram Design?)

Thanks

 

[Dmytro Lapshyn [MVP]]

Hi,

Just FYI:

UserInterfaceProcess AB is known to have poor support for MDI apps - that's
why we had to drop it in one of our commercial projects. The authors might
however have improved it since version 2.0.