Changes for page EOModelDoc

Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.chillatgvc
	1	+XWiki.pierce

Content

...	...	@@ -10,9 +10,9 @@
10	10
11	11	== Overview ==
12	12
13		-EOModelDoc is a command line tool to generate HTML documentation of a set of EOModels. It is a replacement for [[EOReporter>>http://www.rubicode.com/Software/EOReporter/]] (which will not work on Leopard and newer releases of OS X). EOModelDoc was funded by the Apple iTunes Store and released to the community.
	13	+EOModelDoc is a command line tool to generate HTML documentation of a set of EOModels. It is a replacement for [[EOReporter>>http://www.rubicode.com/Software/EOReporter/]] (which will not work on Leopard and newer releases of OS X). EOModelDoc was funded by the Apple iTunes Store and released to the community.
14	14
15		-On the WOLips side, from version 3.3.x, [[Entity Modeler>>Using Entity Modeler]] has a Documentation tab on all of the elements of a model that lets you record HTML documentation for your model, entities, attributes, etc. There is even an HTML preview. You can then run eomodeldoc to produce documentation much like javadoc for your model.
	15	+On the WOLips side, from version 3.3.x, [[Entity Modeler>>Using Entity Modeler]] has a Documentation tab on all of the elements of a model that lets you record HTML documentation for your model, entities, attributes, etc. There is even an HTML preview. You can then run eomodeldoc to produce documentation much like javadoc for your model.
16	16
17	17	== Future Plans ==
18	18
...	...	@@ -20,30 +20,30 @@
20	20
21	21	== Download and Example Output ==
22	22
23		-[[Download EOModelDoc jar>>http://webobjects.mdimension.com/wolips/eomodeldoc.jar]]
	23	+[[Download EOModelDoc jar>>http://webobjects.mdimension.com/wolips/eomodeldoc-latest.jar]]
24	24
25		-This is an example of the current state of eomodeldoc (the default templates are not done, but it will give you an idea of what it can do). The templates are all Velocity-based, and you can override them with custom versions. This was run in the BugTracker project folder. This model does not have documentation added to it with the new Entity Modeler yet, so it looks a little more bare than it would if it was documented properly. I'll probably document it just to have a full example to show.
	25	+This is an example of the current state of eomodeldoc (the default templates are not done, but it will give you an idea of what it can do). The templates are all Velocity-based, and you can override them with custom versions. This was run in the BugTracker project folder. This model does not have documentation added to it with the new Entity Modeler yet, so it looks a little more bare than it would if it was documented properly. I'll probably document it just to have a full example to show.
26	26	[[View Example Output>>http://webobjects.mdimension.com/wolips/eomodeldoc_example/]]
27	27
28	28	== Usage ==
29	29
30	30	The command line syntax of for EOModelDoc:
31		-
32		-##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:~/~/domain/path/to/JavaDocs/$entity.classNamePath.html**##
33	33
34		-|=Parameter|=Usage / Function
35		-|output|Path to the directory where the output HTML files will be written.
36		-|model|Path to one model to generate documentation for. This parameter can be used multiple times, once for each model.
37		-|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.
38		-|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.
39		-|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.
	32	+##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:~/~/domain/path/to/JavaDocs/$entity.classNamePath.html##
40	40
	34	+|= Parameter |= Usage / Function
	35	+| output | Path to the directory where the output HTML files will be written.
	36	+| model | Path to one model to generate documentation for. This parameter can be used multiple times, once for each model.
	37	+| 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.
	38	+| 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.
	39	+| 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.
	40	+
41	41	=== Notes ===
42	42
43		-* Only ##-output## is required
44		-* Usually only one of ##-modelGroup## or ##-model## is used (i.e. not both at the same time)
45		-* The ##-templates## path only needs to point the the templates that you have changed. If any templates are not found on that path, the defaults from the jar are used.
46		-* For ##-entityURLTemplate## the ##http:~/~/domain/path/to/JavaDocs/## the path to the index.html file that JavaDoc generates. It will be something like ##http:~/~/developer.apple.com/documentation/MacOSXServer/Reference/WO54_Reference/##
	43	+* Only ##output## is required
	44	+* Usually only one of ##modelGroup## or ##model## is used (i.e. not both at the same time)
	45	+* The ##templates## path only needs to point the the templates that you have changed. If any templates are not found on that path, the defaults from the jar are used.
	46	+* For ##entityURLTemplate## the ##[[http://domain/path/to/JavaDocs/]]## the path to the index.html file that JavaDoc generates. It will be something like ##[[http://developer.apple.com/documentation/MacOSXServer/Reference/WO54_Reference/]]##. If the EOModelDocs and JavaDocs are on the same server, you can use absolute or relative paths instead of a full URL:##[[http://developer.apple.com/documentation/MacOSXServer/Reference/WO54_Reference/]]##
47	47
48	48	=== Usage Examples ===
49	49
...	...	@@ -55,12 +55,11 @@
55	55
56	56	{{/code}}
57	57
58		-
59		-Document all models based on the Eclipse or IDEA project definition:
	58	+Document all models based on the Eclipse or IDEA project definition:
60	60
61	61	{{code}}
62	62
63		-java -jar /path/to/eomodeldoc.jar -modelgroup /path/to/project -output /tmp/eomodeldoc
	62	+java -jar /path/to/eomodeldoc.jar -modelgroup /path/to/project -output /tmp/eomodeldoc
64	64
65	65	{{/code}}
66	66
...	...	@@ -68,12 +68,14 @@
68	68
69	69	{{code}}
70	70
71		-java -jar /path/to/eomodeldoc.jar -output /tmp/eomodeldoc
	70	+java -jar /path/to/eomodeldoc.jar -output /tmp/eomodeldoc
72	72
73	73	{{/code}}
74	74
75	75	== Running from Ant ==
76	76
	76	+**Note**: do not put this jar on your classpath Chaos and Other Bad Things may ensue.
	77	+
77	77	There is no Ant task (yet) for EOModelDoc. You can run it with an ##java## task following this pattern:
78	78
79	79	{{code value="xml"}}
...	...	@@ -139,23 +139,22 @@
139	139
140	140	{{/code}}
141	141
142		-See the [[EOGenerator template documentation>>EOGenerator Templates and Additions]] documentation for information on customizing these templates. The ##-templates## path only needs to point the the templates that you have changed. If any templates are not found on that path, the defaults from the jar are used.
	143	+See the [[EOGenerator template documentation>>EOGenerator Templates and Additions]] documentation for information on customizing these templates. The ##templates## path only needs to point the the templates that you have changed. If any templates are not found on that path, the defaults from the jar are used.
143	143
144	144	The templates and their function are:
145	145
146		-|=Template Name|=Usage / Function
147		-|indexModels.html.vm|Left pane index of all models.
148		-|indexOverview.html.vm|Left pane index of the contents of all models (e.g. list of entities and stored procedures).
149		-|modelOverview.html.vm|Left pane index of the contents of one model (e.g. list of entities and stored procedures).
150		-|indexContent.html.vm|Main frame description of each model and contents of each model (e.g. list of entities and stored procedures).
151		-|modelContent.html.vm|Main frame contents of one model (list of entities and stored procedures).|
152		-|entityContent.html.vm|Main frame contents for one Entity
153		-|storedProcedureContent.html.vm|Main frame contents for one stored procedure.
154		-|index.html.vm|Top level index.html file defining frameset. You probably won't need to modify this.
155		-|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.
156		-|eomodeldoc.css.vm|CSS file that controls what the generate output looks like.
157		-|eomodeldoc.js.vm|JavaScript file that cleans up the display. You probably won't need to modify this.
158		-
	147	+|= Template Name |= Usage / Function
	148	+| indexModels.html.vm | Left pane index of all models.
	149	+| indexOverview.html.vm | Left pane index of the contents of all models (e.g. list of entities and stored procedures).
	150	+| modelOverview.html.vm | Left pane index of the contents of one model (e.g. list of entities and stored procedures).
	151	+| indexContent.html.vm | Main frame description of each model and contents of each model (e.g. list of entities and stored procedures).
	152	+| modelContent.html.vm | Main frame contents of one model (list of entities and stored procedures).
	153	+| entityContent.html.vm | Main frame contents for one Entity
	154	+| storedProcedureContent.html.vm | Main frame contents for one stored procedure.
	155	+| index.html.vm | Top level index.html file defining frameset. You probably won't need to modify this.
	156	+| 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.
	157	+| eomodeldoc.css.vm | CSS file that controls what the generate output looks like.
	158	+| eomodeldoc.js.vm | JavaScript file that cleans up the display. You probably won't need to modify this. |
159	159	Some pictures will illustrate this:
160	160
161	161	----
...	...	@@ -169,7 +169,6 @@
169	169	----
170	170
171	171	[[image:EOModelDocTemplates3.png||width="800"]]
172		-
173	173
174	174	----
175	175