[tw] Re: copy button in each code block

[TonyM]

Rustem,

What do you define as a Code Block?

How does it differ from the Text or other field?

Regards
Tony


On Wednesday, March 14, 2018 at 11:10:42 AM UTC+11, Rustem wrote:
>
> Now that there is a `copy-to-clipboard` macro in the pre-release, could 
> someone figure out a way to have a "copy" button in a corner of each code 
> block, please? :) I used to have it in TW Classic, it was extremely useful.
>

-- 
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/fc5fe01c-3f7f-45de-a422-ecc9bfb49208%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Single executable version of tiddlywiki

[TonyM]

Jed/Josiah,

The solution is already very easy to distribute, and need not have a 
portableapps.com install, or it would be very easy to make one.

However If someone is trying to distribute a TiddlyWiki they built and want 
to host it through TiddlyWikiMU (my name for Jed's solution), it seems it 
would be simple to package it in a ZIP package, or installer that unpacks 
the folders that are created under the subfolder IndexWiki or any 
additional folders for other wikis.

PS Jed, I think your  settings.json editor is a leap ahead. Thanks

Regards
Tony

On Monday, March 12, 2018 at 10:00:58 PM UTC+11, Jed Carty wrote:
>
> I am going to start this by saying that I appreciate the feedback and I 
> apologise if my tone is (or has been) a bit harsh, this has been very 
> confusing for me.
>
> @TiddlyTweeter try out the instructions from my last post, unless there 
> is some bug that I haven't tracked down it should work the way you are 
> describing as 'portable enough'
> without any sort of configuration.
>

-- 
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/9490275b-a47e-4a05-84d4-2d826b648d19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Single executable version of tiddlywiki

[TonyM]

Jed,

Progress, looking great.

I could not get this working due to something neither of us were aware of, 
I had a windows app installed for NodeJS, So tiddlywiki.exe was opening 
that session in my browser and I never got to see the "Welcome to the 
MultiUser TiddlyWiki."  Somehow they clash, I was not getting "*under that 
say something like "Serving on 127.0.0.1:808 0", 
only *Websockets listening on  8081, nothing was found on 8082 or any other 
port.

Removing the nodeJS from windows Apps & Features resolved this. I can now 
experiment.

It is looking fantastic, I have observed the update of tiddlers across 2 
browser sessions. 
I would like to understand how to break this so as to know how to avoid a 
clash it at all possible.

I am now looking into hosting exiting other wikis, the instructions read

*Go to the Node Settings tab in the $:/ControlPanel 
 and give the wiki a name and 
list its path in the wikis section like this:*

*'otherwiki': ~/Documents/TiddlyWiki/Wikis/MultiUser*



 There is no apparent wikis section in the Node settings.

Can you please tell me what this looks like, and potentially update the 
instructions to make this clear?

I am guessing something like



What does "~" Refer to?, Most of my single file and NodeJS wikis are 
located under;
C:\Data\TW5\Folder
With tiddlywiki.exe installed in
C:\Data\TW5\TiddlyWIkiMU


Thanks in Advance
Tony




On Monday, March 12, 2018 at 8:38:09 PM UTC+11, Jed Carty wrote:
>
> Version 0.0.2 is up so you may have better luck with that. Also do you 
> have the windows firewall blocking things automatically? I can't test on 
> windows but you may have to tell it to allow the server to run or make an 
> exception for node.
>

-- 
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/514bf34b-7677-4070-b910-ec3937127243%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] copy button in each code block

[Rustem]

Now that there is a `copy-to-clipboard` macro in the pre-release, could 
someone figure out a way to have a "copy" button in a corner of each code 
block, please? :) I used to have it in TW Classic, it was extremely useful.

-- 
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/a51c6471-c035-4035-bd13-8b4f27a81ad2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Issue: I'd like to talk about Markup---broadly

[TonyM]

Joe,

I had a similar waking idea a few weeks/months ago, make HTML the common 
language, but community members pointed out there is a potential loss of 
information HTML > TW given the degree of sophistication that can be added 
to HTML, also just think how more is moving into CSS now. Personally this 
would be fine to me, if the conversion process simplified the source HTML.

I agree with your suggestion

Tony

