July 2014 - WebODF - lists.nlnet.nl

Server-side save and load example
by Wally 14 Apr '15

14 Apr '15

I have been working with WebODF and the Wodo editor for a few days and thought I would give back some to the community for making such a great set of tools and libraries. The application I've been developing involves saving and loading ODF files on a server and editing them in the browser and seeing as there are no good examples of how to do this, I thought maybe this could work as an example for others. Note: This application is based off of the wodo editor project's localeditor.html and related files. I use jQuery to simplify stuff, but it probably isn't necessary. First we need to be able to load files from the server. This is easy enough as that is already built into the Wodo editor via editor.openDocumentFromURL(). I get a list of files on the server and add onClick events to the links. function refreshPanelContents() { // Request the HTML containing the list of files available. $.ajax({ url: 'filelist.php', dataType: 'html', success: function(data) { // Update the panel with the new list of files. $('.panel').html(data); // Add onClick events to each file link. $('.fileOpen').click( function(){ var filename = $(this).text(); // We need this random number to stop file caching. var rand = Math.random().toString(36).substr(2); // All of the files are in the 'storage' folder for now... // this should probably call a server-side script to get the file based on some encrypted data. var filepath = 'storage/' + filename + '?rand=' + rand; // loadedFilename is used during saving to know what file to save to. loadedFilename = filename; // Clear the cache so we don't load old docs. runtime.clearCache(); // Close the current document. Probably should check if the document is unsaved first and ask the user what to do. editor.closeDocument(function() { // Load the selected document. editor.openDocumentFromUrl(filepath, null); }); }); } }); } We now need to be able to save to the server. Here I am using the save button in the Wodo toolbar to do a server-side save instead of it downloading it on the client. function save() { function saveByteArray(err, data) { if (err) { alert(err); return; } var filename = loadedFilename || "doc.odt"; var mimetype = "application/vnd.oasis.opendocument.text"; var blob = new Blob([data.buffer], {type: mimetype}); // Ends up calling new FileSaver(blob, filename); saveAs(blob, filename); } editor.getDocumentAsByteArray(saveByteArray); refreshPanelContents(); } Most of the example code from FileSaver.js is unchanged (it might go unused, not sure). Here is what the FileSaver constructor turned into: var FileSaver = function(blob, filename) { // FormData lets us send a blob along with other metadata for saving. var fd = new FormData(); fd.append('name', filename); fd.append('data', blob); // POST data to our save script. $.ajax({ type: 'POST', url: 'save.php', data: fd, processData: false, contentType: false, success: function(data) { // Success! alert('Saved! ' + data); }, error: function(data) { // Failure. alert('We got a big error here.\n' + JSON.stringify(data)); } }); }; The save.php script will be application specific, but just for a completeness, here is my partial implementation (minus error checking and safety stuff): <?php $fileName = $_POST['name']; // PHP now stores Blobs in this $_FILES variable. $fileBlob = $_FILES['data']; // The Blob has some data we need. $tmpPath = $fileBlob['tmp_name']; $fileSize = $fileBlob['size']; // Read the temp file data. $fp = fopen($tmpPath, 'r'); $content = fread($fp, $fileSize); fclose($fp); // Write data. $dir = __DIR__ . DIRECTORY_SEPARATOR . 'storage'; $filePath = $dir . DIRECTORY_SEPARATOR . $fileName; file_put_contents($filePath, $content); ?> Hopefully that helps someone out there get started on a server-side application to save and load documents. Enjoy! Disclaimer: This code is free to use and provided as is without any guarantees or warranty. Use at your own risk, etc.

2 1

Re: [WebODF] WebODF Digest, Vol 19, Issue 8
by simon 18 Aug '14

18 Aug '14

