tiddlywiki/atw

A simple TiddlyWiki application for Android

TiddlyWiki

This is the master repository of the Classic version (2.x.x) of TiddlyWiki (not to be confused with TiddlyWiki5, which is rewritten from scratch and backward incompatible with Classic).

If you simply wish to use TiddlyWiki or to find out more about it, it is easiest to do so at classic.tiddlywiki.com. Also, you can get help in the TiddlyWikiClassic group. If you have some feedback, you can use both the google group and GitHub issues.

TiddlyWiki's source code is split up into a number of separate files which are then joined together by the npm run build-core command (requires Node.js and NPM to be installed) to produce a single HTML file. See scripts and instructions for testing and building TiddlyWiki and docs for tiddlywiki.com in the build/README.md file.

Discussion on TiddlyWiki development takes place on GitHub and on the TiddlyWikiClassic group; the old TiddlyWikiDev group my be useful to discuss issue related to both TWC and TW5.

License

TiddlyWiki is Copyright 2013 UnaMesa Assocation

It is licensed under a BSD License. See html/copyright.txt for the exact terms.

atw's Issues

add aTW to fdroid !!

fdroid : an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform.

https://search.f-droid.org/?q=atw&lang=en ( no result curently)

... https://f-droid.org/en/contribute/
"If you see an application missing from the repository (after reading the inclusion policy), please feel free to submit it via the dedicated Requests For Packaging issue tracker.

If you have the technical skills required, you can also put together the relevant metadata and submit that via the F-Droid Data repository, which will drastically speed up the inclusion of the application."

...
which would require
https://gitlab.com/fdroid/rfp/-/issues - Requests For Packaging

thoughts about necessary CSS adjustments

TiddlyWiki on small devices needs some css adjustments for easier accessibility

I'd like to gather ideas/proposals in this issue

Finally I think we'll create a plugin that the app uses (for every wiki opened inside it?) containing those adjustments

1. sidebar positioning
2. edittemplate appearance, handling of tiddlers that are being edited
3. accessibility of pagecontrols
4. the sidebar-toggle button
5. buttons/tabs in general / size / positioning
6. tiddler frames (opinionated)
   • should have a bit of space left and right, maybe 0.5em
   • should have those rounded corners
   • could probably look like the google cards used in google now

starting this repo right

This repository is going to contain the code for an Android app that runs tiddlywiki files as web-applications

we need to figure some things out

• copy the license from the TiddlyWiki repo over and change things if necessary

• think about the structure of the repo / how to improve the structure (my) Android Studio creates / or just use that

• create a basic skeleton for the app

• create a readme with build instructions and info/instructions about contributing

Mark S. step ... worth mentioning?

I thought this experiment by Mark S. pertinent ...

https://groups.google.com/forum/#!topic/tiddlywiki/zAyLv39MC1Q

Is he @Marxsal?

making requestFullscreen work in a webview

I tried various approaches to make the fullscreen message go/leave fullscreen

It'll need a bit of researching to make it work
I'll use this issue to gather resources for it

thoughts about layouts

Android Studio offers a wide selection of layouts

A drawer navigation layout is a panel we can swipe in from the left, on the right the main content is displayed

A fab button is a small button in the bottom right corner that reveals another panel at the bottom

And there are more, Android users know them, they're widely used in other apps and pretty standard

What I have in mind is a landing page like the one TiddlyDesktop has

That page is a webview based on a HTML file that ships with the application

From that page new wikies can be opened. I think new wikies shouldn't load in the same webview but always create a new app instance, so that we can jump from one to the other using the system ui, closing one without affecting the other...

First thoughts

app icon

what should the app icon be

in my tests I'm using the core tiddlywiki icon which looks very good
on dark backgrounds it's hard to see because it's black

for now I make it the tiddlywiki standard foreground color #333333

User definable packages?

This is just a thought, since you asked for ideas.

My fantasy here is you provide an Android "wrapper" but facilitate an author being able to wrap into it a specific TW such that the wrapper and TW content appear as one app for download ...

It strikes me Android apps that do well are for dedicated purpose. One app type I can think of is e-books. Do you download the system that you have to manually download for or just "Great Expectations" if that is what you want to read? Hope this clear.

Just thoughts

Brainstorming

I thought it might be useful to have a brainstorming location. A place to float ideas about aTW rather than code.

about fonts

Here's the link to a repository I want to keep an eye on

https://github.com/rsms/inter

it provides a font "similar to Roboto, San Francisco ... " but designed for for user-interfaces on small screens
TiddlyDesktop uses the "lato" font family and I think this app could make use of this one

making export-tiddler work

the download messages don't work out-of-the box in the webview

It'll need some reseach to make them work
I'll use this issue to gather resources for it