On Wednesday, March 14, 2018 at 6:15:11 AM UTC+11, Joe Armstrong wrote:
>
> I woke up with the following thought:
>
> I'm not so worried about the difference in markdown / wiki syntaxes
>
> I think this is like language - there are many dialects of English
> American, English, Australian and so on - they differ but we understand 
> each other.
>
> Then there is Swedish, Norwegian, Danish again different but in many ways 
> similar.
>
> What I wondered was about code to convert random HTML to TW code
> and NOT the other way around.
>
> I know how to convert TW to HTML - this is what the system does all the 
> time.
>
> It would be very nice to take any fragment of HTML and turn it into TW 
> tiddlers
>
> This would involve partitioning (splitting big pages into smaller tiddlers)
> removing styling and guessing the structure
>
> Has anybody thought about this
>
> Cheer
>
> /Joe
>
> On Tue, Mar 13, 2018 at 9:04 AM, @TiddlyTweeter  > wrote:
>
>> This is an interesting issue. On the one hand we have markup for wikitext 
>> styling using, for instance, the @@ syntax. On the other hand one 
>> inevitably hits a contradiction in Markup systems that are meant to be 
>> human readable. That to get complex styling is not sane through "Markup", 
>> as Jermolene put it well recently: *that would take us back to the same 
>> level of complexity as HTML itself. *
>>
>> This is precisely why I'm as much interested in styling for specific 
>> Document Types as in generic markup. Markup is a blunt instrument for 
>> specifics IMO. Document types provide a layout that is ITSELF the 
>> TEMPLATE for format. This allows sophisticated styling without any 
>> explicit markup at all.
>>
>> I slightly exaggerate. But not much.
>>
>> Joe Armstrong wrote:
>>>
>>> The problem(s) I want to solve are "make the output beautiful" 
>>> and "make the output programmatically" when this makes sence
>>>
>>> TW seems a pretty good compromise at these - For beautiful output
>>> I'd have to turn TW in LaTeX of something - but I'll cross one
>>> bridge at a time.
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/NKOnq3hKryo/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/f14591a6-f08d-482e-a80e-f10953d57171%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/d0b784c9-b593-4f2a-aaa9-d8f2c26b954a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Issue: I'd like to talk about Markup---broadly

[@TiddlyTweeter]

How important, in your opinion, PMario, are RFC's to TiddlyWiki's uptake?

I can't honestly say for myself that an RFC motivated me to do anything. At 
the same time I do understand they have a role. BUT is it *before* the fact 
or *after*?

In other words, for TW, WHAT exactly should we be promoting to it? And WHY?

Josiah

-- 
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/94271bac-738c-471f-ba7d-bf73abeaa594%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Issue: I'd like to talk about Markup---broadly

[@TiddlyTweeter]

Ciao PMario

I really appreciate your concern over standards.

I have an observation. At 7764:3.4 
 they include Fountain.io 
syntax  as a Markdown variant. 

That is odd in a spec given that Fountain is, when it is working well, a 
non-visible markup. Its a brilliant minimalist FORMATTING system that uses 
Markup ONLY to FORCE compliance, otherwise you never see it. 

In other words that "standard" is a handbag of approaches so diverse its 
melange of discontinuity. 

I can't see the merit when its accepting a non-visible markup system.

Josiah


-- 
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/65f00030-55bd-496e-afe2-83aa9a1c93fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Issue: I'd like to talk about Markup---broadly

[@TiddlyTweeter]

Yes. Jeremy made a careful Text-Slicer edition 
.

Personally I'd be in for reducing on one sweep all HTML. 

There is something very satisfying in reducing carefully wrought HTML to 
ground zero markup.

Josiah

On Tuesday, 13 March 2018 20:15:11 UTC+1, Joe Armstrong wrote:
>
> I woke up with the following thought:
>
> I'm not so worried about the difference in markdown / wiki syntaxes
>
> I think this is like language - there are many dialects of English
> American, English, Australian and so on - they differ but we understand 
> each other.
>
> Then there is Swedish, Norwegian, Danish again different but in many ways 
> similar.
>
> What I wondered was about code to convert random HTML to TW code
> and NOT the other way around.
>
> I know how to convert TW to HTML - this is what the system does all the 
> time.
>
> It would be very nice to take any fragment of HTML and turn it into TW 
> tiddlers
>
> This would involve partitioning (splitting big pages into smaller tiddlers)
> removing styling and guessing the structure
>
> Has anybody thought about this
>
> Cheer
>
> /Joe
>
> On Tue, Mar 13, 2018 at 9:04 AM, @TiddlyTweeter  > wrote:
>
>> This is an interesting issue. On the one hand we have markup for wikitext 
>> styling using, for instance, the @@ syntax. On the other hand one 
>> inevitably hits a contradiction in Markup systems that are meant to be 
>> human readable. That to get complex styling is not sane through "Markup", 
>> as Jermolene put it well recently: *that would take us back to the same 
>> level of complexity as HTML itself. *
>>
>> This is precisely why I'm as much interested in styling for specific 
>> Document Types as in generic markup. Markup is a blunt instrument for 
>> specifics IMO. Document types provide a layout that is ITSELF the 
>> TEMPLATE for format. This allows sophisticated styling without any 
>> explicit markup at all.
>>
>> I slightly exaggerate. But not much.
>>
>> Joe Armstrong wrote:
>>>
>>> The problem(s) I want to solve are "make the output beautiful" 
>>> and "make the output programmatically" when this makes sence
>>>
>>> TW seems a pretty good compromise at these - For beautiful output
>>> I'd have to turn TW in LaTeX of something - but I'll cross one
>>> bridge at a time.
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/NKOnq3hKryo/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/f14591a6-f08d-482e-a80e-f10953d57171%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/7cb1b9b5-5520-4b16-b4c6-6e644d47d3a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Right Justify Sidebar like in The TiddlyWiki ... Wiki

[Sean Bergstedt]

Yes! This is it! Thank you so much!  I thought I was going to have to play 
with the CSS.  This is much better.  Thanks, Ed!