I send you the URL via your email address. Apparently if someone has MSWord installed, the right document will open in MSWord (likely they have MSWord as the default app to open documents set in their browser) 2014-07-30 12:00 GMT+02:00 <webodf-request(a)nlnet.nl>: > Send WebODF mailing list submissions to > webodf(a)nlnet.nl > > To subscribe or unsubscribe via the World Wide Web, visit > https://open.nlnet.nl/mailman/listinfo/webodf > or, via email, send a message with subject or body 'help' to > webodf-request(a)nlnet.nl > > You can reach the person managing the list at > webodf-owner(a)nlnet.nl > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of WebODF digest..." > > > Today's Topics: > > 1. MSWord opens diplayed document (simon) > 2. Re: MSWord opens diplayed document (Jos van den Oever) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 29 Jul 2014 22:24:20 +0200 > From: simon <sknuijver(a)gmail.com> > To: webodf(a)nlnet.nl > Subject: [WebODF] MSWord opens diplayed document > Message-ID: > < > CAJvsvFMDpSpuAqNo+rsFpXnrt+cnWPLDtT6h50KGKfqPxsq3Vw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > If my browser is set to let MS wOrd open documents, it will do so and > prevent webodf from displaying the file in the website (iframe). >

2 2

MSWord opens diplayed document
by simon 29 Jul '14

29 Jul '14

If my browser is set to let MS wOrd open documents, it will do so and prevent webodf from displaying the file in the website (iframe).

2 1

WebODF 0.5.2 released, bringing more fixes
by Friedrich W. H. Kossebau 26 Jul '14

26 Jul '14

