Re: [twdev] Help from Web Developer - iframe interaction

2019-02-15 Thread TonyM 
Jeremy,

I have identified some scenarios for embedded iframes, even  the innerwiki 
plugin, I will share, as suggested by you.

Please forgive me for my rampant imagination, these ideas come from real 
life challenges.

Given, a Parent wiki, even a single file wiki can spawn an innerwiki with a 
subset of tiddlers

   1. In the parent/outer wiki Accept some settings, Generate a seperate 
   wiki based on the settings, in which a user can enter their input and save 
   it to disk. Basically the parent wiki can be a TiddlyWiki factory. It can 
   generate multiple editions from the one edition and with access to the 
   resources / data of the parent, at least at creation time
  1. Spawn an inner wiki which is a standalone wiki containing the 
  results of a process designed in the parent wiki - in effect generating 
  report wikis perhaps for distribution into an intranet.
 1. The report wiki can be a light wiki, only with the results, not 
 the tools to generate the results and could allow for a chinese wall 
with 
 multi-client outputs.
 2. It could even include active plugins disabled in the parent 
 wiki.
  2. Generate a TiddlyWiki as a Document/Website (full or template) in 
  an innerwiki, giving it a unique filename, serial number and other 
features 
  (metadata Stored in the parent wiki as well) then save/export the 
document. 
  The parent wiki can hold a set of templates for the required tiddlywiki 
  documents, and the document can store reference to its parent. Thus every 
  wiki built is automatically known about by the parent "generating" wiki.
  3. Generate "forms" in smart wikis, and allow the answers (in Serial 
  number uniquified tiddlers) to be emailed in response (Ie the parent need 
  not be writable), and imported by the owner of the parent.
   2. Spawn an innerwiki identical to the outer wiki (all tiddlers), 
   install a plugin to the innerwiki and test it sandboxed, from the parent. 
   Optionally migrate changes back to the wiki or save it out and replace the 
   parent.
   3. Publish a parent wiki, that spawns innerwikis with generated tiddler 
   sets, or test data. Users can then replicate there "problems" and 
   "Challenges" in a defined wiki or data set, that that all users can also 
   generate. So if I am having trouble with a special toc, I can test it 
   inside a common wiki and share my broken tiddler and the named data set 
   others can replicate.

Questions arising

   1. Could we save and reopen an innerwiki injecting new content the 
   second time, or harvesting changes within the innerwiki when it was away 
   with another user?
   2. Could we allow innerwikis to be saved into the server hosting the 
   parent wiki?, node, AWS or php for example. 
  1. As a hosted Tiddlywiki solution
  2. The creator could then own the generated wiki but not the parent.
  3. Could we generate an innerwiki with access to an authentication 
   process, that allows the current browser session to be authenticated, then 
   exit that innerwiki and continue within the now authenticated parent?

With a view to continued innovation!

Regards
Tony

On Tuesday, 12 February 2019 19:04:41 UTC+11, Jeremy Ruston wrote:
>
> Hi Tony
>
> It's good to broaden the understanding of the benefits and pitfalls of 
> iframes. One takeaway from this thread is that using iframes is a well 
> understood technique in the developer community, and TW already uses them 
> in several roles (plugin library, viewing HTML tiddlers, innerwiki, 
> Twederation).
>
> We can continue to discuss exposing iframe functionality as primitives 
> that wikitext authors can experiment with, but we'll need some clear 
> scenarios first.
>
> Best wishes
>
> Jeremy
>
>
>
>
>
> --
> Jeremy Ruston
> jer...@jermolene.com 
> https://jermolene.com
>
> On 11 Feb 2019, at 22:59, TonyM > 
> wrote:
>
> Jeremy,
>
> Thanks for your response.
>
>
> The "send to" may be the minimum needed as when constructing a HTML page 
>> we can easily add the javascript, but if it were available as both send and 
>> receive within TiddlyWiki users may also be able to use this possibility? 
>> It would be understandable that it were a plugin if the support is not 
>> already built in due to the plugin library.
>>
>>
>> I don't quite follow the question. The communication used by the plugin 
>> library is bidirectional, if that's what you mean.
>>
>
> As I understand this, the bidirectional aspect is from and to outer and an 
> inner wikis. 
> It would be helpful if we can "access"  in a widget, the  communication 
> used by the plugin library so a super user rather than only developer can 
> access this.
> If the content of iframe is non tiddlywiki such as a html/javascript page 
> we need the matching code to embed in it to also enable the communication.
>  
>
>> Is the Data widget in innerwiki effectively like this?
>>
>> No, the way it works is that

Re: [twdev] General usefulness of the parser rule: syslink ?

2019-02-15 Thread TonyM 
S S ,

Ah, Sorry I did not see them. I just looked and clearly they are a result 
of documenting such "functional system tiddlers" in Tiddlywiki.com, even 
when they are not in use. If you look at empty.html you will see there are 
no "missing tiddlers". It is trivial when writing documentation to use the 
tilde ~ in front to stop them turning into links, but I question why one 
would, since clicking creates the tiddler and you could place notes in it 
for future reference.

I understand your concern they may be disconcerting to some new users who 
have not come to understand the value of automatically providing missing 
links, since in our own wikis this can lead us to learn of incomplete 
information. In some ways it is an inevitable product of the content in 
TiddlyWiki.com, but it it I take a copy of tiddlywiki.com offline for my 
own notes it is true any new missing links will be hard to identify in the 
large number already there. 

