Re: [tw] Re: [TW5] An incremental load command for tiddler backups

[Mal]

As suggested by Jeremy, I've created a plugin for my "loadnew" command and 
published it on tiddlyspot. 

I hope this is of some use and am happy to receive any comments, 
suggestions or questions.

Regards,

Mal

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/d323da04-c132-4aa9-8fed-094a7c0e056a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5] Using jQuery to fetch JSON (tiddlers) directly from Google Sheets?

[Alex Hough]

hi Steve,

Writing for IFTT could open up the possibility of writing tiddlers from
email alerts from google scholar.?

Alex

On Saturday, 30 April 2016, DesignWriteX SteveSchneider <
designwri...@gmail.com> wrote:

> Hey folks, this all looks very intriguing, and I hope to work with it in
> the next week or two. What it makes possible is, among other things,
> allowing individuals to write tiddlers from google forms, and allowing all
> many ifttt.com channels to write tiddlers by appending rows to google
> spreadsheets (thus allowing one to "tweet into their tiddlywiki") among
> other things. Thanks for this work; I look forward to exploring it, and
> will post some examples here once I've built them... //steve.
>
> On Tue, Apr 26, 2016 at 3:29 AM, Jeremy Ruston  > wrote:
>
>> Hi Sini-Kit
>>
>> Hi! Test button don't work. I try in IE and Chrome. google sheets API use
>> keys. So all the examples on .NET and Java (server need). But  we can add
>> information to table without keys using google forms and connecting them to
>> google sheets, but we cant delete or modify old, and BUT we can add new
>> version of tiddler to google sheets without deleting old, and render in TW5
>> only last variant of tiddler. Our table will be great, it will be nice to
>> have way to delete old variants…
>>
>>
>> Just to add that I think this approach of using Google Sheets for tiddler
>> storage is a terrific idea, and would love to see this happen.
>>
>> Best wishes
>>
>> Jeremy
>>
>>
>
>
> --
> DesignWriteX is the administrative account for {{DesignWrite}}, the
> Designing and Writing Interactive Texts learning community.
>
> http://bit.do/designwrite
> Coordinator: Steve Schneider, st...@sunyit.edu
> 
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com
> 
> .
> To post to this group, send email to tiddlywiki@googlegroups.com
> .
> 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/CALqRa%2BJkhxxoMRYqFUEfYgN6AW2Obgtm6RuxPauWeQE8Oqk2Zw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/CALc1hYd%2B5pkn4n%3D1ZUqdo3Z5pRTkQ1XMHv40K5L%2Bk%3DWExMY6Gw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Announcing TiddlyDesktop v0.0.7

[Dave]

Hi Jeremy, 

I tried making a new wiki folder, but in the folder is only one html file 
instead of the separate files per tiddler I was expecting.  Is there some 
setup change I need to do to get that behaviour?

- Dave

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/a2c77bf1-42ff-4651-bef4-6b4d57029bac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] Nesting of Items in Ordered Lists

[Scott Simmons (Secret-HQ)]

On Saturday, April 30, 2016 at 5:21:01 PM UTC-4, Jeremy Ruston wrote:

> Any reason that styling was deliberately left out of TW5? 
>
> It’s more that it’s the default HTML/CSS styling; TW5 doesn’t generally 
> change defaults unless it’s functionally necessary.
>

Thanks!

I wasn't sure if it was a deliberate choice to make TW more transparent 
(and HTML-"bilingual") or just something that got left behind by mistake. 
 I could've seen it going either way — !  ;)

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/29974528-ccd1-41e1-86e4-e1486ec0e262%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5] Final tests for 5.1.12 before release

[Mat]

Apropos the Markdown toolbar, I just stumbled over this that may serve as 
inspiration to use it;

http://mediatemple.net/blog/tips/you-should-probably-blog-in-markdown/

<:-)

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/e7842348-0853-498f-8636-2505c942bd06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] Nesting of Items in Ordered Lists

[Jeremy Ruston]

Hi Scott

> Any reason that styling was deliberately left out of TW5?

It’s more that it’s the default HTML/CSS styling; TW5 doesn’t generally change 
defaults unless it’s functionally necessary.

Best wishes

Jeremy

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/0F5001C9-FB5C-4CC7-8732-12921CB2BE6E%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5] Final tests for 5.1.12 before release

[progetti]

>
> Warning: avoid using any of the characters | [ ] { } " ' in tiddler titles
>

'Single' and "double" quotes are not sanctioned? ... COME on ... that's 
NORMAL language use. Don't mess with it.

