Adithya
As other have noted more features all already demonstrated in the other
apps one way or the other. This idea is just a different way to package
tiddlywiki as an app.
>
> I see the value in what you're suggesting. I am however limited by my
> understanding of how TiddlyWiki operates.
>
Lean on me and the community here to learn more.
Some questions I will try to figure out the answer to in the next few weeks:
> 1) How exactly will the android container facilitate a TW upgrade?
>
First, An application would act as a shell containing a single html file.
One of the android apps has a fork facility. You can provide the link to
tiddlywiki.com and it downloads the whole wiki into the app. The latest
version can be published online, new users get the latest loaded when first
using the app according to a hard coded internet address. All their changes
are saved in the local copy, and the designer can build an update package
that the local wiki can access to update their local copy. This could
leverage existing plugin update processes and/or the library mechanism.
Basically a pull to update, but a rudimentary way to message the app could
be developed to announce and update available. This is all in tiddlywiki,
not the proposed app.
Core updates would be a little more complex but doable.
What is important to note here the app should not need updating much it is
the content in the html that needs this option.
> 2) I would like the functionality to share something in android and add it
> as a tiddler. How will the android container do this?
>
>
This has being done as others account, you can import pdf and images and
more. It may be tricky to import images etc... as external and a single
file tiddlywiki would not want too much embedded content.
So to be clear This is what I imagine.
- An Android app that is a shell that can present a single file
tiddlywiki to use.
- Accepts shares, can access GPS (already), can import content on the
phone (all already done), links to the default browser etc...
- In this case however a designer builds their single file wiki and
posts it online for example a personal journaling tool
- They encode the app with the link to this wiki and generate an apk (or
what ever) with this hardcoded address.
- The app can be placed in the app store as its branding suggests eg
"personal Journal"
- On installation the app either uses the embeded wiki file, or ideally
goes to the coded address and downloads the latest copy.
- Thus updates to the embedded wiki will be distributed to new users
on initialisation.
- Once setup the user just uses the app according to the design of its
embedded wiki.
- In someways this replicates the functions of Progressive WebApps.
- The HTML file saves its self on the local device through the app.
- Import export and backups can be built inside the tiddlywiki or
facilitated by the app.
In future a way for a tiddlywiki to poll a internet address for possible
updates on launch can be developed, the app need only, "not stand in
tiddlywikis way".
A final note, I would pay to have this facility. and if I had a successful
app I would pay more.
Regards
TW Tones.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/ef206eb0-33c7-491f-86e9-2147f0713560o%40googlegroups.com.
