This leads me to the following questions:
1) I am basically adding pages and customizing the project found on the root folder. What's the solution located in \MonoX\Samples\Solution\ for? Is that a better approach than customizing the pages included with the Monox sample portal?
2) I am having trouble understanding point 14.2 of the pdf manual (Developing custom portal pages). What are exactly
template pages ? I usually think of master pages as templates. If I just add a new aspx page to the project, either with a code behind file or without, I simply register that new page with the Page management administration and the page is displayed (along with any web parts included). Is this approach correct?
New portal pages are dynamically instantiated using the Page management administrative pane.
This process works by copying the desired template page to the desired folder under the name given
to it by the user. Template pages are actually ordinary ASPX pages WITHOUT the accompanying
codebehind files. They usually inherit from the MonoSoftware.MonoX.BasePage class, but you can
create a different class file and use it if you need to implement some kind of codebehind functionality.
Here is a code sample for the default template page:
<%@ Page
Language="C#"
MasterPageFile="/MonoX/MasterPages/Default.master"
AutoEventWireup="true"
Inherits="MonoSoftware.MonoX.BasePage"
Theme="Default"
Title=""
%>
<%@ MasterType TypeName="MonoSoftware.MonoX.BaseMasterPage" %>
<%@ Register TagPrefix="MonoX" TagName="Editor" Src
="/MonoX/ModuleGallery/MonoXHtmlEditor.ascx" %>
<%@ Register Assembly="MonoX.Library" Namespace="MonoSoftware.MonoX"
TagPrefix="portal" %>
<
asp:Content
ID
=
"Content1"
ContentPlaceHolderID
=
"cp"
runat
=
"server"
>
... HTML and ASP.NET markup goes here ...
</
asp:Content
>