[TWC] Bullet proof way to publish a TW based application

[Reto]

I am struggling to find a way to publish my TiddlyWiki based application (means: a TWC containing third party plugins, a self written plugin, macros und other necessary tiddlers > basically a bunch of tiddlers working together).

The requirements and wishes:

1. Each application tiddler needs a version number.
   
2. New versions of the application tiddlers should by installed in the user TW by clicking on an upgrade button.
3. Whenever a new version is released the user should get a notification.

I was looking at TiddlySpot and TiddlySpace as publishing platform. The former has the problem not beeing CORS enabled. Using TiddlySpace comes pretty near to the above requirements via the standard import function.

Drawback is that if the user chooses a feed he can't see the version of the local installed tiddler compared to the version on the remote TW and in the list of importable tiddlers.

Any idea how to solve this? I looked at other TWC based applications here but did not find a concept which adresses above requirements.

[Chris Dent]

On Tuesday, March 25, 2014 10:07:40 PM UTC, Reto wrote:

I am struggling to find a way to publish my TiddlyWiki based application (means: a TWC containing third party plugins, a self written plugin, macros und other necessary tiddlers > basically a bunch of tiddlers working together).

If you're able to do your own hosting, you might consider using TiddlyWeb (the code underneath TiddlySpace) with your own set of plugins to get it configured as you like. The TiddlyWeb homepage links to lots more info: http://tiddlyweb.com/

 

[HansWobbe]

Chris:

Am I correct in assuming that Tank is dependent upon TiddlyWeb?  If so, might it be possible to build on Tank's capabilities, in conjunction with TW5 and TWC, to achieve an effective solution.  My interest is simply that I do not have python resources at my disposal and relatively limited server admin resources.  Hence I would prefer to "subscribe" to Tank.

Regards,
Hans

[chris...@gmail.com]

On Wed, 26 Mar 2014, HansWobbe wrote:

> Am I correct in assuming that Tank is dependent upon TiddlyWeb? If so,
> might it be possible to build on Tank's capabilities, in conjunction with
> TW5 and TWC, to achieve an effective solution. My interest is simply that
> I do not have python resources at my disposal and relatively limited server
> admin resources. Hence I would prefer to "subscribe" to Tank.

Yes, Tank is built on TiddlyWeb + a bunch of server side plugins.

It would probably be possible to use it to get the desired combination
of functionality. The reason I didn't mention it directly before is
because of this requirement in the original message:

> Drawback is that if the user chooses a feed he can't see the version
> of the local installed tiddler compared to the version on the remote
> TW and in the list of importable tiddlers.

I didn't quite understand what that meant and how that might fit in
the Tank view of the world.

However, in my experience, with sufficient use of JavaScript and
familiarity with the TiddlyWeb API[1] it is generally possible to do
pretty much anything[2]. The crucial ingredient is effectively decomposing
"anything" into lots of little tasks involving tiddlers.

(For those that don't know, Tank is (yet another) tiddler hosting service:
https://tank.peermore.com )

[1] http://tiddlyweb.tiddlyspace.com/HTTP%20API

[2] This is now even more true with Tank, because Tank just got
support (yesterday) for CORS
(http://en.wikipedia.org/wiki/Cross-origin_resource_sharing) which
makes the resources stored on Tank more accessible.

--
Chris Dent http://burningchrome.com/
[...]

[PMario]

On Tuesday, March 25, 2014 11:07:40 PM UTC+1, Reto wrote:

The requirements and wishes:

1. Each application tiddler needs a version number.
   
2. New versions of the application tiddlers should by installed in the user TW by clicking on an upgrade button.
3. Whenever a new version is released the user should get a notification.

Using TiddlySpace comes pretty near to the above requirements via the standard import function.

I think you should use the TiddlySpace "include mechanism" not tiddler import.
TS has the following behaviour out of the box.

 - A space consists of one or more other spaces.
 - let's say my space is:   asdf

It also contains those system spaces.

• system-plugins
• system-info
• system-images
• system-theme

If one of those spaces changes a plugin and I do a browser reload, the new plugins are used.
There is only one little problem (which can be soved). If a user "clones" a plugin, they are not updated, nor are there any notifications.

Basiclly all "3rd party plugin spaces" on TS work with the include mechanism.
 
-mario

[Reto]

Thanks for the hint to Tank, didn't know this plattform.

> Drawback is that if the user chooses a feed he can't see the version
> of the local installed tiddler compared to the version on the remote
> TW and in the list of importable tiddlers.

I didn't quite understand what that meant and how that might fit in
the Tank view of the world.

This referred to the standard import functionalitiy of TWC (see Backstage) where a feed (aka URL to a hosted TWC) has to be chosen. Currently no version number is indicated in the list of importable tiddlers. Like for instance in the plugin list (also in Backstage).

[Reto]

I think you should use the TiddlySpace "include mechanism" not tiddler import.
TS has the following behaviour out of the box.

 - A space consists of one or more other spaces.
 - let's say my space is:   asdf

It also contains those system spaces.

• system-plugins
• system-info
• system-images
• system-theme

If one of those spaces changes a plugin and I do a browser reload, the new plugins are used.

Thanks for suggestion how to use TS to solve my problem. I have to further investigate how TS might be used in a simple way for users to keep their local TWC application up to date.
 

 

[PMario]

On Friday, March 28, 2014 7:45:41 AM UTC+1, Reto wrote:

Thanks for suggestion how to use TS to solve my problem. I have to further investigate how TS might be used in a simple way for users to keep their local TWC application up to date.

I missed the "local" in your first post. ... If you users do offline editing, it may be not possible to sync stuff back to the server. Browser vendors closed this door.
-m

[Reto]

I have to further investigate how TS might be used in a simple way for users to keep their local TWC application up to date.

I am pretty near the required solution which looks like this:

• The TW containing all the plugins, macros and other tiddlers which are part of the application is placed in public TiddlySpace.
• Local TW based on this application update their application tiddlers via LoadTiddlersPlugin from this TiddlySpace
  

One thing to solve: it seems that the filter of LoadTiddlersPlugin takes only one parameter (a keyword like "changes" or "updates" or "tag:value"). I need to filter for "changes" AND "tag:value" because there are tiddlers I do not want to be loaded from the TiddlySpace. Any idea how to address this? Perhaps it is possible to configure the TiddlySpace in a way that only the application tiddlers are visible ...

[Danielo Rodríguez]

Hello

Wich version of TWC are you using? How good does this works? I'm really interested on it.

[Reto]

Wich version of TWC are you using? How good does this works? I'm really interested on it.

I am using Version 2.8.1. Until now I made only a few tests and am not using it in a "productive" environment.