J.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/3712abec-061d-43f6-9c29-f321790839e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Nesting of Items in Ordered Lists

[Scott Simmons (Secret-HQ)]

Well, that's gloriously simple.  Thanks, Eric!

Any reason that styling was deliberately left out of TW5?

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/9cb0658a-eab1-4993-8e2f-063fc5333225%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [tw5] Final tests for 5.1.12 before release

[progetti]

cmari I concur on point (2) 






cmari I concur on point (2)


On Saturday, 30 April 2016 20:34:41 UTC+2, cmari wrote:
>
> Note/questions from a non-expert (as illustrated by the fact that I'm 
> going to have to wait for more clever people to demonstrate/document what 
> can be done with sticky notes and list-children, because I have no clue!):
>
> 1. Undo/Redo behaves in a couple of unexpected (to me) ways in Chrome:
> - With the Preview pane open, both the undo and redo buttons have to be 
> clicked twice in order to see the change reflected in the Preview pane.
> - Making this discovery caused me to notice that when I undo an extra time 
> (past what was "done" to begin with, but necessary in order to undo in the 
> preview pane), "undoundo" appears in the search bar. 
>
> 2. I made an early transition to TW5 from twclassic precisely because 
> apostrophes in tiddler titles seemed to be ok (great for people's names, 
> book titles, etc), and I've never had any trouble with those titles in TW5. 
> So I found the new warning a bit ominous and have two questions:
> - Has something really changed with this version, or is this fair warning 
> about what has always been a risk? 
> - Although the prerelease notes say "Added 
>  a warning when 
> *creating 
> *tiddler titles containing troublesome characters", in fact, the warning 
> shows up any time I edit an existing tiddler with an apostrophe in its 
> title. Assuming my TW file is not going to blow up because of these already 
> existing tiddlers, would it be possible to suppress the warning (save 
> space) after the tiddler has been created? 
>
> Although I don't tend to put a lot of content into tiddlers (hence my 
> focus on titles), I really like the Editor Toolbar - the "link" lookup is 
> going to be extremely useful - thanks!
> cmari
>
>
>
>
> On Saturday, April 30, 2016 at 6:43:23 AM UTC-7, Jeremy Ruston wrote:
>>
>> OK, after my disappointment recorded below, I came up with another 
>> approach and I think have now got things working on Internet Explorer 11: 
>>
>> http://tiddlywiki.com/prerelease 
>>
>> It needs thoroughly testing under other browsers too, but seems to work 
>> for me, 
>>
>> Best wishes 
>>
>> Jeremy. 
>>
>> > On 30 Apr 2016, at 12:06, Jeremy Ruston  wrote: 
>> > 
>> > Hi Andrew 
>> > 
>> >> Now in IE 11, the whole edit field now clears if you change views and 
>> also randomly. Something is wrong. It was working better. What changed? 
>> > 
>> > Nothing has changed in the code that updates the textarea. I think the 
>> problem that we’re seeing in IE11 with the textarea display not being 
>> updated is some kind of random bug. 
>> > 
>> > I’ve spent a few more hours investigating the problems with IE11 and 
>> once again I’m out of ideas; I’ve been repeatedly finding the same outdated 
>> information via searching Google, StackOverflow etc. 
>> > 
>> > The code in question is this part of framed.js: 
>> > 
>> > // Attempt to use a TextEvent to modify the value of 
>> the control 
>> > var textEvent = 
>> this.domNode.ownerDocument.createEvent("TextEvent"); 
>> > if(textEvent.initTextEvent) { 
>> > textEvent.initTextEvent("textInput", true, 
>> true, null, operation.replacement, 9, "en-US"); 
>> > this.domNode.focus(); 
>> > 
>> 
>> this.domNode.setSelectionRange(operation.cutStart,operation.cutEnd); 
>>
>> > this.domNode.dispatchEvent(textEvent); 
>> > } else { 
>> > this.domNode.value = newText; 
>> > } 
>> > 
>> > IE11 has the initTextEvent method, and so calls the first code path. 
>> The problem is that the value underlying the textarea is updated, but the 
>> display is not updated to match. 
>> > 
>> > Best wishes 
>> > 
>> > Jeremy. 
>> > 
>> >> 
>> >> -- 
>> >> 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 tiddlywiki+...@googlegroups.com. 
>> >> To post to this group, send email to tiddl...@googlegroups.com. 
>> >> Visit this group at https://groups.google.com/group/tiddlywiki. 
>> >> To view this discussion on the web visit 
>> 

