From version < 2.1 >
edited by Richard Johnson
on 2018/07/31 17:44
To version 1.1 >
edited by superadmin
on 2018/07/31 17:43
>
Change comment: Install extension [org.xwiki.platform:xwiki-platform-distribution-flavor-common/10.6.1]

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.raj
1 +xwiki:XWiki.superadmin
Content
... ... @@ -1,26 +1,47 @@
1 -
1 +{{box cssClass="floatinginfobox"}}
2 +{{velocity}}
3 +{{html clean="false"}}
4 +## Chrome's XSS Auditor blocks the preview action if:
5 +## * the submitted content has an iframe with an external URL
6 +## * the preview action displays the submitted iframe
7 +## The workaround is to make sure the submitted content (the macro markers) don't match the preview HTML.
8 +## See XWIKI-14818: Preview triggers ERR_BLOCKED_BY_XSS_AUDITOR in Chrome
9 +#set ($iframe = 'iframe')
10 +<$iframe src="https://www.youtube.com/embed/9QTWrZ7OfzI" allowfullscreen></$iframe>
11 +{{/html}}
12 +{{/velocity}}
13 +{{/box}}
2 2  
3 -This wiki is intended to document my creation of my own automated home.  It all took place over many, many, years, starting as far back as 20 years ago.  (Yes, I was doing Internet of Things long before most people had thought about it.  It's true.)
4 -\\I'll approach this from a hierarchical viewpoint.
5 -\\At the top level, I have my "xten.html" web page.  This invokes the "xt" script.  This script standardizes the names of all items in the house and allows a simple "on" and "off" command line interface, regardless of whether you're controlling an X10 device, a Wink device, or even a Nest Thermostat.  This allows one main web page to control everything in the house, regardless of what type of device it happens to be.  Also, having one primary script which controls everything, allows for a simple, standard, interface which other scripts can utilize in order to accomplish those basic operations.
6 -\\The whole system is built upon a series of simple building blocks.  (You don't have to build, or even design, the whole system from the outset.  This system was built over, literally, decades.  Just make sure that each part of the system does one basic operation in a standardized way, and does it in such a way that it can easily be utilized as a primitive operation in higher level functional units.  This is the basis of the design of Unix, and allows for incremental improvements and additions over time.  Just think, "building block", and don't get carried away with greater functionality.  Then, be willing to rewrite as you go.)
7 -\\The "xt" script controls the following types of devices:
15 += Welcome to your wiki =
8 8  
9 -* X10 devices - via writing X10 commands to "ti103_fifo" (a unix named pipe interface to the "[[ti103>>url:https://mischievous.us/wiki/pages/h1t4x82/ti103.html]]" program.
10 -* Wink devices - via invoking the "[[wink.pl>>url:https://mischievous.us/wiki/pages/w347G1f4/winkpl.html]]" PERL script, which talks REST to Wink's server.
11 -* Nest devices - via invoking the "[[nest_set.python>>url:https://mischievous.us/wiki/pages/j19806/nest_setpython.html]]" script, which talks REST to Nest's server.
12 -(I admit that currently this simple program only turns my thermostat on or off.)
17 +XWiki is the best tool to organize your knowledge. A //wiki// is organized in a hierarchy of //pages//. You can create multiple wikis, each with its own set of pages.
13 13  
14 -(I originally wrote the "nest" script in PERL also, but then wanted to learn Python, so I re-wrote it in Python. Together, the "wink" and "nest" scripts serve as examples of how to do REST in both languages.)
19 +XWiki can be used as a knowledge base (support, documentation, sales, etc.), for collaborative workspaces or even as a complete intranet.
15 15  
16 -(The "ti103" program is written in "C" and talks over a serial line to the "TI103" device.  This device talks the X10 protocol over power lines as well as listens to X10 commands invoked from elsewhere.)
21 += The basics =
17 17  
18 -I have a Davis Weather Station on my roof. [[Here's the program>>url:https://github.com/rajid/davis_weather]] which reads from the console and stores the information into various files.
23 +To make the most out of your wiki, log-in and:
19 19  
20 -Please feel free to contact me with questions about any fo this.
25 +Use the {{velocity}}$services.icon.render('pencil'){{/velocity}} button above to //edit// this page and start customizing your wiki to your needs.
21 21  
22 -(I'll be adding more and more to this description in the future Sorry, but this documentation effort is just starting.)
27 +Use the {{velocity}}$services.icon.render('add'){{/velocity}} button above to //add// more pages to your wiki and create the //hierarchy// that best organizes your content.
23 23  
24 -/raj
29 +Use the {{velocity}}$services.icon.render('home'){{/velocity}} breadcrumbs located above the title to //navigate// inside your pages. It's easy to get lost in a big wiki without them.
25 25  
26 -[[List of Fitbit software projects>>url:https://mischievous.us/wiki/pages/g7W5c3P297/List_of_Fitbit_software_projects.html]]
31 +You can also use the [[Sandbox>>Sandbox.WebHome]] for more demo content and generally a place to experiment with your wiki's features.
32 +
33 + {{box}}Learn more on how to use XWiki with the {{velocity}}[[Getting Started Guide>>http://www.xwiki.org/xwiki/bin/view/Documentation/UserGuide/GettingStarted/WebHome?version=$xwiki.version]]{{/velocity}}.{{/box}}
34 +
35 +|(((
36 += Extend your wiki =
37 +
38 +To extend the power and functionalities of your wiki with the features that //you// need, head over to the {{velocity}}[[Extension Manager>>path:$xwiki.getURL($services.model.createDocumentReference('wiki', 'XWiki', 'XWikiPreferences'), 'admin', 'editor=globaladmin&section=XWiki.AddExtensions')]]{{/velocity}} where you can search for and install extensions.
39 +
40 +To browse through the 900+ community contributed extensions available for XWiki, head over to the [[Extensions Repository>>http://extensions.xwiki.org]].
41 +)))|(((
42 += Create your application =
43 +
44 +Go beyond the available extensions and define the //structure// of your data based on //your// needs, creating //your// own applications with [[App Within Minutes>>AppWithinMinutes]] (AWM).
45 +
46 +AWM will take care of making it easy for you and your users to create and manage the data.
47 +)))