Jed Carty wrote:

First, yes, makes sense to differentiate between node plugin version and 
single executable version so I did this now. but note I'm not sure I got 
the data 100% correct and i still have some editing to do with it. (there's 
also some CSS problem so the popups don't cut the text properly when you 
click the SetUp title)

Please note that the criteria you have difficulty with are probably because 
they are poor guesses to begin with, from my side. 

Here are some questions based on what you write here.


it is a plugin that lets you save tiddlers, so it could be a saver, it 
> serves the wikis so it may be a server (but it isn't a separate piece of 
> software, so I don't know), and it lets you have multiple wikis so it may 
> be a manager but I am not certain what the 'as objects' part means.
>

The idea is that a user should find what is important. If it is a server, 
I'm guessing that it is simply assumed that one can also save to it so I 
would just call it a server. 
 
I've removed the "as objects" part in the descriptions for managers.


Autobackup: no (maybe later)
>

(I've set it to "no" because to different degrees all solutions can have 
"maybe later" ;-)
 

> data-storage-location: it is a server, but the device you are using it on 
> could be the server so I am not sure what to say about that.
>

I changed options to include "Server location" and made a note that this 
can mean "on your local device".
 

> dependencies: nodejs for the plugin version, none for the single 
> executable version
>

I've redefined "dependencies" to mean dependency on something outside of 
the actual SetUp. The SetUp obviously depends on itself to function but it 
may also require some other supporting software or service to funciton. I 
have rephrased the description for dependencies but will rephrase it again 
to say basically what I just wrote here.

file or folder: I am not sure what this means, you have switchable so lets 
> go with that
>

Maybe single-file or multi-file would make more sense... The idea is that 
the single file nature of standard TW has been highlighted as a key 
feature. How can I capture this aspect and what other aspects stand in 
contrast to this one?
 

> format: I don't know what this means
>

It may be a poorly chosen term and I welcome any better one. What I mean, 
which can be seen when clicking that criteria, is how the SetUp solution is 
"packaged" or manifested, i.e as a html-file, a browser add-on, an app etc. 
I know I feel differently about, say, a browser add-on compared to a 
separate app/program. Any better term? 

os: any for the plugin, windows osx and linux for the single executable
>

Is OSX same thing as MacOS?
 

<:-)

-- 
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/0d641a61-57a3-4e7c-86a0-593fe3433e54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to