On Monday, March 12, 2018 at 6:02:17 PM UTC-5, Ed wrote:
>
> Dear Sean,
>
> Click "Open Control Panel" icon.
> Click "Appearances"
> Click "Team Tweaks"
> Find "Sidebar lay-out"
> Click "Fixed Story, fluid sidebar"
> Choose "Fluid story, fixed sidebar"
> Is this what you are looking for?
> Salut! Ed.
>
>
>
> Op maandag 12 maart 2018 22:21:10 UTC+1 schreef Sean Bergstedt:
>>
>> Anyone know how to move the side bar completely to the right like in:
>>
>> https://tiddlywiki.com/
>>
>> ?  I would greatly appreciate the help.  I'm pretty new to 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/edc6047a-05c7-48e1-956e-278e52cf3a00%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: A few questions about macros/widgets/functions

['Mark S.' via TiddlyWiki]

Just go to the shadow tab of the advanced search. Look for the name of the 
widget minus the "widget" term. Like

button.js

I'm guessing that the TextWidget would be simplest because it does the 
least.

There's some documentation how-to on plugins at http://cjhunt.github.io/ 
though for me I found a bit too much was assumed to start.

Good luck!
-- Mark

On Tuesday, March 13, 2018 at 12:08:23 PM UTC-7, Joe Armstrong wrote:
>
> Next question is where is the code for a widget?
>
> I think I understand (famous last words) macros - but not widgets.
>
> Where is the code for a simple widget?
>
> Which is the simplest widget??? 
>
> Cheers
>
> /Joe
>
>
>
> On Tue, Mar 13, 2018 at 10:16 AM, Steven Schneider  > wrote:
>
>> Great thread. Thanks, Joe. And thanks, Xavier.
>>
>> What I find most interesting about TiddlyWiki is that someone like Joe 
>> and someone like me can work with it. Joe has a clearly different approach 
>> to learning and understanding than I do. I never looked at the 
>> <> code, just used it for a while until it didn't do what I 
>> wanted, and poked around and discovered <$list>, and used the dox and 
>> examples on tiddlywiki.com to get it to work (sort of).
>>
>> FWIW: I may have a different need, since I am now frequently teaching 
>> TiddlyWiki, but this term I gave up teaching <> and moved 
>> students into using <$list filter=...> right away. Like Xavier, I agree 
>> that filters are key, and help folks understand the core aspects of 
>> Tiddlywiki. Most of my students are non-programmers, but many have html 
>> experience. 
>>
>> It is always interesting to have computer scientists in my class, as the 
>> way I have them approach TW is so different than how they are taught 
>> programming and languages in the CS department. About half-way into the 
>> semester, they begin to see that there is a language under TW, and that 
>> they can get to that language if they want to. I'm not sure that there are 
>> platforms other than TiddlyWiki that offer this possibility.
>>
>> Anyway, thanks Joe for starting off an interesting thread...
>>
>> //steve.
>>
>>
>> On Saturday, March 10, 2018 at 8:08:52 PM UTC-5, PMario wrote:
>>>
>>> On Saturday, March 10, 2018 at 7:25:48 PM UTC+1, Joe Armstrong wrote:

 ...

 2) widgets - what do they return? how are they evaluated?

>>>
>>> Widgets are the basic building blocks in TW. The whole UI is based on 
>>> widgets. 
>>>
>>> The TiddlyWiki UI starts with a transclusion of the PageTemplate 
>>> tiddler. 
>>> Which simply speaking is a "list all tiddlers that are tagged: 
>>> $:/tags/PageTemplate" + some navigation handling using the NavigatorWidget
>>>
>>> TW wikitext is parsed and transferred to widgets, which produce the 
>>> html-dom, that the browser can use. more about this later.
>>>
>>> 
>>>
>>> A simpler example:
>>>
>>> Macro definitions are converted to SetWidgets 
>>> and 
>>> macro calls are converted to a MacroCallWidgets
>>>
>>> eg: if you go to the *TW-prerelease edtion* you can see the pare-tree 
>>> and the widget-tree. The prerelease contains some development elements, 
>>> that are missing at tiddlywiki.com
>>>
>>>  - open: https://tiddlywiki.com/prerelease/
>>>  - create a new tiddler eg: test-macro
>>>  - enter: \define hello() hello world
>>>  - In the edit toolbar you see: 
>>>
>>>  - *select parse-tree* and you'll see: 
>>>
>>>
>>> [
>>> {
>>> "type": "set",
>>> "attributes": {
>>> "name": {
>>> "type": "string",
>>> "value": "hello"
>>> },
>>> "value": {
>>> "type": "string",
>>> "value": "hello world"
>>> }
>>> },
>>> "children": [],
>>> "params": []
>>> }
>>> ]
>>>  
>>>
>>> -* now add the macro call*  with: <>
>>>
>>> - you'll get: 
>>>
>>>
>>> [
>>> {
>>> "type": "set",
>>> "attributes": {
>>> "name": {
>>> "type": "string",
>>> "value": "hello"
>>> },
>>> "value": {
>>> "type": "string",
>>> "value": "hello world"
>>> }
>>> },
>>> "children": [
>>> {
>>> "type": "macrocall",
>>> "name": "hello",
>>> "params": [],
>>> "isBlock": true
>>> }
>>> ],
>>> "params": []
>>> }
>>> ]
>>>
>>>
>>> These internal structures are created by the TW parsers 
>>> .
>>>  
>>> They produce the parse-tree. 
>>>
>>> This parse-tree is used by the TW renderer to produce the HTML output, 
>>> that the browser can use. 
>>> Every widget has a widget.render() function. ... 
>>>
>>> The module render.js 
>>> 
>>>  
>>> is a startup module, that kicks