Re: [tw] [tw5] Final tests for 5.1.12 before release

[cmari]

Note/questions from a non-expert (as illustrated by the fact that I'm going 
to have to wait for more clever people to demonstrate/document what can be 
done with sticky notes and list-children, because I have no clue!):

1. Undo/Redo behaves in a couple of unexpected (to me) ways in Chrome:
- With the Preview pane open, both the undo and redo buttons have to be 
clicked twice in order to see the change reflected in the Preview pane.
- Making this discovery caused me to notice that when I undo an extra time 
(past what was "done" to begin with, but necessary in order to undo in the 
preview pane), "undoundo" appears in the search bar. 

2. I made an early transition to TW5 from twclassic precisely because 
apostrophes in tiddler titles seemed to be ok (great for people's names, 
book titles, etc), and I've never had any trouble with those titles in TW5. 
So I found the new warning a bit ominous and have two questions:
- Has something really changed with this version, or is this fair warning 
about what has always been a risk? 
- Although the prerelease notes say "Added 
 a warning when *creating 
*tiddler titles containing troublesome characters", in fact, the warning 
shows up any time I edit an existing tiddler with an apostrophe in its 
title. Assuming my TW file is not going to blow up because of these already 
existing tiddlers, would it be possible to suppress the warning (save 
space) after the tiddler has been created? 

Although I don't tend to put a lot of content into tiddlers (hence my focus 
on titles), I really like the Editor Toolbar - the "link" lookup is going 
to be extremely useful - thanks!
cmari




On Saturday, April 30, 2016 at 6:43:23 AM UTC-7, Jeremy Ruston wrote:
>
> OK, after my disappointment recorded below, I came up with another 
> approach and I think have now got things working on Internet Explorer 11: 
>
> http://tiddlywiki.com/prerelease 
>
> It needs thoroughly testing under other browsers too, but seems to work 
> for me, 
>
> Best wishes 
>
> Jeremy. 
>
> > On 30 Apr 2016, at 12:06, Jeremy Ruston  > wrote: 
> > 
> > Hi Andrew 
> > 
> >> Now in IE 11, the whole edit field now clears if you change views and 
> also randomly. Something is wrong. It was working better. What changed? 
> > 
> > Nothing has changed in the code that updates the textarea. I think the 
> problem that we’re seeing in IE11 with the textarea display not being 
> updated is some kind of random bug. 
> > 
> > I’ve spent a few more hours investigating the problems with IE11 and 
> once again I’m out of ideas; I’ve been repeatedly finding the same outdated 
> information via searching Google, StackOverflow etc. 
> > 
> > The code in question is this part of framed.js: 
> > 
> > // Attempt to use a TextEvent to modify the value of the 
> control 
> > var textEvent = 
> this.domNode.ownerDocument.createEvent("TextEvent"); 
> > if(textEvent.initTextEvent) { 
> > textEvent.initTextEvent("textInput", true, true, 
> null, operation.replacement, 9, "en-US"); 
> > this.domNode.focus(); 
> > 
> 
> this.domNode.setSelectionRange(operation.cutStart,operation.cutEnd); 
>
> > this.domNode.dispatchEvent(textEvent); 
> > } else { 
> > this.domNode.value = newText; 
> > } 
> > 
> > IE11 has the initTextEvent method, and so calls the first code path. The 
> problem is that the value underlying the textarea is updated, but the 
> display is not updated to match. 
> > 
> > Best wishes 
> > 
> > Jeremy. 
> > 
> >> 
> >> -- 
> >> 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 tiddlywiki+...@googlegroups.com . 
> >> To post to this group, send email to tiddl...@googlegroups.com 
> . 
> >> 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/5b46be97-e9f8-4f99-ba1c-5b5b2ac3cbe1%40googlegroups.com.
>  
>
> >> For more options, visit https://groups.google.com/d/optout. 
> > 
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/136c27b2-9567-4419-8245-d1078fd268a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5] Final tests for 5.1.12 before release

[progetti]

J.

Small point.

If you try looking at the MODALS DEMO under zoomin it is obscured by any 
other tiddler open. (on firefox 45.0.2)

J. 

