[tw] Re: Blog capabilities of TiddlyWiki

Cari tutti, A bit out-of-left-field, but somehow relevant, is Riz's experiments from a few months back. https://ibnishak.github.io/t-blog/ the discussion of it is here . They are worth a look. They are Node.js generate

[tw] Re: Blog capabilities of TiddlyWiki

Sounds Like a Good Strategy Richard. Do share if you can. Tony On Saturday, August 12, 2017 at 9:13:57 PM UTC+10, RichardWilliamSmith wrote: > > Hi Tony, > > I built an interface that lets you externalise content. The use case > primarily imagined is of accruing content over time (mostly ima

Re: [tw] Re: Blog capabilities of TiddlyWiki

Eric, Yes Understood. Nicely put. But I sill see the following workflow possible, - Create Images folder below Tiddly wiki - Drag and Drop images to tiddly wiki - Check Import as external files/Or Reference - Enter the relative or absolute path (do the Job the browser will not) -

Re: [tw] Re: Blog capabilities of TiddlyWiki

But ... as I asked earlier. Is this true if dragging and dropping from an external web site? I suspect not, since knowing the url to a web site is what browsers do all the time. So, it should be possible to drag and drop and then construct a tiddler based on the file type and file name. AND, if

Re: [tw] Re: Blog capabilities of TiddlyWiki

On Sunday, August 13, 2017 at 6:31:13 PM UTC-7, TonyM wrote: > > Another thought is the import feature, permitting import of external links > to selected files, and allow a multi-select, I would have thought the > browser has to know the full path to do this import?, but I expect I may be > wron

Re: [tw] Re: Blog capabilities of TiddlyWiki

Jeremy That explains the mysterious omission of such a feature. A key use case for me is when I have a folder of images and PDF's I want to display in a tiddlywiki yet I want to avoid loading the tiddly wiki up and making it too big. If I could choose a specific library ..\images Place my files

Re: [tw] Re: Blog capabilities of TiddlyWiki

What I do is have a variation of Tobias ximg macros. I have a drop-down list that let's me set the base path of all the macros depending on platform. In addition, if a tiddler is tagged with D:2017, then the sub-path of the path name will be /2017. This will allow me eventually to archive or h

Re: [tw] Re: Blog capabilities of TiddlyWiki

OBSERVATION 1 -- *Easier translation/conversion to portability*--of absolute paths to relative--could be a godsend for TW. For at least 2 reasons. First, universalism of platform (offline / online). Second, emerging issue if you want to go httpS: ... relative paths don't throw an issue on that

Re: [tw] Re: Blog capabilities of TiddlyWiki

But what if the dropped link was from an external web source? Does the browser still hide the address? Shouldn't it be able to access that url? And if the base url was the same for your TW and the dropped object, wouldn't it be possible to construct the relative path ? I'm thinking that in the

[tw] Re: Blog capabilities of TiddlyWiki

Hi Herb, Oddly, this is exactly the aspect to which I now turn my attention. There are two methods to be compared - the first is to build the static site and deploy the output. The second is to deploy the raw content and then run the build tool "in the cloud" using a 'continuous integration' me

[tw] Re: Blog capabilities of TiddlyWiki

Hi Tony, I built an interface that lets you externalise content. The use case primarily imagined is of accruing content over time (mostly images) and then periodically purging it to an external location. The tool then lets you redefine the 'root' path to the image folder, in the canonical uri

Re: [tw] Re: Blog capabilities of TiddlyWiki

Hi Tony > Drag and Drop but only create external links? Allowing a relative link such > as .\images would allow the tiddlywiki to be moved with its media to a host. That trouble is that browsers do not reveal to JS code the original path of the dragged file. We only get the file name portion. B

[tw] Re: Blog capabilities of TiddlyWiki

On Saturday, 12 August 2017 03:13:45 UTC+3, TonyM wrote: > > Have you heard of a mechanism to Drag and Drop but only create external > links? Allowing a relative link such as .\images would allow the tiddlywiki > to be moved with its media to a host. > That is what I was hoping for. Any impleme

[tw] Re: Blog capabilities of TiddlyWiki

On Saturday, 12 August 2017 01:48:54 UTC+3, RichardWilliamSmith wrote: > > Tiddlywiki can be used to generate a static website where each page is in > its own file. > Excellent. One questions: can the files be generated directly on the remote server (by a remotely located Tiddly generator)? Or w

[tw] Re: Blog capabilities of TiddlyWiki

Additional thought, On the Import page that appears after drag and drop allow a button to import external links only. Create tiddlers with the external links. Just dreaming Tony On Saturday, August 12, 2017 at 10:13:45 AM UTC+10, TonyM wrote: > > Richard, > > TiddlyWiki seems quite capable of

[tw] Re: Blog capabilities of TiddlyWiki

Richard, TiddlyWiki seems quite capable of displaying external media but it seems to me a second class citizen compared to drag drop and import. Have you heard of a mechanism to Drag and Drop but only create external links? Allowing a relative link such as .\images would allow the tiddlywiki t

[tw] Re: Blog capabilities of TiddlyWiki

I should add that the issue of 'externalising' images to reduce the page size is a separate, but related issue, and there are pretty good solutions for managing that too. On Saturday, August 12, 2017 at 8:48:54 AM UTC+10, RichardWilliamSmith wrote: > > Hi Herb, > > Tiddlywiki can be used to gen

[tw] Re: Blog capabilities of TiddlyWiki

Hi Herb, Tiddlywiki can be used to generate a static website where each page is in its own file. This is advantageous for the reasons you state and several others. There are basic instructions available http://tiddlywiki.com/static/Generating%2520Static%2520Sites%2520with%2520TiddlyWiki.html

[tw] Re: Blog capabilities of TiddlyWiki

As an addition to my previous post: when I said "the creation of multiple files" what I had in mind was the possibility of breaking down the TiddlyWiki file into several inter-related sub-files, each one for a major section of the blog (in case the blog has a very articulated and complex struct