[tw] Re: A few questions about macros/widgets/functions

[Jed Carty]

I am not sure if it is the simplest widget, but the text widget is one of 
the simplest widgets.

It is part of every wiki but here is a link to it on 
tiddlywiki.com 
https://tiddlywiki.com/#%24%3A%2Fcore%2Fmodules%2Fwidgets%2Ftext.js

-- 
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/b674fc30-cb1c-4350-aaab-80f3a3c4e8a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Issue: I'd like to talk about Markup---broadly

[Joe Armstrong]

I woke up with the following thought:

I'm not so worried about the difference in markdown / wiki syntaxes

I think this is like language - there are many dialects of English
American, English, Australian and so on - they differ but we understand
each other.

Then there is Swedish, Norwegian, Danish again different but in many ways
similar.

What I wondered was about code to convert random HTML to TW code
and NOT the other way around.

I know how to convert TW to HTML - this is what the system does all the
time.

It would be very nice to take any fragment of HTML and turn it into TW
tiddlers

This would involve partitioning (splitting big pages into smaller tiddlers)
removing styling and guessing the structure

Has anybody thought about this

Cheer

/Joe

On Tue, Mar 13, 2018 at 9:04 AM, @TiddlyTweeter 
wrote:

> This is an interesting issue. On the one hand we have markup for wikitext
> styling using, for instance, the @@ syntax. On the other hand one
> inevitably hits a contradiction in Markup systems that are meant to be
> human readable. That to get complex styling is not sane through "Markup",
> as Jermolene put it well recently: *that would take us back to the same
> level of complexity as HTML itself. *
>
> This is precisely why I'm as much interested in styling for specific
> Document Types as in generic markup. Markup is a blunt instrument for
> specifics IMO. Document types provide a layout that is ITSELF the
> TEMPLATE for format. This allows sophisticated styling without any
> explicit markup at all.
>
> I slightly exaggerate. But not much.
>
> Joe Armstrong wrote:
>>
>> The problem(s) I want to solve are "make the output beautiful"
>> and "make the output programmatically" when this makes sence
>>
>> TW seems a pretty good compromise at these - For beautiful output
>> I'd have to turn TW in LaTeX of something - but I'll cross one
>> bridge at a time.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/tiddlywiki/NKOnq3hKryo/unsubscribe.
> To unsubscribe from this group and all its topics, 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/f14591a6-f08d-482e-a80e-f10953d57171%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/CAL6cY6F%3DkVZbX_8XSBGpWcsQ4sOyi76DKvfKf01cF98d%2BhR_DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: A few questions about macros/widgets/functions

[Joe Armstrong]

Next question is where is the code for a widget?

I think I understand (famous last words) macros - but not widgets.

Where is the code for a simple widget?

Which is the simplest widget???

Cheers

/Joe



On Tue, Mar 13, 2018 at 10:16 AM, Steven Schneider  wrote:

> Great thread. Thanks, Joe. And thanks, Xavier.
>
> What I find most interesting about TiddlyWiki is that someone like Joe and
> someone like me can work with it. Joe has a clearly different approach to
> learning and understanding than I do. I never looked at the <>
> code, just used it for a while until it didn't do what I wanted, and poked
> around and discovered <$list>, and used the dox and examples on
> tiddlywiki.com to get it to work (sort of).
>
> FWIW: I may have a different need, since I am now frequently teaching
> TiddlyWiki, but this term I gave up teaching <> and moved
> students into using <$list filter=...> right away. Like Xavier, I agree
> that filters are key, and help folks understand the core aspects of
> Tiddlywiki. Most of my students are non-programmers, but many have html
> experience.
>
> It is always interesting to have computer scientists in my class, as the
> way I have them approach TW is so different than how they are taught
> programming and languages in the CS department. About half-way into the
> semester, they begin to see that there is a language under TW, and that
> they can get to that language if they want to. I'm not sure that there are
> platforms other than TiddlyWiki that offer this possibility.
>
> Anyway, thanks Joe for starting off an interesting thread...
>
> //steve.
>
>
> On Saturday, March 10, 2018 at 8:08:52 PM UTC-5, PMario wrote:
>>
>> On Saturday, March 10, 2018 at 7:25:48 PM UTC+1, Joe Armstrong wrote:
>>>
>>> ...
>>>
>>> 2) widgets - what do they return? how are they evaluated?
>>>
>>
>> Widgets are the basic building blocks in TW. The whole UI is based on
>> widgets.
>>
>> The TiddlyWiki UI starts with a transclusion of the PageTemplate tiddler.
>> Which simply speaking is a "list all tiddlers that are tagged:
>> $:/tags/PageTemplate" + some navigation handling using the NavigatorWidget
>>
>> TW wikitext is parsed and transferred to widgets, which produce the
>> html-dom, that the browser can use. more about this later.
>>
>> 
>>
>> A simpler example:
>>
>> Macro definitions are converted to SetWidgets
>> and
>> macro calls are converted to a MacroCallWidgets
>>
>> eg: if you go to the *TW-prerelease edtion* you can see the pare-tree
>> and the widget-tree. The prerelease contains some development elements,
>> that are missing at tiddlywiki.com
>>
>>  - open: https://tiddlywiki.com/prerelease/
>>  - create a new tiddler eg: test-macro
>>  - enter: \define hello() hello world
>>  - In the edit toolbar you see:
>>
>>  - *select parse-tree* and you'll see:
>>
>>
>> [
>> {
>> "type": "set",
>> "attributes": {
>> "name": {
>> "type": "string",
>> "value": "hello"
>> },
>> "value": {
>> "type": "string",
>> "value": "hello world"
>> }
>> },
>> "children": [],
>> "params": []
>> }
>> ]
>>
>>
>> -* now add the macro call*  with: <>
>>
>> - you'll get:
>>
>>
>> [
>> {
>> "type": "set",
>> "attributes": {
>> "name": {
>> "type": "string",
>> "value": "hello"
>> },
>> "value": {
>> "type": "string",
>> "value": "hello world"
>> }
>> },
>> "children": [
>> {
>> "type": "macrocall",
>> "name": "hello",
>> "params": [],
>> "isBlock": true
>> }
>> ],
>> "params": []
>> }
>> ]
>>
>>
>> These internal structures are created by the TW parsers
>> .
>> They produce the parse-tree.
>>
>> This parse-tree is used by the TW renderer to produce the HTML output,
>> that the browser can use.
>> Every widget has a widget.render() function. ...
>>
>> The module render.js
>> 
>> is a startup module, that kicks off the whole parsing and rendering
>> process for eg: the PageTemplate
>> 
>> .
>>
>> A little bit earlier in the startup mechanism, the RootWidget is created
>> .
>> It holds a reference to the browser DOM document element, which allows all
>> widgets, to modify the DOM.
>>
>> hope that makes sense
>> have fun!
>> mario
>>
>>
>> --
> You received this message because you are subscribed to

Re: [tw] Re: How can I hide the author's name in all tiddlers?

[Steven Schneider]

Check out http://designwritestudio.com/#Display, which provides buttons to 
turn on/off tiddler titles, subtitles and tags, and conveniently lists 
templates. (Written by Hegart, I think, who used to inhabit this group, and 
was one of the participants in DesignWriteStudio a few years back).

//steve.

On Friday, March 9, 2018 at 8:04:04 AM UTC-5, Tom wrote:
>
> Ahh, tagging it includes it in the stylesheet!
>
> That makes sense!
>
> Thank you Jed.
>
> On Fri, Mar 9, 2018, 20:55 Jed Carty > 
> wrote:
>
>> Create a new tiddler, the name can be anything you want.
>>
>> Give the tiddler the tag $:/tags/Stylesheet
>>
>> in the text field of the tiddler put:
>>
>> .tc-subtitle .tc-tiddlylink {display:none;}
>>
>> save the tiddler and it should be done.
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/m81fjaqtWj0/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/7ce6aa20-8650-4ac6-939c-7b8ff0caf0a8%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/0a2b1d2e-edbe-4d55-8c80-38d417229e92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: A few questions about macros/widgets/functions

[Steven Schneider]

Great thread. Thanks, Joe. And thanks, Xavier.

What I find most interesting about TiddlyWiki is that someone like Joe and 
someone like me can work with it. Joe has a clearly different approach to 
learning and understanding than I do. I never looked at the <> 
code, just used it for a while until it didn't do what I wanted, and poked 
around and discovered <$list>, and used the dox and examples on 
tiddlywiki.com to get it to work (sort of).

FWIW: I may have a different need, since I am now frequently teaching 
TiddlyWiki, but this term I gave up teaching <> and moved 
students into using <$list filter=...> right away. Like Xavier, I agree 
that filters are key, and help folks understand the core aspects of 
Tiddlywiki. Most of my students are non-programmers, but many have html 
experience. 

It is always interesting to have computer scientists in my class, as the 
way I have them approach TW is so different than how they are taught 
programming and languages in the CS department. About half-way into the 
semester, they begin to see that there is a language under TW, and that 
they can get to that language if they want to. I'm not sure that there are 
platforms other than TiddlyWiki that offer this possibility.

Anyway, thanks Joe for starting off an interesting thread...

//steve.


