Silverlight: Page vs. usercontrol

A

andreycha2011-02-15 18:18:54

Microsoft Silverlight

andreycha, 2011-02-15 18:18:54

Greetings.

There was a need to develop a Silverlight application. The concept is closest to the good old MDI. Relatively speaking, there is a main menu, there are various windows, and you need the ability to work with several windows at the same time.

In this regard, the question arose, what to use when developing individual "windows"?
Pages can be displayed inside a single frame, but then the possibility of simultaneous work is lost.
"Windows" designed as controls, which are placed on the tab control, allow such simultaneous work. But what then is their fundamental difference from the page?

Z.Y. Experience in development in SL is zero, I'm only reading the Internet for the second day.

Reply

Answer the question

In order to leave comments, you need to log in

2 answer(s)

C

Certik, 2011-02-16
@Certik

Sorry, I don't really know the technical side of developing silverlight applications, but I have some experience in testing silverlight and flex applications.
“Windows” as tab controls look pretty elegant, the main difference, as I understand it, is that you can name the tabs themselves.
There is another option - these are windows based on pop-ups. Then a certain common part is made, such as a header, statusbars, etc., plus a panel for calling these windows. And the main workspace is just some, roughly speaking, a box in which the necessary modules open with windows. Respectively. windows can be dragged, resized, etc. But get ready to face a lot of restrictions on both the position of windows and their size.

K

kefirr, 2011-02-16
@kefirr

Page are tailored for navigation within a ContentFrame. Actually, Page is inherited from UserControl, with the addition of properties and methods for navigation.
Since you need simultaneous work and do not need navigation, use UserControl. Unless the Title property can be useful for the window title, but because of one string property, I would not use the “wrong” control.
In any case, I think it's better to immediately make some base class for your "windows", which you can initially inherit from UserControl, and then, if anything, replace it with Page.