Last post Jun 23, 2005 11:32 PM by RLyda
Jun 23, 2005 05:47 AM|wilsonjan|LINK
Jun 23, 2005 09:32 AM|codegalaxy|LINK
Jun 23, 2005 10:22 AM|wilsonjan|LINK
Jun 23, 2005 12:52 PM|codegalaxy|LINK
Jun 23, 2005 02:49 PM|RLyda|LINK
Jun 23, 2005 02:59 PM|codegalaxy|LINK
Jun 23, 2005 03:24 PM|wilsonjan|LINK
OK, so I'm getting the impression that this can't be done automatically. By that I mean it can't be done through any kind of configuration of a module and/or page in DNN.
Replies have stated that a view control could render the appropriate controls by inspecting parameters. Would this view be constrained to the phyical boundary of a module in the pane that it appears or can I dynamically load another control in to another pane?
If so, how could I locate a pane on the page?
Sorry if this is dragging on, I really do appreciate your replies.
Jun 23, 2005 08:05 PM|cniknet|LINK
Jun 23, 2005 11:32 PM|RLyda|LINK
I can certainly see instances where one would WANT to isolate a module's edit control on a seperate page. But that's a choice. If the edit contents are many fields, long text, or significant enough to require reall focused attention from the user, then
I would choose a seperate page.
But the core code SHOULD be changed to use whatever the main view control's page skin & container were! This would relieve a lot of the fuss over the aesthetics... Sure, I can make the default page and "Admin" page skins the same--but then that's not really
and "Admin" skin now is it?!?! If you're on a seperate page for a core "Admin" module, then use the "Admin" skin.....but if I'm just editing a simple third party control, then respect my primary choice of skin!
While presrving the primary skin like that would address the aesthetics, there are also functional reasons to want to switch controls "in place" instead of switching to a seperate page... Again, the coder can choose....seems like a NavigateURL param choice