September 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

WebODF 0.5.4 & ViewerJS 0.5.4 released, undoing regressions slipped into 0.5.3
by Friedrich W. H. Kossebau 17 Sep '14

17 Sep '14

Dear WebODF-interested and enthusiasts, Just 24 hours passed since the release of WebODF 0.5.3 and ViewerJS 0.5.3, and there has to be another, fixing regressions once we learned about them. So go to the Download pages (http://webodf.org/download/ or http://viewerjs.org/getit/) and update your deployment of webodf.js, the Wodo.TextEditor or ViewerJS. Changes between 0.5.3 and 0.5.4 WebODF Fixes * Only highlight ODF fields in edit mode (https://github.com/kogmbh/WebODF/issues/816) Wodo.TextEditor (See also section about WebODF) Fixes * Fix broken loading of other files via "Open file..." button in localfileeditor example ViewerJS (See section about WebODF) Sorry for the regressions. No, we do not do this to grep more of your attention. That we only try with new features. :) Cheers Friedrich -- Friedrich W. H. Kossebau // KO GmbH http://kogmbh.com/legal/

1 0

ViewerJS 0.5.3 released, bringing support for template and flat-xml ODF file variants
by Friedrich W. H. Kossebau 16 Sep '14

16 Sep '14

Dear WebODF-interested and enthusiasts, following the release of WebODF 0.5.3, also ViewerJS, the WebODF-based Open Source document viewer for webpages, is available in an updated version. The new version 0.5.3 brings support for displaying the template and flat-xml variants of the OpenDocument formats ODT, ODP, ODS: * OTT (application/vnd.oasis.opendocument.text-template) * OTP (application/vnd.oasis.opendocument.presentation-template) * OTS (application/vnd.oasis.opendocument.spreadsheet-template) and * FODT (application/vnd.oasis.opendocument.text-flat-xml) * FODP (application/vnd.oasis.opendocument.presentation-flat-xml) * FODS (application/vnd.oasis.opendocument.spreadsheet-flat-xml) In presentation mode the screen can now be blanked (or whited), by pressing the "b" or "." key (or the "w" or "," key) And of course this latest ViewerJS brings all rendering improvements of WebODF 0.5.3 for files in the OpenDocument 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. Please visit http://viewerjs.org/ to learn more about ViewerJS, play with the examples at http://viewerjs.org/examples/, and give it a deployment in your webpages. And then spread your knowledge among your peers :) Cheers Friedrich PS: WordPress users will be interested in the ViewerJS WordPress plugin, available on http://viewerjs.org as well. -- Friedrich W. H. Kossebau // KO GmbH http://kogmbh.com/legal/

1 0

WebODF 0.5.3 released, bringing another round of improvements and fixes
by Friedrich W. H. Kossebau 16 Sep '14

16 Sep '14

Dear WebODF-interested and enthusiasts, we WebODF developers are happy to declare that: WebODF version 0.5.3 is tagged and out! The latest version of WebODF brings improvements in the rendering of text styled as subscript or superscript, fixes positioning of the IME composition menu & avatar when entering characters, 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.2 and 0.5.3 WebODF Improvements * Add support for double line-through in Firefox (Chrome/Safari + IE don't support this feature) (https://github.com/kogmbh/WebODF/pull/758) * Add support for subscript & superscript (https://github.com/kogmbh/WebODF/pull/755) * In odf.OdfContainer allow creation of document template types as well as querying and setting the template state of the document Fixes * Fixed occasional crash when splitting a paragraph (https://github.com/kogmbh/WebODF/issues/723) * Keep IME composition menu & avatar in the correct position when entering characters * Allow screen-readers to read the document content correctly in OSX 10.8+ versions of Safari * Scroll newly created annotations completely into view (https://github.com/kogmbh/WebODF/issues/486) * Improve line ending detection when word-wrapping occurs (https://github.com/kogmbh/WebODF/pull/774) Wodo.TextEditor (See section about WebODF) Cheers Friedrich -- Friedrich W. H. Kossebau // KO GmbH http://kogmbh.com/legal/

1 0

RFC: Move to a standard JS test framework (e.g., jasmine)
by Philip Peitsch 15 Sep '14

15 Sep '14

Hi everyone, In an effort to ease some of the cross-browser development aspects, I’m spending some time getting the karma test runner work that Jos started a while ago functional again. This migration is somewhat trickier than it should be, mainly because WebODF has a completely custom test framework (core.UnitTester). This means that: * all karma integration must be written from scratch * it is difficult to run individual tests from karma (very handy when developing from WebStorm) * text reporting from karma is *very* messy * missing shiny features from other test frameworks :'( I was wondering if anyone would have complaints about ripping out the custom framework and replacing with an existing, widely used one (e.g., Jasmine, http://jasmine.github.io/2.0/introduction.html)? The only reason I suggest Jasmine is that I'm familiar with it's features from other projects I work on. Key benefits of switching to Jasmine (probably apply to other frameworks too!): * already has integration for karma via the karma-jasmine plugin * individual tests can be ignored or run directly from any IDE with karma support * has a host of existing addins (e.g., better HTML reporters) which means we can easily improve the usability of the test results from the browser as well as in the qtjsruntimetests (which currently spit out raw html in the console :-/) * good documentation * support for async tests * easier fixture creation >From what I can tell, everything implemented in the existing custom test framework is supported (or supportable without much work) in jasmine without too much work. I'm happy to do the work... just wanted to get wider approval before spending time on such a patch :-). So… any objections? Cheers, Philip

3 5

Annotation reply facility.
by govind mane 12 Sep '14

12 Sep '14

Hi all, If there is a facility to reply to the annotation then it will be the best editor for me. If you have any suggestion regarding this please reply. Thanks, Govind

2 1

help wodotexteditor into java web application + tomcat
by Carlos Andrés Ovalle 04 Sep '14

04 Sep '14

Hi everybody Im trying to use the modulo wodo texteditor in java web application but dont work, Any can help me? Look the next image [image: Imágenes integradas 1] [image: Imágenes integradas 2] Thnks Carlos Andres Ovalle. *Director de Proyectos - CEO* Tel: 805 2954 Móvil: 301 5118782 Skype: s2ctech Calle 57 # 7 - 11 Ofc 405. Bogotá, Colombia. www.s2ctechnology.com Desarrollamos tus Ideas! /s2ctech @s2ctech s2c-technology-sas ü Por favor considere el medio ambiente antes de imprimir este e-mail ü Please consider the environment before printing this e-mail *La información contenida en este mensaje es confidencial y sólo puede ser utilizada por el individuo o la compañía a la cual está dirigido. Si no es el receptor autorizado, cualquier retención, reproducción, difusión, distribución o copia de este correo electrónico es prohibida y será sancionada por la ley. Excepto en casos de culpa grave o dolo, no aceptamos ninguna responsabilidad por pérdidas o daño causados por virus informáticos en correos electrónicos o en programas de computador (software). El que ilícitamente sustraiga, oculte, extravíe, destruya, intercepte, controle o impida esta comunicación, antes de que llegue a su destinatario, estará sujeto a las sanciones penales correspondientes. Igualmente, incurrirá en sanciones penales el que, en provecho propio o ajeno o con perjuicio de otro, divulgue o emplee la información contenida en esta comunicación. En particular, los servidores públicos que reciban este mensaje están obligados a asegurar y mantener la confidencialidad de la información en él contenida y, en general, a cumplir con los deberes de custodia, cuidado, manejo y demás previstos en el régimen disciplinario. Si por error recibe este mensaje, le solicitamos enviarlo de vuelta a S2C Technology a la dirección de correo electrónico que se lo envió y borrarlo de sus archivos electrónicos o destruirlo.*

2 1