On Saturday, 23 April 2016 14:14:24 UTC+2, Jeremy Ruston wrote:
>
> Now that the editor toolbar work is completed, I’d like to release 
> TiddlyWiki 5.1.12 in the next couple of days. I’d be very grateful for help 
> with testing this release; there are a lot of changes this time around 
> which brings a potential for things to go wrong. 
>
> There’s a prerelease available for testing: 
>
> http://tiddlywiki.com/prerelease 
>
> Please give it a try - be cautious about your personal data, and take 
> careful backups. Perform a test upgrade of your wikis and check for any 
> problems: 
>
> http://tiddlywiki.com/prerelease/upgrade.html 
>
> Please let me know if you spot any issues. This is a great time to submit 
> documentation updates but I’m afraid its too late for any further 
> functional changes. In particular if you have published TiddlyWiki 
> resources that are not currently linked from 
> http://tiddlywiki.com/prerelease do please consider submitting a pull 
> request. 
>
> Best wishes 
>
> Jeremy

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/7190c1a8-b1c0-442d-9aa8-076146fc0ade%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [tw5] Final tests for 5.1.12 before release

[andrew harrison]

I'm still getting the delete effect in Internet Explorer 11. Interestingly
if you click the edit button it shows "Type the text for this Tiddler" at
the beginning before all the text already in the tiddler and the preview
window initially shows a preview and then clears. I think it has something
to do with the new setText function in framed.js. It wasn't doing that
before it was merged from http://rich-text-editor.tiddlyspot.com/. It used
to be called the getEditInfo function and had a lot more to the function.
Now Internet Explorer hits it first and passes a value of null via text
where as the other browsers don't even seem to initially hit that function
at all, maybe because of focus. It is checking if it has focus and then it
does this.domNode.value = text; which deletes the text because at this
point text has nothing in it. Strange how it only does this in IE 11 and
not Chrome or Edge.
Please forgive me Jeremy if I am completely wrong.

On Sat, Apr 30, 2016 at 6:43 AM, Jeremy Ruston 
wrote:

> OK, after my disappointment recorded below, I came up with another
> approach and I think have now got things working on Internet Explorer 11:
>
> http://tiddlywiki.com/prerelease
>
> It needs thoroughly testing under other browsers too, but seems to work
> for me,
>
> Best wishes
>
> Jeremy.
>
> > On 30 Apr 2016, at 12:06, Jeremy Ruston  wrote:
> >
> > Hi Andrew
> >
> >> Now in IE 11, the whole edit field now clears if you change views and
> also randomly. Something is wrong. It was working better. What changed?
> >
> > Nothing has changed in the code that updates the textarea. I think the
> problem that we’re seeing in IE11 with the textarea display not being
> updated is some kind of random bug.
> >
> > I’ve spent a few more hours investigating the problems with IE11 and
> once again I’m out of ideas; I’ve been repeatedly finding the same outdated
> information via searching Google, StackOverflow etc.
> >
> > The code in question is this part of framed.js:
> >
> >   // Attempt to use a TextEvent to modify the value of the
> control
> >   var textEvent =
> this.domNode.ownerDocument.createEvent("TextEvent");
> >   if(textEvent.initTextEvent) {
> >   textEvent.initTextEvent("textInput", true, true,
> null, operation.replacement, 9, "en-US");
> >   this.domNode.focus();
> >
>  this.domNode.setSelectionRange(operation.cutStart,operation.cutEnd);
> >   this.domNode.dispatchEvent(textEvent);
> >   } else {
> >   this.domNode.value = newText;
> >   }
> >
> > IE11 has the initTextEvent method, and so calls the first code path. The
> problem is that the value underlying the textarea is updated, but the
> display is not updated to match.
> >
> > Best wishes
> >
> > Jeremy.
> >
> >>
> >> --
> >> 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 tiddlywiki+unsubscr...@googlegroups.com.
> >> To post to this group, send email to tiddlywiki@googlegroups.com.
> >> 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/5b46be97-e9f8-4f99-ba1c-5b5b2ac3cbe1%40googlegroups.com
> .
> >> For more options, visit https://groups.google.com/d/optout.
> >
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywiki@googlegroups.com.
> 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/CE449E5B-A200-42BC-8C89-C7BD31C10726%40gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/CAL0r7zvr4Euofcj7F5A0S5vDCQt3wNYoPtz%3DO907hhb8GyQPNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [tw5] Final tests for 5.1.12 before release

[Mat]

Jeremy,

Stamping:[...]
>
> Sorry Mat, can you be a bit clearer; I clicked through to QuickTid but 
> didn’t see a button labelled “Content”. Perhaps you can just show the code 
> that you want me to see?
>

