>
> On the other end of debate is people who do not have the necessary admin
> privileges to install node js on their system. -- Riz


You can copy the node.exe file into the TiddlyServer (downloaded from the
releases page) or TiddlyWiki directory (downloaded from the main code page)
and then everything will basically work the same, except for any npm
commands.

As for how one actually does 'run a node server', I worry that we have
> over-dramatised it in previous discussions. It isn't difficult and doesn't
> require any special knowledge. You install Node like any other piece of
> software (https://nodejs.org) and you need to run half a dozen commands
> from the command line (they're given briefly at the start of my static
> sites tutorial here: https://www.didaxy.com/exporting-static-sites-from-
> tiddlywiki-part-1). I suppose if you haven't used the command line at
> all, it's a bit of a pain, but learning is good for you :-) -- Richard


Great point. Just thought I'd point out that this is for static sites, not
TiddlyServer. And you've made it really simple! A glance-over looks like
I've finally hit gold when it comes to static sites. TiddlyServer is even
simpler -- after installing Node, you just extract a zip file and edit
settings.json to your liking.

This is OPINION. Its obvious we have MANY methods to save TW. Perhaps the
> single biggest issue is lack of a RESOURCE POINT that DOCUMENTS in detail
> how to set them up.  -- Josiah


I share your opinion. So I created this page:
https://en.wikibooks.org/wiki/TiddlyWiki_Manual/Saving_Methods and added
Mark's script to it.

Arlen

On Wed, Sep 20, 2017 at 7:54 AM, RichardWilliamSmith <
[email protected]> wrote:

> 1. Consider packing it to deb/exe/whatever-mac-uses formats. The installer
>> should ideally place necessary shortcuts and menu entries in the
>> corresponding folder to each OS.
>>
>
> Excellent idea. I started researching how we might do that. My best guess
> so far is nexe: https://github.com/nexe/nexe
>
>
>> 2. The opening HTML is replaced by a TW itself. It should show links to
>> the various TW as it does now. In addition, that tiddlywiki should also
>> have a control panel, which would allow the user to new TW paths, and
>> modify settings. It won't be hard to cook up a button that will export
>> these settings to json format.
>>
>
> Terrible idea (no offence) - the current interface is nice and simple and
> wouldn't gain anything from being a Tiddlywiki itself. Controls for adding
> new paths and creating new tiddlywiki folders and single-file editions is a
> great idea though and I think Arlen already mentioned the possibility.
>
> As to your general point, I do agree that there are some people who may
> get value from Tiddlywiki but not know how to run a node server - having
> something that 'just works' is a worthwhile goal. But, let's be honest,
> Tiddlywiki is really mostly for 'geeks' at the end of the day :-). (imagine
> telling someone "oh, right, you've accidentally nested a list of all your
> notes inside a list of all your notes, so your 'wordprocessor' crashed.
> Just restart it and figure out a way to delete that note without opening
> it...") :-)
>
> As for how one actually does 'run a node server', I worry that we have
> over-dramatised it in previous discussions. It isn't difficult and doesn't
> require any special knowledge. You install Node like any other piece of
> software (https://nodejs.org) and you need to run half a dozen commands
> from the command line (they're given briefly at the start of my static
> sites tutorial here: https://www.didaxy.com/exporting-static-sites-from-
> tiddlywiki-part-1). I suppose if you haven't used the command line at
> all, it's a bit of a pain, but learning is good for you :-)
>
>
>
>
>>
>>
>> On the other end of debate is people who do not have the necessary admin
>> privileges to install node js on their system.
>>
> --
> 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/a343ff21-80a3-4df5-8067-0abc3e548c9e%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/a343ff21-80a3-4df5-8067-0abc3e548c9e%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAJ1vdSTzZB4EccE0EZobpmc-2XZk7oOOH%3Dedp01hYUG6i_d8RQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to