- CKEditor Samples » Create and Destroy Editor Instances for Ajax Applications -
-
- This sample shows how to create and destroy CKEditor instances on the fly. After the removal of CKEditor the content created inside the editing
- area will be displayed in a <div> element.
-
- For details of how to create this setup check the source code of this sample page - for JavaScript code responsible for the creation and destruction of a CKEditor instance. -
-Click the buttons to create and remove a CKEditor instance.
-- - -
- -- CKEditor Samples » Using CKEditor JavaScript API -
-- This sample shows how to use the - CKEditor JavaScript API - to interact with the editor at runtime. -
-- For details on how to create this setup check the source code of this sample page. -
-- CKEditor Samples » Append To Page Element Using JavaScript Code -
-
- The CKEDITOR.appendTo() method serves to to place editors inside existing DOM elements. Unlike CKEDITOR.replace(),
- a target container to be replaced is no longer necessary. A new editor
- instance is inserted directly wherever it is desired.
-
CKEDITOR.appendTo( 'container_id',
- { /* Configuration options to be used. */ }
- 'Editor content to be used.'
-);
- - - - diff --git a/cgi-bin/html/ckeditor/samples/old/assets/inlineall/logo.png b/cgi-bin/html/ckeditor/samples/old/assets/inlineall/logo.png deleted file mode 100644 index b4d5979..0000000 Binary files a/cgi-bin/html/ckeditor/samples/old/assets/inlineall/logo.png and /dev/null differ diff --git a/cgi-bin/html/ckeditor/samples/old/assets/outputxhtml/outputxhtml.css b/cgi-bin/html/ckeditor/samples/old/assets/outputxhtml/outputxhtml.css deleted file mode 100644 index 726d95c..0000000 --- a/cgi-bin/html/ckeditor/samples/old/assets/outputxhtml/outputxhtml.css +++ /dev/null @@ -1,204 +0,0 @@ -/* - * Copyright (c) 2003-2017, CKSource - Frederico Knabben. All rights reserved. - * For licensing, see LICENSE.md or https://ckeditor.com/legal/ckeditor-oss-license - * - * Styles used by the XHTML 1.1 sample page (xhtml.html). - */ - -/** - * Basic definitions for the editing area. - */ -body -{ - font-family: Arial, Verdana, sans-serif; - font-size: 80%; - color: #000000; - background-color: #ffffff; - padding: 5px; - margin: 0px; -} - -/** - * Core styles. - */ - -.Bold -{ - font-weight: bold; -} - -.Italic -{ - font-style: italic; -} - -.Underline -{ - text-decoration: underline; -} - -.StrikeThrough -{ - text-decoration: line-through; -} - -.Subscript -{ - vertical-align: sub; - font-size: smaller; -} - -.Superscript -{ - vertical-align: super; - font-size: smaller; -} - -/** - * Font faces. - */ - -.FontComic -{ - font-family: 'Comic Sans MS'; -} - -.FontCourier -{ - font-family: 'Courier New'; -} - -.FontTimes -{ - font-family: 'Times New Roman'; -} - -/** - * Font sizes. - */ - -.FontSmaller -{ - font-size: smaller; -} - -.FontLarger -{ - font-size: larger; -} - -.FontSmall -{ - font-size: 8pt; -} - -.FontBig -{ - font-size: 14pt; -} - -.FontDouble -{ - font-size: 200%; -} - -/** - * Font colors. - */ -.FontColor1 -{ - color: #ff9900; -} - -.FontColor2 -{ - color: #0066cc; -} - -.FontColor3 -{ - color: #ff0000; -} - -.FontColor1BG -{ - background-color: #ff9900; -} - -.FontColor2BG -{ - background-color: #0066cc; -} - -.FontColor3BG -{ - background-color: #ff0000; -} - -/** - * Indentation. - */ - -.Indent1 -{ - margin-left: 40px; -} - -.Indent2 -{ - margin-left: 80px; -} - -.Indent3 -{ - margin-left: 120px; -} - -/** - * Alignment. - */ - -.JustifyLeft -{ - text-align: left; -} - -.JustifyRight -{ - text-align: right; -} - -.JustifyCenter -{ - text-align: center; -} - -.JustifyFull -{ - text-align: justify; -} - -/** - * Other. - */ - -code -{ - font-family: courier, monospace; - background-color: #eeeeee; - padding-left: 1px; - padding-right: 1px; - border: #c0c0c0 1px solid; -} - -kbd -{ - padding: 0px 1px 0px 1px; - border-width: 1px 2px 2px 1px; - border-style: solid; -} - -blockquote -{ - color: #808080; -} diff --git a/cgi-bin/html/ckeditor/samples/old/assets/posteddata.php b/cgi-bin/html/ckeditor/samples/old/assets/posteddata.php deleted file mode 100644 index b1e4baf..0000000 --- a/cgi-bin/html/ckeditor/samples/old/assets/posteddata.php +++ /dev/null @@ -1,59 +0,0 @@ - - - - - -
- CKEditor — Posted Data -
-| Field Name | -Value | -
|---|---|
| - | - |
- CKEditor Samples » Data Filtering and Features Activation -
-- This sample page demonstrates the idea of Advanced Content Filter - (ACF), a sophisticated - tool that takes control over what kind of data is accepted by the editor and what - kind of output is produced. -
-When and what is being filtered?
-- ACF controls - every single source of data that comes to the editor. - It process both HTML that is inserted manually (i.e. pasted by the user) - and programmatically like: -
--editor.setData( '<p>Hello world!</p>' ); --
- ACF discards invalid, - useless HTML tags and attributes so the editor remains "clean" during - runtime. ACF behaviour - can be configured and adjusted for a particular case to prevent the - output HTML (i.e. in CMS systems) from being polluted. - - This kind of filtering is a first, client-side line of defense - against "tag soups", - the tool that precisely restricts which tags, attributes and styles - are allowed (desired). When properly configured, ACF - is an easy and fast way to produce a high-quality, intentionally filtered HTML. -
- -How to configure or disable ACF?
-
- Advanced Content Filter is enabled by default, working in "automatic mode", yet
- it provides a set of easy rules that allow adjusting filtering rules
- and disabling the entire feature when necessary. The config property
- responsible for this feature is config.allowedContent.
-
- By "automatic mode" is meant that loaded plugins decide which kind
- of content is enabled and which is not. For example, if the link
- plugin is loaded it implies that <a> tag is
- automatically allowed. Each plugin is given a set
- of predefined ACF rules
- that control the editor until
- config.allowedContent
- is defined manually.
-
- Let's assume our intention is to restrict the editor to accept (produce) paragraphs
- only: no attributes, no styles, no other tags.
- With ACF
- this is very simple. Basically set
- config.allowedContent to 'p':
-
-var editor = CKEDITOR.replace( textarea_id, {
- allowedContent: 'p'
-} );
-
- - Now try to play with allowed content: -
--// Trying to insert disallowed tag and attribute. -editor.setData( '<p style="color: red">Hello <em>world</em>!</p>' ); -alert( editor.getData() ); - -// Filtered data is returned. -"<p>Hello world!</p>" --
- What happened? Since config.allowedContent: 'p' is set the editor assumes
- that only plain <p> are accepted. Nothing more. This is why
- style attribute and <em> tag are gone. The same
- filtering would happen if we pasted disallowed HTML into this editor.
-
- This is just a small sample of what ACF - can do. To know more, please refer to the sample section below and - the official Advanced Content Filter guide. -
-
- You may, of course, want CKEditor to avoid filtering of any kind.
- To get rid of ACF,
- basically set
- config.allowedContent to true like this:
-
-CKEDITOR.replace( textarea_id, {
- allowedContent: true
-} );
-
-
- Beyond data flow: Features activation
-
- ACF is far more than
- I/O control: the entire
- UI of the editor is adjusted to what
- filters restrict. For example: if <a> tag is
- disallowed
- by ACF,
- then accordingly link command, toolbar button and link dialog
- are also disabled. Editor is smart: it knows which features must be
- removed from the interface to match filtering rules.
-
- CKEditor can be far more specific. If <a> tag is
- allowed by filtering rules to be used but it is restricted
- to have only one attribute (href)
- config.allowedContent = 'a[!href]', then
- "Target" tab of the link dialog is automatically disabled as target
- attribute isn't included in ACF rules
- for <a>. This behaviour applies to dialog fields, context
- menus and toolbar buttons.
-
Sample configurations
-- There are several editor instances below that present different - ACF setups. All of them, - except the inline instance, share the same HTML content to visualize - how different filtering rules affect the same input data. -
-
- This editor is using default configuration ("automatic mode"). It means that
-
- config.allowedContent is defined by loaded plugins.
- Each plugin extends filtering rules to make it's own associated content
- available for the user.
-
- -
- This editor is using a custom configuration for - ACF: -
-
-CKEDITOR.replace( 'editor2', {
- allowedContent:
- 'h1 h2 h3 p blockquote strong em;' +
- 'a[!href];' +
- 'img(left,right)[!src,alt,width,height];' +
- 'table tr th td caption;' +
- 'span{!font-family};' +'
- 'span{!color};' +
- 'span(!marker);' +
- 'del ins'
-} );
-
- - The following rules may require additional explanation: -
--
-
-
-
h1 h2 h3 p blockquote strong em- These tags - are accepted by the editor. Any tag attributes will be discarded. -
- -
-
a[!href]-hrefattribute is obligatory - for<a>tag. Tags without this attribute - are disarded. No other attribute will be accepted. -
- -
-
img(left,right)[!src,alt,width,height]-src- attribute is obligatory for<img>tag. -alt,width,height- andclassattributes are accepted but -classmust be eitherclass="left"- orclass="right"-
- -
-
table tr th td caption- These tags - are accepted by the editor. Any tag attributes will be discarded. -
- -
-
span{!font-family},span{!color}, -span(!marker)-<span>tags - will be accepted if eitherfont-familyor -colorstyle is set orclass="marker"- is present. -
- -
-
del ins- These tags - are accepted by the editor. Any tag attributes will be discarded. -
-
- Please note that UI of the
- editor is different. It's a response to what happened to the filters.
- Since text-align isn't allowed, the align toolbar is gone.
- The same thing happened to subscript/superscript, strike, underline
- (<u>, <sub>, <sup>
- are disallowed by
- config.allowedContent) and many other buttons.
-
- -
- This editor is using a custom configuration for - ACF. - Note that filters can be configured as an object literal - as an alternative to a string-based definition. -
-
-CKEDITOR.replace( 'editor3', {
- allowedContent: {
- 'b i ul ol big small': true,
- 'h1 h2 h3 p blockquote li': {
- styles: 'text-align'
- },
- a: { attributes: '!href,target' },
- img: {
- attributes: '!src,alt',
- styles: 'width,height',
- classes: 'left,right'
- }
- }
-} );
-
- - -
- This editor is using a custom set of plugins and buttons. -
-
-CKEDITOR.replace( 'editor4', {
- removePlugins: 'bidi,font,forms,flash,horizontalrule,iframe,justify,table,tabletools,smiley',
- removeButtons: 'Anchor,Underline,Strike,Subscript,Superscript,Image',
- format_tags: 'p;h1;h2;h3;pre;address'
-} );
-
-
- As you can see, removing plugins and buttons implies filtering.
- Several tags are not allowed in the editor because there's no
- plugin/button that is responsible for creating and editing this
- kind of content (for example: the image is missing because
- of removeButtons: 'Image'). The conclusion is that
- ACF works "backwards"
- as well: modifying UI
- elements is changing allowed content rules.
-
- -
- This editor is built on editable <h1> element.
- ACF takes care of
- what can be included in <h1>. Note that there
- are no block styles in Styles combo. Also why lists, indentation,
- blockquote, div, form and other buttons are missing.
-
- ACF makes sure that
- no disallowed tags will come to <h1> so the final
- markup is valid. If the user tried to paste some invalid HTML
- into this editor (let's say a list), it would be automatically
- converted into plain text.
-
- Apollo 11 was the spaceflight that landed the first humans, Americans Neil Armstrong and Buzz Aldrin, on the Moon on July 20, 1969, at 20:18 UTC. -
-- -
- This editor is using a custom configuration for ACF.
- It's using the
- Disallowed Content property of the filter to eliminate all title attributes.
-
-CKEDITOR.replace( 'editor6', {
- allowedContent: {
- 'b i ul ol big small': true,
- 'h1 h2 h3 p blockquote li': {
- styles: 'text-align'
- },
- a: {attributes: '!href,target'},
- img: {
- attributes: '!src,alt',
- styles: 'width,height',
- classes: 'left,right'
- }
- },
- disallowedContent: '*{title*}'
-} );
-
- - -
- This editor is using a custom configuration for ACF.
- It's using the
- Disallowed Content property of the filter to eliminate all a and img tags,
- while allowing all other tags.
-
-CKEDITOR.replace( 'editor7', {
- allowedContent: {
- // Allow all content.
- $1: {
- elements: CKEDITOR.dtd,
- attributes: true,
- styles: true,
- classes: true
- }
- },
- disallowedContent: 'img a'
-} );
-
- - CKEditor Samples » Using CKEditor Dialog API -
-- This sample shows how to use the - CKEditor Dialog API - to customize CKEditor dialog windows without changing the original editor code. - The following customizations are being done in the example below: -
-- For details on how to create this setup check the source code of this sample page. -
-A custom dialog is added to the editors using the pluginsLoaded event, from an external dialog definition file:
-
-
- Creating a custom dialog window – "My Dialog" dialog window opened with the "My Dialog" toolbar button. -
- Creating a custom button – Add button to open the dialog with "My Dialog" toolbar button. -
The below editor modify the dialog definition of the above added dialog using the dialogDefinition event:
-
-
- Adding dialog tab – Add new tab "My Tab" to dialog window. -
- Removing a dialog window tab – Remove "Second Tab" page from the dialog window. -
- Adding dialog window fields – Add "My Custom Field" to the dialog window. -
- Removing dialog window field – Remove "Select Field" selection field from the dialog window. -
- Setting default values for dialog window fields – Set default value of "Text Field" text field. -
- Setup initial focus for dialog window – Put initial focus on "My Custom Field" text field. -
- CKEditor Samples » Replace DIV with CKEditor on the Fly -
-
- This sample shows how to automatically replace <div> elements
- with a CKEditor instance on the fly, following user's doubleclick. The content
- that was previously placed inside the <div> element will now
- be moved into CKEditor editing area.
-
- For details on how to create this setup check the source code of this sample page. -
-
- Double-click any of the following <div> elements to transform them into
- editor instances.
-
- Part 1 -
-- Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Cras et ipsum quis mi - semper accumsan. Integer pretium dui id massa. Suspendisse in nisl sit amet urna - rutrum imperdiet. Nulla eu tellus. Donec ante nisi, ullamcorper quis, fringilla - nec, sagittis eleifend, pede. Nulla commodo interdum massa. Donec id metus. Fusce - eu ipsum. Suspendisse auctor. Phasellus fermentum porttitor risus. -
-- Part 2 -
-- Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Cras et ipsum quis mi - semper accumsan. Integer pretium dui id massa. Suspendisse in nisl sit amet urna - rutrum imperdiet. Nulla eu tellus. Donec ante nisi, ullamcorper quis, fringilla - nec, sagittis eleifend, pede. Nulla commodo interdum massa. Donec id metus. Fusce - eu ipsum. Suspendisse auctor. Phasellus fermentum porttitor risus. -
-- Donec velit. Mauris massa. Vestibulum non nulla. Nam suscipit arcu nec elit. Phasellus - sollicitudin iaculis ante. Ut non mauris et sapien tincidunt adipiscing. Vestibulum - vitae leo. Suspendisse nec mi tristique nulla laoreet vulputate. -
-- Part 3 -
-- Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Cras et ipsum quis mi - semper accumsan. Integer pretium dui id massa. Suspendisse in nisl sit amet urna - rutrum imperdiet. Nulla eu tellus. Donec ante nisi, ullamcorper quis, fringilla - nec, sagittis eleifend, pede. Nulla commodo interdum massa. Donec id metus. Fusce - eu ipsum. Suspendisse auctor. Phasellus fermentum porttitor risus. -
-- CKEditor Samples » ENTER Key Configuration -
-
- This sample shows how to configure the Enter and Shift+Enter keys
- to perform actions specified in the
- enterMode
- and shiftEnterMode
- parameters, respectively.
- You can choose from the following options:
-
-
-
ENTER_P– new<p>paragraphs are created;
- ENTER_BR– lines are broken with<br>elements;
- ENTER_DIV– new<div>blocks are created.
-
- The sample code below shows how to configure CKEditor to create a <div> block when Enter key is pressed.
-
-CKEDITOR.replace( 'textarea_id', {
- enterMode: CKEDITOR.ENTER_DIV
-});
-
- Note that textarea_id in the code above is the id attribute of
- the <textarea> element to be replaced.
-
- -
- -
- - - - diff --git a/cgi-bin/html/ckeditor/samples/old/htmlwriter/assets/outputforflash/outputforflash.fla b/cgi-bin/html/ckeditor/samples/old/htmlwriter/assets/outputforflash/outputforflash.fla deleted file mode 100644 index 27e68cc..0000000 Binary files a/cgi-bin/html/ckeditor/samples/old/htmlwriter/assets/outputforflash/outputforflash.fla and /dev/null differ diff --git a/cgi-bin/html/ckeditor/samples/old/htmlwriter/assets/outputforflash/outputforflash.swf b/cgi-bin/html/ckeditor/samples/old/htmlwriter/assets/outputforflash/outputforflash.swf deleted file mode 100644 index dbe17b6..0000000 Binary files a/cgi-bin/html/ckeditor/samples/old/htmlwriter/assets/outputforflash/outputforflash.swf and /dev/null differ diff --git a/cgi-bin/html/ckeditor/samples/old/htmlwriter/assets/outputforflash/swfobject.js b/cgi-bin/html/ckeditor/samples/old/htmlwriter/assets/outputforflash/swfobject.js deleted file mode 100644 index 0700921..0000000 --- a/cgi-bin/html/ckeditor/samples/old/htmlwriter/assets/outputforflash/swfobject.js +++ /dev/null @@ -1,19 +0,0 @@ -var swfobject=function(){function w(){if(!u){try{var a=d.getElementsByTagName("body")[0].appendChild(d.createElement("span"));a.parentNode.removeChild(a)}catch(b){return}u=!0;for(var a=z.length,c=0;c
- CKEditor Samples » Producing Flash Compliant HTML Output -
-
- This sample shows how to configure CKEditor to output
- HTML code that can be used with
-
- Adobe Flash.
- The code will contain a subset of standard HTML elements like <b>,
- <i>, and <p> as well as HTML attributes.
-
- To add a CKEditor instance outputting Flash compliant HTML code, load the editor using a standard - JavaScript call, and define CKEditor features to use HTML elements and attributes. -
-- For details on how to create this setup check the source code of this sample page. -
-- To see how it works, create some content in the editing area of CKEditor on the left - and send it to the Flash object on the right side of the page by using the - Send to Flash button. -
-|
-
-
- - - - |
- - - | -
- CKEditor Samples » Producing HTML Compliant Output -
-
- This sample shows how to configure CKEditor to output valid
- HTML 4.01 code.
- Traditional HTML elements like <b>,
- <i>, and <font> are used in place of
- <strong>, <em>, and CSS styles.
-
- To add a CKEditor instance outputting legacy HTML 4.01 code, load the editor using a standard - JavaScript call, and define CKEditor features to use the HTML compliant elements and attributes. -
-- A snippet of the configuration code can be seen below; check the source of this page for - full definition: -
-
-CKEDITOR.replace( 'textarea_id', {
- coreStyles_bold: { element: 'b' },
- coreStyles_italic: { element: 'i' },
-
- fontSize_style: {
- element: 'font',
- attributes: { 'size': '#(size)' }
- }
-
- ...
-});
- - CKEditor Samples -
-- Basic Samples -
--
-
- Replace textarea elements by class name -
- Automatic replacement of all textarea elements of a given class with a CKEditor instance. - -
- Replace textarea elements by code -
- Replacement of textarea elements with CKEditor instances by using a JavaScript call. - -
- Create editors with jQuery -
- Creating standard and inline CKEditor instances with jQuery adapter. -
- Basic Customization -
--
-
- User Interface color -
- Changing CKEditor User Interface color and adding a toolbar button that lets the user set the UI color. - -
- User Interface languages -
- Changing CKEditor User Interface language and adding a drop-down list that lets the user choose the UI language. -
Plugins
--
-
- Magicline plugin -
- Using the Magicline plugin to access difficult focus spaces. - -
- Full page support -
- CKEditor inserted with a JavaScript call and used to edit the whole page from <html> to </html>. -
- Inline Editing -
--
-
- Massive inline editor creation -
- Turn all elements with
contentEditable = trueattribute into inline editors.
-
- - Convert element into an inline editor by code -
- Conversion of DOM elements into inline CKEditor instances by using a JavaScript call. - -
- Replace textarea with inline editor New! -
- A form with a textarea that is replaced by an inline editor at runtime. - - -
- Advanced Samples -
--
-
- Data filtering and features activation New! -
- Data filtering and automatic features activation basing on configuration. - -
- Replace DIV elements on the fly -
- Transforming a
divelement into an instance of CKEditor with a mouse click.
-
- - Append editor instances -
- Appending editor instances to existing DOM elements. - -
- Create and destroy editor instances for Ajax applications -
- Creating and destroying CKEditor instances on the fly and saving the contents entered into the editor window. - -
- Basic usage of the API -
- Using the CKEditor JavaScript API to interact with the editor at runtime. - -
- XHTML-compliant style -
- Configuring CKEditor to produce XHTML 1.1 compliant attributes and styles. - -
- Read-only mode -
- Using the readOnly API to block introducing changes to the editor contents. - -
- "Tab" key-based navigation -
- Navigating among editor instances with tab key. - - - -
- Using the JavaScript API to customize dialog windows -
- Using the dialog windows API to customize dialog windows without changing the original editor code. - -
- Using the "Enter" key in CKEditor -
- Configuring the behavior of Enter and Shift+Enter keys. - -
- Output for Flash -
- Configuring CKEditor to produce HTML code that can be used with Adobe Flash. - -
- Output HTML -
- Configuring CKEditor to produce legacy HTML 4 code. - -
- Toolbar Configurations -
- Configuring CKEditor to display full or custom toolbar layout. - -
CKEditor Samples » Massive inline editing
-This sample page demonstrates the inline editing feature - CKEditor instances will be created automatically from page elements with contentEditable attribute set to value true:
-<div contenteditable="true" > ... </div>-
Click inside of any element below to start editing.
-
- CKEditor
Goes Inline!
-
- - Lorem ipsum dolor sit amet dolor duis blandit vestibulum faucibus a, tortor. -
-- Lorem ipsum dolor sit amet enim. Etiam ullamcorper. Suspendisse a pellentesque dui, non felis. Maecenas malesuada elit lectus felis, malesuada ultricies. -
-- Curabitur et ligula. Ut molestie a, ultricies porta urna. Vestibulum commodo volutpat a, convallis ac, laoreet enim. Phasellus fermentum in, dolor. Pellentesque facilisis. Nulla imperdiet sit amet magna. Vestibulum dapibus, mauris nec malesuada fames ac. -
-- Fusce vitae porttitor -
-- - Lorem ipsum dolor sit amet dolor. Duis blandit vestibulum faucibus a, tortor. - -
-- Proin nunc justo felis mollis tincidunt, risus risus pede, posuere cubilia Curae, Nullam euismod, enim. Etiam nibh ultricies dolor ac dignissim erat volutpat. Vivamus fermentum nisl nulla sem in metus. Maecenas wisi. Donec nec erat volutpat. -
---- Fusce vitae porttitor a, euismod convallis nisl, blandit risus tortor, pretium. - Vehicula vitae, imperdiet vel, ornare enim vel sodales rutrum -
-
--- Libero nunc, rhoncus ante ipsum non ipsum. Nunc eleifend pede turpis id sollicitudin fringilla. Phasellus ultrices, velit ac arcu. -
-
Pellentesque nunc. Donec suscipit erat. Pellentesque habitant morbi tristique ullamcorper.
-Mauris mattis feugiat lectus nec mauris. Nullam vitae ante.
- Integer condimentum sit amet -
-- Aenean nonummy a, mattis varius. Cras aliquet. - Praesent magna non mattis ac, rhoncus nunc, rhoncus eget, cursus pulvinar mollis.
-Proin id nibh. Sed eu libero posuere sed, lectus. Phasellus dui gravida gravida feugiat mattis ac, felis.
-Integer condimentum sit amet, tempor elit odio, a dolor non ante at sapien. Sed ac lectus. Nulla ligula quis eleifend mi, id leo velit pede cursus arcu id nulla ac lectus. Phasellus vestibulum. Nunc viverra enim quis diam.
-- Praesent wisi accumsan sit amet nibh -
-Donec ullamcorper, risus tortor, pretium porttitor. Morbi quam quis lectus non leo.
-Integer faucibus scelerisque. Proin faucibus at, aliquet vulputate, odio at eros. Fusce gravida, erat vitae augue. Fusce urna fringilla gravida.
-In hac habitasse platea dictumst. Praesent wisi accumsan sit amet nibh. Maecenas orci luctus a, lacinia quam sem, posuere commodo, odio condimentum tempor, pede semper risus. Suspendisse pede. In hac habitasse platea dictumst. Nam sed laoreet sit amet erat. Integer.
-
- 
-
Quisque justo neque, mattis sed, fermentum ultrices posuere cubilia Curae, Vestibulum elit metus, quis placerat ut, lectus. Ut sagittis, nunc libero, egestas consequat lobortis velit rutrum ut, faucibus turpis. Fusce porttitor, nulla quis turpis. Nullam laoreet vel, consectetuer tellus suscipit ultricies, hendrerit wisi. Donec odio nec velit ac nunc sit amet, accumsan cursus aliquet. Vestibulum ante sit amet sagittis mi.
-- Nullam laoreet vel consectetuer tellus suscipit -
--
-
- Ut sagittis, nunc libero, egestas consequat lobortis velit rutrum ut, faucibus turpis. -
- Fusce porttitor, nulla quis turpis. Nullam laoreet vel, consectetuer tellus suscipit ultricies, hendrerit wisi. -
- Mauris eget tellus. Donec non felis. Nam eget dolor. Vestibulum enim. Donec. -
Quisque justo neque, mattis sed, fermentum ultrices posuere cubilia Curae, Vestibulum elit metus, quis placerat ut, lectus.
-Nullam laoreet vel, consectetuer tellus suscipit ultricies, hendrerit wisi. Ut sagittis, nunc libero, egestas consequat lobortis velit rutrum ut, faucibus turpis. Fusce porttitor, nulla quis turpis.
-Donec odio nec velit ac nunc sit amet, accumsan cursus aliquet. Vestibulum ante sit amet sagittis mi. Sed in nonummy faucibus turpis. Mauris eget tellus. Donec non felis. Nam eget dolor. Vestibulum enim. Donec.
-- inline, editing, floating, CKEditor -
-- CKEditor Samples » Inline Editing by Code -
-- This sample shows how to create an inline editor instance of CKEditor. It is created - with a JavaScript call using the following code: -
--// This property tells CKEditor to not activate every element with contenteditable=true element. -CKEDITOR.disableAutoInline = true; - -var editor = CKEDITOR.inline( document.getElementById( 'editable' ) ); --
- Note that editable in the code above is the id
- attribute of the <div> element to be converted into an inline instance.
-
Apollo 11
-
- Apollo 11 was the spaceflight that landed the first humans, Americans Neil Armstrong and Buzz Aldrin, on the Moon on July 20, 1969, at 20:18 UTC. Armstrong became the first to step onto the lunar surface 6 hours later on July 21 at 02:56 UTC.
- -Armstrong spent about three and a half two and a half hours outside the spacecraft, Aldrin slightly less; and together they collected 47.5 pounds (21.5 kg) of lunar material for return to Earth. A third member of the mission, Michael Collins, piloted the command spacecraft alone in lunar orbit until Armstrong and Aldrin returned to it for the trip back to Earth.
Broadcasting and quotes
- -Broadcast on live TV to a world-wide audience, Armstrong stepped onto the lunar surface and described the event as:
- --- -One small step for [a] man, one giant leap for mankind.
-
Apollo 11 effectively ended the Space Race and fulfilled a national goal proposed in 1961 by the late U.S. President John F. Kennedy in a speech before the United States Congress:
- --- -[...] before this decade is out, of landing a man on the Moon and returning him safely to the Earth.
-
Technical details
- -| Position | -Astronaut | -
|---|---|
| Commander | -Neil A. Armstrong | -
| Command Module Pilot | -Michael Collins | -
| Lunar Module Pilot | -Edwin "Buzz" E. Aldrin, Jr. | -
Launched by a Saturn V rocket from Kennedy Space Center in Merritt Island, Florida on July 16, Apollo 11 was the fifth manned mission of NASA's Apollo program. The Apollo spacecraft had three parts:
- --
-
- Command Module with a cabin for the three astronauts which was the only part which landed back on Earth -
- Service Module which supported the Command Module with propulsion, electrical power, oxygen and water -
- Lunar Module for landing on the Moon. -
After being sent to the Moon by the Saturn V's upper stage, the astronauts separated the spacecraft from it and travelled for three days until they entered into lunar orbit. Armstrong and Aldrin then moved into the Lunar Module and landed in the Sea of Tranquility. They stayed a total of about 21 and a half hours on the lunar surface. After lifting off in the upper part of the Lunar Module and rejoining Collins in the Command Module, they returned to Earth and landed in the Pacific Ocean on July 24.
- --
Source: Wikipedia.org
-- CKEditor Samples » Replace Textarea with Inline Editor -
-
- You can also create an inline editor from a textarea
- element. In this case the textarea will be replaced
- by a div element with inline editing enabled.
-
-// "article-body" is the name of a textarea element. -var editor = CKEDITOR.inline( 'article-body' ); --
- CKEditor Samples » Create Editors with jQuery -
-- CKEditor Samples » Using Magicline plugin -
-- This sample shows the advantages of Magicline plugin - which is to enhance the editing process. Thanks to this plugin, - a number of difficult focus spaces which are inaccessible due to - browser issues can now be focused. -
-- Magicline plugin shows a red line with a handler - which, when clicked, inserts a paragraph and allows typing. To see this, - focus an editor and move your mouse above the focus space you want - to access. The plugin is enabled by default so no additional - configuration is necessary. -
-- This editor uses a default Magicline setup. -
--
- This editor is using a blue line. -
-
-CKEDITOR.replace( 'editor2', {
- magicline_color: 'blue'
-});
- - CKEditor Samples » Using the CKEditor Read-Only API -
-
- This sample shows how to use the
- setReadOnly
- API to put editor into the read-only state that makes it impossible for users to change the editor contents.
-
- For details on how to create this setup check the source code of this sample page. -
-- CKEditor Samples » Replace Textarea Elements by Class Name -
-
- This sample shows how to automatically replace all <textarea> elements
- of a given class with a CKEditor instance.
-
- To replace a <textarea> element, simply assign it the ckeditor
- class, as in the code below:
-
-<textarea class="ckeditor" name="editor1"></textarea> --
- Note that other <textarea> attributes (like id or name) need to be adjusted to your document.
-
- CKEditor Samples » Replace Textarea Elements Using JavaScript Code -
-' + requires[ i ] + '' );
- }
-
- if ( missing.length ) {
- var warn = CKEDITOR.dom.element.createFromHtml(
- '- -------------------------------------------------------------------------------------------- - CKEditor - Posted Data - - We are sorry, but your Web server does not support the PHP language used in this script. - - Please note that CKEditor can be used with any other server-side language than just PHP. - To save the content created with CKEditor you need to read the POST data on the server - side and write it to a file or the database. - - Copyright (c) 2003-2017, CKSource - Frederico Knabben. All rights reserved. - For licensing, see LICENSE.md or https://ckeditor.com/legal/ckeditor-oss-license -------------------------------------------------------------------------------------------- - -