summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2014-11-30android: extract JavaPanZoomController (PZC becomes an interface)feature/droid_calcimpress3Tomaž Vajngerl4-967/+987
Change-Id: I87e63008fe7c6db62c18bf461dc4dcda733393ac
2014-11-30android: Fennec change - move classes from gecko.ui to gecko.gfxTomaž Vajngerl7-13/+7
Change-Id: I510e0d601e293ed8e013a0273d5ae0f9be078d8a
2014-11-30android: change LOKitThread.draw to return voidTomaž Vajngerl1-4/+2
Change-Id: I00f3ed059bd633e662e5bee09703ca505bf3b9a5
2014-11-30android: Fennec PanZoomControler updates..Tomaž Vajngerl7-22/+98
Change-Id: I277fbf522b16d9b479260df8372a5ee160adcc37
2014-11-30fdo#85845 android: draw tiles immediately when they are readyTomaž Vajngerl7-68/+90
Change-Id: I924a212210703b0f6136ddefacd77d98dc89f42d
2014-11-28android: rearange anc clean-up GeckoLayerClientTomaž Vajngerl2-266/+246
Change-Id: I6b4a7f8053adea6d86ee625201eeead188bbadcc
2014-11-27android: Fold LayerController into GeckoLayerClientTomaž Vajngerl10-359/+335
Change-Id: I6a6e702e243b389f1c487b6b5390f28a4292cc74
2014-11-27android: introduce getDisplayMetrics - reduce code duplicationTomaž Vajngerl2-6/+12
Change-Id: Ic020d9604814213e13c339b07b6e74de77a9f400
2014-11-27android: reset document dimensions when changing document partTomaž Vajngerl1-7/+17
Change-Id: I2f7967ee20ad71b58e2b0dc7f182769499910373
2014-11-17android: Change the handle type (long too ByteBuffer)Tomaž Vajngerl1-1/+1
Change-Id: Ia2ed94dbbb43d2e768da5af5ca7a51f5cda5bae0
2014-11-17android: use ByteBuffer to send or store pointers in JNI bindingsTomaž Vajngerl5-27/+24
Using direct ByteBuffer is much nicer option to store or send pointers between C(++) code and Java via JNI as it handles endiness and pointer size for us. Using "long" type can have unexpected results in 32-bit architectures (mostly Android). This was causing grief especially when Android introduced support for 64-bit architectures starting with SDK 19. Change-Id: Ie92d0f913b668e1724e846d70d1820445d9cb086
2014-11-17android: cleanup LibreOfficeKit initialization in JavaTomaž Vajngerl2-17/+15
Change-Id: I7688968e92ae4b3d6fef19c4544ae91bdcd8b1b9
2014-11-17android: use different function to prevent stripping JNI symbolsTomaž Vajngerl1-2/+2
Change-Id: Ib003da5c7fec7fc3783f01a33a63deb384c7e770
2014-11-17lok: improve error reporting in lok implementationTomaž Vajngerl1-20/+67
Change-Id: Ifc7b18e173b0c91c24a53fad9c35ac3a34a4b33e
2014-11-17android: extract gathering document info into postLoad methodTomaž Vajngerl1-25/+28
Change-Id: Id90680d3b207973b55927add1c91111268bb2a48
2014-11-17android: improve error messages in DirectBufferAllocatorTomaž Vajngerl1-7/+7
Change-Id: Iefab77e543606cfad937a79743fb3b9a68a0f2a2
2014-11-10android: add destroy and exit as a separate JNI callTomaž Vajngerl2-0/+7
Change-Id: Ia8516da556b3736f34b366e2eb89ad8bbd7bafc1
2014-11-10android: VM based implementation of DirectBufferAllocatorTomaž Vajngerl1-6/+47
DirectBufferAllocator is responsible to allocate buffer. We used Fennec JNI based allocation (and freeing) because of overallocation bug in some Android versions. With this the VM based allocator implementation is added and used by default because of bugs that happen in newer Android versions (specifically when ART is used as the Android VM). Change-Id: I07eb364fd1647b3a09d1568d4fef82398a02dfeb
2014-11-08android: use int type for size in DirectBufferAllocator allocateTomaž Vajngerl1-6/+10
Change-Id: Ied2687d334f7d1ff9ff2f3cb6664848d50814b7c
2014-10-27We seem to crash unless we have org.openoffice.Office.UI/FactoriesTor Lillqvist1-1/+0
Change-Id: Ie172f60a7134173462ff9711a40dc74c94ad8206
2014-10-27Do the configuration pruning only in the DISABLE_UI caseTor Lillqvist1-3/+3
Change-Id: If85c6a86434c0aa32d188a0f128f6b6cd613bbb5
2014-10-27The configuration pruning with mobile-config.py seems to work nowTor Lillqvist1-1/+3
Change-Id: I1b1891f0d7d7b8aa407e7da346ff5f8e3cbe8657
2014-10-27Don't prune org.openoffice.Office/UITor Lillqvist1-1/+0
It apparently contains color schemes and stuff that the code wants access to here and there. Change-Id: Ie3f0de5e3846df99a02a2693156679cc6c010d10
2014-10-27Avoid automatic toolbars in the non-desktop caseTor Lillqvist1-0/+6
Change-Id: I9e5bff735b0035c147e10ae066da3a4873d66749
2014-10-27Ignore exceptions when getting the background color configurationTor Lillqvist1-3/+14
We are experimenting with a pruned configuration database in the desktop case, and letting the exception propagate here killed the document loading. Change-Id: I59e5d016617c17c2bc36de2fd69c6691bfa6b135
2014-10-27Beware of modifying a list being iteratedTor Lillqvist1-10/+18
Change-Id: Ib9cf1a47eb20bd28d954ddcded89f67cf6865f1c
2014-10-24Revert "Temporarily do more verbose logging"Tor Lillqvist1-2/+2
This reverts commit 00d2482326af17ac61d3c2aaa21d837f0e72bb37.
2014-10-24Add (commented-out) invocation of mobile-config.pyTor Lillqvist1-0/+1
Change-Id: I379601099bda928b9eeeaeb29030bc009e3cbbf2
2014-10-24Temporarily do more verbose loggingTor Lillqvist1-2/+2
Change-Id: I3d0db329311e9f2496f80931e6d2776e18f1b2d9
2014-10-24Try to be less eagerTor Lillqvist1-2/+0
Change-Id: I83a395c628b00b6ca96c93d5d5362ea750e57b2b
2014-10-24Log parsing time of each xcd fileTor Lillqvist2-1/+5
Change-Id: I290e2c84b17b9b5063139c6027b72f6cd3a78a99
2014-10-24SAL_INFO how long parseXcsXcuLayer() and parseResLayer() tookTor Lillqvist1-0/+4
Change-Id: I1e71b8a6348301cd5b3fed0ae8b3346ae3e07d8e
2014-10-24Rename --enable-sal-info to --enable-sal-logTor Lillqvist3-7/+7
Change-Id: I896c9ac1c941b85d052fbefb902c4341664881d4
2014-10-24Add --enable-sal-infoTor Lillqvist3-0/+16
Change-Id: I014d70ace7ce34b804ea2a018d3de8f94f7e0cbc
2014-10-22Bin duplicatesTor Lillqvist1-22/+7
Change-Id: Ie6347ed6b9c1b8bee7a08950d5c67d4a2039fba5
2014-10-21CosmeticsTor Lillqvist1-4/+0
Change-Id: I4d819f59ecb2462aee5998628ad034657bf3b0f9
2014-10-21Log time since object creation, not since epochTor Lillqvist1-4/+8
Change-Id: I43c7725b88c9326e269abc277f42e47c08acefb5
2014-10-16android: Stopgap: _exit() is better than a hangTor Lillqvist1-0/+4
Change-Id: Iaada020e85a8d2557e270f7d1514f2260ffb2af0
2014-10-16basebmp: accelerated method to create a clipping device.Michael Meeks3-6/+28
This was some staggering proportion of tiled rendering documents with complex clipping; it seems 'clear' is not what memset is for 1bit clip masks. Change-Id: I9142ffb7d7016603feb7782d6f03b9992b9494e3
2014-10-15Add a SAL_INFOTor Lillqvist1-0/+1
The "bootstrap" errors tend to end up being displayed in some error dialog attempt which of course does nothing on mobile platforms, and that crack seems to crash on Android even, so this should give us some chance to get some idea at least what the code thinks is wrong... Change-Id: I070b017baf042ff692766d1efd1511e1addb6ecf
2014-10-15Use maximum logging verbosity while attempting the restartTor Lillqvist1-0/+2
Change-Id: I3e3162474db1edef3b92e252b249fe373dedbbfd
2014-10-15Reduce log verbiageTor Lillqvist1-1/+1
Change-Id: I0da75df61d129aaaf03ac546fcf1e5dbcff9d404
2014-10-15Add a small script to run adb logcat with filteringTor Lillqvist1-0/+19
We use arbitrary tags when logging stuff in our code so we can't use the built-in filtering of adb logcat. Change-Id: I2d607b86bde975c5cbdd17adc22d0fc15076be51
2014-10-15If loading a document fails, try restarting the 'main loop' and try againTor Lillqvist1-1/+14
Does not work, though, we end up with a crash that is hard to debug thanks to the rubbish tool-chain. Change-Id: Ie1954e35e649fac8dd106f0ccbc6951c4a6c1c63
2014-10-15Call DetachCurrentThread() in the AndroidSalInstance destructorTor Lillqvist1-0/+2
As we call AttachCurrentThread() in the constructor, it seems logical to call DetachCurrentThread() in the destructor. Some warning messages in the logcat indicated that DetachCurrentThread() hadn't been called for a thread that died. Actually I would prefer to call both AttachCurrentThread() and DetachCurrentThread() in the actual thread function, instead of somewhat haphazardly and imlicitly in the AndroidSalInstance constructor and destructor. Do we know for sure that the lifetime of the AndroidSalInstance singleton (is is a singleton, right?) is 1:1 coupled to that of the LO "main thread"? Change-Id: Ifcc0e0b9af88b19389c416c5646499d44ad0e941
2014-10-15Skip the 'desktop' app for nowTor Lillqvist1-1/+0
Change-Id: I040bd49f8cfeec74c3225135a110140c1816be43
2014-10-15The 'bInitialized' state needs to be global, and unset in lo_destroy()Tor Lillqvist1-1/+6
I assume, for lo_destroy() to be useful at all. Not that I know for sure what the exact intended semantics of lo_destroy() and lo_initialize() are. But I assume that the idea is that after lo_destroy() has been called, lo_initialize() can be called again. Change-Id: I2dea26db150d19ed438427e1c119a5297b9bc9c3
2014-10-15Don't keep the LibreOfficeKit pointer in a global variableTor Lillqvist1-7/+4
It is invalid in case lo_destroy() has been called. Change-Id: I45533b66d32fc650e48748da8ea1d2f2aaa381e0
2014-10-13android: Dump my debugging notes to the readme's.Jan Holesovsky2-0/+18
Change-Id: I8f91e73fe5df5dfef054df80d43be3c74d01388b
2014-10-13android: When debugging, the installLocation must be "internalOnly".Jan Holesovsky2-10/+14
Otherwise the gdbserver ends up with run-as: exec failed for /data/data/org.libreoffice/lib/gdbserver Error:Permission denied (you need to run ndk-gdb with --verbose to see that). Change-Id: Iccdf0ff268c20d2fb5abc1e93404375fa51c1cf1
generated by cgit v1.2.3 (git 2.39.1) at 2024-04-23 21:02:17 +0000