dWebSpec Dictionary
CONTEXT: descriptors->segment->type



All Details Standard Only Platform Only
Structured Web info and helpTechnologies
 Home Page
 Product Page
 Download Page
 Feedback
Javascript Tree Menu
Results for:
 segment.type 
Prev  Topic  Next

The type of segment includes some standard HTML partition elements, like frames, divisions and layers, listed below.

<table>
<frame> (dynamic)
<iframe>(dynamic)
<span>
<div>
<row>
<td>
<layer>

On some platforms, these could have implementation as dynamic components that could allow application of behaviors to their rendering and enabling capabilities.

Apart from the HTML segments, there are other segments that could be demarcated using dWebSpec annotations. They are listed as follows:

inline (default):
This allows demarcation of sections on the pages.


static-include:
Used to demarcate a segment of the page that is included by the server during assembly or compilation. In essence, identical segments could exist in multiple places: reuse. Of which, one of these would be declared as the template. Others would then extend the template.

See attributes extends, base-page-id and value.

dynamic-include: All information concerning static include also pertains to dynamic include. However, the dynamic include does involve dynamic request.

See attributes extends, base-page-id and event-id.

The data aspect of dynamic segments usually involves additional steps for the data interchange to work in cooperation with that of the rest of the page. This is owing to the fact that such segments might not share the same page or request scope with the rest of the page.

The support for dynamic include as well as the impact on bindings, would vary from platform to platform.

insert-include:

This could be similar to the dynamic includes, with the distinction that the assembly process is triggered by external controls rather than actions or directives from within the page. The presence of this tag on a page would normally signify that the page is involved in template scheme.

A page involved in a template scheme could either be the template, in some cases called the master page, or else the page could use a template. The distinction is that the user would specify the template page in use, in the page descriptor.

For the template page, the insert-include segments are those segment that should be or could be replace by the pages using the template. A page using a template would override the segments with its own segments that match the id of those segments in the template.
 ASP.NET  
The types of segments are described below.

inline (default):

This would show in the source content, as shown below:

  <!--aws:segment id="actionEqualNew" -->
    
  . . . . Code for Create . . . .
  <!--/aws:segment -->
This would be implemented as show here. 
<asp:Panel id="actionEqualNew" runat="server" Visible="<%# Action==’NEW’">
 . . . . Code for Create . . . .
 </asp:Panel>

There are other inline segments like <table>, <td< and <tr<, that do not need annotation, but would be translated to their equivalent Web Controls, whenever there are dynamic specifications associated with them in the segment descriptors.

static-include:

Static include is implemented with the include directive. 

<!-- #include file="NavigationButtons.inc" -->

The inc extension of preceding the name with inc_ makes it obvious that a file would be included by others. This is not required; the content might be browsable with the ?inc? extension, it might be thus preferable to use the aspx extension.

The file entry is derived from the value entry of the segment descriptor.

dynamic-include:

Dynamic include, in some sense allows the same facilities as the static-include, except for the fact that the inclusion is done at runtime, rather than at an earlier or deploy time. The file name could also be specified dynamically.

There is no match for this facility on the ASP.NET platform. The suggested avenue for reuse is to build user components, which could be included in any page.

insert-include:

This type of segment is used for template re-use scheme, or the Master page scheme on the ASP.NET platform. From the specification point, ?insert-include? segments are placeholders for segments that could be overridden by client pages using the template.


  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
  <html xmlns="http://www.w3.org/1999/xhtml">

  <head>
  </head>
  <body>
  <!--aws:segment id="CPH1" type="insert-include" -->

  <!--/aws:segment -->
  </body>
  </html>
The implementation of such page would be as follows. 

  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
  <html xmlns="http://www.w3.org/1999/xhtml">

  <head runat="server">
  </head>
  <body>
  <asp:ContentPlaceHolder id="CPH1" runat="server">
  </asp:ContentPlaceHolder>
  </body>
  </html>

The pages that use this template would specify the page above as a template in the page descriptor. All that is needed is for the page to have a segment (content) with the same id as that of the place holders. It would imply an override of the specific content holder. The code segment below, serves as an example. 

  <%@ Page MasterPageFile="master1.master" %>
  <asp:Content ContentPlaceHolderId="CPH1" runat="server">
  <h2>Individual Content</h2>
  <p>Paragraph 1</p>
  <p>Paragraph 2</p>
  </asp:Content>

Prev Next