ODF 1.2 Word CloudsIve been playing around today with a preview build of ODFDOM 0.9. One of the capabilities were adding is a simple text extraction API. The idea is to have a very simple API, a single function call in fact, that will allow you to extract the plain text from a document. So strip all formatting, all [...] 29/07/2010, source: Rob Weir: An Antic Disposition New: OOo-DEV 3.3.x Developer Snapshot (build OOO330m2) availableDeveloper Snapshot OOo-Dev OOO330m2 is available for download. OOO330 is the development codeline for upcoming OOo 3.3.x releases. If you find issues within this build please file them to
OpenOffice.org's bug tracking system IssueTracker. Download: Release Notes: MD5 checksums: 28/07/2010, source: GullFOSS The value of restricting choiceThe language game Microsofts talking points go something like this (summarized in my words): If you adopt ODF instead of OOXML then you restrict choice. Why would you want to do that? Youre in favor of openness and competition, right? So naturally, you should favor choice. You can see a hundreds of variations on this theme, in Microsoft [...] 27/07/2010, source: Rob Weir: An Antic Disposition Weekly Links #14DataNucleus Access Platform ODF Documents DataNucleus supports persisting/retrieving objects to/from Open Document Format (ODF) documents (using the datanucleus-odf plugin). Such documents can then be used in applications like OpenOffice and KOffice. It makes use of the ODF Toolkit project. tags: ODF Producing ODF spreadsheets So, the remaining question is: How to produce the ODF XML? What I did was, [...] 25/07/2010, source: Rob Weir: An Antic Disposition New: OOo-DEV 3.x Developer Snapshot (build DEV300m85) availableDeveloper Snapshot OOo-Dev DEV300m85 is available for download. DEV300 is the development codeline for upcoming OOo 3.x releases. If you find issues within this build please file them to
OpenOffice.org's bug tracking system IssueTracker. Download: Release Notes: MD5 checksums: 22/07/2010, source: GullFOSS New: OOo-DEV 3.3.x Developer Snapshot (build OOO330m1) availableDeveloper Snapshot OOo-Dev OOO330m1 is available for download. OOO330 is the development codeline for upcoming OOo 3.3.x releases. If you find issues within this build please file them to
OpenOffice.org's bug tracking system IssueTracker. Download: Release Notes: MD5 checksums: 19/07/2010, source: GullFOSS ODF 1.2 Begins Final 60-day Public ReviewA major milestone was reached for the OASIS Open Document Format (ODF) TC last week. The latest Committee Draft of ODF 1.2 (CD 05) was sent out for a 60-day public review. As you may recall, ODF 1.2 is a single standard in three parts: Part 1 specifies the core schema, and was send out for [...] 13/07/2010, source: Rob Weir: An Antic Disposition Testing/Translation the Features and EnhancementsLast week Marcus Lange announced the branch of the new code-line OOO330 for the next release of OpenOffice.org. It is based on developer snapshot DEV300m84. For such milestone I finalized the list of features/enhancements. I announced this list some weeks ago on the relevant OOo-mailing lists for QA and L10N and since then only some more entries came in. This list isn't a 'what's new'-guide. It more technical orientated and is for L10N testing and for checking the new features by the QA and the L10N teams. If you are interested what is in the next release, please take a look.
Since last week the Pootle servers for translation are updated with this milestone and Joost Andrae created the last TCM-testcases for the new features to help the translators to find the new strings in the user interface. A showstopper Meta-issue for Beta and for Final are opened. So everything is prepared to get a Beta of OpenOffice.org 3.3 soon. If you want to help the QA team or the L10N teams, do not hesitate to download the current build (DEV300m84). 12/07/2010, source: GullFOSS Public Review of OpenDocument v1.211/07/2010, source: Open Document - Online Community for the OpenDocument OASIS Standard New branch for OOo 3.3: OOO330With entering the timeline for the new
feature release OOo 3.3, a new master workspace (MWS) was created: OOO330. In HG (Mercurial) the OOO330 branch can be found here: hg.services.openoffice.org/hg/OOO330. It was branched off from DEV300 m84 and will help to stabilize the new milestones towards 3.3. The first milestone is scheduled soon. Explained in a picture:
05/07/2010, source: GullFOSS Better multimedia support for OpenOffice.org on Unix systemsPlaying back audio and video content on Unix system was and is still a matter of choices.
01/07/2010, source: GullFOSS New: OOo-DEV 3.x Developer Snapshot (build DEV300m84) availableDeveloper Snapshot OOo-Dev DEV300m84 is available for download. DEV300 is the development codeline for upcoming OOo 3.x releases. If you find issues within this build please file them to OpenOffice.org's bug tracking system IssueTracker. Download: Release Notes: MD5 checksums: 01/07/2010, source: GullFOSS Weekly Links #12TeX4ht: LaTeX and TeX for Hypertext Appears to offer TeX to ODF conversion support. Would be interesting to see how well this works. tags: ODF ODF visualization using WebKit kdedevelopers.org Today is day 1 of of the OdfKit Hack Week. We wrote a list of things we want to achieve this week. In order to avoid embarrassment, [...] 27/06/2010, source: Rob Weir: An Antic Disposition Linux Tag in Berlin
I was in Berlin for the LinuxTag trade fair on Friday, June 11. It was a great day to be there because it was the day of the UX meetup and the OpenOffice.org booth party. The day began with the very lively and informative gathering of 9 people (plus one more who showed up after it was over but stayed on for the continued discussion in the hallway: see pics on wiki) for the UX workshop announced by Christoph Noack on Usability in FOSS. That was fantastic because there were people from several different types of companies, including Novell, pidoco and Apliki, as well as all sorts of backgrounds: ranging from psychologists and HMI experts to software developers and even a lawyer. Then I proceeded to work at the OOo booth for the rest of the day, including handing out soft preztels at our very successful booth party. I didn't have to point out the beer: All those crates were hard to overlook! Thanks go out to Jacqueline and Thomas and Joerg and Co. who organized it all. On the train on the way back to Hamburg I may have been able to motivate a few more people to download and try the OpenOffice.org office suite. I was still in my trade fair t-shirt, so I just kept talking! People who have met me will understand that this is unusual for me. ;-) ha ha! No matter where I go, I will always put in a good word for this wonderful software and open source community. All the best, Liz 20/06/2010, source: GullFOSS New: OOo-DEV 3.x Developer Snapshot (build DEV300m83) availableDeveloper Snapshot OOo-Dev DEV300m83 is available for download. DEV300 is the development codeline for upcoming OOo 3.x releases. If you find issues within this build please file them to
OpenOffice.org's bug tracking system IssueTracker. Download: Release Notes: MD5 checksums: 18/06/2010, source: GullFOSS New: OOo-DEV 3.x Developer Snapshot (build DEV300m82) availableDeveloper Snapshot OOo-Dev DEV300m82 is available for download. DEV300 is the development codeline for upcoming OOo 3.x releases. If you find issues within this build please file them to OpenOffice.org's bug tracking system IssueTracker. Download: Release Notes: MD5 checksums: 14/06/2010, source: GullFOSS Weekly Links #11Jeff Duntemanns ContraPositive Diary EPub and Word Processors tags: EPub Eugenes Opinions: ODF Templates For OpenOffice.org [Lulu.com, Turabian, misc] tags: ODF EU Commissioner Warns IT Buyers Against Vendor Lock-in I think Sayer hints at the significance of the speech here. It is not merely a reiteration of the importance of open standards against vendor lock-in. We all [...] 13/06/2010, source: Rob Weir: An Antic Disposition New: OOo-DEV 3.x Developer Snapshot (build DEV300m81) is availableDeveloper Snapshot OOo-Dev DEV300m81 is available for download. DEV300 is the development codeline for upcoming OOo 3.x releases. If you find issues within this build please file them to
OpenOffice.org's bug tracking system IssueTracker. Download: Release Notes: MD5 checksums: 09/06/2010, source: GullFOSS What's Cooking in the Renaissance Kitchen?
Yum, yum. Are we talking about better recipes? OK, the title of this blog was a bit misleading. We are actually talking about Better Defaults, which are the focus of the most recent Renaissance status presentation, which you can munch on if you find time for a light snack. The focus is still "Thinning Out Impress" so we are getting OpenOffice.org Impress fit by focusing on healthy changes in the Impress default settings diet. ;-) Thanks again to everyone who added dietary advice. Have a look at the presentation before you go on your daily jog. Or just eat a celery stick while you watch the videos: I heard that you burn more calories chewing celery sticks than your body intakes from the celery. I hope it is true, because I'm not much of a jogger, but I love celery. :-)
Best wishes to everyone for a healthy life! Liz 07/06/2010, source: GullFOSS Weekly Links #10xkcd: Infrastructures tags: ODF ODFDOM 0.8.5 The new Release of the OpenDocument Java Library tags: ODF The Art of Standards Wars [PDF] tags: standards EmacsWiki: Open Document View and edit OpenDocument files inside Emacs tags: ODF ODT interoperability, jerez and tapas at the ODF Plugfest in Granada, Spain We’ve went through testing scenarios from all previous workshops as well as from the current one [...] 06/06/2010, source: Rob Weir: An Antic Disposition 154 million and counting...When looking at today's download statistic I counted 154,582,489 downloads since version 3.0 (29,283,218 since version 3.2.0) based on data provided by the load balancer MirrorBrain which is used on OpenOffice.org's download page. This is a huge number but this number doesn't count all distribution specific variants. The number could even be higher when taking the download numbers from other build providers into account. Is there anyone who'd like to provide additional numbers ?
btw. OpenOffice.org 3.2.1 has been released today 04/06/2010, source: GullFOSS OpenOffice.org 3.2.1 was released todayOpenOffice.org 3.2.1 (build OOO320m18) was released today. This is a bugfix release, so no new features implemented and the Feature Documentation from 3.2.0 is still valid. As this is the first release from OpenOffice.org's new sponsor Oracle, we have included a refreshed brand as it was necessary due to the acquisition of Sun Microsystems by Oracle in Januar 2010. Among this there are a few other things implemented. Read all about this on Brand Refresh. Much more details about this version can be found in the technical Release Notes. Of course there is also an Announcement. 04/06/2010, source: GullFOSS OpenOffice.org Conference 2010 - Call for Papers till June 16
This is not only the annual OpenOffice.org world conference, but also the 10th anniversary of the community and open source product. From August 31st - September 3rd, 2010, Budapest is the place to be if you are interested or involved in OOo. Submit your paper at http://www.ooocon.org Budapest: The OpenOffice.org community's choice for 2010! For information on how to register for the conference, see the website.
04/06/2010, source: GullFOSS ODFDOM 0.8.5 - The new Release of the OpenDocument Java LibraryThe new version of ODFDOM - our Apache 2 licensed ODF library in Java has been released! Aside of a more than a dozen patches there were two outstanding new features for the 0.8.5 release:
Still this release was not a feature release, but focused on
performance improvements and bug fixes, like the support of none ODF XML
within documents. Another goal is a diplomatic one. The exchange of ideas with other ODF library implementors. Maybe we can agree on a common ODF Package and DOM API, which are the base APIs of the layered architecture:
The ODF Package Layer:
If there are any further question on ODFDOM, we would be happy to
answer them on one of our ODFDOM mailing lists. See you there! 04/06/2010, source: GullFOSS New: OOo-DEV 3.x Developer Snapshot (build DEV300m80) availableDeveloper Snapshot OOo-Dev DEV300m80 is available for download. DEV300 is the development codeline for upcoming OOo 3.x releases. If you find issues within this build please file them to OpenOffice.org's bug tracking system IssueTracker. Download: Release Notes: MD5 checksums: 01/06/2010, source: GullFOSS New: OOo-DEV 3.x Developer Snapshot (build DEV300m79) availableDeveloper Snapshot OOo-Dev DEV300m79 is available for download. DEV300 is the development codeline for upcoming OOo 3.x releases. If you find issues within this build please file them to OpenOffice.org's bug tracking system IssueTracker. Download: Release Notes: MD5 checksums: 31/05/2010, source: GullFOSS New: OpenOffice.org 3.2.1 Release Candidate 2 (build OOO320m18) availableOpenOffice.org 3.2.1 Release Candidate 2 is now available on the download website. Please note that currently a few Windows builds are not yet ready, these files need a bit more time to be available. If you find severe issues within this build please file them to OpenOffice.org's bug tracking system IssueTracker: Download website: Release notes: MD5 checksums:
EDIT: 28/05/2010, source: GullFOSS Renaissance Video on YouTubeFor those of you who haven't seen it yet, the most recent status presentation is online here. The very brief slide show includes a link to the really juicy stuff: The latest Renaissance Impress video on YouTube. In the video, you will get a sneak-peek of the improved slide handling and slide layouts as well as how quickly you can now insert tables, charts, images, and video. If you want to skip the presentation and just go to the video, then feel free to do so. Either way, comments and feedback are welcome. The next Renaissance status update will be out by mid-June, so even if the weather doesn't get much better, you still have something to look forward to! :-) Best regards, Liz
25/05/2010, source: GullFOSS New: OOo-DEV 3.x Developer Snapshot (build DEV300m78) availableDeveloper Snapshot OOo-Dev DEV300m78 is available for download. DEV300 is the development codeline for upcoming OOo 3.x releases. If you find issues within this build please file them to OpenOffice.org's bug tracking system IssueTracker. Download: Release Notes: MD5 checksums: 21/05/2010, source: GullFOSS Weekly Links #9The ODF Podcast 001: Svante Schubert on ODF, RDF and ODFDOM Open Document Last month OASIS ODF Adoption TC member Rob Weir sat down with Svante Schubert at the Plugfest in Granada to discuss a range of topics, including ODF 1.2s RDF-based metadata and Svantes work on ODFDOM. You can listen to this interview [...] 16/05/2010, source: Rob Weir: An Antic Disposition The ODF Podcast 001: Svante Schubert on ODF, RDF and ODFDOM12/05/2010, source: Open Document - Online Community for the OpenDocument OASIS Standard New: OpenOffice.org 3.2.1 Release Candidate 1 (build OOO320m17) availableOpenOffice.org 3.2.1 Release Candidate 1 is now available on the download website. If you find severe issues within this build please file them to OpenOffice.org's bug tracking system IssueTracker: Download website: Release notes: MD5 checksums: 10/05/2010, source: GullFOSS Weekly Links #8How To Read Open Document Format ODF documents on Symbian I learned about a quite decent Symbian reader for ODF files, called Office Reader. I tested it using Funambol email push and sync client on my Nokia E71 and the results are quite good. You can see from the screenshots below (taken from a pretty complex [...] 09/05/2010, source: Rob Weir: An Antic Disposition ODF Turns Five05/05/2010, source: Open Document - Online Community for the OpenDocument OASIS Standard Thanks for Suggesting Better Default Settings
Many thanks go out to everyone who added one of the 90+ suggestions for the Better Defaults collection. Impress is currently in focus for Project Renaissance, so any suggestions relevant to Impress (presentation application) have now been taken to be evaluated by the iTeam. Those entries are therefore now in italics. If you have default settings that you wish were standard, then you can still add them to the list on the wiki page. Even if your suggestion conflicts with a suggestion made by somebody else, add it to the list. That is important for the iTeam to know. The mission of Project Renaissance is... “Create a User Interface so that OpenOffice.org becomes the users' choice not only out of need, but also out of desire” ...so, the UX community wants to know your desires, in this case, for default settings in the various OOo applications. I'm looking forward to seeing even more action in the Renaissance subproject "Better Defaults". For example, Chris has been fleshing out his Grid Handling wiki page and would welcome any comments and feedback on the ideas there. As the iTeam looks at each suggestion, many wiki pages may arise to get into the nitty gritty details. So be on the look out for more calls to action. Thanks again to those of you who have shared your thoughts so far. Liz 03/05/2010, source: GullFOSS QA weekend 2010 in Essen, GermanyI'm back from this year's QA weekend in Essen, Germany. There were several discussions about various QA related topics and deep discussions related to the QA team of the German native language community. All in all we had a lot of fun and were productive. Some information about the planning details of this event can be found here (in German only...sorry) 03/05/2010, source: GullFOSS ODF at 5 YearsFive years ago today, on May 1st, 2005 OASIS approved Open Document Format 1.0 as an OASIS Standard. Id like to take a few brief minutes to reflect on this milestone, but only a few. Were busy at work in OASIS making final edits to ODF 1.2. Were in our final weeks of that revision [...] 01/05/2010, source: Rob Weir: An Antic Disposition The Naming of StandardsI am occasionally asked, what is the correct name of the ODF standard? Is it OpenDocument Format? Or is it Open Document Format, with a space between Open and Document? Id like (hopefully) to clear this up. The naming decision happened back in 2004. At that point Sun had contributed their specification for the OpenOffice XML format [...] 28/04/2010, source: Rob Weir: An Antic Disposition Why some compilers suck more than others“That's clever. How do they do that?”
An important part of our build system rework is reducing complexity and diversity. When applying these rules to the linking of libraries on Windows, we where hit by an “interesting feature” of the MS Visual Studio compiler. In our current build system we use two different ways to define exported symbols in DLLs:
As we have already made SAL_DLLPUBLIC_IM/EXPORT declarations in most of our libraries (as that helped to minimize symbol exports on the Unix platforms), there is no reason to use DEF files any longer. So we decided to add the missing SAL_DLLPUBLIC_IM/EXPORT declarations and get rid of DEF files in our build system completely. This also makes FLT files obsolete and MAP files won't be used anymore on Windows. The problemThe first code module where we applied that new strategy was “ framework”. In the framework module we have the libraries fwemi.dll and fwimi.dll that export all of their symbols, until now using DEF files. When we added export statements to the code of the fwemi.dll and changed the linking procedure to work without a DEF file, all code in the framework module compiled and linked fine. Even the sfxmi.dll, that links against the import library of fwemi.dll, compiled and linked without a problem. The trouble started later. Linking the scdmi.dll in the sc module and similar libraries in other modules failed due to missing symbols (output edited for display):
Hey, wait a moment – ::cppu::WeakImplHelper1 is a template. Shouldn't we expect that a compiler will just instantiate it when needed? The answer comes from Radio Yerevan: “Yes, but not if the compiler is MS Visual Studio!”. This compiler wants to be smart, but at the end is just too clever by half. Let's have a look on what goes on behind the scene. The root causeHere's the template usage that causes the problem (it's an excerpt from the file framework/inc/dispatch/interaction.hxx):
FWE_DLLPUBLIC is a macro (currently only available in the child workspace where we made the conversion) that on Windows expands to __declspec(dllexport) when compiled as a source file for the fwemi.dll (code that contributes to this dll) and to __declspec(dllimport) in any other case (code that uses it). What does the Visual Studio compiler make out of that? Here's what the documentation says: “As a rule, everything that is accessible to the DLL's client (according to C++ access rules) should be part of the exportable interface. This includes private data members referenced in inline functions”. So you also have access to various internals of exported classes - superclasses, protected internals, and anything that is used in inline functions (because they are compiled in your importing code, so they have to be exported). In case of the framework::RequestFilterSelect class the superclass is based on a template and the Visual Studio Compiler will export all symbols of this specialization of ::cppu::WeakImplHelper1 automatically. Here's the reason why: “Because of a change in behavior introduced in Visual C++ .NET to make the application of dllexport more consistent between regular classes and specializations of class templates, if you apply dllexport to a regular class that has a base class that is not marked as dllexport, the compiler will generate C4275. The compiler generates the same warning if the base class is a specialization of a class template. To work around this, mark the base-class with dllexport. The problem with a specialization of a class template is where to place the __declspec(dllexport); you are not allowed to mark the class template. Instead, explicitly instantiate the class template and mark this explicit instantiation with dllexport. (...) Because this is common pattern with templates, the compiler changed the semantics of dllexport when it is applied to a class that has one or more base-classes and when one or more of the base classes is a specialization of a class template. In this case, the compiler implicitly applies dllexport to the specializations of class templates.” So it seems that the compiler issued an inadequate warning and instead of fixing that, the behavior suggested by the warning is enforced, even if it creates much nastier problems in some situations. Not so clever. This is declaring darkness as the standard if you are not able to screw in the light bulb. In the ::frameworl::RequestFilterSelect example the compiler will instantiate the base-class template ::cppu::WeakImplHelper1 and export its symbols as part of the DLL interface of fwemi.dll. This can create two problems that both have been found in our code. Which of the two problems will appear depends on whether code using ::cppu::WeakImplHelper1 includes framework/interaction.hxx (the class definition that causes the export of the template symbols) or not and if the code links against the import library of fwemi.dll (the library containing the exported symbols) or not.
Possible solutionsWhile it might be bearable to bite the bullet in that single case and add the import library of fwemi.dll to the list of linked libraries for scdmi.dll, it can't be a general solution. The same is true for the analogue step to workaround the situation in the first problem, adding the header that lets the compiler know that it must not create a template instantiation. Developers would have to search for libraries containing the missed symbols or header files containing the export declaration time and again. So there must be better solutions. Before we proceed with them, let's see why the switch from exporting everything to exporting only selected symbols caused this breakage. As discussed above, in the version with explicit FWE_DLLPUBLIC declarations the compiler sees a __declspec(dllimport) for the template symbols and so it does not create its own instance when scdetect.cxx is compiled. In the prior version without the declarations the compiler also exported these symbols in fwemi.dll (I can see them in the DEF file of the library), but there is no __declspec(dllimport) that declares that these symbols are exported. So the compiler creates its own instance of the template in scdetect.cxx. Even if scdmi.dll linked against the import library of fwmi.dll, the additional instance of this template found there would be ignored. The linker seems to complain about a duplicate symbol only if it is declared __declspec(dllimport) at least once. I can't backup this with documentation, but this is the only explanation for what I see. So it looks as if the pairing of dllexport and dllimport is the culprit here. There is no workaround, so the only way to fix the problem is: don't export classes that derive from template specializations. There are two ways to implement that. One is trivial: don't export the class, export only the members that shall be accessible. This works in case of the classes shown in the example. I would say it could make problems when RTTI comes into play, but I couldn't reproduce that with a simple example. This is left as an exercise to the well-disposed reader. ;-) If for whatever reason the whole class still should be exported, there is only one way: hide the base class. Here's a way how this could be done for the classes shown above.
The original class now becomes an implementation class (it was just renamed with an _Impl postfix and removed from the public interface) and some wrapper methods to access the implementation without exposing its details are provided. The GetRequest() methods return an entry to the UNO API of the class and the other methods just forward other (non UNO interface based) calls to the implementation. In case only UNO API calls are needed, the implementation can be easier and the whole class may consist of a static method returning a reference to a UNO interface. Alternatively the visible C++ class could be converted to the implementation of a real UNO service that is instantiated with the UNO Service Manager. There is another option: don't let the compiler see the __declspec(dllimport) declaration. It is documented that this might lead to some overhead ("thunks") in calls to the imported symbols, but if used rarely it shouldn't make things worse, and until we added the FWE_DLLPUBLIC macros the calls where done through thunks anyway. We could achieve that by using a FWE_DLL_TEMPLATEPUBLIC macro that expands to nothing if the code is compiled outside the context of the fwemi.dll. When the fwemi.dll is compiled, it expands to __declspec(dllexport) as usual and the symbols are exported properly. Edit: of course this workaround does help only for the problem of missing symbols, not against the problem of duplicate symbols. On the other hand, for the problem of duplicate symbols there is also an additional possible workaround (defining the problematic template instantiation as an imported symbols explicitly as explained here), but this won't help for our case here. Conclusion
If the problem is that the compiler can't cope with exported classes that have a template specialization as a base class, there is only one safe way to deal with it that works in all situations: don't use them. Instead of that use one of the two ways shown above: don't export the whole class and export only members (if possible) or hide the base class. 27/04/2010, source: GullFOSS New: OOo-DEV 3.2.1 Developer Snapshot (build OOO320m16) availableDeveloper Snapshot OOo-Dev OOO320m16 is available for download. OOO320 is the development codeline for upcoming OOo 3.2.x releases. If you find issues within this build please file them to OpenOffice.org's bug tracking system IssueTracker. Download: Release Notes: MD5 checksums: 27/04/2010, source: GullFOSS New: OOo-DEV 3.x Developer Snapshot (build DEV300m77) availableDeveloper Snapshot OOo-Dev DEV300m77 is available for download. DEV300 is the development codeline for upcoming OOo 3.x releases. If you find issues within this build please file them to
OpenOffice.org's bug tracking system IssueTracker. Download: Release Notes: MD5 checksums: 26/04/2010, source: GullFOSS Weekly Links #7lpOD languages platforms OpenDocument lpOD 0.9.1 Granada is released View lpOD 0.9.1 Granada is released lpOD 0.9.1 has just been released, together with its documentation. You can download lpOD 0.9.1 here. tags: ODF Workshop on Document Freedom Presentations Open Technologies Resource Center OTRC organized one day workshop regarding Free Document Formats on Document Freedom [...] 25/04/2010, source: Rob Weir: An Antic Disposition Why I like Oracle’s $90 ODF PluginThere has been a flurry of news articles about Oracles price change on their (formerly Suns) ODF Plugin for MS Office. What was previously free (as in beer), at least for individual use, is now sold for $90 and with a minimum quantity of 100. The broad coverage (ZDNet, BusinessWeek, CNET, NBC, IDG, etc.) of [...] 21/04/2010, source: Rob Weir: An Antic Disposition Just 10 More DaysThere are just ten more days till the end of April, so you know what that means...it is almost May. :-) No, seriously, you have ten more days to make suggestions to improve default settings in Impress as part of the Renaissance subproject "Better Defaults". The wiki page has been visited 1414 times as of this moment, so if you haven't seen the growing list there yet, get a move on and possibly even add your own favorite default setting improvement. If, however, default settings are not on your personal list of "oh yeah, gotta change that!" stuff, but you still want to help, then here is the opportunity you've been waiting for: A nice little list (OK...not really, but the huge one I had before this worked like a stun-gun so this is like a squirt gun) of Issues that might fit the criteria for better defaults. When you find one that you think sounds good, add that issue (especially the number) to the wiki page. Thank you everybody who has already "been there and done that". Liz 20/04/2010, source: GullFOSS What's the Status of Project Renaissance?
Doing laps in the pool and jogging through the park have done wonders for thinning out the presentation application. Is it getting more sexy as a result? We think so. ;-) Have a look at the most recent monthly status update presentation to see for yourself how Impress is shaping up. Discussion is taking place on the ux-discuss mailing list, so if you are curious or have some points to add, head on over there and jump right in. :-) Liz 19/04/2010, source: GullFOSS Weekly Links #6Group:OpenDocument/Reject LibrePlanet Can you please resend your attachment in OpenDocument format? I refuse to accept Microsoft Word documents or Microsoft Excel documents, because using proprietary formats is bad for freedom and bad for the web. Please visit http://www.fsf.org/campaigns/opendocument to get started with OpenDocument today tags: ODF And the Winners are… The Nokia Guide You guys are fantastic, [...] 11/04/2010, source: Rob Weir: An Antic Disposition ODF Performance Tip #1: Don’t re-compress imagesODFDOM is an open source (Apache 2.0) Java library for reading, writing and modifying ODF documents. It runs standalone, not requiring OpenOffice.org or any other editor to be installed. It operates directly on the ODF document itself. One of the things were focusing on in the next release of (the 0.9 release) is optimizing the performance, [...] 07/04/2010, source: Rob Weir: An Antic Disposition Weekly Links #5Making the Grade With the Open Document Format HOSEF conducts a monthly ‘Open Source Pizza’ so that people can learn more about what is happening with Free and Open Source Software. Thіѕ presentation is about the adoption of the Open Document Format by the University of Hawaii’s College of Education. tags: ODF ODFDOM for Java: Simplifying programmatic control [...] 04/04/2010, source: Rob Weir: An Antic Disposition ODF Plugfest
02/03/2010, source: Open Document - Online Community for the OpenDocument OASIS Standard Open document formats in the public sector
05/01/2010, source: Open Document - Online Community for the OpenDocument OASIS Standard OfficeReader26/12/2009, source: Open Document - Online Community for the OpenDocument OASIS Standard ezComponents Document26/12/2009, source: Open Document - Online Community for the OpenDocument OASIS Standard Drupal ODF Import25/12/2009, source: Open Document - Online Community for the OpenDocument OASIS Standard OASIS Announces Public Review of OpenDocument Format for Office Applications Version 1.216/11/2009, source: Open Document - Online Community for the OpenDocument OASIS Standard ODFDOM - the new opensourced multi-tiered API for the ISO OpenDocument FormatODFDOM is the name of the upcoming free OpenDocument framework sponsored by Sun Microsystems Inc. It will be the next evolutionary step after AODL and Odf4j. Designed together with their architects with the intent to provide an easy lightwork programming API for the ODF developer community. ODFDOM is meant to be portable to any object-oriented language. The first pre-version of the Java 5 reference implementation of ODFDOM is planned to become available under LGPL3 in May 2008. 25/04/2008, source: Svante Schubert's blog |
|
