Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


Hi Tor,

On Wed, 2012-06-06 at 14:43 +0300, Tor Lillqvist wrote:
OK, so I did some design of how an API to render (tiles of) pages
would look like that could be used both on Android and iOS apps.

        :-)

public interface org.libreoffice.touch.XDocument extends
com.sun.star.uno.XInterface{
    public static final com.sun.star.lib.uno.typeinfo.TypeInfo[] UNOTYPEINFO;
    public abstract int getnumberOfPages();
    public abstract void render(long, int,
org.libreoffice.touch.XDocumentRenderCallback, int, int, int, int)
  throws com.sun.star.lang.IllegalArgumentException;
}

        It'd be rather nice to have some parameter names rather than just
'long' 'int' etc. etc ;-) I assume that the last four are pixel
co-ordinates to render ? (perhaps doubles would be better), and the
first long is ? I imagine we want to be able to fetch the size of pages
in the same co-ordinate system (?) or do we use the existing render
interface for that ?

But, that's the *specification* and *use*. *Implementing* UNO services
in C++, especially if you don't want to just copy-paste existing code

        One of the big missing nasties is a standard signal/slot mechanism that
is part of the language, and maps (where possible) to a native language
construct.

        HTH,

                Michael.

-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot


Context


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.