Well, the actual code is a likely not pretty (tiddler TidSec/Tool/Content 
) but the 
functionality is seen using the Content button which should be found in the 
QuickTid toolbar - i.e you click the thumbtack and, well, the button is 
there next to the Done buttons.

Link
> IMO, the user should be able to create a link to a not yet existing 
> tiddler. I.e if Foo doesn't exist as a selectable title, there's some kind 
> of "make" button that stamps [[Foo]] - or, perhaps more elegantly, just 
> clicking enter creates it.
>
>
> Perhaps. It seems a bit roundabout to use the ‘link’ tool to create a link 
> to a non-existent tiddler, since the whole raison d’etre of the tool is to 
> permit searching of existing tiddlers.
>

I interpreted the raison d'etre is to be able to create links generally? 
Not a difficult task but with the suggested funtionality, one can create a 
missing link right away both in the case of wanting to do that to begin 
with or in the case of not finding the title one was hoping for.
 

> Button layout
> The backticks button appears grouped (slightly left distanced) with X2 
> rather than blockticks. 
>
>
> That’s intentional; the tools are now divided into groups. I’ll increase 
> the spacing so that people don’t think it’s accidental.
>

Ok, I figured it belongs more with the group on its right than on its left. 

Tooltips
> I feel (now) it would be valuable to see the name of the tool as a tooltip 
> so it is easier to reference it such as when writing about them here on the 
> boards.
>
>
> Can you give an example of a tool where the current tooltip doesn’t 
> include words that could be used to describe the tool here?
>

Ok, disregard thsi. No tooltips showed at all and I now suspect this was 
due to my computer/browser because there have been other browser issues for 
me lately. On computer reboot the tooltips now look good and sufficient.
 

Setting tools [...]
>
>
> That sounds like an optimisation. I’d be concerned about clutter, and I’m 
> not really convinced that people need to be regularly switching toolbar 
> buttons on and off.
>

Sorry, my misunderstanding, please forget about it! I didn't realize the 
unchecked buttons appear in the More menu but thought one was forced into 
Ctrlpanel to use a turned off formatting button.
 

> Markdown editor (yay!):
> Instead of a *page controll* button to open a tiddler with that special 
> editor, I think it would be much better with a toggle button showing in 
> tiddler edit view - either appearing just like one of the other buttons, 
> but at one of the extreme ends - maybe even out in the (left) gutter.
>
>
> I think you’re suggesting two separate things here:
>
> * Move the tiddler type controls into the toolbar. The obstacle here is 
> that not all editor types support the toolbar, so one would lose the 
> ability to change the type for those tiddlers
>

No, I am only referring to the "Create a new Markdown tiddler " button. I'm 
suggesting it is enough with the usual "Create a new tiddler" button and 
then, in the text editor toolbar, instead have a button to toggle between 
those tiddler types that do feature different editor toolbars.
 

> Clicking the more(?) button opens empty popup.
>
> In situations where there are no hidden toolbar buttons then the more 
> dropdown will be empty. You see the same thing with the more button in the 
> view template or in the sidebar when the dropdown is empty.
>

Ah. That's a bit confusing to me. Particularly if default is to have it 
empty as it is in the prerelease.
 

> I see no mention of DesignWrite.
> And IMO at least the conversations between you and prof. Steve could be 
> linked to in the Videos tiddler.
>
> Good point,
>

(ah, at least I managed  to make something made sense, hehe ;-) 


<:-)

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/1fcb81d0-147f-4401-a149-ed80fa980754%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [tw5] Final tests for 5.1.12 before release

[Sylvain Naudin]

Hi Jeremy,

I've notice that wikibar for Markdown is shorter than WikiText, for example 
there is no underline icon, but on prerelease notes we can suppose it does 
(*with 
support for Markdown*)

Maybe a bug with bullet and number list with Markddown ? Not seen this in 
WikiText.



I'm very happy like others fr this huge release for TiddlyWiki :)

Regards,
Sylvain


@Xavier : you have new wikitext link to translate in french :p


