The package is org.libreoffice.experimental.desktop so put the source file in
src/org/libreoffice/experimental/desktop.
Change-Id: I08660962dbd44eb48da0c966e218f49287ab5ca7
If the property log.tag.LODesktopSleepOnCreate is set to "VERBOSE" then sleep
after liblo-native-code.so has been loaded to give the developer a chance to
start ndk-gdb and set breakpoints. Yeah, a bit silly to overload a logging
property like this, but it was the first idea I came up with.
Change-Id: I665f87778d083d2d167a5d16f24e2d50b1fba042
Remote icon artwork from Issa Alkurtass <ialkurtass@kacst.edu.sa>,
info box banner from Maxim Darak.
Change-Id: I4a7ddd51b47dba109a75a60ad184cbbc4e2cef8f
The View size is available only after the view has been connected to the
activity, it seems, so move the Bitmap creation to onDraw().
Note that the code in SvpSalFrame::SvpSalFrame() in vcl/headless/svpframe.cxx
still hardcodes another (!) size, 800x600. This affcects the size of the
desktop-style "top-level window" displayed by the android/experimental/desktop
app. I didn't yet figure out the right way to pass the actual view size to the
SvpSalFrame. And there is also a hardcoded third (!) size, 1280x750, in
AndroidSalInstance::GetWorkArea(), although I don't know what that affects, if
anything.
Change-Id: I042bf764cd66efa7069c36601170b90d57fa174c
Partially revert 52a8744afee2cd589813f0377d93f821fce7aedd, i.e. once again
start to remove stuff related only to using NativeActivity... (Because it is
confusing and misleading to keep it around.) Let's do it in small pieces this
time.
Change-Id: Ifdc52eb0ae32c7c510418611cbf01a857a8bc697
It used the same package name as DocumentLoader and the same .apk name as the
eary sc cppunit test app. Probably having two unrelated apps with the same
package name causes some confusion somewhere.
Change-Id: I11414b9cd59694eb97d39bfaeac4ed1066ae3aab
There is no use for non-exported symbols and debugging information in the .so
on the device.
Debugging with ndk-gdb uses the non-stripped copy of the .so located on the
build machine and works fine (as fine as the NDK gdb can work) even if the .so
that is actually running on the device includes no debugging information.
Change-Id: If4e77284a74427261eefac0e167ed42161c773f8
Only renders on very-first-start after install (oddly).
We initialize vcl in it's own thread to avoid problems.
Thanks to tml for fixing a linking issue.
Change-Id: I960d11c6098681356fea0634970545aa9af9bacb
Adjust check to not rely on lexicographical order. This amends
8ae3ddca7e99d2bdbaadd5e0c82de2f0fbd30f91.
Change-Id: I5023b07af819eb09ea9dc569bdbac806f936485f
Why "Choose a Computer" but "Add Server"? Let's always call them "computers"
in the UI.
And in fact I think the feature to add a computer manually is kinda pointless;
is it too much to ask people to have their machines discoverable? I doubt
keeping a computer not discoverable through Bluetooth thwarts a determined
attacker from finding it anyway. (I am not saying that just finding it would
mean compromising it.)
Change-Id: Ib8041a8a793d84bee24587adac582c5fad03d1be
The existing code in refreshLists() was somewhat hard to understand, and it
actually crashed (if uncommented-out). Now it simply empties the maps and view
lists and then rebuilds them.
The visible end result, at least for me, is that I no longer get duplicate
servers in the list...
Change-Id: I1543292e219e666e7dcbc68473f40a11e2eb3381
After 5adefb21244ca57b95e9f8df6ec18880438201bf the "computer" names on the
main ("Choose a Computer") dialog (which probably isn't the right term) were
invisible for me on my Android 4.1 device at least. Very light grey on white,
or something like that. Let's try with default colours and then if that
doesn't work *slowly* modify the colours one item by one.
Change-Id: I9ae2ee8232cfa85eee4aba0fbcf69b8c245a1ad6
