Ciao Stef
ste...@gmail.com wrote:
> Try replacing both occurrences of "!!tiddlertitle" with
> "tweetButton!!tiddlertitle". Does this work?
>
Many thanks! Its working. Much appreciated.
Best wishes
Josiah
--
You received this message because you are subscribed to the Google Groups
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
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
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
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'
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.
I'm trying to understand your data flow. What are the contents of the
target field, and how do they differ from the title? If you put the title
into target, then your scenarios (e.g. <$link
to={{tiddlerToShow}}>{{tiddlerToShow}} and <$transclude
tiddler={{tiddlerToShow}}/>) work fine (goes to
Correction, if you link like this:
<$link to={{tiddlerToShow}}><$view tiddler=tiddlerToShow
field=text/>
it will both link and view correctly. However, even if you did it as <$link
to={{tiddlerToShow}}>{{tiddlerToShow}} it would link correctly --
it would look slightly different, but given
A while back, I put together a tiddlywiki for a Forth language I'm writing
as part of a retrocomputing project.
http://chitselb.com/files/tiddlypettil.html . This file is automatically
generated each time I build the source, and most of the tiddlers are the
Forth dictionary, with the
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
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
On Saturday, August 12, 2017 at 9:35:19 AM UTC-7, Steven Schneider wrote:
>
> I am using the widget to allow users to make a selection.
> The select field is are choosing among tiddlers listed in the list field
> of my
> <$select tiddler="tiddlerToShow" default='Cover'>
> <$list
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
Inspired by the really high quality discussions/help lately, I wanted to
take the opportunity for a little challenge:
*What's the best way to construct a table consisting of tiddlers?*
*You should also be be able to "target" an arbitrary tiddler therein, i.e
so you can access its fields data.*
I am using the widget to allow users to make a selection.
The select field is are choosing among tiddlers listed in the list field
of my
<$select tiddler="tiddlerToShow" default='Cover'>
<$list filter='[list]'>
<$vars target={{!!target}}>
>><$view field='caption'/>
The values of
On Saturday, August 12, 2017 at 3:34:24 PM UTC-7, Steven Schneider wrote:
>
> I get how the <$text text={{tiddlerToShow}}/> works -- so I can see the
> content with the //
>
> But, how do I use my new tiddler [[tiddlerToShow]]? I need to be able to
> do <$link
Eric, thanks. Your suggestions are, as usual, right on. So I see that my
select is creating a [[tiddlerToShow]] with the text field set to the name
of a tiddler with "//" in its name.
I get how the <$text text={{tiddlerToShow}}/> works -- so I can see the
content with the //
But, how do I
17 matches
Mail list logo
