TiddlyWiki5 icon indicating copy to clipboard operation
TiddlyWiki5 copied to clipboard

Innerwiki Plugin issues and features

Open AnthonyMuscio opened this issue 6 years ago • 3 comments

Jeremy et all,

I have mentioned previously in the discussion announcing innerwiki I see some key advantages to using it for more than composing screenshots, although that is a bonus.

I have being trying to do two things I can't manage

  • Create an Innerwiki with all tiddlers (or all except)
  • Take a tiddler which contains an innerwiki and open it in a new window and see the innerwiki in it.

For some reason when I scroll down in the innerwiki I see a lot of unrendered code

I have a range of reasons for the above to be so. These include

  • taking snaphots with an interactive desktop application
  • Interacting with the innerwiki to save custom sub TiddlyWikis (Make a wiki factory) or export "run time" wiki versions.
  • some experimental tiddlywiki self referral tricks
  • A lot more in my dreams

See https://tiddlywiki.com/prerelease/plugins/tiddlywiki/innerwiki/ With the following in a tiddler

;Problem with content below inside inner wiki
<$innerwiki width="1200" height="400" style="width:100%;" filename="screenshot-1.png">
	<$data $filter="[all[]]"/>
</$innerwiki>

;Also open in new Window and see how the innerwiki iframe will not be presented.

AnthonyMuscio avatar Jun 22 '19 04:06 AnthonyMuscio

Jeremy et al,

With 5.1.20 now here I have begin to play with the Innerwiki plugin for which I see a great potential.

Here is an example of my data tiddlers showing how to manufacture tiddlers not actually in the parent wiki

<$innerwiki>
 <$data title="$:/SiteTitle" text="Innerwiki title"/>
 <$data title="$:/config/SaveWikiButton/Filename" text="mywiki.tw"/>
 <$data title="Home" text="Here we are in Home"/>
 <$data title=More <<include-tiddler "$:/payload/More">> />
 <$data title="$:/DefaultTiddlers" text="Home More"/>
</$innerwiki>

However you can see the More tiddler I am trying to provide all the fields from a tiddler called $:/payload/More to include it. This is my include tiddler macro (Which works but not in the data tiddler)

\define include-tiddler(tiddlername)
<$list filter="[[$tiddlername$]fields[]] -[[title]]" variable=fieldname>
 <$text text=<<fieldname>>/>=<$text text={{{ [[$tiddlername$]get<fieldname>addprefix["""]addsuffix["""]] }}}/>
</$list>
\end

I am wondering if we could have a way to use the data tiddler that sources tiddlers with a named prefix eg $:/wikiname/ such that we could then present all $:/wikiname/tiddlernames as tiddlername in the innerwiki, along with the other fields. We could then have a filter to batch all the tiddlers that are used to create the innerwiki. We could even import them while adding prefix then store more than one wilkis worth of tiddlers in the parent.

What do you think?

Regards Tony

AnthonyMuscio avatar Aug 27 '19 09:08 AnthonyMuscio

Hi @AnthonyMuscio I can see three issues here:

  • Innerwiki currently only works in the primary window, and not in new windows
  • Making it possible to directly open the innerwiki as a new window instead of an iframe (the code is much the same in both cases)
  • Making it possible for the <$data> widget when used with the $filter attribute to also specify a prefix or suffix to be added or removed to tiddler titles

Does that miss anything?

Jermolene avatar Aug 27 '19 15:08 Jermolene

Jeremy that sounds good. I had not being thinking of the first two items but yes.

On the data tiddler filter it would be good if payload tiddlers could be stored under a prefix in the parent wiki which is removed as it is presented in the child wiki.

Perhaps later we could get the payload from tiddlers in a json tiddler.

Thanks Tony

AnthonyMuscio avatar Aug 28 '19 22:08 AnthonyMuscio