Le vendredi 29 avril 2016 20:24:55 UTC+2, Jeremy Ruston a écrit :
>
> I’ve just uploaded an update to the prerelease with a new “link” button 
> for the editor toolbar, along the lines suggested by Alex below:
>
> * Click the button to search for the target tiddler
> ** The dropdown search shares the same extensible tab system as the 
> sidebar search
> * Click the title of the tiddler to insert the link
> * If there is no selection, a plain [[link]] is created
> * If there is selected text, a [[selected text|link]] is created
>
> As part of the work, I’ve also added a new way to invoke action widgets 
> that allows them to be used with the select widget and the linkcatcher 
> widget:
>
>
> http://tiddlywiki.com/prerelease/#ActionWidgets:ActionWidgets%20SelectWidget
>
> I’m still keen to release 5.1.12 in the next few days, so please do keep 
> the feedback coming,
>
> Best wishes
>
> Jeremy
>
>
> I am on the iPad  Just wondered if the edit toolbar would benefit from 
> a [[link]] button.
>
>
> Good point. One could imagine a dropdown that showed a search dialogue; 
> clicking a result would paste the link at the cursor position. I’ll have a 
> look if I have time, but would suggest that it would be a neat little self 
> contained improvement if anybody else wants to give it a try. Bonus points 
> for re-using the existing search infrastructure (so that the dropdown shows 
> the optional search result tabs).
>
> Best wishes
>
> Jeremy
>
>
> Best wishes 
>
> Alex
>
> On Sunday, 24 April 2016, Pau Deluca  
> wrote:
>
>> I've now seen the shortcut editor. It's just great.
>>
>> Regarding translation plugin, I just have a doubt. I see the new 
>> translatable strings on the translators edition. Ok so far, but: 
>>
>> The already translated strings belong to the existing 5.1.11 version, 
>> which I have already revised for version 5.1.12 and I am now testing while 
>> translating the documentation.
>>
>> How could I manage to have those strings I  already have revised (present 
>> in languages/es-ES in my translation es-ES GitHub branch)? 
>>
>> I think I could just translate the new strings and leave the old ones 
>> untouched, then extract all the tiddlers and merge the new output folder 
>> with those already in languages/es-ES, refusing to replace the already 
>> existing files, but I would like to be sure if there is a simpler way I am 
>> jut overlooking.
>>
>> P.-)
>>
>>
>>
>>
>>
>> I've polished the translation
>>
>> El domingo, 24 de abril de 2016, 14:26:49 (UTC+2), Jeremy Ruston escribió:
>>>
>>> Hi Pau
>>>
>>> a) Ctrl-P shortcut toggles off the preview only. When trying to toggle 
>>> the preview back, the shortcut collides with with the system shortcut, 
>>> opening the print dialog. Would it be possible to make it e.g. Ctrl-Mays-P? 
>>> Any possibility to customise the shortcuts in the editor to better adapt 
>>> to, eg, different localisation standards? 
>>>
>>>
>>> Good point, Ctrl-P probably isn’t a good choice. I’ll change it to 
>>> Alt-P.  However, a problem remains: after using the shortcut, the editor no 
>>> longer has the focus so further keyboard shortcuts aren’t recognised. I 
>>> don’t have a fix for this at the moment.
>>>
>>> There is a full shortcut editor in the control panel, by the way.
>>>
>>> b) I see a lot of work ahead in my domain (i.e., documentation and 
>>> translation). Is the prerelease translators plugin also updated with the 
>>> new strings yet? 
>>>
>>>
>>> Yes, it is up to date.
>>>
>>> c) Just whistle in case the documentation of the new features needs to 
>>> be written. 
>>>
>>>
>>> Thanks! There are many holes in the documentation, and much to do,
>>>
>>> Best wishes
>>>
>>> Jeremy
>>>
>>>
>>> P.-)
>>>
>>>
>>>
>>>
>>>
>>> El sábado, 23 de abril de 2016, 14:14:24 (UTC+2), Jeremy Ruston escribió:

 Now that the editor toolbar work is completed, I’d like to release 
 TiddlyWiki 5.1.12 in the next couple of days. I’d be very grateful for 
 help 
 with testing this release; there are a lot of changes this time around 
 which brings a potential for things to go wrong. 

 There’s a prerelease available for testing: 

 http://tiddlywiki.com/prerelease 
 
  

 Please give it a try - be cautious about your 

Re: [tw] [tw5] Final tests for 5.1.12 before release

[Jeremy Ruston]

OK, after my disappointment recorded below, I came up with another approach and 
I think have now got things working on Internet Explorer 11:

http://tiddlywiki.com/prerelease

It needs thoroughly testing under other browsers too, but seems to work for me,

Best wishes

Jeremy.

