@Tobias, I really appreciate the input.

> What control do we have over a TW *via the browsers URL field?*
>>
>
> Whatever url "paramifiers" are supported,
>

I got a chuckle as I googled  
<https://www.google.se/search?q=paramifier&oq=paramifier&aqs=chrome.0.69i59j69i60.1825j0j7&sourceid=chrome&es_sm=93&ie=UTF-8#q=paramifiers>the
 
term "paramifiers" - sounds like something established but to my surprise 
it's TW lingo.

...and, it seems a certain Mr. Beer was involved on the matter concerning 
TiddlySpace; Startup Parameters <http://tiddlywiki.org/Startup%20Parameters>
.

(BTW, some quick tests to apply it to TW5 failed, unsurprisingly)
 

the full documentation of which appears missing.
> This should be (y)our primary concern for now.
>

Yes. But does anyone other than @Jeremy have the knowledge?

The little I do find is the tiddlre on PermaLinks 
<http://tiddlywiki.com/#PermaLinks>. It briefly mentions the filter-via-url 
possibility and under last paragraph ("Techical Details") basically details 
how to set a target tiddler in the river.

 
 

>
>    1. is encoded in the url hash
>       - unpacked by tiddlywiki
>       - rendered using an appropriate component that knows how to handle 
>       it
>    
> Is it really necessary that TW knows what to do with it? I mean, given the 
examples I provided that created instantaneous divs etc - could the URL 
perhaps "force" the display, by concatenating(?) the URL stuff and the TW 
stuff. Perhaps inject is a better term. As you note in the "instant code 
editor" example it contains js and I'm thinking it could perhaps create a 
div and insert it 
<http://stackoverflow.com/questions/14004117/create-div-and-append-div-dynamically>
 
at some specified position in the document?


> All this sounds reaaaally man-hour-intensive in terms of development.
> So, the question would be: What's are the benefits of all this?
>


Actually, I think it is one of those concepts that would be so useful that 
I can't even say what it would open up for (including risks). But I'll 
mention some ideas off the top of my head (an in a very arbitrary order);

*You could show an iframe where the src is this special URL so that what is 
displayed is a, by you, formatted list of the plugins in the target TW (for 
the 2-step import I discovered the other day).
*...or, bigger, "community aggregator" that consists totally of iframes 
like a trello display, each frame displaying a list of tiddlers from all 
included TWs, but where you set tags to filter their lists by.  
*...or even much bigger a concept; what if the URL can really merge 
multiple wikis from different sources by scrubbing so only the body content 
from multiple wikis are displayed in main document. I understnad the URL is 
limited in length, preventing too many such added wikis, but it sounds a 
bit like federation.
*More humbly; inject a custom stylesheet to get your personal settings 
("Big font for my poor eyes, beautiful polka stripes and blinking fonts 
everywhere")
*etc, ad infinitum... my imagination (and knowledge) is too limited.

<:-)

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d8e04a77-6715-44e1-b513-58c8b7939545%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to