On Saturday, March 10, 2018 at 8:08:52 PM UTC-5, PMario wrote:
>
> On Saturday, March 10, 2018 at 7:25:48 PM UTC+1, Joe Armstrong wrote:
>>
>> ...
>>
>> 2) widgets - what do they return? how are they evaluated?
>>
>
> Widgets are the basic building blocks in TW. The whole UI is based on 
> widgets. 
>
> The TiddlyWiki UI starts with a transclusion of the PageTemplate tiddler. 
> Which simply speaking is a "list all tiddlers that are tagged: 
> $:/tags/PageTemplate" + some navigation handling using the NavigatorWidget
>
> TW wikitext is parsed and transferred to widgets, which produce the 
> html-dom, that the browser can use. more about this later.
>
> 
>
> A simpler example:
>
> Macro definitions are converted to SetWidgets 
> and 
> macro calls are converted to a MacroCallWidgets
>
> eg: if you go to the *TW-prerelease edtion* you can see the pare-tree and 
> the widget-tree. The prerelease contains some development elements, that 
> are missing at tiddlywiki.com
>
>  - open: https://tiddlywiki.com/prerelease/
>  - create a new tiddler eg: test-macro
>  - enter: \define hello() hello world
>  - In the edit toolbar you see: 
>
>  - *select parse-tree* and you'll see: 
>
>
> [
> {
> "type": "set",
> "attributes": {
> "name": {
> "type": "string",
> "value": "hello"
> },
> "value": {
> "type": "string",
> "value": "hello world"
> }
> },
> "children": [],
> "params": []
> }
> ]
>  
>
> -* now add the macro call*  with: <>
>
> - you'll get: 
>
>
> [
> {
> "type": "set",
> "attributes": {
> "name": {
> "type": "string",
> "value": "hello"
> },
> "value": {
> "type": "string",
> "value": "hello world"
> }
> },
> "children": [
> {
> "type": "macrocall",
> "name": "hello",
> "params": [],
> "isBlock": true
> }
> ],
> "params": []
> }
> ]
>
>
> These internal structures are created by the TW parsers 
> . 
> They produce the parse-tree. 
>
> This parse-tree is used by the TW renderer to produce the HTML output, 
> that the browser can use. 
> Every widget has a widget.render() function. ... 
>
> The module render.js 
> 
>  
> is a startup module, that kicks off the whole parsing and rendering 
> process for eg: the PageTemplate 
> 
> .
>
> A little bit earlier in the startup mechanism, the RootWidget is created 
> .
>  
> It holds a reference to the browser DOM document element, which allows all 
> widgets, to modify the DOM.
>
> hope that makes sense
> have fun!
> mario
>
>
>

-- 
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/6

[tw] Re: TiddlyWiki and Hyperstructures - "zzstructures, mSpaces, and Polyarchies"

[Steven Schneider]

Mario, thanks for the insight.

I like this q: Is it possible to represent tiddlywiki content using 
"zzstructures, mSpaces or polyarchies?

I'll continue to share here (and elsewhere) as I progress in this work...

On Monday, March 12, 2018 at 7:21:33 AM UTC-4, PMario wrote:
>
> Edited the tree to make it consistent with the text. 
>
>AA  A
> \ / 
>  B   
> / \
>C   D
>
>

-- 
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/c9108687-71d4-4337-b704-8ffa33fe8aba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Issue: I'd like to talk about Markup---broadly

[@TiddlyTweeter]

This is an interesting issue. On the one hand we have markup for wikitext 
styling using, for instance, the @@ syntax. On the other hand one 
inevitably hits a contradiction in Markup systems that are meant to be 
human readable. That to get complex styling is not sane through "Markup", 
as Jermolene put it well recently: *that would take us back to the same 
level of complexity as HTML itself. *

This is precisely why I'm as much interested in styling for specific 
Document Types as in generic markup. Markup is a blunt instrument for 
specifics IMO. Document types provide a layout that is ITSELF the TEMPLATE 
for format. This allows sophisticated styling without any explicit markup 
at all.

I slightly exaggerate. But not much.

Joe Armstrong wrote:
>
> The problem(s) I want to solve are "make the output beautiful" 
> and "make the output programmatically" when this makes sence
>
> TW seems a pretty good compromise at these - For beautiful output
> I'd have to turn TW in LaTeX of something - but I'll cross one
> bridge at a time.
>

-- 
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/f14591a6-f08d-482e-a80e-f10953d57171%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Issue: I'd like to talk about Markup---broadly

[@TiddlyTweeter]

I'm kinda of the opinion that for some types of document structures that we 
can in TW "make input even easier than Markdown"

Joe Armstrong wrote:
>
> Markdown solves the problem "make the input easy"
>

-- 
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/da09f861-05dd-4d6c-aa09-a48ba0a5eafe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Issue: I'd like to talk about Markup---broadly

[@TiddlyTweeter]

I just want to add the footnote that its easy in TW to COMBINE a "personal 
markup system" with the standard markup it has. If you composite your own 
markup BEFORE the main parser runs then you can have the best of both as 
first it would deal with your markup and then standard TW markup. The 
downside is you'd need a "Content Type" that likely only your wiki would 
have. In many cases this would not matter. 

TonyM wrote:
>
> But I would like to add this nuance,  I do often want ways to ensure I 
> have a consistent look and feel in a given solution.
>
> Perhaps this is where people get confused, because they see having YAML 
> yet another markup language as providing a consistent look and feel when 
> all that is needed is some of our own personal standards.
>

-- 
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/f51c6314-7f84-4a71-9619-e6388e82e049%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Issue: I'd like to talk about Markup---broadly

[@TiddlyTweeter]

Right

Recently Mark S. worked with Lua (inside Pandoc) to create a "proof of 
concept" converter WikiPedia -> TiddlyWiki. 
https://groups.google.com/d/msg/tiddlywiki/0Z4F7fBOBgQ/ebTapW6zBgAJ

Lua is interesting as both a convertor and a sophisticated support for 
complex formatting.

