V5.3.2: story river fails to scroll to open linked tiddler ... why? (conflict w plugins that uglify)

#61

Could you explain what you mean here?

A key value with tiddlywiki is you can use its own code to explore how it works, to make modifications and even find out how to do your own thing based on the existing core.

It would seem to me that source mapping as I imagine it to be would benefit from readable code.

On an external core

In a very simple way to understand an externalised core is consider the plugins in a wiki, it always comes with the “$:/core” plugin. Now imagine this in a separate file that gets loaded when you open your wiki. Only your customisations are stored in your wiki, making it quicker to load and save every time.

  • Your wiki will not load if it cant find the external core.
  • Multiple wikis can use the same external core.
    • Download once use many times.
#62

I’m starting to see documentation on external cores. Didn’t know Tiddlywiki could do that. I’ll look into it. I guess tiddlyhost uses that too?

sourcemapping is when a server provides uglified javascript for browsers to run, but if the end-user should open up their debugger, their browser will ask the server both the original source and a “map”, which is a JSON file following specific ECMA notation or whatever that indicates what parts of the uglified code correspond to the original source. It lets people use ugly code while still being able to debug with the original at the same time.

It’s not perfect, Uglfifying can rearrange stuff, so stepping through even with a source map can be a little strange sometimes, but it’s viable, and you get all the original variable names and such.

If you run TW-Uglify on NodeJS, then it provides sourcemapping automatically. You can check it out. It would make sense if TW-Uglify can do the same with these external cores, and I’d be happy to look into it sometimes soon if y’all think you’d make use of it. Though I would like to know if there’d be interest. It sounds like this recent mishap with Uglify and 5.3.2 has turned this group off of using Uglify, which I’d understand.

(Sorry about that, everyone!)

1 Like
#63

Thanks for the explanation, I would however expect you don’t even need source mapping if you don’t uglify, but surely any tools could use a pretty source as well?

#64

I would however expect you don’t even need source mapping if you don’t uglify

That is true, and I understand if you guys drop it. Though I am sad that Uglify disappointed you all enough to not bother with it anymore.

#65

External-core wiki is an option, not on by default, but available as part of the interface for generating a new wiki at tiddlyhost.

#66

On the contrary! I think it’s very useful! My suggestion is simply that for the external core used at tiddlyhost, the benefit of shrinking the code is minimal (because it’s download-once, read-many). I think there are instances where uglify can really cut down on both server and download burdens.

The suggestion that it be not on (especially for the external core) by default was simply an upshot of frustration over how long it took to troubleshoot the issue in this thread. Perhaps something like sourcemapping actually can avoid that frustration. I don’t know enough to understand whether — when you say it’s “not perfect” — it’s good enough to conveniently enable people to read what they need to from the source.

1 Like
#67

Not at all, it is critical to have such options, its particularly good to help those with older computers and not very good internet. Apparently in India and other places a lot of USB drives are exchanged packed with software and media people have difficulty accessing. Similarly its great to add to Rasbery Pi’s and other small computers and devices.

  • Just because I have broadband and a 32GB multi-core processor on SSD does not mean others do.

See the discussion about Editions, it would be great to add a minified core editions of empty.html to the set.

1 Like
#68

For those of you who are interested. Just dropping a message here to let you all know that Uglify can now sourcemap with external-js setups, and even tiddlywiki files. It generates a directory of sourcemaps and original sources beside your files.

I’m not super familiar with TiddlyHost, but if you guys were interested, Uglify and its sourcemapping should be able to work with it now. Up to you all. I just released a new topic discussing the most recent Uglify improvements.

1 Like