Skip to content

Commit e144e0d

Browse files
committed
Apply toc to writingzeppelinapplication.md
1 parent 7dc0b95 commit e144e0d

File tree

1 file changed

+29
-27
lines changed

1 file changed

+29
-27
lines changed

docs/development/writingzeppelinapplication.md

Lines changed: 29 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -19,13 +19,16 @@ limitations under the License.
1919
-->
2020
{% include JB/setup %}
2121

22-
# What is Zeppelin Application (Experimental)
22+
# Writing a new Application (Experimental)
2323

24-
Apache Zeppelin Application is a package that runs on Interpreter process and displays it's output inside of the notebook. While application runs on Interpreter process, it's able to access resources provided by Interpreter through ResourcePool. Output is always rendered by AngularDisplaySystem. Therefore application provides all the possiblities of making interactive graphical application that uses data and processing power of any Interpreter.
24+
<div id="toc"></div>
25+
26+
## What is Apache Zeppelin Application
2527

28+
Apache Zeppelin Application is a package that runs on Interpreter process and displays it's output inside of the notebook. While application runs on Interpreter process, it's able to access resources provided by Interpreter through ResourcePool. Output is always rendered by AngularDisplaySystem. Therefore application provides all the possiblities of making interactive graphical application that uses data and processing power of any Interpreter.
2629

2730

28-
## Writing your own Application
31+
## Make your own Application
2932

3033
Writing Application means extending `org.apache.zeppelin.helium.Application`. You can use your favorite IDE and language while Java class files are packaged into jar. `Application` class looks like
3134

@@ -57,7 +60,7 @@ You can check example applications under [./zeppelin-examples](https://github.co
5760

5861
In the development mode, you can run your Application in your IDE as a normal java application and see the result inside of Zeppelin notebook.
5962

60-
org.apache.zeppelin.interpreter.dev.ZeppelinApplicationDevServer can run Zeppelin Application in development mode.
63+
`org.apache.zeppelin.interpreter.dev.ZeppelinApplicationDevServer` can run Zeppelin Application in development mode.
6164

6265
```java
6366

@@ -68,11 +71,10 @@ public static void main(String[] args) throws Exception {
6871
LocalResourcePool pool = new LocalResourcePool("dev");
6972
pool.put("date", new Date());
7073

71-
// run application in devlopment mode with give resource
74+
// run application in devlopment mode with given resource
7275
// in this case, Clock.class.getName() will be the application class name
7376
ZeppelinApplicationDevServer devServer = new ZeppelinApplicationDevServer(
74-
Clock.class.getName(),
75-
pool.getAll());
77+
Clock.class.getName(), pool.getAll());
7678

7779
// start development mode
7880
devServer.start();
@@ -84,12 +86,10 @@ public static void main(String[] args) throws Exception {
8486
In the Zeppelin notebook, run `%dev run` will connect to application running in development mode.
8587

8688

87-
88-
8989
## Package file
9090

9191
Package file is a json file that provides information about the application.
92-
Json file contains following informations
92+
Json file contains the following information
9393

9494
```
9595
{
@@ -108,51 +108,53 @@ Json file contains following informations
108108

109109
#### name
110110

111-
Name is a string in '[group].[name]' format.
112-
[group] and [name] allows only [A-Za-z0-9_].
113-
Group is normally organization name who creates this application.
111+
Name is a string in `[group].[name]` format.
112+
`[group]` and `[name]` allow only `[A-Za-z0-9_]`.
113+
Group is normally the name of organization who creates this application.
114114

115115
#### description
116116

117-
Short description. about application
117+
A short description about the application
118118

119119
#### artifact
120120

121121
Location of the jar artifact.
122-
"groupId:artifactId:version" will make load artifact from maven repository.
123-
If jar is in local filesystem, absolute/relative can be used.
122+
`"groupId:artifactId:version"` will load artifact from maven repository.
123+
If jar exists in the local filesystem, absolute/relative can be used.
124124

125125
e.g.
126126

127127
When artifact exists in Maven repository
128128

129-
`artifact: "org.apache.zeppelin:zeppelin-examples:0.6.0"`
130-
131-
When artifact exists in local filesystem
129+
```
130+
artifact: "org.apache.zeppelin:zeppelin-examples:0.6.0"
131+
```
132132

133-
`artifact: "zeppelin-example/target/zeppelin-example-0.6.0.jar"`
133+
When artifact exists in the local filesystem
134134

135+
```
136+
artifact: "zeppelin-example/target/zeppelin-example-0.6.0.jar"
137+
```
135138

136139
#### className
137140

138141
Entry point. Class that extends `org.apache.zeppelin.helium.Application`
139142

140-
141143
#### resources
142144

143-
Two dimensional array that defines required resources by name or by className. Helium Application launcher will compare resources in the ResourcePool with informations in this field and suggest application only when all required resources are available in the ResourcePool.
145+
Two dimensional array that defines required resources by name or by className. Helium Application launcher will compare resources in the ResourcePool with the information in this field and suggest application only when all required resources are available in the ResourcePool.
144146

145-
Resouce name is a string which will be compared with name of objects in the ResourcePool. className is a string with ":" prepended, which will be compared with className of the objects in the ResourcePool.
147+
Resouce name is a string which will be compared with the name of objects in the ResourcePool. className is a string with ":" prepended, which will be compared with className of the objects in the ResourcePool.
146148

147-
Application may require two or more resources. Required resource can be listed inside of json array. For example, if application requires object "name1", "name2" and "className1" type of object to run, resources field can be
149+
Application may require two or more resources. Required resources can be listed inside of the json array. For example, if the application requires object "name1", "name2" and "className1" type of object to run, resources field can be
148150

149151
```
150152
resources: [
151153
[ "name1", "name2", ":className1", ...]
152154
]
153155
```
154156

155-
If Application can handle alternative combination of required resource, alternative set can be listed as below.
157+
If Application can handle alternative combination of required resources, alternative set can be listed as below.
156158

157159
```
158160
resources: [
@@ -162,7 +164,7 @@ resources: [
162164
]
163165
```
164166

165-
Easier way of understanding this scheme is
167+
Easier way to understand this scheme is
166168

167169
```
168170
resources: [
@@ -175,7 +177,7 @@ resources: [
175177

176178
#### icon
177179

178-
Icon to be used on the application button. String in this field will be rendered as a html.
180+
Icon to be used on the application button. String in this field will be rendered as a HTML tag.
179181

180182
e.g.
181183

0 commit comments

Comments
 (0)