Tony if you check the thread you referenced then you will see that I have
commented extensively there because that is my main theme!
Nonetheless I tried many themes on mobile and obviously the vanilla one.
I want to mention, given how many people use their phones for things like
that, that I
Adam,
So you are using tiddlywiki out of the box on mobile firefox. and there you
are finding performance and user interface difficulties? OK
Creating entering text strings, editing blockes of text is a kind of
activity that small screen touch devices do not do well with, in many
different
Hello Tony,
when I press the more actions button in a tiddler then I am not able to see
the full window listing those actions and no matter what I do then without
seeing them I can't press them.
Also when I move through tabs in the sidebar in Android it is very slow.
Generally the layout of
Jed,
Nicely done. Could this be generalised or branched to download as a file
any tiddler as a file encoded or otherwise?
I understand to do this you are effectively decoding and exporting the
content of a tiddler into a file (without tid or json info), returning the
file to its native state.
Adam Antios
Can you list at a high level where you are finding tiddlywiki on android
falling down?
I support Jeds comments and add there are solutions such as PhoneGap that
try and be a dev environment for multiple phone platforms, but it seems
they are always coding to the lowest common
I made an action-widget to do this. The code is on GitHub
here: https://github.com/OokTech/TW5-DownloadBinary and a quick demo is
here: https://www.ooktech.xyz:8443/Public#Download%20Binary%20Demo
If this looks like a good way to solve the problem I can make a pull
request.
--
You received
This fits with some work I have been doing so I will just throw together a
quick plugin to test it out. I think that the best way to implement it
would be to create an action widget and then add a 'download as file'
option to tiddlers that have base64 encoded contents. Would that work for
your
I of course can't talk for the full dev team so this is just my reasoning.
But my answer is both it is technically difficult and not a priority.
First, contemporary Phones are designed to be limited. Touch screens are,
for people who can use them (I can barely use touch screens so I am a bit
