Ok, gave it a quick test and also updated my CKEditor while I was at it,
and it seems a lot more stable and usable now, CKEditor now correctly
resizes and errors seem less frequent.
Some script errors here and there but they are most likely caused by
CKeditor plugins not Tiddlywiki itself (I've
On Friday, March 25, 2016 at 4:10:03 PM UTC-7, Mark S. wrote:
>
> Hi Eric,
>
> That seems to be the final tweak. I put the triple quotes in (not BJ)
> before I realized that the name/argument were mismatched. I fixed the
> mismatch, but should have removed the quotes.
>
> I'm still very confused
This is really kind of klugey (sp?) but it gets you (or at least me) about
90% of the way towards turning HTML from web pages into TW5 mark-up. It
attempts to convert most common markups including links, images and tables.
Someone who understood TW5 better would probably build a DOM tree
Hi Eric,
That seems to be the final tweak. I put the triple quotes in (not BJ)
before I realized that the name/argument were mismatched. I fixed the
mismatch, but should have removed the quotes.
I'm still very confused about all this. If all that a macro does is
substitution, how does it
Hi BJ,
While defining new rules for TiddlyClip, and I have bumped into a
characteristic of TiddlyClip's #variables: the scope of a #variable is
limited to the operations run inside the tiddler referenced in the 'Fields
modifiers' column.
Would it be possible to extend the scope of #variables
On Friday, March 25, 2016 at 2:53:48 PM UTC-7, Mark S. wrote:
>
> <$macrocall $name="amacro" x="""{{$:/html2tw/title}}"""/>
>
> Maybe some other tweak?
>
should be:
<$macrocall $name="amacro" x={{$:/html2tw/title}}/>
e.g., remove the tripled-quotes so that the parameter retrieves the value
Could be more problems but one is it should probably read:
<$set name="name_of_tiddler" value="$x$">
i.e with quotes around $x$. Maybe even """$x$""".
<:-)
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop
Thanks BJ. I had great hopes for this approach. But in this case,
<> is empty and doesn't even show up when dropped in ... as
shown below.
I had to tweak your suggested code to match up parameter and argument
names. I put the label THIS IS EMPTY to show where there's no contents at
all being
Hi mark,
this is a typical tw5 2'gotcha'
<$set name="text2convert" value=<> >
the macro only does basic text substitution.
You need to use this pattern
<$set name="text2convert" value={{$x$}} >
and so must put your code inside a macro
\define amacro(x)
<$set name="name_of_tiddler"
Hi Chris,
I have followed your instructions as far as I understood them, but I
unfortunately know too little about tiddlyweb to make sense of everything.
Here is what I have done:
1. created a test instance in tiddlyweb with `twinstance test`
2. Added the tiddlywebplugins.status and
Hi Jed,
I've tried this in all sorts of iterations. I was hoping that wrapping a
macro in a macro could finally force it to acknowledge the actual text in
the dereferenced name tiddler.
Your variation put this into the "converted" tiddler:
*{{TitleIUsedInTheForm}}*
So the literal string with
It is probably the <$set name="text2convert" value=<> > line
that does it.
Why don't you just use one macro instead of creating a macro that just
calls a second macro? Make textin:
\define textin() {{$(name_of_tiddler)$}}
and use that as the value for text2convert instead of textin2
--
Hey that's great news BJ, gonna give it a try as soon as I get a chance.
Thanks for the update
On Friday, 25 March 2016 10:32:41 UTC, BJ wrote:
>
>
>
> On Friday, March 25, 2016 at 4:33:22 AM UTC, Duarte Farrajota Ramos wrote:
>>
>> The way I see it you could try two different methods
>>
>>
>>
I wrote a javascript macro for converting html into TW5 markup. It works
fine when I run it on a tiddler with a known name. But when I tried to
launch it it from a form, it never gets the text -- even though the macro
itself sitting on it's own line will run perfectly.
In the form, I collect
On Friday, March 25, 2016 at 4:33:22 AM UTC, Duarte Farrajota Ramos wrote:
>
> The way I see it you could try two different methods
>
>
>1. If you really want to edit them directly inside TiddlyWiki in a
>WYSIWYG manner you could try using the fantastic CKEditor plugin for
>
In addition to the tabs you can create scrolling for each tab/tiddler by
changing the style. create a tiddler (you could call it $:/scroll), tag it
$:/tags/Stylesheet and add this as contents:
.tc-tiddler-body {
height: 70vh;
overflow: scroll;
}
I think this is what you want
all the
Hi, Tryign —
You may like substories, which allow you to open and close tiddlers
"inside" a current tiddler. They're great for opening content you need to
read before getting back to reading the main tiddler content.
http://tiddlywiki.com/#Creating%20SubStories
--
You received this message
@Tryign - could you post a simple drawing of your vision? I'm not even sure
what you mean with a "pane" so it would hopefully clarify a lot.
<:-)
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving
I sometimes "pin" a tiddler to the top left menu or put it above the story
using system tags
Alex
On Friday, 25 March 2016, Tryign It wrote:
>
> Thank you both for the suggestions,
> As for the Zoomin option, that is slightly less annoying than the scroll -
>
19 matches
Mail list logo