Dear WebODF-interested and enthusiasts, we WebODF developers are happy to declare that: WebODF version 0.5.2 is tagged and out! Not even two weeks passed after the first update to WebODF 0.5 and there is the second. It brings improvements in the rendering of the ODP slides and makes nagivation in ODT documents via home/end keys or up/down cursor keys more reliable in all browsers. So go to the Download page (http://webodf.org/download/) and update your deployment of webodf.js or the Wodo.TextEditor. Changes between 0.5.1 and 0.5.2 WebODF Fixes * For ODP files sometimes template elements from the master pages were rendered inside the actual slides. * More elements from master pages are now correctly positioned when displayed inside slides. * In slides elements of class "header", "footer", "page-number" and "date-time" from master pages are now hidden when configured so. * Navigation via home/end keys, or up/down cursor keys is more reliable on all browsers. (https://github.com/kogmbh/WebODF/pull/555, https://github.com/kogmbh/WebODF/pull/405, https://github.com/kogmbh/WebODF/pull/224, https://github.com/kogmbh/WebODF/pull/185, https://github.com/kogmbh/WebODF/pull/124, https://github.com/kogmbh/WebODF/pull/98) Wodo.TextEditor (See section about WebODF) Cheers Friedrich -- Friedrich W. H. Kossebau // KO GmbH http://kogmbh.com/legal/

1 0

WebODF 0.5 out and gains text editor: edit OpenDocument format files in webpages and webapps
by Friedrich W. H. Kossebau 23 Jul '14

23 Jul '14

Dear WebODF-interested and enthusiasts, we WebODF developers are happy to declare that: WebODF version 0.5.0 is tagged and out! Please find below the press release, then read it, follow it, spread it! Cheers Friedrich --- 8< --- FOR IMMEDIATE RELEASE WebODF 0.5 GAINS TEXT EDITOR: EDIT OPENDOCUMENT FORMAT FILES IN WEBPAGES AND WEBAPPS June 30, 2014 Magdeburg, Germany - KO GmbH (KO) and the developers of WebODF[1], the JavaScript library for OpenDocument Format (ODF) support in webpages and HTML5 apps, today released WebODF 0.5. So far it has been a library for the pure display. After a long period of hard work this new version features also editing of OpenDocument Text files. It also contains lots of display improvements. WebODF still uses only HTML, CSS and JavaScript without any need for a special server software. WebODF 0.5 adds an API for implementing editors for OpenDocument Format. This allows for custom extensions and adaptions to different backends and UIs. In this version there is built-in support for enabling annotations, editing of hyperlinks and predefined paragraph styles, as well as direct formatting of text and paragraphs, with more to come. WebODF 0.5 is accompanied by the simple to use JavaScript component Wodo.TextEditor, which is built on top of WebODF 0.5. It makes it easy to add an ODT editor element e.g. to your webpage in a few lines of JavaScript. [2] With the 0.5 release out, future WebODF releases will be done approximately once every month to get improvements quickly into your hands. Support for realtime-collaborative editing has already been part of special WebODF variants for the document editor ownCloud Documents, added in version 6 of the cloudstorage solution ownCloud. It is currently worked on more and will be officially part of WebODF in the upcoming weeks. Download the webodf.js library, the Wodo.TextEditor component and more from webodf.org, and enhance your webpages and HTML5 apps with viewing and editing support for ODF files. About WebODF WebODF is a JavaScript library which enables viewing and editing support for OpenDocument Format (ODF) on websites and in mobile or desktop applications, using only web standards. It was started in 2010 by Jos van den Oever at KO GmbH and is now developed by a growing team including external collaborators. WebODF is used by ViewerJS, ownCloud Documents, Zarafa, and more. All code is available under the Affero General Public License (AGPLv3). KO GmbH offers proprietary licenses upon request. For more information, please visit http://webodf.org/. About KO KO provides services and products for document workflows. KO has created office productivity applications for several generations of Nokia smartphones such as the N900 and N9. It has also created the WebODF web-based document technology framework. KO has sponsored employees to take part in the OASIS working group for the Open Document Format (as KDE representatives). Contact Contact the developers of WebODF either in the IRC channel #webodf on freenode or by the mailinglist https://lists.opendocsociety.org/mailman/listinfo/webodf . For commercial support, please contact: Tobias Hintze KO GmbH, Schilfbreite 3, D-39120 Magdeburg, Germany Email: webodf-support(a)kogmbh.com Telephone: +49 391 251915 50 Links [1] http://webodf.org Homepage of the WebODF project [2] https://github.com/kogmbh/WebODF/blob/master/programs/editor/HOWTO-wodotext… How-to for using the Wodo.TextEditor Images See http://webodf.org/news/2014-06-30.html ### --- 8< --- -- Friedrich W. H. Kossebau // KO GmbH http://kogmbh.com/legal/

3 2

Re: [WebODF] [webodf-support] viewerjs
by simon 23 Jul '14

23 Jul '14

Hello, want to ask how I can make adjustments to the layout so that it displays >> two documents side by side. >> > > The rendering in ViewerJS is done by WebODF for ODF and PDF.js for PDF. If > you would like to help with the ODF rendering you can join > https://open.nlnet.nl/mailman/listinfo/webodf > If you want to display two documents side by side, you can add two > ViewerJS instances to your page. > > Best regards, > Jos van den Oever > > So, my question to the list (new here) is where or how do the instances get instantiated? Second, ViewerJS causes my Eclipse IDE to run out of heap space. It is difficult to debug because I'm new to the library (and to JS memory leaks for that matter), but I could imagine a JS function eating up memory with a faulty recursion.. please advice thanks Simon

2 2

WebODF 0.5.1 released, bringing fixes
by Jos van den Oever 21 Jul '14

21 Jul '14

This message comes to you from Friedrich Kossebau: Dear WebODF-interested and enthusiasts, we WebODF developers are happy to declare that: WebODF version 0.5.1 is tagged and out! Less than 3 weeks after the release of WebODF 0.5.0 there is the first update. It brings improvements in the rendering of the numbering of multi-level lists, solves issues during the startup of the Wodo.TextEditor on Safari and more. So go to the Download page (http://webodf.org/download/) and update your deployment of webodf.js or the Wodo.TextEditor. Changes between 0.5.0 and 0.5.1 WebODF Improvements * numbering of multi-level lists is now well supported in rendering, including display of only a subset of the list numbers and continued numbering from previous lists (both `text:continue-numbering` and `text:continue-list`) (https://github.com/kogmbh/WebODF/pull/565) Fixes * Loading of documents without optional <style:list-level-properties> or <style:list-level-label-alignment> no longer fails and stalls * Loading of ODT files with annotations in Internet Explorer 10 (and possibly other versions) no longer fails and stalls Wodo.TextEditor (See also section about WebODF) Fixes * Start-up of editor no longer hangs in some browsers: Two different bugs were fixed which so far broke the start-up with Safari and other browsers using older WebKit versions as well as the default browser on Android 4.0.3 (https://github.com/kogmbh/WebODF/issues/693) * All toolbar elements are now disabled when no document is loaded. (https://github.com/kogmbh/WebODF/issues/709) Cheers Friedrich -- Friedrich W. H. Kossebau // KO GmbH http://kogmbh.com/legal/

1 0

ViewerJS 0.5.1 released, bringing rendering improvements
by Friedrich W. H. Kossebau 21 Jul '14

21 Jul '14

Dear WebODF-interested and enthusiasts, following the release of WebODF 0.5.1, now also ViewerJS, the WebODF based Open Source document viewer for webpages, is available in an updated version. It brings all the rendering improvements of WebODF 0.5.1 for files in the OpenDocument Format as well as a newer version of PDF.js for files in PDF format. ViewerJS continues to be the candidate for embedding ODF or PDF files directly in webpages, without any external server dependencies, just done with HTML, CSS and Javascript. You might remember that deployment of ViewerJS is quickly done: 1. download http://viewerjs.org/releases/ViewerJS-latest.zip 2. unzip the file 3, move the folder "ViewerJS" to the toplevel dir of the folder structure served by your webserver (could also be another dir) 4. for a given ODF or PDF file add this line to an html file: <a href="/ViewerJS/#../relative/path/from/ViewerJS/to/some/filename"> (filename needs to have ".pdf", ".odt", ".odp" or ".ods" extension) Now reload that html page in your browser and find the document in the file displayed inside the html page, with toolbars to navigate between pages, control the zoom level or go to presentation mode or fullscreen. Please visit http://viewerjs.org/ to learn more about ViewerJS, and give it a deployment in your webpages. And then spread your knowledge among your peers :) Cheers Friedrich -- Friedrich W. H. Kossebau // KO GmbH http://kogmbh.com/legal/

1 0

WebODF 0.5.1 released, bringing fixes
by Friedrich W. H. Kossebau 19 Jul '14

19 Jul '14

Dear WebODF-interested and enthusiasts, we WebODF developers are happy to declare that: WebODF version 0.5.1 is tagged and out! Less than 3 weeks after the release of WebODF 0.5.0 there is the first update. It brings improvements in the rendering of the numbering of multi-level lists, solves issues during the startup of the Wodo.TextEditor on Safari and more. So go to the Download page (http://webodf.org/download/) and update your deployment of webodf.js or the Wodo.TextEditor. Changes between 0.5.0 and 0.5.1 WebODF Improvements * numbering of multi-level lists is now well supported in rendering, including display of only a subset of the list numbers and continued numbering from previous lists (both `text:continue-numbering` and `text:continue-list`) (https://github.com/kogmbh/WebODF/pull/565) Fixes * Loading of documents without optional <style:list-level-properties> or <style:list-level-label-alignment> no longer fails and stalls * Loading of ODT files with annotations in Internet Explorer 10 (and possibly other versions) no longer fails and stalls Wodo.TextEditor (See also section about WebODF) Fixes * Start-up of editor no longer hangs in some browsers: Two different bugs were fixed which so far broke the start-up with Safari and other browsers using older WebKit versions as well as the default browser on Android 4.0.3 (https://github.com/kogmbh/WebODF/issues/693) * All toolbar elements are now disabled when no document is loaded. (https://github.com/kogmbh/WebODF/issues/709) Cheers Friedrich -- Friedrich W. H. Kossebau // KO GmbH http://kogmbh.com/legal/

1 0

Sample ODT
by Rubén Sánchez Paredes 09 Jul '14

09 Jul '14

Hi, I'm rubinhozzz from the IRC. I have attached the odt file. Some colleagues told me the plugin is based on a old ODT version, as they get the same errors, well no errors but inconsistences. - No bullets or numerations - No red arrows - Images are a bit moved from their real location. Thanks in advance -- Ruben Sanchez Protonic Holland. tel.: +31 (0) 229 212928 fax.: +31 (0) 229 210930 Factorij 36 / 1689 AL Zwaag

1 0