Ste Wilson wrote:
>
> Here we are.. Luatex
>
> https://www.overleaf.com/blog/571-an-introduction-to-luatex-part-1-what-is-it-and-what-makes-it-so-different

-- 
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/d18e0524-b232-400c-8ee1-4feeefd14cce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: How about a Bookmarks section on TiddlyWiki.com ?

[@TiddlyTweeter]

 
*Mark... "The thing is, they wouldn't be lost."*Bingo!

Mark S. wrote:
>
> We're talking about small bookmarks. It doesn't have to be triple-vetted 
> (it's all going to be vetted 2x -- once for the submission and 2nd when it 
> gets merged). Mediocre ideas and sensational ideas might live hand-in-hand 
> in harmony. The thing is, they wouldn't be lost.
>
> -- Mark
>

-- 
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/587090e9-c4b1-4f85-994e-e4f8247f886a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: How about a Bookmarks section on TiddlyWiki.com ?

['Mark S.' via TiddlyWiki]

We're talking about small bookmarks. It doesn't have to be triple-vetted 
(it's all going to be vetted 2x -- once for the submission and 2nd when it 
gets merged). Mediocre ideas and sensational ideas might live hand-in-hand 
in harmony. The thing is, they wouldn't be lost.

-- Mark

On Tuesday, March 13, 2018 at 7:00:14 AM UTC-7, @TiddlyTweeter wrote:
>
> +1
>
> I think that would be a good step. The issues arise in how to "metadata 
> it" & whether it should go through "peer approval." My sense is that its 
> "yet more work." I mean, WHO is gonna organise this?
>
> One thing I thought about was posting links to such "special posts" to 
> Twitter. I've largely held off because I don't feel (1) I have enough 
> competence to judge what is best; (2) not enough hours in the day as one 
> person to get it "rightly thorough". The upside would be that I could Tweet 
> just those links from a TW and then publish that TW as a resource, properly 
> tagged. I'd be perfectly happy to do that as a "holding area" for something 
> that could then also get more seriously considered. But I could not 
> reliably do the decision part of what to include alone.
>
> Best wishes
> Josiah
>
> Mark S. wrote:
>>
>> The complaint has been made frequently that good stuff posted in this 
>> forum gets lost. 
>>
>> How about we have a Bookmark section consisting primarily of a succinct 
>> title, a brief description, and a link to interesting threads in this 
>> forum? Ok, it could be to other discussions too, such as on reddit.
>>
>

-- 
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/48f1aa11-777c-47e6-85e2-d8bcc795f2fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: How about a Bookmarks section on TiddlyWiki.com ?

[@TiddlyTweeter]

Footnote.

One way to gather "candidate posts" would be to have a forwarding address. 
Both GG online and email versions of this group support forwarding. That 
seems a low-hassle approach?

Josiah

-- 
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/30f5f848-c69f-4ef4-b495-e1c503e16a79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: How about a Bookmarks section on TiddlyWiki.com ?

[@TiddlyTweeter]

+1

I think that would be a good step. The issues arise in how to "metadata it" 
& whether it should go through "peer approval." My sense is that its "yet 
more work." I mean, WHO is gonna organise this?

One thing I thought about was posting links to such "special posts" to 
Twitter. I've largely held off because I don't feel (1) I have enough 
competence to judge what is best; (2) not enough hours in the day as one 
person to get it "rightly thorough". The upside would be that I could Tweet 
just those links from a TW and then publish that TW as a resource, properly 
tagged. I'd be perfectly happy to do that as a "holding area" for something 
that could then also get more seriously considered. But I could not 
reliably do the decision part of what to include alone.

Best wishes
Josiah

Mark S. wrote:
>
> The complaint has been made frequently that good stuff posted in this 
> forum gets lost. 
>
> How about we have a Bookmark section consisting primarily of a succinct 
> title, a brief description, and a link to interesting threads in this 
> forum? Ok, it could be to other discussions too, such as on reddit.
>

-- 
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/c2220a42-7dea-4cb7-b96b-bb3948e3836a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: tiddler list with titles and tags

[Captain Packers]

Thanks Jed.

I ended up using this:

<$list filter="[!has[draft.of]tag[Task]!tag[Done]tag[Next]]">
<$checkbox tag="Done"> 
<$link to={{!!title}}><$view field="title"/> - {{!!tags}}



which creates a comma separated tag list.

On Monday, March 12, 2018 at 10:49:00 AM UTC-4, Jed Carty wrote:
>
> Yes, that is possible. Try this:
>
> <$list filter="[!has[draft.of]tag[Tasks]!tag[Done]tag[Next]]">
> <$checkbox tag="Done"> 
> <$link to={{!!title}}><$view field="title"/> <$list 
> filter='[tags[]]'><>-
> 
> 
>

-- 
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/e0caf060-820b-48e4-8b0f-6226585207d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Issue: I'd like to talk about Markup---broadly

[@TiddlyTweeter]

This discussion is really interesting!

One thing is more clear to me, from the excellent, relevant, replies, is 
how discussion of "Markup" quickly invokes multiple issues: amongst others, 
conversion, compliance standards, nice styling & working-practices. 