> On 30 Apr 2016, at 12:06, Jeremy Ruston  wrote:
> 
> Hi Andrew
> 
>> Now in IE 11, the whole edit field now clears if you change views and also 
>> randomly. Something is wrong. It was working better. What changed?
> 
> Nothing has changed in the code that updates the textarea. I think the 
> problem that we’re seeing in IE11 with the textarea display not being updated 
> is some kind of random bug.
> 
> I’ve spent a few more hours investigating the problems with IE11 and once 
> again I’m out of ideas; I’ve been repeatedly finding the same outdated 
> information via searching Google, StackOverflow etc.
> 
> The code in question is this part of framed.js:
> 
>   // Attempt to use a TextEvent to modify the value of the control
>   var textEvent = 
> this.domNode.ownerDocument.createEvent("TextEvent");
>   if(textEvent.initTextEvent) {
>   textEvent.initTextEvent("textInput", true, true, null, 
> operation.replacement, 9, "en-US");
>   this.domNode.focus();
>   
> this.domNode.setSelectionRange(operation.cutStart,operation.cutEnd);
>   this.domNode.dispatchEvent(textEvent);
>   } else {
>   this.domNode.value = newText;
>   }
> 
> IE11 has the initTextEvent method, and so calls the first code path. The 
> problem is that the value underlying the textarea is updated, but the display 
> is not updated to match.
> 
> Best wishes
> 
> Jeremy.
> 
>> 
>> -- 
>> 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 tiddlywiki+unsubscr...@googlegroups.com.
>> To post to this group, send email to tiddlywiki@googlegroups.com.
>> 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/5b46be97-e9f8-4f99-ba1c-5b5b2ac3cbe1%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/CE449E5B-A200-42BC-8C89-C7BD31C10726%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [tw5] Final tests for 5.1.12 before release

[Jeremy Ruston]

Hi Mat

> Stamping:
> I've implemented a stamping tool in QuickTid 
>  (the button called "Content"). One feature 
> of it is that some snips can surround already typed content. This is useful 
> e.g when stamping html tags (start and end) but also to, say, in one go stamp 
> both Hello and a Goodbye+signature. The Example with prepost 
>  
> is intended to illustrate this and how it works (see edit mode).

Sorry Mat, can you be a bit clearer; I clicked through to QuickTid but didn’t 
see a button labelled “Content”. Perhaps you can just show the code that you 
want me to see?

> Link
> IMO, the user should be able to create a link to a not yet existing tiddler. 
> I.e if Foo doesn't exist as a selectable title, there's some kind of "make" 
> button that stamps [[Foo]] - or, perhaps more elegantly, just clicking enter 
> creates it.

Perhaps. It seems a bit roundabout to use the ‘link’ tool to create a link to a 
non-existent tiddler, since the whole raison d’etre of the tool is to permit 
searching of existing tiddlers.

> ...and, btw, the X button for the Link tool would be prettier if it looked 
> like e.g the search tool X button.

Yes.

> Button layout
> The backticks button appears grouped (slightly left distanced) with X2 rather 
> than blockticks. 

That’s intentional; the tools are now divided into groups. I’ll increase the 
spacing so that people don’t think it’s accidental.

> Tooltips
> I feel (now) it would be valuable to see the name of the tool as a tooltip so 
> it is easier to reference it such as when writing about them here on the 
> boards.

Can you give an example of a tool where the current tooltip doesn’t include 
words that could be used to describe the tool here?

> Setting tools
> It is very rare that I use, say subscript or superscript. It is not 
> convenient to have have it appear all the time or to have it disabled and 
> then be forced to go deep into the Ctrlpanel to activate it, (possibly even 
> just for a few seconds). I would strongly suggest a setting accessed 
> tiddler-locally, perhaps a popup like the more button, floating to extreme 
> right. (I've expressed similar opinions before regarding local controls of 
> things, but for the text editor toolbuttons this is even more relevant 
> because of the number of buttons and how infrequently some are used.)

That sounds like an optimisation. I’d be concerned about clutter, and I’m not 
really convinced that people need to be regularly switching toolbar buttons on 
and off.

> Markdown editor (yay!):
> Instead of a page controll button to open a tiddler with that special editor, 
> I think it would be much better with a toggle button showing in tiddler edit 
> view - either appearing just like one of the other buttons, but at one of the 
> extreme ends - maybe even out in the (left) gutter.

I think you’re suggesting two separate things here:

* Move the tiddler type controls into the toolbar. The obstacle here is that 
not all editor types support the toolbar, so one would lose the ability to 
change the type for those tiddlers
* Have a separate button for each type, rather a dropdown (this seems less 
scalable than a dropdown)

Overall, I’m confused why one would want to optimise changing the type of an 
existing tiddler; isn’t specifying the type of a new tiddler more common?

