6db34b6b33
...via unoidl-write and the new source-format registry provicers, instead of
using idlc to produce .urd files, regmerge to merge them into legacy .rdb files,
and unoidl-write to translate those to new UNOIDL .rdb files.
gb_UnoApi and gb_InternalUnoApi ctors take an additional argument now that is
the path (below $(SRCDIR)) of the source-format registry from which to obtain
UNOIDL entity definitions. It can either be an .idl file (in which case no
*_add_idlfiles calls should be used and the resulting .rdb will contain all the
entities from that one .idl file; used in some tests to conveniently define all
test-specific entities in a single file) or a directory denoting the root of an
.idl file tree (in which case *_add_idlfiles calls specify the entites to
include in the resulting .idl file). (In the first case, the generated .rdb
file needs to depend on that single .idl file, so the gb_UnoApiTarget ctor
contains a dependency on that additional argument, which happens, as a side
effect, to trigger rebuilds in the second, tree-based case when addition/removal
of .idl files in the tree causes updates of directory time-stamps.)
UnoApiPartTarget and all the dependency-tracking logic based on .urd files in
solenv/gbuild/UnoApiTarget.mk is gone. Generation of an .rdb file now depends
on its source registry (see previous paragraph) and all the .idl files specified
with *_add_idlfiles (in the second, tree-based case above).
A consequence of that is that gb_UnoApi_add_idlfile, -_nohdl, and -_noheader all
do the same now. I left them in for now anyway, maybe they become relevant
again when the use of cppumaker is changed to read directly from a source-format
registry instead of going via a .rdb registry.
The legacy tools idlc, regcompare, regmerge, and regview are still contained in
the URE or SDK for now.
|
||
|---|---|---|
| .. | ||
| idl/org/libreoffice/touch | ||
| source | ||
| CustomTarget_touch_javamaker.mk | ||
| InternalUnoApi_touch.mk | ||
| Library_libotouch.mk | ||
| Makefile | ||
| Module_touch.mk | ||
| README | ||
Library that provides API used by LO-based apps on touch devices
This is all very much a work in progress and the design can change
radically at any moment. And actually at the moment it is unclear
whether this will be used or not.
The name "touch" for this module and the library name "libotouch" are
not fixed and might change if somebody comes up with niftier names.
This module will contain an UNO API to be called either from Java (for
Android), or directly (iOS). (Or, on iOS, possibly through some thin
Objective-C layer to hide the UNO.)
The API will provide a mechanism to render "tiles" of a document at some
requested zoom level. Initially for viewer style apps, but the work should
ideally be open-ended to potentially be a base for editing apps, too.
For starters, concentrating on text ("Writer") documents as they are
easiest. With spreadsheets come the added complexity of the cell grid being
potentially unbounded and no clear "page" area. With presentations come the
animation complications, and possibly LO-based viewer apps for presentations
will be done in a totally different fashion.