[ 
https://issues.apache.org/jira/browse/OFBIZ-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472426#comment-13472426
 ] 

Tom Burns commented on OFBIZ-4941:
----------------------------------

Jacques,

Good, I guess there are no more issues.

Note a fix is needed relating to -
Rev 1361130 
Moved the "birt" component out of framework to specialpurpose; moved all the 
birt reports from the applications to the birt component itself, where the 
_*application webapps are overriden to inject the reports*_; the end result is 
the same but since all these birt reports are simply a proof of concepts that 
cannot be used in production (for example they use hardcoded userlogin for 
authentication) the birt component should be probably disabled by default (but 
this will be discussed in the dev list).
Now it will be very easy to extract the birt component (for OFBiz Extras) or to 
disable it when deploying to production or when interested in sparing some 
hardware resources. I did some cursory tests but since the work has been 
challenging and rather complex I would appreciate testing help and also reviews 
to finds chunks of code that I could have missed and that could be moved out as 
well.

I've added a patch to OFBIZ-5033 that simply places remarks around the problem 
code. Others may have a better solution.

Tom
                
> Proposal for a new help system
> ------------------------------
>
>                 Key: OFBIZ-4941
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-4941
>             Project: OFBiz
>          Issue Type: Wish
>          Components: ALL COMPONENTS
>    Affects Versions: SVN trunk
>            Reporter: Jacques Le Roux
>            Priority: Minor
>             Fix For: SVN trunk
>
>         Attachments: docbook diff.patch, docbook-xsl-1.77.1.zip, 
> HelpAccounting.jpg, help_content.jpg, help_ofbizhelp.jpg, helppdf.zip, 
> HelpPerformanceReview1.jpg, HelpPerformanceReview2.jpg, HelpRoadmap.jpg, 
> help_webhlep.jpg, jh.jar, LICENSE.html, OFBIZ-4941 POC HR Help.patch, 
> WebhelpFiles.zip, WebhelpHRAppDocbook.zip, webhelp.jpg
>
>
> Quoting Tom Burns at OFBIZ-4869
> {quote}
> This is a status update just to let anyone who is interested know that this 
> item is being worked on.
> I started out using the OFBiz structure for help docs but after a while I 
> needed/wanted something more expressive.
> Here is what I wound up using for development:
>     Java Help System http://java.net/projects/javahelp/content
>     DocBook 5: The Definitive Guide
>     http://www.docbook.org/tdg5/en/html/docbook.html
>     http://www.docbook.org/xml/5.0/
>     DocBook XSL: The Complete Guide
>     http://www.sagehill.net/docbookxsl/index.html
>     
> http://sourceforge.net/projects/docbook/files/docbook-xsl/1.77.1/docbook-xsl-1.77.1.zip
>     Help Master - FE for managing java help files. Best feature drag and drop 
> TOC creates TOC matching file folder structure. Convenient launcher for 
> viewing & testing. http://www.halogenware.com/software/helpmaster.html
>     XML Mind XML Editor - Free Personal Edition is far better then editing in 
> Eclipse. download from http://www.xmlmind.com/xmleditor/download.shtml
>     Tutorial - DocBook editing with XML Mind XML Editor. Worth going through 
> http://www.xmlmind.com/xmleditor/tutorial.html
>     Read Me First style guide from Sun (cost from Amazon 1 cent + shipping)
> Attached are some screen shots of the results.
> Every screen is/will be documented in a similar structure. This is as much 
> for defining requirements and testing as for help. More work but worth it.
> The screenshots show a Java Help format generated using DocBook XSL. This 
> will likely not be the final presentation format.
> Note the Performance Review screen shots do not match the trunk. There is a 
> bug in update screen and I did some clean up of labels and drop-down list. 
> There are issues like this all through the application so I did not want to 
> get bogged down with patches at this time.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to