[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-425) Document 7.1.0 N&N in User Guide
Michelle Murray (JIRA)
jira-events at lists.jboss.org
Wed Nov 13 22:56:05 EST 2013
[ https://issues.jboss.org/browse/TOOLSDOC-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923345#comment-12923345 ]
Michelle Murray commented on TOOLSDOC-425:
------------------------------------------
Hi [~xcoulon],
I am adding info about AsciiDoc ability to LiveReload chapter in JBDS User Guide. 2 questions:
1) I haven't used LiveReload for a while so am trying to remind myself how it works. Couldn't get it to work with xhtml files but is that because it only works with html files (and now asciidoc)?
2) I think the AsciiDoctor.js is just rendering the asciidoc file in the browser. And LiveReload (and/or LiveReload browser extensions) does all of the LiveReload work. Is that right? If so and LiveReload Server in IDE is doing all of the work, why is the AsciiDoctor.js necessary?
> Document 7.1.0 N&N in User Guide
> --------------------------------
>
> Key: TOOLSDOC-425
> URL: https://issues.jboss.org/browse/TOOLSDOC-425
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Original Estimate: 2 days, 2 hours
> Remaining Estimate: 2 days, 2 hours
>
> For info see:
> 1) N&N http://docs.jboss.org/tools/whatsnew/
> 2) RNs http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBoss_Developer_Studio/7.1/html/Release_Notes_7.1.0/index.html
> Specifically:
> * *BrowserSim* - touch events, error log *[Done]*
> * *JSF Tools* - properties tab *[Not necessary to doc]*
> * *LiveReload Tools* - asciidoc files *[Waiting on info]*
> * *OpenShift Tools* - multiple domains, env variables, new openshift app wizard, custom commit message, tail files function *[Done]*
--
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
More information about the jbosstools-issues
mailing list