Model/View architecture

[jp4symbian]

Hey folks,

I am new to Qt for Symbian, though I have been working on it since the past few months.

I need to develop a Qt application on Symbian having multiple screens/views. I need to retain my data for each view even though its not visible.

So I want to know whether it is necessary or a good practice to use the Model/View architecture in Qt to develop an application?
Or just using widgets / windows would also suffice?

Can anyone please help me out with this?

[divanov]

An answer to both questions is "yes".

[jp4symbian]

hey divanov,

Thanks for the prompt reply.
Actually I want to persist my data, just the way we do in View classes and destroy containers (controls).
But I am finding it a bit difficult to understand/implement similar stuff in Qt.

I cannot keep the widget/window class available just for the data. So I was trying to figure out if Model/View is the way to go or not.
Havent seen a proper multiview app in Qt on Symbian, so that I can get a complete idea.

Could you please clear my doubts?

[divanov]

Good example of MVC pattern implementation in Qt is model/view widgets
http://doc.trolltech.com/4.6/model-v...ogramming.html

[jp4symbian]

Hey,

Thanks. I am already referring to the help on Model/View programming.

Was just looking for some pro advice whether this kind of architecture is an absolute necessity or just a better way to do stuff.
And if it is the norm in Qt like we have the View architecture in Symbian..

[divanov]

Was just looking for some pro advice whether this kind of architecture is an absolute necessity or just a better way to do stuff.

This is general architecture question basically not related to Qt. In simple applications you can avoid using MVC, but with sophisticated designs it would be difficult (however not impossible) to implement this design.

[jp4symbian]

This is general architecture question basically not related to Qt. In simple applications you can avoid using MVC, but with sophisticated designs it would be difficult (however not impossible) to implement this design.

Thanks.