You need to log in before you can comment on or make changes to this bug.
The doc builder will now have to identify the javascript files that the each widget uses. If you look at the schema of this new section you will notice that it has included js variables and function sections. Although important sections for the js file. It is not expected that the docbuilder will go into the js file and extract this information. Please make sure the the jsfile name is populated if a jsfile is used by a widget. eg. MapDHTML - <ca:widgetdoc><ca:jsfiles><ca:jsfiles><ca:name>
assign to bill and target to rc1
This has not been added, bill may want to make comments on this. Since, there maybe some technical issues. The widget docs has this new section so still can be manually added if important. moving target to final release
Looking at this one now.
The doc builder part is fixed in CVS. The <db:jsfiles><db:jsfile><db:name>ttt</db:name>.... entries now get populated. Re-assigning to Chris to update the XML templates etc. to merge correctly. Chris, we should discuss how the merging will happen, I think there might be some confusion on where the javascript functions come from. There are basically 2 sources of JS functions and I'm not sure how these should be handled in the docs. One source is native in the widget and the other source is from the js files. To date only the native functions have been documented to date.
changed target to future. Doc builder does not have a merging process from widget doc to new widget doc. I was only able to build an xslt to build new widgets docs from the default template.
Only the functionality changes will be addressed, in documentation, in the release cycle. Setting to FUTURE.