> Clicking the more(?) button opens empty popup.

In situations where there are no hidden toolbar buttons then the more dropdown 
will be empty. You see the same thing with the more button in the view template 
or in the sidebar when the dropdown is empty.

> Minor
> ctrlpanel > Appearance > Toolbars > ViewToolbar ... seems to be missing icon 
> for bottom most item.\

That last item is the “fold bar” introduced a few releases ago. It doesn’t 
appear as an icon, which is why there’s no icon shown.

> I see no mention of DesignWrite.
> And IMO at least the conversations between you and prof. Steve could be 
> linked to in the Videos tiddler.

Good point,

Best wishes

Jeremy

> 
> 
> <:-)
> 
> -- 
> 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 tiddlywiki+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to tiddlywiki@googlegroups.com 
> .
> 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/774b754c-8562-4050-968b-6a869aebbb20%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> 

Re: [tw] [tw5] Final tests for 5.1.12 before release

[Jeremy Ruston]

Hi Andrew

> Now in IE 11, the whole edit field now clears if you change views and also 
> randomly. Something is wrong. It was working better. What changed?

Nothing has changed in the code that updates the textarea. I think the problem 
that we’re seeing in IE11 with the textarea display not being updated is some 
kind of random bug.

I’ve spent a few more hours investigating the problems with IE11 and once again 
I’m out of ideas; I’ve been repeatedly finding the same outdated information 
via searching Google, StackOverflow etc.

The code in question is this part of framed.js:

// Attempt to use a TextEvent to modify the value of the control
var textEvent = 
this.domNode.ownerDocument.createEvent("TextEvent");
if(textEvent.initTextEvent) {
textEvent.initTextEvent("textInput", true, true, null, 
operation.replacement, 9, "en-US");
this.domNode.focus();

this.domNode.setSelectionRange(operation.cutStart,operation.cutEnd);
this.domNode.dispatchEvent(textEvent);
} else {
this.domNode.value = newText;
}

IE11 has the initTextEvent method, and so calls the first code path. The 
problem is that the value underlying the textarea is updated, but the display 
is not updated to match.

Best wishes

Jeremy.

> 
> -- 
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywiki@googlegroups.com.
> 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/5b46be97-e9f8-4f99-ba1c-5b5b2ac3cbe1%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/A0BDD6C3-ACDF-4B73-A9B7-FA519A797F79%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] What is the exact syntax for an imported image in my custom stylesheet?

[Mat]

On Friday, April 29, 2016 at 12:24:56 PM UTC+2, peter@hotmail.de wrote:
>
>  @Mat
> Thanks for your forpeter tiddler ^^
> Correct me if I'm wrong. You simply avoid my problem by adding a new 
> html-element to the tiddlers (if needed). You gave me a huge playground. If 
> thats work for my ideas that would be great. Again thank you!
> I will post my experience and hopefully succes
>

 So what's happening is thsi

* an image (twaddle)
* create a new viewtemplate (myviewtemplate) -  i.e a tiddler is made up of 
a list of viewtemplates (the title is one, the tags, the body, etc). They 
are all tagged $:/tags/ViewTemplate. You are creating an additional one.
*...and in this viewtemplate, there is the image transclusion.
*The viewtemplate also has a field list-before:$:/core/ui/ViewTemplate/body 
to ensure that the image is before the body viewtemplate because you dont 
want the image do be pushed down from the text in the tiddler body.
*However, this viewtemplate affects all tiddlers. So the image would show 
up in all tiddlers! You want to control this so first step is to block it 
everywhere by wrapping the image transclusion in a div that is styled to 
"display:none"
*...and instead change this to display:block only in tiddlers tagged with 
applymyimage. This is achieved in the stylesheet, using the 
tc-tagged-applymyimage.
*In the stylesheet the image is also styled for position, size etc. You'd 
also add the colored field here. (and you might need to use css 
pointer-events: 
none to 
prevent a color field fro blocking underlying buttons etc)

FYI, I'm also not a coder (yet). A year ago I would not have figured this 
out. But I would also think there are easier/more direct solutions. The 
whole route with a special viewtemplate for just an image feels convoluted 
but that's what I come up with right now. But, the idea to have it 
accessible for every tiddler is appealing if you add loads of things into 
it, i.e have everything display:none and then on a per-tiddler basis 
activate whatever bits you want.

<:-)

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/f3d42457-e8f8-4fa0-a200-2db01cac5fc2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.