Development is a process. Development of Tiddlywiki - is a process too. By
itself, any process is purposeless - it is just a manifestation of specific
laws under certain boundary and initial conditions. Similarly, with the
development of Tiddlywiki - indeed it is the exciting saga for the sake of
self-improvement. But really that is not a goal. That is a process.
So, now about specific things. No doubt Tiddlywiki is an outstanding tool
for Web content creating. There were said a lot about that. It would be
better once to touch it, to come to the same conclusion independently.
However, with all the advantages Tiddlywiki does not lack shortcomings,
which significantly slow down its wider use.
Main "stumble stones" in Tiddlywiki use, in my humble opinion, is in the
entry resistance of "zero" users (newcomers) who need a tool with a
convincing set of capabilities for organization a personal space as well as
cooperation in the global network, but who are of little interest to study
how it is devised inside.
*Reasons*
More specifically these "stumble stones" could be described as follow:
- Some inconvenience of use:
1. Multi-step installation procedure, especially when one runs
multiuser tiddlywiki in git-network under Node.js + git + tortoisegit
+ githab / gitlab.
2. Control elements for the whole (git-network based) system are not
consolidated, i.e. dispersed over various separate software components.
- Intrinsic scalability limits:
1. A sole tiddlywiki is pretty closed document - all the benefits of
internal tiddler use: filtering, transclusion, powerful search, links
etc.
are not applicable to external tiddlers.
2. For scalability one tiddlywiki needs permanent links to other
(i.e. external) tiddlywikis. Permanent external links are usually
achieved
by placing a tiddlywiki or its generated static pages under a permanent
domain name.
3. But even the latter is not completely solve the issue: usually a
tiddlywiki itself is quite heavy file from several upto several dozen MB;
also intrinsic API for external tiddlywiki data manipulation is absent
(at
least for my knowledge); generated by Tiddlywiki static pages are
helpless
in this context as well.
4. Somewhat aside, but equally important for scalability is creating
a basic mechanism for multilingual synchronization of several tiddlywikis.
*Primary task list*
Based on the aforesaid here I formulated a primary task list. It is just my
personal vision. So everyone is free to add own issues, however, keeping in
mind the two main priorities:
1. ease of installation and management, and
2. scalability as a platform for multiuser web collaboration.
So the primary task list looks like:
1. A single installer is required for all the necessary starting
components and settings, including: Node.js, tiddlywiki, git, tortoisegit
(if
necessary), etc. for main operational systems.
2. A shell for multiple tiddlywikis management is required (e.g. a type
of TiddlyDesktopQ <https://github.com/Eucaly/TiddlyDesktopQ> extension).
Among other things, the shell must be capable of:
- Interoperable in respect of variety of operating systems and
browsers;
- Locally create, delete, move, etc. tiddlywikis under node.js;
- Run a separate tiddlywiki under node.js from a file explorer of a
given operating system through, for example, double click or a context
menu;
- Carry out a minimum required set of operations to synchronize local
and global repos, including: commit, push, pull, diff, etc.
- Minimum required control over static pages publishing on Githab /
Gitlab Pages;
3. Providing a type of mediawiki interwiki
<https://www.mediawiki.org/wiki/Extension:Interwiki> syntax for links to
external tiddlywikis. For example, a reference to a tiddler from another
tiddlywiki may have a look like: [[anotherTW:Interesting staff]].
Realization of certain interwiki web services also is possible.
4. Organizational Page
<https://help.github.com/articles/user-organization-and-project-pages/>
on Githab / Gitlab Pages is a root page for a number of other pages of
projects or user groups under this root page. API for automated collection
of information about underlying pages for the organizational page is
required for further use.
--
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/af9fe0ed-bfbb-42da-99cd-2b5795f0a097%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
