Re: Resources on writing import/export file filters for Writer

Jens Tröger <jens.troeger -AT- light-speed.de>
Sat, 19 May 2018 21:26:18 -0700 (MST)

Hello,

I haven’t yet had the time to dive into the topic yet—unfortunately.  So
perhaps my question is somewhat of a guess: compared to using the Python UNO
interface to load and traverse a document, can I expect a performance
improvement when I use a filter to save the information that I currently
extract using UNO?

If the guesstimated answer is “maybe/likely no” then I’d shift my current
priorities…

Cheers,
Jens



--
Sent from: http://nabble.documentfoundation.org/Dev-f1639786.html

Context

Resources on writing import/export file filters for Writer · Jens Tröger
- Re: Resources on writing import/export file filters for Writer · Miklos Vajna
  - Re: Resources on writing import/export file filters for Writer · Jens Tröger
    - Re: Resources on writing import/export file filters for Writer · David Tardon
      - Re: Resources on writing import/export file filters for Writer · Jens Tröger
        
        Re: Resources on writing import/export file filters for Writer · David Tardon
        
        Re: Resources on writing import/export file filters for Writer · Jens Tröger
        
        Re: Resources on writing import/export file filters for Writer · David Tardon
        Re: Resources on writing import/export file filters for Writer · Jens Tröger
        Re: Resources on writing import/export file filters for Writer · Miklos Vajna
        Re: Resources on writing import/export file filters for Writer · Jens Tröger
        Re: Resources on writing import/export file filters for Writer · Miklos Vajna
        Re: Resources on writing import/export file filters for Writer · Jens Tröger
        Re: Resources on writing import/export file filters for Writer · Noel Grandin
        Re: Resources on writing import/export file filters for Writer · Jens Tröger

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.