[
https://jira.codehaus.org/browse/JBEHAVE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276744#comment-276744
]
Mauro Talevi commented on JBEHAVE-584:
--------------------------------------
Presumably, we should be able to maintain the format in txt too, like in a
wiki.
Let's decide what formats we are going to or can support and then we can decide
whether it warrants a separate module or not. Not against it, just would like
to understand the usecase first.
For the google access, ideally we'd want to create a group access and have a
read-only user. It'd be great if you could investigate the issue with the
Google Docs folks and present the options we have. I'd be surprised if they
did not offer some sort of test access (but perhaps it's not available for
general public).
> Support loading stories from Google Docs
> ----------------------------------------
>
> Key: JBEHAVE-584
> URL: https://jira.codehaus.org/browse/JBEHAVE-584
> Project: JBehave
> Issue Type: New Feature
> Components: Core, ODF Support
> Reporter: Bart De Neuter
> Assignee: Mauro Talevi
> Priority: Minor
> Fix For: 3.5
>
> Attachments: googledocs.patch
>
>
> As a BA I want to be able to write my story in Google Docs.
> This has the advantage that the stories are in the cloud and multiple
> stakeholders (BA, developer, ...) work at the same time on the same document.
> By using the Google docs API, a document can be exported to ODT and be
> delegated to the ODT support in JBehave.
> ATTENTION: the given patch contains also a fix for the class OdfUtils in the
> module jbehave-odf. The class OdfTextExtractor is used to convert ODT
> correctly to text.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
