Changes for page EOModelDoc

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -19,42 +19,26 @@
19	19
20	20	The command line syntax of for EOModelDoc:
21	21
22		-##java --jar eomodeldoc.jar --output /path/to/output/folder -model /path/to/model.eomodeld]** -modelgroup /path/to/working/dir] -templates /path/to/templates] -entityURLTemplate "http:~/~/whatever?$entity.classNamePath}.html**##
	22	+##eomodeldoc --output /path/to/output/folder --model /path/to/model.eomodeld]** -modelgroup /path/to/working/dir] -templates /path/to/templates] -entityURLTemplate "http:~/~/whatever?$entity.classNamePath}.html**##
23	23
24		-|=Parameter|=Usage / Function
25		-|output|Path to the directory where the output HTML files will be written.
26		-|model|Path to one model to generate documentation for. This parameter can be used multiple times, once for each model.
27		-|modelgroup|The path to an Eclipse or IDEA project. All models listed in the project will be documented. This defaults to the current working directory.
28		-|templates|Path to the directory where the Velocity templates are stored. See the [[||anchor="Template Files"]] section below for details on these templates. If this is not specified, the default templates inside the eomodeldoc.jar file will be used.
29		-|entityURLTemplate|URL to the JavaDocs for the classes in the model. This is used to create links from the EOModel documentation to the JavaDoc documentation. The dots in the classpath are replaced with "/" when the path is generated.
30		-
31		-=== Usage Examples ===
32		-
33		-Document one model:
34		-
35		-{{code}}
36		-
37		-java -jar eomodeldoc.jar -model /path/to/model.eomodeld -output /tmp/eomodeldoc
38		-
39		-{{/code}}
40		-
	24	+Still working on all the model loaders, but you should be able to do
41	41
42		-Document all models based on the Eclipse or IDEA project definition:
	26	+java --jar eomodeldoc.jar --model /path/to/model.eomodeld --output /tmp/
	27	+eomodeldoc
	28	+(will load all the models in the modelgroup based on your eclipse or
	29	+IDEA project files ..... allegedly ... still working the kinks out on
	30	+this)
	31	+or
	32	+
	33	+java --jar eomodeldoc.jar --modelgroup /path/to/project --output /tmp/
	34	+eomodeldoc
	35	+(i haven't tried that one yet)
	36	+
	37	+or
	38	+
	39	+java --jar eomodeldoc.jar --output /tmp/eomodeldoc
	40	+from inside your project
43	43
44		-{{code}}
45		-
46		-java -jar eomodeldoc.jar -modelgroup /path/to/project -output /tmp/eomodeldoc
47		-
48		-{{/code}}
49		-
50		-Document all models based on the Eclipse/IDEA project definition (when current working directory is the top level of the project):
51		-
52		-{{code}}
53		-
54		-java -jar eomodeldoc.jar -output /tmp/eomodeldoc
55		-
56		-{{/code}}
57		-
58	58	== Template Files ==
59	59
60	60	Default templates are included in the eomodeldoc.jar file. You can extract these templates to use as a basis for your own templates with this command:
...	...	@@ -65,21 +65,17 @@
65	65
66	66	{{/code}}
67	67
68		-Only need to have the templates that are different from the jar?
69		-
70	70	The templates and their function are:
71	71
72	72	|=Template Name|=Usage / Function
73		-|indexModels.html.vm|Left pane index of all models.
74		-|indexOverview.html.vm|Left pane index of the contents of all models (e.g. list of entities and stored procedures).
75		-|modelOverview.html.vm|Left pane index of the contents of one model (e.g. list of entities and stored procedures).
76		-|indexContent.html.vm|Main frame description of each model and contents of each model (e.g. list of entities and stored procedures).
77		-|modelContent.html.vm|Main frame contents of one model (list of entities and stored procedures).|
78		-|entityContent.html.vm|Main frame contents for one Entity
79		-|storedProcedureContent.html.vm|Main frame contents for one stored procedure.
80		-|index.html.vm|Top level index.html file defining frameset. You probably won't need to modify this.
81		-|prototype.js.vm|[[Prototype>>http://www.prototypejs.org/learn]] JavaScript file so that the generated documentation can use Ajax whizziness. You probably won't need to modify this.
82		-|eomodeldoc.css.vm|CSS file that controls what the generate output looks like.
83		-|eomodeldoc.js.vm|JavaScript file that cleans up the display. You probably won't need to modify this.
84		-
85		-== Running from Ant ==
	55	+|entityContent.html.vm|
	56	+|eomodeldoc.css.vm|
	57	+|eomodeldoc.js.vm|
	58	+|index.html.vm|
	59	+|indexContent.html.vm|
	60	+|indexModels.html.vm|
	61	+|indexOverview.html.vm|
	62	+|modelContent.html.vm| |
	63	+|modelOverview.html.vm|
	64	+|prototype.js.vm|
	65	+|storedProcedureContent.html.vm|