Pre-release on Node

[Alex Hough]

Dear TW

Is there a command to get the latest pre-release running under node?

thanks in advance

Alex

[Jeremy Ruston]

Hi Alex

Try these instructions:

1. Clone a local copy of the TiddlyWiki5 GitHub repository from https://github.com/Jermolene/TiddlyWiki5
2. Open a command line terminal and change the current working directory to the root of the TiddlyWiki5 repo
3. Type npm link (Windows) or sudo npm link (Mac/Linux) to tell npm to use this copy of the repo as the globally installed one

After this procedure you can work with TiddlyWiki5 via npm as though it had been installed in the usual way with npm install -g tiddlywiki.

Update the clone from time to time in order to ensure that you have the latest code.

Let me know how you get on,

Best wishes

Jeremy.

--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CALc1hYedMmR4BUmM0JVD-mS712vUaAVi-DDmeXzcmBNXwgmZVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Jeremy Ruston
mailto:jeremy...@gmail.com

[Alex Hough]

Hi Jeremy,

I can get the latest release, but how do I get the //pre//release?

best wishes

Alex

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAPKKYJbz5TCbmGrg2saF58LCvLCoJ%3Djvd-ETf0C2xjOVOxp6WQ%40mail.gmail.com.

[Jeremy Ruston]

The instructions are for getting the prerelease; they differ from the usual installation instructions (which use npm to install the latest stable release of TiddlyWiki). The master branch of the GitHub repo corresponds to the prerelease you see at http://tiddlywiki.com/prerelease.

Best wishes

Jeremy.

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CALc1hYegMFnGvAJFYaZdLQgW%3DhfQnH9CSo3mz58PCOw1sHSySQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Alex Hough]

Ahhh.... many apologies!

It makes sense, of course

will try in the week

Alex

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAPKKYJZ%3Dqmf-ey2ESKdb6oaztyythA8jfSXoVd%2BR0_ZdJfO6Kw%40mail.gmail.com.

[Alex Hough]

Hi Jeremy,

I've got it working, thank you.

Correct me if I have got it wrong, but I have now "linked" my local copy of TW5 to the TW program I have installed. That program runs on node.

Instead of getting its data from the TW node site, it gets it from my local site

best wishes

Alex

[Alex Hough]

Jeremy et al,

Maybe I should start another thread, but moving on from where I am now, I want to be able to create TiddlyWikis with some of my favourite plugings installed, or maybe one of my own custom editions.

The first one would be one with just the TiddlySnip plugin

I guess I would add my choice of plugins to a version of the clone and perform the sudo npm link move? But I suspect that there is a standard way of doing this where I can update the pre-release without having to install the plugins each time. Any advice would be most appreciated.

Personal Editions

I can visualise a workflow where tiddlers are worked on in different editions. 

For example, I first collect loads of snippets using tiddly clip, then I edit them and put them into a TiddlyMap edition, then at some point output certain sets of tiddlers as static html files.

TiddlyWiki.Com on its head

I imagined a set up along these lines, I think its a bit like TiddlyWiki.com but the other way round.

Static pages are generated from my personal TW and are presented according to a URL schema like this

http://mydomain.com/about

http://mydomain.com/projects

http://mydomain.com/projects/garden

Then on each static page there would be a link pointing to a TW

http://wiki.mydomain.com

The user can then navigate the TW and experience more a connected resource

Am I barking up the right tree here? It feels like a penny is about to drop...

best 

Alex

[Tobias Beer]

Hi Alex,

interesting to see you asking similar question to those I was about to. ;-)

I just started to port tb5 to a node.js managed version with neatly assorted folders only to be pushed some day onto GitHub ...and there is a host of questions bubbling up.

For example, there are more wikis than just tb5 and I will eventually do the same process with all of them. This introduces interesting problems. I have separate content bits but then some of the underlying framework of custom components I'd like to share amongst those wikis.

So, I will eventually setup a folder structure like so...

• common
  
• config ...gobal config for all wikis
• templates ...global templates for all wikis
• macros ...global macros for all wikis
• plugins ...selectively added to any of the wikis below
  
• KaTex
• Tinka
• MyPlugin
• wikis ...maybe these correspond to the editions folder in the TiddlyWiki repo?
  
