Recent Changes - Search:

Introduction to Microcontroller Programming * Course Index * Introduction * About the Author * About this Course * Feedback * Course Navigation * Quick Course Navigation * How to use this Course * Acronyms Used and Course Conventions

About PICmicro Chips * What is a PICmicro? * Microcontrollers * Digital versus Analogue * Inputs and Outputs * Memory * Programming * 16F1937 Architecture

Clocking Your PICmicro Devices * Introduction * The Clock Circuit * Clock Settings * Clock Confusion

E-Blocks * Introduction to E-blocks * Using E-blocks * E-blocks Boards

Flowcode Step By Step * Introduction to Flowcode * Basic Flowcode Functions * Digital Outputs * Digital Inputs * Basic Loops * The LCD Display * Binary Numbers * Decisions * Goto (Connection Point) * 7-Segment Displays * Software Macro * Strings and Memory * A Simple Hi-Fi

PICmicro Projects * Introduction to PICmicro Projects * Construction Methods * Choosing a Power Source * Adding Inputs * Input Conditioning * Adding Outputs * Adding Drivers

Labs * Introduction and Lesson Plan * 1. Output * 2. Delay * 3. Connection Point * 4. Calculations * 5. Loop * 6. Input * 7. Decision * 8. LCD * 9. Keypad * 10. Analogue + EEPROM * 11. Software Macro * 12. External Interrupt * 13. Timer Interrupt

(:Summary:Contains the 'action' links (like Browse, Edit, History, etc.), placed at the top of the page, see site page actions:) (:comment This page can be somewhat complex to figure out the first time you see it. Its contents are documented at PmWiki.SitePageActions if you need help. :) * Print (:comment (:if group Site,SiteAdmin,Cookbook,Profiles,PmWiki*:) (:comment delete if and ifend to enable backlinks:) * %item rel=nofollow class=backlinks accesskey='$[ak_backlinks]'% [[{*$Name}?action=search&q=link={*$FullName} | $[Backlinks] ]] (:ifend:) :) * Login

PmWiki /

BlockMarkup

(:Summary: PmWiki group header. Includes styles and trail.:) (:comment please leave the multiple style definitions concatenated as a single line. Linebreaks do appear in the output when the wiki is configured with linebreaks enabled -- thanks!:) (:comment included in PmWiki localisation headers and footers :)

(:nl:)(:Summary:Markup resulting in paragraphs:)

"Block markup" is a term used in the sources of PmWiki indicating all markups resulting in HTML block elements'^[1]^' or in other words multiple paragraphs and other content.

* Forms * paragraphs * indent/outdent * lists * list items * headings * divisions and semantic HTML5 elements * images * pre * tables

WikiStyles can be applied to blocks, else you don't need to bother about "blockmarkup" as a PmWiki user.

Division blocks

Division <div> HTML blocks are inserted with the (:div:)...(:divend:) markup. You can have the HTML @@id=@@ and @@class=@@ attributes like (:div id=id1 class="class1 class2":). A (:div:) markup automatically closes a previously open such tag. To have nested tags, you need to number the tag, and the matching tag end: 

(:div:)
Outer block
(:div2:)
Inner block
(:div2end:)
(:divend:)

Semantic HTML5 elements

Since version 2.2.75, PmWiki allows the inclusion of a few semantic HTML5 elements. Note that an opening semantic markup automatically closes any previously opened tag of the same type, but does not verify or tidy the structure for you, so make sure you use closing tags when needed.

:(:article:)...(:articleend:):Inserts an <article> tag. You can have the HTML @@id=@@ and @@class=@@ attributes like (:article id=id1 class="class1 class2":). An (:article:) markup automatically closes a previously open such tag. To have nested tags, you need to number the tag, and the matching tag end: 

(:article:)
Outer article
(:article2:)
Inner article
(:article2end:)
(:articleend:)

:(:section:)...(:sectionend:):Inserts a <section> tag. You can have the HTML @@id=@@ and @@class=@@ attributes like (:section id=id1 class="class1 class2":). A (:section:) markup automatically closes a previously open such tag. To have nested tags, you need to number the tag, and the matching tag end, like the (:article:) markup.

:(:header:)...(:headerend:):Inserts a <header> tag. You can have the HTML @@id=@@ and @@class=@@ attributes like (:header id=id1 class="class1 class2":). A (:header:) markup automatically closes a previously open such tag, and it is not possible to nest such tags.

:(:footer:)...(:footerend:):Inserts a <footer> tag. You can have the HTML @@id=@@ and @@class=@@ attributes like (:footer id=id1 class="class1 class2":). A (:footer:) markup automatically closes a previously open such tag, and it is not possible to nest such tags.

:(:aside:)...(:asideend:):Inserts an <aside> tag. You can have the HTML @@id=@@ and @@class=@@ attributes like (:aside id=id1 class="class1 class2":). An (:aside:) markup automatically closes a previously open such tag, and it is not possible to nest such tags.

:(:address:)...(:addressend:):Inserts an <address> tag. You can have the HTML @@id=@@ and @@class=@@ attributes like (:address id=id1 class="class1 class2":). An (:address:) markup automatically closes a previously open such tag, and it is not possible to nest such tags.

:(:nav:)...(:navend:):Inserts a <nav> tag. You can have the HTML @@id=@@ and @@class=@@ attributes like (:nav id=id1 class="class1 class2":). A (:nav:) markup automatically closes a previously open such tag, and it is not possible to nest such tags.

:(:details summary="Summary":)...(:detailsend:):Inserts a <details> and embedded <summary> section. Standard-compliant browsers will only show the summary, and the user can click on it to open the full section, without a need for JavaScript. A (:details:) markup automatically closes a previously open such tag. To have nested tags, you need to number the tag, and the matching tag end, like the (:article:) markup. This is a recent addition to the HTML5 standard, see https://caniuse.com/#feat=details for current browser support (browsers that do not support it show the section open). 

(:details summary="Click for more information...":)
Here is the content of the <details> section.
(:detailsend:)
Click for more information...

Here is the content of the <details> section.

: : To have a details section open by default, add the attribute @@open=open@@ like (:details open=open summary="Summary":)

See also

* BlockMarkup &nbsp; Markup resulting in paragraphs * ConditionalMarkup &nbsp; The if directive allows portions of a page to be included or excluded from rendering * CustomMarkup &nbsp; Using the Markup() function for custom wiki syntax; migration to PHP 5.5 * MarkupExpressions &nbsp; String and formatting operations * Markup Master Index &nbsp; Tabulation of all PmWiki markup

(:nl:)(:Summary:Trail and talk page links:) (:comment included in PmWiki localisation headers and footers :) <<? >>bgcolor=#ffe border-top="1px solid black" font-size=.8em<< This page may have a more recent version on pmwiki.org: PmWiki:BlockMarkup, and a talk page: PmWiki:BlockMarkup-Talk. >><<

(:Summary: Website page footer:)

Print - (:comment (:if group Site,SiteAdmin,Cookbook,Profiles,PmWiki*:) (:comment delete if and ifend to enable backlinks:) %item rel=nofollow class=backlinks accesskey='$[ak_backlinks]'% [[{*$Name}?action=search&q=link={*$FullName} | $[Backlinks] ]] (:ifend:) :) Search - Login

Page last modified on June 07, 2020, at 01:07 AM