zeppelin/docs/displaysystem/front-end-angular.md

171 lines
6 KiB
Markdown
Raw Normal View History

[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
---
layout: page
[ZEPPELIN-1219] Add searching feature to Zeppelin docs site ### What is this PR for? As more and more document pages are added, it's really hard to find specific pages. So I added searching feature to Zeppelin documentation site([jekyll](https://jekyllrb.com/) based site) using [lunr.js](http://lunrjs.com/). - **How does it work?** I created [`search_data.json`](https://github.com/AhyoungRyu/zeppelin/blob/6e02423f541cc406e4e41031629609a276a9f481/docs/search_data.json) which is used for docs info template. `lunr.js` combines all of the text from all of the docs in `docs/` into `_site/search_data.json`. It looks like below. ![screen shot 2016-08-03 at 4 49 59 am](https://cloud.githubusercontent.com/assets/10060731/17342828/f2908be8-5935-11e6-8eee-b189677c0531.png) All the info are comes from [Jekyll YAML front matter](https://jekyllrb.com/docs/frontmatter/) variables. (i.e. title, group, description.. that's why I rewrote all docs' title and description.) [search.js](https://github.com/AhyoungRyu/zeppelin/blob/6e02423f541cc406e4e41031629609a276a9f481/docs/assets/themes/zeppelin/js/search.js) will do this job using this data! ### What type of PR is it? Improvement & Feature ### Todos * [x] - Keep consistency for all docs pages' `Title` * [x] - Add some overview sentences to all docs pages' `Description` section (this will be used as the result preview) * [x] - Add apache license header to all docs page (some pages are missing the license header currently) * [x] - Add LICENSE for `lunr.min.js` ### What is the Jira issue? [ZEPPELIN-1219](https://issues.apache.org/jira/browse/ZEPPELIN-1219) ### How should this be tested? 1. Apply this patch and build `ZEPPELIN_HOME/docs` dir -> please see [docs/README.md#build-documentation](https://github.com/apache/zeppelin/tree/master/docs#build-documentation) 2. Click `search` icon in navbar and go to `search.html` page 3. Type anything you want to search in the search bar (i.e. type `python`, `spark`, `dynamic` ... ) ### Screenshots (if appropriate) ![screen shot 2016-08-03 at 4 42 28 pm](https://cloud.githubusercontent.com/assets/10060731/17357851/d092e2ca-5999-11e6-9917-a3d4113e6e43.png) ![search](https://cloud.githubusercontent.com/assets/10060731/17357828/b2486cd6-5999-11e6-873b-121fac033b03.gif) ### Questions: * Does the licenses files need update? Yes, for `lunr.min.js` * Is there breaking changes for older versions? no * Does this needs documentation? no Author: AhyoungRyu <fbdkdud93@hanmail.net> Closes #1266 from AhyoungRyu/ZEPPELIN-1219 and squashes the following commits: 7ec8854 [AhyoungRyu] Modify 'no result' sentence 91b71a7 [AhyoungRyu] Remove Apache license header since JSON doesn't allow comment 34afd5d [AhyoungRyu] Add Apache license header to search_data.json 6784282 [AhyoungRyu] Minor search page UI update 0389d28 [AhyoungRyu] Make index.md not to be searched 9f1ba42 [AhyoungRyu] Disable enterkey press & change icon bd4956a [AhyoungRyu] Add docs.js & search.js to exclude list in pom.xml 624b051 [AhyoungRyu] Add Apache license header to search.js 1381152 [AhyoungRyu] Fix search result skipping issue 6e775f5 [AhyoungRyu] Make pleasecontribute.md not to be searched ee11136 [AhyoungRyu] Fix some typos fa01299 [AhyoungRyu] Refine 'description' in some docs as @bzz suggested da0cff9 [AhyoungRyu] Exclude lunr.min.js 36ba7f1 [AhyoungRyu] Add lunr.min.js license info f6a05a6 [AhyoungRyu] Apply css style for the search results 68eb997 [AhyoungRyu] Attach 'Apache Zeppelin ZEPPELIN_VERSION Documentation: ' to title d908c37 [AhyoungRyu] Add searching page a951fa6 [AhyoungRyu] Add search icon to navbar 0688a79 [AhyoungRyu] Keep consistency all docs' front matter for the right search result 040f532 [AhyoungRyu] Add template for storing docs info based on jekyll front matter 0705bd6 [AhyoungRyu] Add js files: lunr.min.js & search.js
2016-08-06 05:50:25 +00:00
title: "Front-end Angular API in Apache Zeppelin"
description: "In addition to the back-end API to handle Angular objects binding, Apache Zeppelin exposes a simple AngularJS z object on the front-end side to expose the same capabilities."
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
group: display
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
{% include JB/setup %}
[ZEPPELIN-1018] Apply auto "Table of Contents" generator to Zeppelin docs website ### What is this PR for? I added auto TOC(Table of Contents) generator for Zeppelin documentation website. TOC can help people looking through whole contents at a glance and finding what they want quickly. I just added `<div id="toc"></div>` to the each documentation header. [`toc`](https://github.com/apache/zeppelin/compare/master...AhyoungRyu:ZEPPELIN-1018?expand=1#diff-85af09fb498a5667ea455391533f945dR3) recognize `<h2>` & `<h3>` as a title in the docs and it automatically generate TOC. So I set a rule for this work. (I'll write this rule on `docs/CONTRIBUTING.md` or [docs/howtocontributewebsite](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/howtocontributewebsite.html)). ``` # Level-1 Heading <- Use only for the main title of the page ## Level-2 Heading <- Start with this one ### Level-3 heading <- Only use this one for child of Level-2 toc only recognize Level-2 & Level-3 ``` Please see the below attached screenshot image. ### What type of PR is it? Improvement & Documentation ### Todos * [x] - Add TOC generator * [x] - Apply TOC(`<div id="toc"></div>`) to every documentation and reorganize each headers(apply the above rule) * [x] - Fix some broken code block in several docs * [x] - Apply TOC to `r.md` (Currently R docs has some duplicated info since [this one](https://github.com/apache/zeppelin/commit/d5e87fb8ba98f08db5b0a4995104ce19f182c678) and [this one](https://github.com/apache/zeppelin/commit/7d6cc7e99154e2d337c11fdf8be1a874ed3e9ada) ) * [x] - Apply TOC to `install.md` after #1010 merged * [x] - Apply TOC to `interpreterinstallation.md` after #1042 merged ### What is the Jira issue? [ZEPPELIN-1018](https://issues.apache.org/jira/browse/ZEPPELIN-1018) ### How should this be tested? 1. Apply this patch and build `docs/` with [this guide](https://github.com/apache/zeppelin/tree/master/docs#build-documentation) 2. Visit some docs page. Then you can see TOC in the header of page. ### Screenshots (if appropriate) - Automatically generated TOC in Spark interpreter docs page <img width="831" alt="screen shot 2016-06-16 at 9 37 18 pm" src="https://cloud.githubusercontent.com/assets/10060731/16140902/945b9c7a-340a-11e6-91f3-b6174738bed0.png"> ### Questions: * Does the licenses files need update? No. Actually I used [jekyll-table-of-contents#copyright](https://github.com/ghiculescu/jekyll-table-of-contents#copyright). But I don't need to add a license for this :) * Is there breaking changes for older versions? No * Does this needs documentation? Maybe Author: AhyoungRyu <fbdkdud93@hanmail.net> Closes #1031 from AhyoungRyu/ZEPPELIN-1018 and squashes the following commits: e66397b [AhyoungRyu] Apply TOC to interpreterinstallation.md 009579b [AhyoungRyu] Add more info to 'What is the next?' in install.md 04cf501 [AhyoungRyu] Revert 'where to start' section b7cbe5f [AhyoungRyu] Fix typo cf0911c [AhyoungRyu] Rename license file 388f35a [AhyoungRyu] Add jekyll-table-of-contents license info 6394c70 [AhyoungRyu] Fix image path in python.md d00e4b1 [AhyoungRyu] Move interpreter/screenshot/ -> asset/../img/docs-img/ 3ffb383 [AhyoungRyu] Remove duplicated info in r.md & apply toc a03ca99 [AhyoungRyu] Exclude toc.js from pom.xml 3fae7df [AhyoungRyu] Apply auto generated toc to install.md d114a9d [AhyoungRyu] Address @felixcheung feedback 6a788fe [AhyoungRyu] Resize TOC tab indent 6760c00 [AhyoungRyu] Apply auto TOC to all of docs under docs/storage/ fbde57f [AhyoungRyu] Apply auto TOC to all of docs under docs/quickstart/ db76eb6 [AhyoungRyu] Apply auto TOC to all of docs under docs/install/ f35db47 [AhyoungRyu] Apply auto TOC to all of docs under docs/displaysystem/ b05365f [AhyoungRyu] Apply auto TOC to all of docs under docs/rest-api/ 163691c [AhyoungRyu] Apply auto TOC to all of docs under docs/manual/ bef398e [AhyoungRyu] Apply auto TOC to all of docs under docs/development/ 9c5f76b [AhyoungRyu] Apply auto TOC to all of docs under docs/interpreter/ 587d4ba [AhyoungRyu] Apply auto TOC to all of docs under docs/security/ 1f10b97 [AhyoungRyu] Change toc configuration 78dca9e [AhyoungRyu] Add toc.js for auto generating TOC
2016-06-25 19:44:53 +00:00
# Front-end Angular API in Apache Zeppelin
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
[ZEPPELIN-1018] Apply auto "Table of Contents" generator to Zeppelin docs website ### What is this PR for? I added auto TOC(Table of Contents) generator for Zeppelin documentation website. TOC can help people looking through whole contents at a glance and finding what they want quickly. I just added `<div id="toc"></div>` to the each documentation header. [`toc`](https://github.com/apache/zeppelin/compare/master...AhyoungRyu:ZEPPELIN-1018?expand=1#diff-85af09fb498a5667ea455391533f945dR3) recognize `<h2>` & `<h3>` as a title in the docs and it automatically generate TOC. So I set a rule for this work. (I'll write this rule on `docs/CONTRIBUTING.md` or [docs/howtocontributewebsite](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/howtocontributewebsite.html)). ``` # Level-1 Heading <- Use only for the main title of the page ## Level-2 Heading <- Start with this one ### Level-3 heading <- Only use this one for child of Level-2 toc only recognize Level-2 & Level-3 ``` Please see the below attached screenshot image. ### What type of PR is it? Improvement & Documentation ### Todos * [x] - Add TOC generator * [x] - Apply TOC(`<div id="toc"></div>`) to every documentation and reorganize each headers(apply the above rule) * [x] - Fix some broken code block in several docs * [x] - Apply TOC to `r.md` (Currently R docs has some duplicated info since [this one](https://github.com/apache/zeppelin/commit/d5e87fb8ba98f08db5b0a4995104ce19f182c678) and [this one](https://github.com/apache/zeppelin/commit/7d6cc7e99154e2d337c11fdf8be1a874ed3e9ada) ) * [x] - Apply TOC to `install.md` after #1010 merged * [x] - Apply TOC to `interpreterinstallation.md` after #1042 merged ### What is the Jira issue? [ZEPPELIN-1018](https://issues.apache.org/jira/browse/ZEPPELIN-1018) ### How should this be tested? 1. Apply this patch and build `docs/` with [this guide](https://github.com/apache/zeppelin/tree/master/docs#build-documentation) 2. Visit some docs page. Then you can see TOC in the header of page. ### Screenshots (if appropriate) - Automatically generated TOC in Spark interpreter docs page <img width="831" alt="screen shot 2016-06-16 at 9 37 18 pm" src="https://cloud.githubusercontent.com/assets/10060731/16140902/945b9c7a-340a-11e6-91f3-b6174738bed0.png"> ### Questions: * Does the licenses files need update? No. Actually I used [jekyll-table-of-contents#copyright](https://github.com/ghiculescu/jekyll-table-of-contents#copyright). But I don't need to add a license for this :) * Is there breaking changes for older versions? No * Does this needs documentation? Maybe Author: AhyoungRyu <fbdkdud93@hanmail.net> Closes #1031 from AhyoungRyu/ZEPPELIN-1018 and squashes the following commits: e66397b [AhyoungRyu] Apply TOC to interpreterinstallation.md 009579b [AhyoungRyu] Add more info to 'What is the next?' in install.md 04cf501 [AhyoungRyu] Revert 'where to start' section b7cbe5f [AhyoungRyu] Fix typo cf0911c [AhyoungRyu] Rename license file 388f35a [AhyoungRyu] Add jekyll-table-of-contents license info 6394c70 [AhyoungRyu] Fix image path in python.md d00e4b1 [AhyoungRyu] Move interpreter/screenshot/ -> asset/../img/docs-img/ 3ffb383 [AhyoungRyu] Remove duplicated info in r.md & apply toc a03ca99 [AhyoungRyu] Exclude toc.js from pom.xml 3fae7df [AhyoungRyu] Apply auto generated toc to install.md d114a9d [AhyoungRyu] Address @felixcheung feedback 6a788fe [AhyoungRyu] Resize TOC tab indent 6760c00 [AhyoungRyu] Apply auto TOC to all of docs under docs/storage/ fbde57f [AhyoungRyu] Apply auto TOC to all of docs under docs/quickstart/ db76eb6 [AhyoungRyu] Apply auto TOC to all of docs under docs/install/ f35db47 [AhyoungRyu] Apply auto TOC to all of docs under docs/displaysystem/ b05365f [AhyoungRyu] Apply auto TOC to all of docs under docs/rest-api/ 163691c [AhyoungRyu] Apply auto TOC to all of docs under docs/manual/ bef398e [AhyoungRyu] Apply auto TOC to all of docs under docs/development/ 9c5f76b [AhyoungRyu] Apply auto TOC to all of docs under docs/interpreter/ 587d4ba [AhyoungRyu] Apply auto TOC to all of docs under docs/security/ 1f10b97 [AhyoungRyu] Change toc configuration 78dca9e [AhyoungRyu] Add toc.js for auto generating TOC
2016-06-25 19:44:53 +00:00
<div id="toc"></div>
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
[ZEPPELIN-1018] Apply auto "Table of Contents" generator to Zeppelin docs website ### What is this PR for? I added auto TOC(Table of Contents) generator for Zeppelin documentation website. TOC can help people looking through whole contents at a glance and finding what they want quickly. I just added `<div id="toc"></div>` to the each documentation header. [`toc`](https://github.com/apache/zeppelin/compare/master...AhyoungRyu:ZEPPELIN-1018?expand=1#diff-85af09fb498a5667ea455391533f945dR3) recognize `<h2>` & `<h3>` as a title in the docs and it automatically generate TOC. So I set a rule for this work. (I'll write this rule on `docs/CONTRIBUTING.md` or [docs/howtocontributewebsite](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/howtocontributewebsite.html)). ``` # Level-1 Heading <- Use only for the main title of the page ## Level-2 Heading <- Start with this one ### Level-3 heading <- Only use this one for child of Level-2 toc only recognize Level-2 & Level-3 ``` Please see the below attached screenshot image. ### What type of PR is it? Improvement & Documentation ### Todos * [x] - Add TOC generator * [x] - Apply TOC(`<div id="toc"></div>`) to every documentation and reorganize each headers(apply the above rule) * [x] - Fix some broken code block in several docs * [x] - Apply TOC to `r.md` (Currently R docs has some duplicated info since [this one](https://github.com/apache/zeppelin/commit/d5e87fb8ba98f08db5b0a4995104ce19f182c678) and [this one](https://github.com/apache/zeppelin/commit/7d6cc7e99154e2d337c11fdf8be1a874ed3e9ada) ) * [x] - Apply TOC to `install.md` after #1010 merged * [x] - Apply TOC to `interpreterinstallation.md` after #1042 merged ### What is the Jira issue? [ZEPPELIN-1018](https://issues.apache.org/jira/browse/ZEPPELIN-1018) ### How should this be tested? 1. Apply this patch and build `docs/` with [this guide](https://github.com/apache/zeppelin/tree/master/docs#build-documentation) 2. Visit some docs page. Then you can see TOC in the header of page. ### Screenshots (if appropriate) - Automatically generated TOC in Spark interpreter docs page <img width="831" alt="screen shot 2016-06-16 at 9 37 18 pm" src="https://cloud.githubusercontent.com/assets/10060731/16140902/945b9c7a-340a-11e6-91f3-b6174738bed0.png"> ### Questions: * Does the licenses files need update? No. Actually I used [jekyll-table-of-contents#copyright](https://github.com/ghiculescu/jekyll-table-of-contents#copyright). But I don't need to add a license for this :) * Is there breaking changes for older versions? No * Does this needs documentation? Maybe Author: AhyoungRyu <fbdkdud93@hanmail.net> Closes #1031 from AhyoungRyu/ZEPPELIN-1018 and squashes the following commits: e66397b [AhyoungRyu] Apply TOC to interpreterinstallation.md 009579b [AhyoungRyu] Add more info to 'What is the next?' in install.md 04cf501 [AhyoungRyu] Revert 'where to start' section b7cbe5f [AhyoungRyu] Fix typo cf0911c [AhyoungRyu] Rename license file 388f35a [AhyoungRyu] Add jekyll-table-of-contents license info 6394c70 [AhyoungRyu] Fix image path in python.md d00e4b1 [AhyoungRyu] Move interpreter/screenshot/ -> asset/../img/docs-img/ 3ffb383 [AhyoungRyu] Remove duplicated info in r.md & apply toc a03ca99 [AhyoungRyu] Exclude toc.js from pom.xml 3fae7df [AhyoungRyu] Apply auto generated toc to install.md d114a9d [AhyoungRyu] Address @felixcheung feedback 6a788fe [AhyoungRyu] Resize TOC tab indent 6760c00 [AhyoungRyu] Apply auto TOC to all of docs under docs/storage/ fbde57f [AhyoungRyu] Apply auto TOC to all of docs under docs/quickstart/ db76eb6 [AhyoungRyu] Apply auto TOC to all of docs under docs/install/ f35db47 [AhyoungRyu] Apply auto TOC to all of docs under docs/displaysystem/ b05365f [AhyoungRyu] Apply auto TOC to all of docs under docs/rest-api/ 163691c [AhyoungRyu] Apply auto TOC to all of docs under docs/manual/ bef398e [AhyoungRyu] Apply auto TOC to all of docs under docs/development/ 9c5f76b [AhyoungRyu] Apply auto TOC to all of docs under docs/interpreter/ 587d4ba [AhyoungRyu] Apply auto TOC to all of docs under docs/security/ 1f10b97 [AhyoungRyu] Change toc configuration 78dca9e [AhyoungRyu] Add toc.js for auto generating TOC
2016-06-25 19:44:53 +00:00
## Basic Usage
In addition to the [back-end API](./back-end-angular.html) to handle Angular objects binding, Apache Zeppelin also exposes a simple AngularJS <code>**z**</code> object on the front-end side to expose the same capabilities.
This <code>**z**</code> object is accessible in the Angular isolated scope for each paragraph.
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
### Bind / Unbind Variables
[ZEPPELIN-1018] Apply auto "Table of Contents" generator to Zeppelin docs website ### What is this PR for? I added auto TOC(Table of Contents) generator for Zeppelin documentation website. TOC can help people looking through whole contents at a glance and finding what they want quickly. I just added `<div id="toc"></div>` to the each documentation header. [`toc`](https://github.com/apache/zeppelin/compare/master...AhyoungRyu:ZEPPELIN-1018?expand=1#diff-85af09fb498a5667ea455391533f945dR3) recognize `<h2>` & `<h3>` as a title in the docs and it automatically generate TOC. So I set a rule for this work. (I'll write this rule on `docs/CONTRIBUTING.md` or [docs/howtocontributewebsite](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/howtocontributewebsite.html)). ``` # Level-1 Heading <- Use only for the main title of the page ## Level-2 Heading <- Start with this one ### Level-3 heading <- Only use this one for child of Level-2 toc only recognize Level-2 & Level-3 ``` Please see the below attached screenshot image. ### What type of PR is it? Improvement & Documentation ### Todos * [x] - Add TOC generator * [x] - Apply TOC(`<div id="toc"></div>`) to every documentation and reorganize each headers(apply the above rule) * [x] - Fix some broken code block in several docs * [x] - Apply TOC to `r.md` (Currently R docs has some duplicated info since [this one](https://github.com/apache/zeppelin/commit/d5e87fb8ba98f08db5b0a4995104ce19f182c678) and [this one](https://github.com/apache/zeppelin/commit/7d6cc7e99154e2d337c11fdf8be1a874ed3e9ada) ) * [x] - Apply TOC to `install.md` after #1010 merged * [x] - Apply TOC to `interpreterinstallation.md` after #1042 merged ### What is the Jira issue? [ZEPPELIN-1018](https://issues.apache.org/jira/browse/ZEPPELIN-1018) ### How should this be tested? 1. Apply this patch and build `docs/` with [this guide](https://github.com/apache/zeppelin/tree/master/docs#build-documentation) 2. Visit some docs page. Then you can see TOC in the header of page. ### Screenshots (if appropriate) - Automatically generated TOC in Spark interpreter docs page <img width="831" alt="screen shot 2016-06-16 at 9 37 18 pm" src="https://cloud.githubusercontent.com/assets/10060731/16140902/945b9c7a-340a-11e6-91f3-b6174738bed0.png"> ### Questions: * Does the licenses files need update? No. Actually I used [jekyll-table-of-contents#copyright](https://github.com/ghiculescu/jekyll-table-of-contents#copyright). But I don't need to add a license for this :) * Is there breaking changes for older versions? No * Does this needs documentation? Maybe Author: AhyoungRyu <fbdkdud93@hanmail.net> Closes #1031 from AhyoungRyu/ZEPPELIN-1018 and squashes the following commits: e66397b [AhyoungRyu] Apply TOC to interpreterinstallation.md 009579b [AhyoungRyu] Add more info to 'What is the next?' in install.md 04cf501 [AhyoungRyu] Revert 'where to start' section b7cbe5f [AhyoungRyu] Fix typo cf0911c [AhyoungRyu] Rename license file 388f35a [AhyoungRyu] Add jekyll-table-of-contents license info 6394c70 [AhyoungRyu] Fix image path in python.md d00e4b1 [AhyoungRyu] Move interpreter/screenshot/ -> asset/../img/docs-img/ 3ffb383 [AhyoungRyu] Remove duplicated info in r.md & apply toc a03ca99 [AhyoungRyu] Exclude toc.js from pom.xml 3fae7df [AhyoungRyu] Apply auto generated toc to install.md d114a9d [AhyoungRyu] Address @felixcheung feedback 6a788fe [AhyoungRyu] Resize TOC tab indent 6760c00 [AhyoungRyu] Apply auto TOC to all of docs under docs/storage/ fbde57f [AhyoungRyu] Apply auto TOC to all of docs under docs/quickstart/ db76eb6 [AhyoungRyu] Apply auto TOC to all of docs under docs/install/ f35db47 [AhyoungRyu] Apply auto TOC to all of docs under docs/displaysystem/ b05365f [AhyoungRyu] Apply auto TOC to all of docs under docs/rest-api/ 163691c [AhyoungRyu] Apply auto TOC to all of docs under docs/manual/ bef398e [AhyoungRyu] Apply auto TOC to all of docs under docs/development/ 9c5f76b [AhyoungRyu] Apply auto TOC to all of docs under docs/interpreter/ 587d4ba [AhyoungRyu] Apply auto TOC to all of docs under docs/security/ 1f10b97 [AhyoungRyu] Change toc configuration 78dca9e [AhyoungRyu] Add toc.js for auto generating TOC
2016-06-25 19:44:53 +00:00
Through the **`z`**, you can bind / unbind variables to **AngularJS view**.
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
Bind a value to an angular object and a **mandatory** target paragraph:
```html
%angular
<form class="form-inline">
<div class="form-group">
<label for="superheroId">Super Hero: </label>
<input type="text" class="form-control" id="superheroId" placeholder="Superhero name ..." ng-model="superhero"></input>
</div>
<button type="submit" class="btn btn-primary" ng-click="z.angularBind('superhero',superhero,'20160222-232336_1472609686')"> Bind</button>
</form>
```
<img src="../assets/themes/zeppelin/img/screenshots/z_angularBind.gif" />
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
<hr/>
Unbind/remove a value from angular object and a **mandatory** target paragraph:
```html
%angular
<form class="form-inline">
<button type="submit" class="btn btn-primary" ng-click="z.angularUnbind('superhero','20160222-232336_1472609686')"> UnBind</button>
</form>
```
<img src="../assets/themes/zeppelin/img/screenshots/z_angularUnbind.gif" />
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
The signature for the **`z.angularBind() / z.angularUnbind()`** functions are:
```javascript
[ZEPPELIN-1018] Apply auto "Table of Contents" generator to Zeppelin docs website ### What is this PR for? I added auto TOC(Table of Contents) generator for Zeppelin documentation website. TOC can help people looking through whole contents at a glance and finding what they want quickly. I just added `<div id="toc"></div>` to the each documentation header. [`toc`](https://github.com/apache/zeppelin/compare/master...AhyoungRyu:ZEPPELIN-1018?expand=1#diff-85af09fb498a5667ea455391533f945dR3) recognize `<h2>` & `<h3>` as a title in the docs and it automatically generate TOC. So I set a rule for this work. (I'll write this rule on `docs/CONTRIBUTING.md` or [docs/howtocontributewebsite](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/howtocontributewebsite.html)). ``` # Level-1 Heading <- Use only for the main title of the page ## Level-2 Heading <- Start with this one ### Level-3 heading <- Only use this one for child of Level-2 toc only recognize Level-2 & Level-3 ``` Please see the below attached screenshot image. ### What type of PR is it? Improvement & Documentation ### Todos * [x] - Add TOC generator * [x] - Apply TOC(`<div id="toc"></div>`) to every documentation and reorganize each headers(apply the above rule) * [x] - Fix some broken code block in several docs * [x] - Apply TOC to `r.md` (Currently R docs has some duplicated info since [this one](https://github.com/apache/zeppelin/commit/d5e87fb8ba98f08db5b0a4995104ce19f182c678) and [this one](https://github.com/apache/zeppelin/commit/7d6cc7e99154e2d337c11fdf8be1a874ed3e9ada) ) * [x] - Apply TOC to `install.md` after #1010 merged * [x] - Apply TOC to `interpreterinstallation.md` after #1042 merged ### What is the Jira issue? [ZEPPELIN-1018](https://issues.apache.org/jira/browse/ZEPPELIN-1018) ### How should this be tested? 1. Apply this patch and build `docs/` with [this guide](https://github.com/apache/zeppelin/tree/master/docs#build-documentation) 2. Visit some docs page. Then you can see TOC in the header of page. ### Screenshots (if appropriate) - Automatically generated TOC in Spark interpreter docs page <img width="831" alt="screen shot 2016-06-16 at 9 37 18 pm" src="https://cloud.githubusercontent.com/assets/10060731/16140902/945b9c7a-340a-11e6-91f3-b6174738bed0.png"> ### Questions: * Does the licenses files need update? No. Actually I used [jekyll-table-of-contents#copyright](https://github.com/ghiculescu/jekyll-table-of-contents#copyright). But I don't need to add a license for this :) * Is there breaking changes for older versions? No * Does this needs documentation? Maybe Author: AhyoungRyu <fbdkdud93@hanmail.net> Closes #1031 from AhyoungRyu/ZEPPELIN-1018 and squashes the following commits: e66397b [AhyoungRyu] Apply TOC to interpreterinstallation.md 009579b [AhyoungRyu] Add more info to 'What is the next?' in install.md 04cf501 [AhyoungRyu] Revert 'where to start' section b7cbe5f [AhyoungRyu] Fix typo cf0911c [AhyoungRyu] Rename license file 388f35a [AhyoungRyu] Add jekyll-table-of-contents license info 6394c70 [AhyoungRyu] Fix image path in python.md d00e4b1 [AhyoungRyu] Move interpreter/screenshot/ -> asset/../img/docs-img/ 3ffb383 [AhyoungRyu] Remove duplicated info in r.md & apply toc a03ca99 [AhyoungRyu] Exclude toc.js from pom.xml 3fae7df [AhyoungRyu] Apply auto generated toc to install.md d114a9d [AhyoungRyu] Address @felixcheung feedback 6a788fe [AhyoungRyu] Resize TOC tab indent 6760c00 [AhyoungRyu] Apply auto TOC to all of docs under docs/storage/ fbde57f [AhyoungRyu] Apply auto TOC to all of docs under docs/quickstart/ db76eb6 [AhyoungRyu] Apply auto TOC to all of docs under docs/install/ f35db47 [AhyoungRyu] Apply auto TOC to all of docs under docs/displaysystem/ b05365f [AhyoungRyu] Apply auto TOC to all of docs under docs/rest-api/ 163691c [AhyoungRyu] Apply auto TOC to all of docs under docs/manual/ bef398e [AhyoungRyu] Apply auto TOC to all of docs under docs/development/ 9c5f76b [AhyoungRyu] Apply auto TOC to all of docs under docs/interpreter/ 587d4ba [AhyoungRyu] Apply auto TOC to all of docs under docs/security/ 1f10b97 [AhyoungRyu] Change toc configuration 78dca9e [AhyoungRyu] Add toc.js for auto generating TOC
2016-06-25 19:44:53 +00:00
// Bind
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
z.angularBind(angularObjectName, angularObjectValue, paragraphId);
[ZEPPELIN-1018] Apply auto "Table of Contents" generator to Zeppelin docs website ### What is this PR for? I added auto TOC(Table of Contents) generator for Zeppelin documentation website. TOC can help people looking through whole contents at a glance and finding what they want quickly. I just added `<div id="toc"></div>` to the each documentation header. [`toc`](https://github.com/apache/zeppelin/compare/master...AhyoungRyu:ZEPPELIN-1018?expand=1#diff-85af09fb498a5667ea455391533f945dR3) recognize `<h2>` & `<h3>` as a title in the docs and it automatically generate TOC. So I set a rule for this work. (I'll write this rule on `docs/CONTRIBUTING.md` or [docs/howtocontributewebsite](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/howtocontributewebsite.html)). ``` # Level-1 Heading <- Use only for the main title of the page ## Level-2 Heading <- Start with this one ### Level-3 heading <- Only use this one for child of Level-2 toc only recognize Level-2 & Level-3 ``` Please see the below attached screenshot image. ### What type of PR is it? Improvement & Documentation ### Todos * [x] - Add TOC generator * [x] - Apply TOC(`<div id="toc"></div>`) to every documentation and reorganize each headers(apply the above rule) * [x] - Fix some broken code block in several docs * [x] - Apply TOC to `r.md` (Currently R docs has some duplicated info since [this one](https://github.com/apache/zeppelin/commit/d5e87fb8ba98f08db5b0a4995104ce19f182c678) and [this one](https://github.com/apache/zeppelin/commit/7d6cc7e99154e2d337c11fdf8be1a874ed3e9ada) ) * [x] - Apply TOC to `install.md` after #1010 merged * [x] - Apply TOC to `interpreterinstallation.md` after #1042 merged ### What is the Jira issue? [ZEPPELIN-1018](https://issues.apache.org/jira/browse/ZEPPELIN-1018) ### How should this be tested? 1. Apply this patch and build `docs/` with [this guide](https://github.com/apache/zeppelin/tree/master/docs#build-documentation) 2. Visit some docs page. Then you can see TOC in the header of page. ### Screenshots (if appropriate) - Automatically generated TOC in Spark interpreter docs page <img width="831" alt="screen shot 2016-06-16 at 9 37 18 pm" src="https://cloud.githubusercontent.com/assets/10060731/16140902/945b9c7a-340a-11e6-91f3-b6174738bed0.png"> ### Questions: * Does the licenses files need update? No. Actually I used [jekyll-table-of-contents#copyright](https://github.com/ghiculescu/jekyll-table-of-contents#copyright). But I don't need to add a license for this :) * Is there breaking changes for older versions? No * Does this needs documentation? Maybe Author: AhyoungRyu <fbdkdud93@hanmail.net> Closes #1031 from AhyoungRyu/ZEPPELIN-1018 and squashes the following commits: e66397b [AhyoungRyu] Apply TOC to interpreterinstallation.md 009579b [AhyoungRyu] Add more info to 'What is the next?' in install.md 04cf501 [AhyoungRyu] Revert 'where to start' section b7cbe5f [AhyoungRyu] Fix typo cf0911c [AhyoungRyu] Rename license file 388f35a [AhyoungRyu] Add jekyll-table-of-contents license info 6394c70 [AhyoungRyu] Fix image path in python.md d00e4b1 [AhyoungRyu] Move interpreter/screenshot/ -> asset/../img/docs-img/ 3ffb383 [AhyoungRyu] Remove duplicated info in r.md & apply toc a03ca99 [AhyoungRyu] Exclude toc.js from pom.xml 3fae7df [AhyoungRyu] Apply auto generated toc to install.md d114a9d [AhyoungRyu] Address @felixcheung feedback 6a788fe [AhyoungRyu] Resize TOC tab indent 6760c00 [AhyoungRyu] Apply auto TOC to all of docs under docs/storage/ fbde57f [AhyoungRyu] Apply auto TOC to all of docs under docs/quickstart/ db76eb6 [AhyoungRyu] Apply auto TOC to all of docs under docs/install/ f35db47 [AhyoungRyu] Apply auto TOC to all of docs under docs/displaysystem/ b05365f [AhyoungRyu] Apply auto TOC to all of docs under docs/rest-api/ 163691c [AhyoungRyu] Apply auto TOC to all of docs under docs/manual/ bef398e [AhyoungRyu] Apply auto TOC to all of docs under docs/development/ 9c5f76b [AhyoungRyu] Apply auto TOC to all of docs under docs/interpreter/ 587d4ba [AhyoungRyu] Apply auto TOC to all of docs under docs/security/ 1f10b97 [AhyoungRyu] Change toc configuration 78dca9e [AhyoungRyu] Add toc.js for auto generating TOC
2016-06-25 19:44:53 +00:00
// Unbind
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
z.angularUnbind(angularObjectName, angularObjectValue, paragraphId);
```
All the parameters are mandatory.
<br />
### Run Paragraph
You can also trigger paragraph execution by calling **`z.runParagraph()`** function passing the appropriate paragraphId:
```html
%angular
<form class="form-inline">
<div class="form-group">
<label for="paragraphId">Paragraph Id: </label>
<input type="text" class="form-control" id="paragraphId" placeholder="Paragraph Id ..." ng-model="paragraph"></input>
</div>
<button type="submit" class="btn btn-primary" ng-click="z.runParagraph(paragraph)"> Run Paragraph</button>
</form>
```
<img src="../assets/themes/zeppelin/img/screenshots/z_runParagraph.gif" />
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
<br />
[ZEPPELIN-1018] Apply auto "Table of Contents" generator to Zeppelin docs website ### What is this PR for? I added auto TOC(Table of Contents) generator for Zeppelin documentation website. TOC can help people looking through whole contents at a glance and finding what they want quickly. I just added `<div id="toc"></div>` to the each documentation header. [`toc`](https://github.com/apache/zeppelin/compare/master...AhyoungRyu:ZEPPELIN-1018?expand=1#diff-85af09fb498a5667ea455391533f945dR3) recognize `<h2>` & `<h3>` as a title in the docs and it automatically generate TOC. So I set a rule for this work. (I'll write this rule on `docs/CONTRIBUTING.md` or [docs/howtocontributewebsite](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/howtocontributewebsite.html)). ``` # Level-1 Heading <- Use only for the main title of the page ## Level-2 Heading <- Start with this one ### Level-3 heading <- Only use this one for child of Level-2 toc only recognize Level-2 & Level-3 ``` Please see the below attached screenshot image. ### What type of PR is it? Improvement & Documentation ### Todos * [x] - Add TOC generator * [x] - Apply TOC(`<div id="toc"></div>`) to every documentation and reorganize each headers(apply the above rule) * [x] - Fix some broken code block in several docs * [x] - Apply TOC to `r.md` (Currently R docs has some duplicated info since [this one](https://github.com/apache/zeppelin/commit/d5e87fb8ba98f08db5b0a4995104ce19f182c678) and [this one](https://github.com/apache/zeppelin/commit/7d6cc7e99154e2d337c11fdf8be1a874ed3e9ada) ) * [x] - Apply TOC to `install.md` after #1010 merged * [x] - Apply TOC to `interpreterinstallation.md` after #1042 merged ### What is the Jira issue? [ZEPPELIN-1018](https://issues.apache.org/jira/browse/ZEPPELIN-1018) ### How should this be tested? 1. Apply this patch and build `docs/` with [this guide](https://github.com/apache/zeppelin/tree/master/docs#build-documentation) 2. Visit some docs page. Then you can see TOC in the header of page. ### Screenshots (if appropriate) - Automatically generated TOC in Spark interpreter docs page <img width="831" alt="screen shot 2016-06-16 at 9 37 18 pm" src="https://cloud.githubusercontent.com/assets/10060731/16140902/945b9c7a-340a-11e6-91f3-b6174738bed0.png"> ### Questions: * Does the licenses files need update? No. Actually I used [jekyll-table-of-contents#copyright](https://github.com/ghiculescu/jekyll-table-of-contents#copyright). But I don't need to add a license for this :) * Is there breaking changes for older versions? No * Does this needs documentation? Maybe Author: AhyoungRyu <fbdkdud93@hanmail.net> Closes #1031 from AhyoungRyu/ZEPPELIN-1018 and squashes the following commits: e66397b [AhyoungRyu] Apply TOC to interpreterinstallation.md 009579b [AhyoungRyu] Add more info to 'What is the next?' in install.md 04cf501 [AhyoungRyu] Revert 'where to start' section b7cbe5f [AhyoungRyu] Fix typo cf0911c [AhyoungRyu] Rename license file 388f35a [AhyoungRyu] Add jekyll-table-of-contents license info 6394c70 [AhyoungRyu] Fix image path in python.md d00e4b1 [AhyoungRyu] Move interpreter/screenshot/ -> asset/../img/docs-img/ 3ffb383 [AhyoungRyu] Remove duplicated info in r.md & apply toc a03ca99 [AhyoungRyu] Exclude toc.js from pom.xml 3fae7df [AhyoungRyu] Apply auto generated toc to install.md d114a9d [AhyoungRyu] Address @felixcheung feedback 6a788fe [AhyoungRyu] Resize TOC tab indent 6760c00 [AhyoungRyu] Apply auto TOC to all of docs under docs/storage/ fbde57f [AhyoungRyu] Apply auto TOC to all of docs under docs/quickstart/ db76eb6 [AhyoungRyu] Apply auto TOC to all of docs under docs/install/ f35db47 [AhyoungRyu] Apply auto TOC to all of docs under docs/displaysystem/ b05365f [AhyoungRyu] Apply auto TOC to all of docs under docs/rest-api/ 163691c [AhyoungRyu] Apply auto TOC to all of docs under docs/manual/ bef398e [AhyoungRyu] Apply auto TOC to all of docs under docs/development/ 9c5f76b [AhyoungRyu] Apply auto TOC to all of docs under docs/interpreter/ 587d4ba [AhyoungRyu] Apply auto TOC to all of docs under docs/security/ 1f10b97 [AhyoungRyu] Change toc configuration 78dca9e [AhyoungRyu] Add toc.js for auto generating TOC
2016-06-25 19:44:53 +00:00
## Overriding dynamic form with Angular Object
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
The front-end Angular Interaction API has been designed to offer richer form capabilities and variable binding. With the existing **Dynamic Form** system you can already create input text, select and checkbox forms but the choice is rather limited and the look & feel cannot be changed.
The idea is to create a custom form using plain HTML/AngularJS code and bind actions on this form to push/remove Angular variables to targeted paragraphs using this new API.
[ZEPPELIN-1018] Apply auto "Table of Contents" generator to Zeppelin docs website ### What is this PR for? I added auto TOC(Table of Contents) generator for Zeppelin documentation website. TOC can help people looking through whole contents at a glance and finding what they want quickly. I just added `<div id="toc"></div>` to the each documentation header. [`toc`](https://github.com/apache/zeppelin/compare/master...AhyoungRyu:ZEPPELIN-1018?expand=1#diff-85af09fb498a5667ea455391533f945dR3) recognize `<h2>` & `<h3>` as a title in the docs and it automatically generate TOC. So I set a rule for this work. (I'll write this rule on `docs/CONTRIBUTING.md` or [docs/howtocontributewebsite](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/howtocontributewebsite.html)). ``` # Level-1 Heading <- Use only for the main title of the page ## Level-2 Heading <- Start with this one ### Level-3 heading <- Only use this one for child of Level-2 toc only recognize Level-2 & Level-3 ``` Please see the below attached screenshot image. ### What type of PR is it? Improvement & Documentation ### Todos * [x] - Add TOC generator * [x] - Apply TOC(`<div id="toc"></div>`) to every documentation and reorganize each headers(apply the above rule) * [x] - Fix some broken code block in several docs * [x] - Apply TOC to `r.md` (Currently R docs has some duplicated info since [this one](https://github.com/apache/zeppelin/commit/d5e87fb8ba98f08db5b0a4995104ce19f182c678) and [this one](https://github.com/apache/zeppelin/commit/7d6cc7e99154e2d337c11fdf8be1a874ed3e9ada) ) * [x] - Apply TOC to `install.md` after #1010 merged * [x] - Apply TOC to `interpreterinstallation.md` after #1042 merged ### What is the Jira issue? [ZEPPELIN-1018](https://issues.apache.org/jira/browse/ZEPPELIN-1018) ### How should this be tested? 1. Apply this patch and build `docs/` with [this guide](https://github.com/apache/zeppelin/tree/master/docs#build-documentation) 2. Visit some docs page. Then you can see TOC in the header of page. ### Screenshots (if appropriate) - Automatically generated TOC in Spark interpreter docs page <img width="831" alt="screen shot 2016-06-16 at 9 37 18 pm" src="https://cloud.githubusercontent.com/assets/10060731/16140902/945b9c7a-340a-11e6-91f3-b6174738bed0.png"> ### Questions: * Does the licenses files need update? No. Actually I used [jekyll-table-of-contents#copyright](https://github.com/ghiculescu/jekyll-table-of-contents#copyright). But I don't need to add a license for this :) * Is there breaking changes for older versions? No * Does this needs documentation? Maybe Author: AhyoungRyu <fbdkdud93@hanmail.net> Closes #1031 from AhyoungRyu/ZEPPELIN-1018 and squashes the following commits: e66397b [AhyoungRyu] Apply TOC to interpreterinstallation.md 009579b [AhyoungRyu] Add more info to 'What is the next?' in install.md 04cf501 [AhyoungRyu] Revert 'where to start' section b7cbe5f [AhyoungRyu] Fix typo cf0911c [AhyoungRyu] Rename license file 388f35a [AhyoungRyu] Add jekyll-table-of-contents license info 6394c70 [AhyoungRyu] Fix image path in python.md d00e4b1 [AhyoungRyu] Move interpreter/screenshot/ -> asset/../img/docs-img/ 3ffb383 [AhyoungRyu] Remove duplicated info in r.md & apply toc a03ca99 [AhyoungRyu] Exclude toc.js from pom.xml 3fae7df [AhyoungRyu] Apply auto generated toc to install.md d114a9d [AhyoungRyu] Address @felixcheung feedback 6a788fe [AhyoungRyu] Resize TOC tab indent 6760c00 [AhyoungRyu] Apply auto TOC to all of docs under docs/storage/ fbde57f [AhyoungRyu] Apply auto TOC to all of docs under docs/quickstart/ db76eb6 [AhyoungRyu] Apply auto TOC to all of docs under docs/install/ f35db47 [AhyoungRyu] Apply auto TOC to all of docs under docs/displaysystem/ b05365f [AhyoungRyu] Apply auto TOC to all of docs under docs/rest-api/ 163691c [AhyoungRyu] Apply auto TOC to all of docs under docs/manual/ bef398e [AhyoungRyu] Apply auto TOC to all of docs under docs/development/ 9c5f76b [AhyoungRyu] Apply auto TOC to all of docs under docs/interpreter/ 587d4ba [AhyoungRyu] Apply auto TOC to all of docs under docs/security/ 1f10b97 [AhyoungRyu] Change toc configuration 78dca9e [AhyoungRyu] Add toc.js for auto generating TOC
2016-06-25 19:44:53 +00:00
Consequently if you use the **Dynamic Form** syntax in a paragraph and there is a bound Angular object having the same name as the `${formName}`, the Angular object will have higher priority and the **Dynamic Form** will not be displayed. Example:
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
<img src="../assets/themes/zeppelin/img/screenshots/z_angularJs_overriding_dynamic_form.gif" />
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
<br />
[ZEPPELIN-1018] Apply auto "Table of Contents" generator to Zeppelin docs website ### What is this PR for? I added auto TOC(Table of Contents) generator for Zeppelin documentation website. TOC can help people looking through whole contents at a glance and finding what they want quickly. I just added `<div id="toc"></div>` to the each documentation header. [`toc`](https://github.com/apache/zeppelin/compare/master...AhyoungRyu:ZEPPELIN-1018?expand=1#diff-85af09fb498a5667ea455391533f945dR3) recognize `<h2>` & `<h3>` as a title in the docs and it automatically generate TOC. So I set a rule for this work. (I'll write this rule on `docs/CONTRIBUTING.md` or [docs/howtocontributewebsite](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/howtocontributewebsite.html)). ``` # Level-1 Heading <- Use only for the main title of the page ## Level-2 Heading <- Start with this one ### Level-3 heading <- Only use this one for child of Level-2 toc only recognize Level-2 & Level-3 ``` Please see the below attached screenshot image. ### What type of PR is it? Improvement & Documentation ### Todos * [x] - Add TOC generator * [x] - Apply TOC(`<div id="toc"></div>`) to every documentation and reorganize each headers(apply the above rule) * [x] - Fix some broken code block in several docs * [x] - Apply TOC to `r.md` (Currently R docs has some duplicated info since [this one](https://github.com/apache/zeppelin/commit/d5e87fb8ba98f08db5b0a4995104ce19f182c678) and [this one](https://github.com/apache/zeppelin/commit/7d6cc7e99154e2d337c11fdf8be1a874ed3e9ada) ) * [x] - Apply TOC to `install.md` after #1010 merged * [x] - Apply TOC to `interpreterinstallation.md` after #1042 merged ### What is the Jira issue? [ZEPPELIN-1018](https://issues.apache.org/jira/browse/ZEPPELIN-1018) ### How should this be tested? 1. Apply this patch and build `docs/` with [this guide](https://github.com/apache/zeppelin/tree/master/docs#build-documentation) 2. Visit some docs page. Then you can see TOC in the header of page. ### Screenshots (if appropriate) - Automatically generated TOC in Spark interpreter docs page <img width="831" alt="screen shot 2016-06-16 at 9 37 18 pm" src="https://cloud.githubusercontent.com/assets/10060731/16140902/945b9c7a-340a-11e6-91f3-b6174738bed0.png"> ### Questions: * Does the licenses files need update? No. Actually I used [jekyll-table-of-contents#copyright](https://github.com/ghiculescu/jekyll-table-of-contents#copyright). But I don't need to add a license for this :) * Is there breaking changes for older versions? No * Does this needs documentation? Maybe Author: AhyoungRyu <fbdkdud93@hanmail.net> Closes #1031 from AhyoungRyu/ZEPPELIN-1018 and squashes the following commits: e66397b [AhyoungRyu] Apply TOC to interpreterinstallation.md 009579b [AhyoungRyu] Add more info to 'What is the next?' in install.md 04cf501 [AhyoungRyu] Revert 'where to start' section b7cbe5f [AhyoungRyu] Fix typo cf0911c [AhyoungRyu] Rename license file 388f35a [AhyoungRyu] Add jekyll-table-of-contents license info 6394c70 [AhyoungRyu] Fix image path in python.md d00e4b1 [AhyoungRyu] Move interpreter/screenshot/ -> asset/../img/docs-img/ 3ffb383 [AhyoungRyu] Remove duplicated info in r.md & apply toc a03ca99 [AhyoungRyu] Exclude toc.js from pom.xml 3fae7df [AhyoungRyu] Apply auto generated toc to install.md d114a9d [AhyoungRyu] Address @felixcheung feedback 6a788fe [AhyoungRyu] Resize TOC tab indent 6760c00 [AhyoungRyu] Apply auto TOC to all of docs under docs/storage/ fbde57f [AhyoungRyu] Apply auto TOC to all of docs under docs/quickstart/ db76eb6 [AhyoungRyu] Apply auto TOC to all of docs under docs/install/ f35db47 [AhyoungRyu] Apply auto TOC to all of docs under docs/displaysystem/ b05365f [AhyoungRyu] Apply auto TOC to all of docs under docs/rest-api/ 163691c [AhyoungRyu] Apply auto TOC to all of docs under docs/manual/ bef398e [AhyoungRyu] Apply auto TOC to all of docs under docs/development/ 9c5f76b [AhyoungRyu] Apply auto TOC to all of docs under docs/interpreter/ 587d4ba [AhyoungRyu] Apply auto TOC to all of docs under docs/security/ 1f10b97 [AhyoungRyu] Change toc configuration 78dca9e [AhyoungRyu] Add toc.js for auto generating TOC
2016-06-25 19:44:53 +00:00
## Feature matrix comparison
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
[ZEPPELIN-1018] Apply auto "Table of Contents" generator to Zeppelin docs website ### What is this PR for? I added auto TOC(Table of Contents) generator for Zeppelin documentation website. TOC can help people looking through whole contents at a glance and finding what they want quickly. I just added `<div id="toc"></div>` to the each documentation header. [`toc`](https://github.com/apache/zeppelin/compare/master...AhyoungRyu:ZEPPELIN-1018?expand=1#diff-85af09fb498a5667ea455391533f945dR3) recognize `<h2>` & `<h3>` as a title in the docs and it automatically generate TOC. So I set a rule for this work. (I'll write this rule on `docs/CONTRIBUTING.md` or [docs/howtocontributewebsite](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/howtocontributewebsite.html)). ``` # Level-1 Heading <- Use only for the main title of the page ## Level-2 Heading <- Start with this one ### Level-3 heading <- Only use this one for child of Level-2 toc only recognize Level-2 & Level-3 ``` Please see the below attached screenshot image. ### What type of PR is it? Improvement & Documentation ### Todos * [x] - Add TOC generator * [x] - Apply TOC(`<div id="toc"></div>`) to every documentation and reorganize each headers(apply the above rule) * [x] - Fix some broken code block in several docs * [x] - Apply TOC to `r.md` (Currently R docs has some duplicated info since [this one](https://github.com/apache/zeppelin/commit/d5e87fb8ba98f08db5b0a4995104ce19f182c678) and [this one](https://github.com/apache/zeppelin/commit/7d6cc7e99154e2d337c11fdf8be1a874ed3e9ada) ) * [x] - Apply TOC to `install.md` after #1010 merged * [x] - Apply TOC to `interpreterinstallation.md` after #1042 merged ### What is the Jira issue? [ZEPPELIN-1018](https://issues.apache.org/jira/browse/ZEPPELIN-1018) ### How should this be tested? 1. Apply this patch and build `docs/` with [this guide](https://github.com/apache/zeppelin/tree/master/docs#build-documentation) 2. Visit some docs page. Then you can see TOC in the header of page. ### Screenshots (if appropriate) - Automatically generated TOC in Spark interpreter docs page <img width="831" alt="screen shot 2016-06-16 at 9 37 18 pm" src="https://cloud.githubusercontent.com/assets/10060731/16140902/945b9c7a-340a-11e6-91f3-b6174738bed0.png"> ### Questions: * Does the licenses files need update? No. Actually I used [jekyll-table-of-contents#copyright](https://github.com/ghiculescu/jekyll-table-of-contents#copyright). But I don't need to add a license for this :) * Is there breaking changes for older versions? No * Does this needs documentation? Maybe Author: AhyoungRyu <fbdkdud93@hanmail.net> Closes #1031 from AhyoungRyu/ZEPPELIN-1018 and squashes the following commits: e66397b [AhyoungRyu] Apply TOC to interpreterinstallation.md 009579b [AhyoungRyu] Add more info to 'What is the next?' in install.md 04cf501 [AhyoungRyu] Revert 'where to start' section b7cbe5f [AhyoungRyu] Fix typo cf0911c [AhyoungRyu] Rename license file 388f35a [AhyoungRyu] Add jekyll-table-of-contents license info 6394c70 [AhyoungRyu] Fix image path in python.md d00e4b1 [AhyoungRyu] Move interpreter/screenshot/ -> asset/../img/docs-img/ 3ffb383 [AhyoungRyu] Remove duplicated info in r.md & apply toc a03ca99 [AhyoungRyu] Exclude toc.js from pom.xml 3fae7df [AhyoungRyu] Apply auto generated toc to install.md d114a9d [AhyoungRyu] Address @felixcheung feedback 6a788fe [AhyoungRyu] Resize TOC tab indent 6760c00 [AhyoungRyu] Apply auto TOC to all of docs under docs/storage/ fbde57f [AhyoungRyu] Apply auto TOC to all of docs under docs/quickstart/ db76eb6 [AhyoungRyu] Apply auto TOC to all of docs under docs/install/ f35db47 [AhyoungRyu] Apply auto TOC to all of docs under docs/displaysystem/ b05365f [AhyoungRyu] Apply auto TOC to all of docs under docs/rest-api/ 163691c [AhyoungRyu] Apply auto TOC to all of docs under docs/manual/ bef398e [AhyoungRyu] Apply auto TOC to all of docs under docs/development/ 9c5f76b [AhyoungRyu] Apply auto TOC to all of docs under docs/interpreter/ 587d4ba [AhyoungRyu] Apply auto TOC to all of docs under docs/security/ 1f10b97 [AhyoungRyu] Change toc configuration 78dca9e [AhyoungRyu] Add toc.js for auto generating TOC
2016-06-25 19:44:53 +00:00
How does the front-end AngularJS API compares to the [back-end API](./back-end-angular.html) ? Below is a comparison matrix for both APIs:
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
[ZEPPELIN-1018] Apply auto "Table of Contents" generator to Zeppelin docs website ### What is this PR for? I added auto TOC(Table of Contents) generator for Zeppelin documentation website. TOC can help people looking through whole contents at a glance and finding what they want quickly. I just added `<div id="toc"></div>` to the each documentation header. [`toc`](https://github.com/apache/zeppelin/compare/master...AhyoungRyu:ZEPPELIN-1018?expand=1#diff-85af09fb498a5667ea455391533f945dR3) recognize `<h2>` & `<h3>` as a title in the docs and it automatically generate TOC. So I set a rule for this work. (I'll write this rule on `docs/CONTRIBUTING.md` or [docs/howtocontributewebsite](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/howtocontributewebsite.html)). ``` # Level-1 Heading <- Use only for the main title of the page ## Level-2 Heading <- Start with this one ### Level-3 heading <- Only use this one for child of Level-2 toc only recognize Level-2 & Level-3 ``` Please see the below attached screenshot image. ### What type of PR is it? Improvement & Documentation ### Todos * [x] - Add TOC generator * [x] - Apply TOC(`<div id="toc"></div>`) to every documentation and reorganize each headers(apply the above rule) * [x] - Fix some broken code block in several docs * [x] - Apply TOC to `r.md` (Currently R docs has some duplicated info since [this one](https://github.com/apache/zeppelin/commit/d5e87fb8ba98f08db5b0a4995104ce19f182c678) and [this one](https://github.com/apache/zeppelin/commit/7d6cc7e99154e2d337c11fdf8be1a874ed3e9ada) ) * [x] - Apply TOC to `install.md` after #1010 merged * [x] - Apply TOC to `interpreterinstallation.md` after #1042 merged ### What is the Jira issue? [ZEPPELIN-1018](https://issues.apache.org/jira/browse/ZEPPELIN-1018) ### How should this be tested? 1. Apply this patch and build `docs/` with [this guide](https://github.com/apache/zeppelin/tree/master/docs#build-documentation) 2. Visit some docs page. Then you can see TOC in the header of page. ### Screenshots (if appropriate) - Automatically generated TOC in Spark interpreter docs page <img width="831" alt="screen shot 2016-06-16 at 9 37 18 pm" src="https://cloud.githubusercontent.com/assets/10060731/16140902/945b9c7a-340a-11e6-91f3-b6174738bed0.png"> ### Questions: * Does the licenses files need update? No. Actually I used [jekyll-table-of-contents#copyright](https://github.com/ghiculescu/jekyll-table-of-contents#copyright). But I don't need to add a license for this :) * Is there breaking changes for older versions? No * Does this needs documentation? Maybe Author: AhyoungRyu <fbdkdud93@hanmail.net> Closes #1031 from AhyoungRyu/ZEPPELIN-1018 and squashes the following commits: e66397b [AhyoungRyu] Apply TOC to interpreterinstallation.md 009579b [AhyoungRyu] Add more info to 'What is the next?' in install.md 04cf501 [AhyoungRyu] Revert 'where to start' section b7cbe5f [AhyoungRyu] Fix typo cf0911c [AhyoungRyu] Rename license file 388f35a [AhyoungRyu] Add jekyll-table-of-contents license info 6394c70 [AhyoungRyu] Fix image path in python.md d00e4b1 [AhyoungRyu] Move interpreter/screenshot/ -> asset/../img/docs-img/ 3ffb383 [AhyoungRyu] Remove duplicated info in r.md & apply toc a03ca99 [AhyoungRyu] Exclude toc.js from pom.xml 3fae7df [AhyoungRyu] Apply auto generated toc to install.md d114a9d [AhyoungRyu] Address @felixcheung feedback 6a788fe [AhyoungRyu] Resize TOC tab indent 6760c00 [AhyoungRyu] Apply auto TOC to all of docs under docs/storage/ fbde57f [AhyoungRyu] Apply auto TOC to all of docs under docs/quickstart/ db76eb6 [AhyoungRyu] Apply auto TOC to all of docs under docs/install/ f35db47 [AhyoungRyu] Apply auto TOC to all of docs under docs/displaysystem/ b05365f [AhyoungRyu] Apply auto TOC to all of docs under docs/rest-api/ 163691c [AhyoungRyu] Apply auto TOC to all of docs under docs/manual/ bef398e [AhyoungRyu] Apply auto TOC to all of docs under docs/development/ 9c5f76b [AhyoungRyu] Apply auto TOC to all of docs under docs/interpreter/ 587d4ba [AhyoungRyu] Apply auto TOC to all of docs under docs/security/ 1f10b97 [AhyoungRyu] Change toc configuration 78dca9e [AhyoungRyu] Add toc.js for auto generating TOC
2016-06-25 19:44:53 +00:00
<table class="table-configuration">
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
<thead>
<tr>
<th>Actions</th>
<th>Front-end API</th>
<th>Back-end API</th>
</tr>
</thead>
<tr>
<td>Initiate binding</td>
<td>z.angularbind(var, initialValue, paragraphId)</td>
<td>z.angularBind(var, initialValue)</td>
</tr>
<tr>
<td>Update value</td>
<td>same to ordinary angularjs scope variable, or z.angularbind(var, newValue, paragraphId)</td>
<td>z.angularBind(var, newValue)</td>
</tr>
<tr>
<td>Watching value</td>
<td>same to ordinary angularjs scope variable</td>
<td>z.angularWatch(var, (oldVal, newVal) => ...)</td>
</tr>
<tr>
<td>Destroy binding</td>
<td>z.angularUnbind(var, paragraphId)</td>
<td>z.angularUnbind(var)</td>
</tr>
<tr>
<td>Executing Paragraph</td>
<td>z.runParagraph(paragraphId)</td>
<td>z.run(paragraphId)</td>
[ZEPPELIN-1665] Z.run with external note executable and access resource for zeppelin in each interpreter ### What is this PR for? Currently, the z.run command is restricted. Only paragraphs in a single note can be executed. I have modified this to allow you to freely execute paragraphs of other notes. This PR provides the basis for the freeful use of Zeppelin's resources at each Interpreter implementation. ### What type of PR is it? Improvement, Feature ### Todos - [x] extends z.run - [x] run all paragraph in external note - [x] run paragraph for external note. - [x] get resource for zeppelin in each interpreter. - [x] improve test case. - [x] how to use docuement ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-1665 ### How should this be tested? Currently under development. run paragraph in same note ``` %spark z.run("paragraphID") ``` run paragraph with external note ``` z.run("noteid", "paragraphid"); ``` all note run ``` z.runNote("noteid"); ``` ### Screenshots (if appropriate) - paragraph run ![zrun](https://cloud.githubusercontent.com/assets/10525473/20304857/ca056300-ab75-11e6-8276-0fe0667a5a24.gif) - noterun ![runnote](https://cloud.githubusercontent.com/assets/10525473/20472104/527cd8de-affa-11e6-9587-0438140e264f.gif) ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? yes Author: CloverHearts <cloverheartsdev@gmail.com> Closes #1637 from cloverhearts/extends-zrun-remote-transaction and squashes the following commits: 41fa9d7 [CloverHearts] restore unless changed and import 113b475 [CloverHearts] Merge branch 'master' into extends-zrun-remote-transaction 03a3a2b [CloverHearts] testcase change z.run(2, context) to z.run(2) 2a2c173 [CloverHearts] Merge branch 'master' into extends-zrun-remote-transaction f2e3bcf [CloverHearts] fix TestCase 5a80a5a [CloverHearts] last test case time check to print string e6cd82c [CloverHearts] Merge branch 'master' into extends-zrun-remote-transaction 3862166 [CloverHearts] regenerate thrfit class 5ec4640 [CloverHearts] change defined protocol for thrift 7562535 [CloverHearts] remove unused import and asterisk import 8a54917 [CloverHearts] Merge branch 'master' into extends-zrun-remote-transaction 342752d [CloverHearts] add document for extends z.run and z.runNote 292319a [CloverHearts] add test case for extends z.run and z.runNote 10c2a47 [CloverHearts] Implement runNote and re implement run method f9661c8 [CloverHearts] Merge branch 'master' into extends-zrun-remote-transaction 9ab05af [CloverHearts] Change structure and remove remoteWorksManager 8cbe46c [CloverHearts] remote remoteworksController in interpreter.java 8d42c16 [CloverHearts] Merge branch 'master' into extends-zrun-remote-transaction f11fed4 [CloverHearts] Merge branch 'workflow' into extends-zrun-remote-transaction c074f07 [CloverHearts] fix sio support 4b1ef08 [CloverHearts] fix thrift interface 2628a20 [CloverHearts] fix thrift 6fbe08a [CloverHearts] Merge branch 'master' into workflow 3f75bd5 [CloverHearts] support scald 55e8704 [CloverHearts] support spark r 5a7886f [CloverHearts] fix sio support afb9db7 [CloverHearts] Merge branch 'master' into workflow 3ed556c [CloverHearts] remove debug console message. 3d34f9e [CloverHearts] Implement getParagraphRunner transaction. 2523238 [CloverHearts] Implement eventForWait class 0570ae8 [CloverHearts] add remote works controller class and include interpreter factory 6e1f219 [CloverHearts] code base workflow for remote zeppelin server control default thrift transaction.
2016-11-28 15:09:33 +00:00
</tr>
<tr>
<td>Executing Paragraph (Specific paragraphs in other notes) (</td>
<td></td>
<td>z.run(noteid, paragraphId)</td>
</tr>
<tr>
<td>Executing note</td>
<td></td>
<td>z.runNote(noteId)</td>
</tr>
[ZEPPELIN-742] Add documentation for front-end AngularJS AP ### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId** ![zeppelin_ui_layout](https://cloud.githubusercontent.com/assets/1532977/14898823/346a5e3e-0d89-11e6-85af-7483f93f1172.gif) New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic ![front-end angular interactions](https://cloud.githubusercontent.com/assets/1532977/14898847/546cf692-0d89-11e6-850d-ae40cf676541.gif) ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: fde4fb4 [DuyHai DOAN] Update menu name after code review 2a1fa9b [DuyHai DOAN] [ZEPPELIN-742] Add documentation for front-end AngularJS API 0b719d3 [DuyHai DOAN] [ZEPPELIN-742] Add documentation for Zeppelin UI Layout & paragraphId
2016-04-30 12:44:45 +00:00
<tbody>
<tbody>
</table>
Both APIs are pretty similar, except for value watching where it is done naturally by AngularJS internals on the front-end and by user custom watcher functions in the back-end.
There is also a slight difference in term of scope. Front-end API limits the Angular object binding to a paragraph scope whereas back-end API allows you to bind an Angular object at the global or note scope. This restriction has been designed purposely to avoid Angular object leaks and scope pollution.