I'm thinking about how to restate some of the issues I was trying to make 
originally a bit more clearly so I can answer some of the points raised in 
a way that is helpful. The fact its quite difficult to articulate them is, 
I think, part of the issue too. "Markup" ideas, I think, can be a 
conceptual trap that is limiting.

ONE thing that I don't see explicitly in the replies, apart from PMario's, 
a grasp of the fundamental open (unique?) structure of TW parsing. FWIW, I 
wouldn't have written those posts without that looming in my mind. 

Best wishes
Josiah  

-- 
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/06b5e9e5-8e24-4595-8f21-33c7228b4c15%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Install Tiddlymap Plugin

[BurningTreeC]

I tried it and it works for me

I've downloaded all the tiddlymap things.. hotzone, vis, topstoryview and 
tiddlymap itself

I made a folder "felixhayashi" inside plugins/tiddlywiki - this is 
different to what you did, maybe this solves the problem
Inside that folder I moved all the folders from the 4 plugins

The felixhayashi folder then looks like: 

hotzone
tiddlymap
topstoryview
vis

The tiddlywiki.info file looks like

...
   "plugins": [
"tiddlywiki/tiddlyweb",
"tiddlywiki/filesystem",
"tiddlywiki/highlight",
"tiddlywiki/felixhayashi/topstoryview",
"tiddlywiki/felixhayashi/vis",
"tiddlywiki/felixhayashi/hotzone",
"tiddlywiki/felixhayashi/tiddlymap"
],
...

Here I put vis before tiddlymap, I don't know if that changes something, 
but I know that tiddlymap depends on vis, and if the order here has 
something to say (if!) then this would be right


Now I am running a tiddlywiki with the tiddlymap plugin working

If you follow these steps it should work for you
If it doesn't, then you should probably check where your tiddlywiki folder 
is, and if you've edited the correct tiddlywiki.info file

BTC

-- 
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/6c59b5d9-26ab-436a-81bc-410eed3e43b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Install Tiddlymap Plugin

[pandi . v]

Hi,

Thank You For your Reply.

I have deleted the *",". *Still the plugin is not installed. It does not 
show up.

Please help to install the plugins.

Thank You.

On Saturday, March 10, 2018 at 10:06:50 AM UTC+5:30, Joshua Fontany wrote:
>
> Check the syntax there, you may need to delete that last coma "," from 
> the final array item.
>
> On Wednesday, March 7, 2018 at 9:25:56 PM UTC-8, pan...@askpundit.com 
> wrote:
>>
>> Hi,
>>
>> I have tried 
>>
> ...
>>
>> 3. Updated *tiddlywiki.info * file,
>>
>> "plugins": [
>> "tiddlywiki/tiddlyweb",
>> "tiddlywiki/filesystem",
>> "tiddlywiki/highlight",
>> "felixhayashi/tiddlymap",
>> "felixhayashi/vis",
>> "felixhayashi/hotzone",
>> "felixhayashi/topstoryview",
>> ],
>>
>> Thank you!
>>
>

-- 
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/d205bebd-3989-42b4-a280-a03154404364%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Issue: I'd like to talk about Markup---broadly

[PMario]

On Monday, March 12, 2018 at 5:16:00 PM UTC+1, @TiddlyTweeter wrote:
>
> from another thread, relevant here ...
>
> Jeremy Ruston wrote:
>>
>> ... In retrospect I was far too influenced by Markdown back in 2011/12 
>> when TW5 wikitext was first being defined.
>>
>
> Side note I want to make on just this point about Markdown. I remember 
> when Markdown emerged (as an end-user / avid blogger) thinking "this is a 
> godsend". But also, "this is likely to become a somewhat messy non-standard 
> standard long-term" -- because its "just too easy." If you get what I mean? 
>

It actually is a standard type (since 2016) text/markdown (RFC 7763 
), and this makes it even stronger. 
The good thing, that markdown already had a lot of different dialects, as 
the standard was developed, they where also registered as markdown-variants 
(RFC 7764), which can be specified in the mime type. The variant servers as 
a hint for parser, what to do. .. If it doesn't know something, it just 
renders it as plain/text.

See: RFC 7764  - Guidance on Markdown: 
Design Philosophies, Stability Strategies, and Select Registrations

RFC 7764 also formalizes the registration process 
 for MD-variants. ... So TW 
syntax, that is out of range in MD atm could be made a variant, imo without 
loosing functionality.

the mime type with a variant  
looks like this: 

 Content-Type: text/markdown; charset=UTF-8; variant=Original

As you pointed out, there is a lot missing in "original" markdown, but now 
there is a formalized mechanism to register all kind of new very specific 
syntax additions. ... 
AND TW is _not_ one of them. So in the long run we will loose, if we don't do 
it right. 

As you pointed out. TW has the potential, to convert one syntax to an other 
(with some limitations). ... BUT ... not with the internal AST, that we use at 
the moment. 
See my first post. ATM we are loosing whitespace information. 

just some thoughts
mario

-- 
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/54ac0ad1-6b68-4351-b238-b73d2cd81498%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: How about a Bookmarks section on TiddlyWiki.com ?

[HC Haase]

+1

-- 
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/ae2bde1b-0db4-47cf-945f-a047782e0632%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.