• tb5
• system ...anything beyond the common components
• content ...the actual content of tb5
• filters
• system
• content
• style
• system
• content
• MyPlugin
  
• system
• content ...showcasing the plugin and demos for it
• etc...

For example, for the MyPlugin wiki there will be some repo on github where I maintain the code for MyPlugin, that I want to then utilize and demonstrate in the MyPlugin wiki. Preferably, building that wiki will somehow point to my local copy of that repo so as to include the latest built, me assuring that I haven't just switched to some bugfix-branch.

Also, for some or all wikis I will eventually want to render static files, too. So I am wondering not only how to render those, as I've not done any of that yet, but also where to sensibly render them to. I have a similar problem for the actually built wikis, that I haven't yet figured out how to built, as their location will be outside of the above folder structure, since I don't want the output to be part of the same content-repository, as that would possibly blow that out of proportion. Currently, I have one big repo with all the standalone wikis in it that at some point were on TiddlySpot, so as to manage them more close-by... and I am a bit concerned that GitHub will at some point remind me of some quota I am about to reach. So, I started to, again, create individual TiddlySpot wikis for demonstrating things like modifications associated with a pull request. That way I don't add ever more wikis for that to a GitHub repo.

On top of all things, I will also want to be able to quickly built a pre-release version with the modifications of a given branch for whichever pull requests I make to the TiddlyWiki repository. So far I have always been editing the affected components in the browser, which is possibly not ideal. Not yet done that prerelease built process, and so it needs more studying to run it under node... with respect to my forked folder. I guess Jeremy's instructions above deliver the basic how2 to doing that. But then the demo-tiddlers to showcase the changes will have to be somewhere else, however not part of any pull requests. Ah, the complexity. :D

I guess I'll have to constantly link and unlink different versions from where to compile my output as I probably wouldn't want to construct my main wikis from a pre-release built... as you do... although I can understand why you would. ;-)

Much doing ahead.

Best wishes,

— tb

[Tobias Beer]

Hi Jeremy,

Try these instructions

1. Clone a local copy of the TiddlyWiki5 GitHub repository from https://github.com/Jermolene/TiddlyWiki5
2. Open a command line terminal and change the current working directory to the root of the TiddlyWiki5 repo
3. Type npm link (Windows) or sudo npm link (Mac/Linux) to tell npm to use this copy of the repo as the globally installed one 

Just tried this for the first time on win 10,

trying to serve my tb5 wiki folder on localhost

and got this popping up in the browser...

Internal JavaScript Error

Well, this is embarrassing. It is recommended that you restart TiddlyWiki by refreshing your browser

Uncaught TypeError: options.wiki.getTiddlerDataCached is not a function

Best wishes,

— tb

[Jeremy Ruston]

Hi Tobias

Just tried this for the first time on win 10,

trying to serve my tb5 wiki folder on localhost

and got this popping up in the browser…

Does the same wiki work under TiddlyWiki 5.1.9?

Internal JavaScript Error

Well, this is embarrassing. It is recommended that you restart TiddlyWiki by refreshing your browser

Uncaught TypeError: options.wiki.getTiddlerDataCached is not a function

The error is a bit worrying; that function getTiddlerDataCached() was introduced in 5.1.10. The fact that it can’t be found makes me worry that you’ve got some core modules overridden with pre-5.1.10 versions. Is that possible?

Best wishes

Jeremy.

Best wishes,

— tb

[Tobias Beer]

Hi Jeremy,

Does the same wiki work under TiddlyWiki 5.1.9?

Yes, I use it to build and then push tb5 since maybe 2 weeks.

The error is a bit worrying; that function getTiddlerDataCached() was introduced in 5.1.10. The fact that it can’t be found makes me worry that you’ve got some core modules overridden with pre-5.1.10 versions. Is that possible?

I just went through the list and noticed I was actually overwriting wiki.js, ouch. It was tagged "cleanup 5.1.8"... but recovering from abstinence over two releases I never did clean it up. Sorry about that.

Thanks a lot, it works now with the pre-release version... and who knows what I was actually missing form the final version of 5.1.8 or 5.1.9.

~

One question now would be, how to get back to building with the current stable release?

Best wishes,

— tb