Last post Jun 08, 2005 10:59 AM by BoarK
Jun 08, 2005 10:59 AM|BoarK|LINK
I am reading through the NewBlog source, released by Hans-Peter over at dnn.de, in my quest to learn how to make custom modules of my own.
The NewBlog module has five child modules that reside on the main UI tab. The child modules act like any other module, thus they can be moved around to different panes within the skin. Clicking on some links within the BlogList and ViewBlog
child modules will inject content in the current tab without messing up the layout. However, if you click a ViewEntry or EditEntry link, the resultant control loads in a new tab all by itself breaking the layout.
I've been trying to figure out how the EditEntry control displays itself maximized within a tab while the BlogList and ViewBlog controls restrict themselves to the content pane and adheres to the current skin layout dictated by the tab.
My intention is to have the ViewBlog control display the content of the blog inside the current content pane and not maximized in a tab on its own. I suspect that this "maximized" behaviour is due to the redirection to another control through
the use of a control key.
Could some one please give me some pointers to where I can change these control display settings?
Jun 08, 2005 12:47 PM|BoarK|LINK
This is a reply to the email I sent Hans :
It is not a special setting which I made in NewBlog.
If you register a control in the module definition, each control which has a key defined will be displayed in the admin skin (maximized) In the case you describe:
The EditEntry control is registered with the key "Edit".
And the BlogList is registered without any key.
In my actual version I have done a lot of changes so that the EditEntry is also in the normal skin and not in the admin skin.