Rather than stop the *syslink* parsing could I suggest the best approach 
would be to create the missing tiddlers either empty (they will stop being 
missing) and/or with descriptive content, or even listing all the 
references to that tiddler as part of the documentation process, users on 
tiddlywiki.com could then find where that formally missing tiddler is 
discussed. The truth is many of these missing tiddlers, system or otherwise 
do in fact often point to shortfalls in the internal documentation and need 
attention anyway, so creating these should be part of the documentation 
effort. Where the link is clearly not required it should be edited to stop 
camel case or add the tilde, however this is unlikely to be valid with most 
system tiddlers named.

Another approach may be to provide the ability to list "missing tiddlers" 
that are exceptions and filter them out of the list of missing tiddlers. If 
a tiddler is missing and not in the list it will still appear.

Regards
Tony



On Saturday, 16 February 2019 00:18:51 UTC+11, S. S. wrote:
>
> Tony,
>
> My post a couple of days ago 
>  
> lists many tiddlers having missing tiddlers caused by auto syslinks. For 
> missing tiddlers linked to by CamelCase, the full list can be seen in the 
> side-bar, More, Missing.
>
> Altogether there are a lot of them.
>
> Regards. 
>
> On Friday, February 15, 2019 at 1:31:16 PM UTC+7, TonyM wrote:
>>
>> S S ,
>>
>> Can you share some of the cases where "* visitors to tiddlywiki.com 
>>  *[DO]* encounter meaningless links to 
>> non-existent tiddlers"*
>>
>> I am curious where these are being encountered and why.
>>
>> Regards
>> tony
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/cd710113-a090-423f-b3d6-9d1e95d959fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] Creating new tiddler types

2019-02-15 Thread stefano franchi 
How does the addition of new tiddler types work?

>From reading the railroad plugin code and the tw-dev pages on Parser and
Widget, I gather that it is as simple as creating a new parser module and
assigning the newly defined type to a specific widget.

Railroad does it in its  super-simple typed-parser.js module:
```
(function(){

/*jslint node: true, browser: true */
/*global $tw: false */
"use strict";

var RailroadParser = function(type,text,options) {
var element = {
type: "railroad",
tag: "$railroad",
text: text
};
this.tree = [element];
console.log(text);
};

exports["text/vnd.tiddlywiki.railroad"] = RailroadParser;

})();
...

The intent is clear, and the code could not be simpler. It maps the new
tiddler type text/vnd.tiddlywiki.railroad to the railroad plugin. But it
feels like a bit of magic. Where is that mapping actually established?  I
have not been able to find how it  actually implemented  in the core, and I
would like to get a better grasp of the overall mechanism. Where should I
look?

Cheers,

S.
-- 
__
Stefano Franchi

stefano.fran...@gmail.com 
http://stefano.cleinias.org

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CAJODLwZodcay8hnXKBDK%2BJK%3DDs_X2NNfx9ZAXZeqdDDBiXvXBw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: How to change font size in editor or Font Scroller (tiddler) - $:/jd/Buttons/font-size

2019-02-15 Thread Stefan Pfister 
Hi Ton,

thank you very much. It works. 

Regards,
Stefan

Am Freitag, 15. Februar 2019 15:35:40 UTC+1 schrieb Ton Gerner:
>
>
> Hi Stefan,
>
> Try something like below in a tiddler tagged with $:/tags/Stylesheet
>
> textarea.tc-edit-texteditor {
>  font-size: 1.5em;
> }
>
> Cheers,
>
> Ton
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/68613633-5f41-4c54-8ee1-570f9653badb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: How to change font size in editor or Font Scroller (tiddler) - $:/jd/Buttons/font-size

2019-02-15 Thread Ton Gerner 

Hi Stefan,

Try something like below in a tiddler tagged with $:/tags/Stylesheet

textarea.tc-edit-texteditor {
 font-size: 1.5em;
}

Cheers,

Ton

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/13a30acf-6439-4e12-89c3-ffc57c37c441%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] General usefulness of the parser rule: syslink ?

2019-02-15 Thread S. S. 
Tony,

My post a couple of days ago 
 
lists many tiddlers having missing tiddlers caused by auto syslinks. For 
missing tiddlers linked to by CamelCase, the full list can be seen in the 
side-bar, More, Missing.

Altogether there are a lot of them.

Regards. 

On Friday, February 15, 2019 at 1:31:16 PM UTC+7, TonyM wrote:
>
> S S ,
>
> Can you share some of the cases where "* visitors to tiddlywiki.com 
>  *[DO]* encounter meaningless links to 
> non-existent tiddlers"*
>
> I am curious where these are being encountered and why.
>
> Regards
> tony
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/fa0b1ab1-ffbd-4573-9af1-1711ea9ea3bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] How to change font size in editor or Font Scroller (tiddler) - $:/jd/Buttons/font-size

2019-02-15 Thread Stefan Pfister 
Hi there,

how can I change the font size in the editor. I'm using tiddlydesktop and 
there is no way two scale the text like in chrome with a shortkey. I tested 
the plugin font scroller, but only the rendered text in tiddlers changes 
its size. 

I need a bigger font in the editor. Its way too small. Can the font 
scroller be adjusted? Or is there another programmable solution?

Thanks,

Stefan

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/699c1743-9bbf-428c-85ee-4ab7d56d2b7a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.