Master & Details Page Reload

[Janet]

Hi,

I'm trying to use the master/detail page to display the information of
staff. The master page will display some general information, while the
differen detail pages will show the different kinds of staff details, like
family member details, contact information, etc.

Hence, this case, I'll have
- Staff.master
- Family.aspx
- Contact.aspx

where Family.aspx and Contact.aspx have master page defined as Staff.master.

So if I need to place the items in the menu, I can only use Family.aspx and
Contact.aspx, in order to show the Staff.master details.

The master page has a main "Save" button, and also a "Show" button, so that
when user types in the Staff ID and press the Show button, the page will
load the staff information.

The event of the Show button, of course it's in the master page, where I can
also kick off the loading of master details. However, how can i reload the
child page in this case?

Thanks for your kind help.

Regards,
Janet

 

[Mark Rae]

I'm trying to use the master/detail page to display the information of
staff. The master page will display some general information, while the
differen detail pages will show the different kinds of staff details, like
family member details, contact information, etc.

Hence, this case, I'll have
- Staff.master
- Family.aspx
- Contact.aspx

where Family.aspx and Contact.aspx have master page defined as
Staff.master.

So if I need to place the items in the menu, I can only use Family.aspx
and Contact.aspx, in order to show the Staff.master details.

The master page has a main "Save" button, and also a "Show" button, so
that when user types in the Staff ID and press the Show button, the page
will load the staff information.

The event of the Show button, of course it's in the master page, where I
can also kick off the loading of master details. However, how can i
reload the child page in this case?

MasterPages are designed for providing a common look and feel across your
site - but they should contain only those elements which are common to
several pages e.g. header, menu, logo, layout, JavaScript include files,
links to stylesheets etc.

IMO you should try to avoid coding any actual functionality into your
MasterPages e.g. loading and saving records - this should stay within the
ContentPages themselves.

 

[Janet]

Mark, thanks for the advice.

In this case, what are other options/suggestions that you think it's
feasible to such information display/maintenance page? I have thought of
using Panels/MultiView, but the page will simply load all controls, and I'll
just their visibility. This case, the loading of the page is very heavy.

Please advice.

Thanks.

Janet

 

[Mark Rae]

In this case, what are other options/suggestions that you think it's
feasible to such information display/maintenance page? I have thought of
using Panels/MultiView, but the page will simply load all controls, and
I'll just their visibility. This case, the loading of the page is very
heavy.

Please advice.

As you've already discovered, when it comes to getting good performance from
web apps, small and many is better than big and few.

So make separate ContentPages...

 

[apathetic]

The event of the Show button, of course it's in the master page

Can your child page override the method from the master page? You
could then call something like base.ShowButton_Click() to also call the
master page method once the child has done it's work.

Alternatively, you could call the method by using the Master property
of the child page, e.g. Page.Master.ShowButton_Click().

Tim