from:"@TiddlyTweeter"

Ciao Reid

Your have 4 identical icons on the same row, albeit with labels above ...



Even so I'd have DIFFERENT icons. "Filter" maybe a symbol of a filter (like 
a funnel). "Search" could be a magnifying glass. Height an icon we already 
have ... 

Width something like that turned on its side.

Then you could also remove the explanatory text badges to make the layout 
more economical?

Best wishes
Josiah

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

[twdev] Re: Code review needed! BLC Plugin 0.2.0 - Release Candidate 1 (Soon to be Dropboard 1.0.0)

Ciao Reid

Not so much code-read as browser observation ... When you collapse to 
columns in the latest Chrome all is dandy ...


But in Firefox 52.3 64bit on Windows the formatting breaks.


Best wishes
Josiah

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

[twdev] Re: Code review needed! BLC Plugin 0.2.0 - Release Candidate 1 (Soon to be Dropboard 1.0.0)

Ciao Reid

I would get rid of the outer dashes. I don't think they add anything--if 
anything they unnecessarily weaken the design.

Best wishes
Josiah



Best wishes
Josiah

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/35bfc376-da1b-48f1-91bf-af9eeede3e4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: [TWX] tiddler = filter

Ciao Mat, PMario & Jeremy

I don't have skill to comment on the technical changes you suggest.

I DO have, I think, competence enough to say a couple of things about 
*functional 
outcomes*, whether now or in a "TWX".

I strongly believe that the "FRAGMENT MODEL" of TW--building wholes from 
small bits--whilst good--ALSO needs complementing with a clearer "WHOLES 
MODEL". Most ordinary uses think in terms of final objectives and, at the 
moment, it can be hard to get a clear sense of HOW you get bits to mesh 
into wholes. Anything that eases that would be a good outcome IMO. One that 
might also help increase the userbase.

Mat put it like this: 

> make TW more *suitable* for narrative applications like creating 
> documents or "multi page things". Currently, TW is a kind of "digital 
> post-it note manager". The OP would widen TW to also be a kind of document 
> manager. 
>

PMario like this:

>  - structured stories,
>  - export content eg: into 'stand alone' web sites and 
>  - compose or re-compose 'stories' with a simple drag and drop mechanism."


One quite large part of that same functional issue--making WHOLES--I found, 
slowly through experience, is how ID's function in TW.  They work 
differently than in normal web pages being reserved for Tiddler Titles. It 
makes it much HARDER to generate longer web pages with built in navigation. 
Its also counter what most everything else is doing so newbies more used to 
the normal approach can struggle with it. Though to solve that I see that 
would needs be more a "TWX" innovation than a TW5 one?

Best wishes
Josiah 

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

[twdev] Re: Code review needed! BLC Plugin 0.2.0 - Release Candidate 1 (Soon to be Dropboard 1.0.0)

Ciao Reid

The "on hover" text for ...



... reads "Drop tiddler here to place in list position."

I suggest changing it to something like ...

"Drop tiddler here to title a new column."

Best wishes
Josiah

On Friday, 6 October 2017 21:02:36 UTC+2, Reid Gould wrote:
>
> BLC Plugin  (soon to 
> be Dropboard) is almost complete, all features and interface changes have 
> been done and are ready to be finalized. Internals have been refactored and 
> tidied up. 
>
> But before the big rename and version bump, it could really use the one 
> thing it hasn't gotten yet, which is a good code review. 
>
> The plugin is entirely implemented in WikiText, Widgets, and Macros. No 
> original Javascript is used. As WikiText is very dense, there is actually 
> not much code. The unminified built tid file for 0.2.0 clocks in at 94 KB.
>
> If there is anyone interested or willing to do me (and those in the 
> community who use it) a huge favor by reviewing, I recommend starting at 
> the main view template, "Board.tid":
>
>
> https://github.com/reidgould/tiddlywiki-blc-plugin/blob/0.2.0/Source/editions/blc-plugin/plugins/blc/tiddlers/templates/view/Board.tid
>
> The "User Guide" demo linked above will have many more examples of use and 
> much more documentation when Dropboard version 1 comes out, but for now if 
> you just try out all the buttons and drop areas (shaded) you should be able 
> to see how most things are supposed to work. If anything doesn't do what 
> you expect, I'm happy to chat with you about its intended purpose here.
>
> All comments are welcome. If you have a GitHub account, I prefer issues to 
> be started there.
>
> At this time I'm mostly looking for any problems with the main macros 
> 
>  that 
> do the listops, display bugs (try out themes and different text sizes), or 
> performance issues. Requests for changes to features or new feature 
> requests are welcome, but won't be addressed till after version 1.
>
> This has been a very fun project and I can't wait to finish it.
> Thanks to anyone who takes a glance.
>
> - Reid
>
>

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

[twdev] Re: Code review needed! BLC Plugin 0.2.0 - Release Candidate 1 (Soon to be Dropboard 1.0.0)

Ciao Reid

I know my comments were not about code. But still relevant, I think. And I 
hope useful.

FYI I tried to break the basic functions but it seems robust so far.

Best wishes
Josiah

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

[twdev] Re: Code review needed! BLC Plugin 0.2.0 - Release Candidate 1 (Soon to be Dropboard 1.0.0)

Ciao Reid

Honestly I'm between a rock and a hard place. Between Riz's visuals and 
your superb logic. Not wanting to offend either of you.

The point is that the tiddler you asking me about is not scaled up to the 
point that its free enough yet. Of course it looks crap (in both versions), 
because the CONTEXT is inappropriate for wide flow. That would come with 
full screen takeover IMO. I hope you get my point.

Best wishes
Josiah  

On Saturday, 7 October 2017 21:22:32 UTC+2, Reid Gould wrote:
>
> Josiah,
>
> Here's a comparison with the side borders on and off. This image shows the 
> case of a board that is partially scrolled in the horizontal direction. The 
> borders are intended to reduce the broken visual effect of the list cutting 
> of in the middle. If you have a suggestion for a different way to handle 
> that case, I'd like to hear it.
>
>
>
> <https://lh3.googleusercontent.com/-MrO13xyY7hs/WdkpAes_aHI/Dxw/yy7FAceN5wUrD_4T-OjHT6E5B7wtkb8UgCLcBGAs/s1600/bordersOn.png>
>  
> <https://lh3.googleusercontent.com/-2GTNsfy4Khs/WdkpEN7SckI/Dx0/9lk-F9RQu-kG31tLjWWVSaK3ue3UJhzmQCLcBGAs/s1600/bordersOff.png>
>  
>
>
> - Reid
>
>
> On Saturday, October 7, 2017 at 9:16:59 AM UTC-5, @TiddlyTweeter wrote:
>>
>> Ciao Reid
>>
>> I would get rid of the outer dashes. I don't think they add anything--if 
>> anything they unnecessarily weaken the design.
>>
>> Best wishes
>> Josiah
>>
>>
>>
>> Best wishes
>> Josiah
>>
>

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

[twdev] Re: Code review needed! BLC Plugin 0.2.0 - Release Candidate 1 (Soon to be Dropboard 1.0.0)

2017-10-09 Thread @TiddlyTweeter

Ciao Reid

Duh! my bad for not paying more attention. My only excuse is its feature 
rich & takes a while to grasp all it can do.

Josiah 

Reid Gould wrote:
>
> You can get the fixed width in the normal view by setting a value inside 
> the popup that appears when you click the "width" control button. The 
> default used in the window mode is 16.
>

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

[twdev] Re: [TWX] Naming "X"

2017-12-16 Thread @TiddlyTweeter

Ciao Tobias

FWIW, I think there should at least be a *TW5 vs. TWC* tiddler on 
> tiddlywiki.com,
> seeing how much the two are being used, esp. in the groups.
>

Right. I hadn't thought of that route. 

It makes a lot of sense to me to help new users understand the differences 
between TWC & TW5.

I do think "how  to start using TW?" is a broad issue of interest & 
relevance. Whilst "saving" is one major issue, especially at the moment 
(albeit we have multiple ways forward), "TWC v. TW5" is another that is 
also still in play.

Best wishes
Josiah

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

[twdev] Re: What causes the slowness?

2017-12-06 Thread @TiddlyTweeter

I have no idea other than TW5 is pretty complex. AND that if you reduce the 
sidebar, especially anything tracking a history, to bare essentials 
everything speeds up.  

J.

On Monday, 4 December 2017 17:25:23 UTC+1, Mat wrote:
>
> This is really a question way above my head but I'm just curious;
>
> Slowness is a particularly noticeable bottleneck in TW. This forces 
> compromises, e.g the sidebar lists are better not too long and the editview 
> selection of tags can be painful.
>
> What would you (the skilled coders here) say is the main cause of this? Is 
> javascript a slow language per se? Is it some fundamental structure of TW? 
> Maybe the plentitude of divs in TW? Is it simply that browsers are not made 
> for several MB's of loaded data? Have we chosen algos that are 
> less-than-optimal for perfomance but beneficial for something else? Do we 
> use recursions-in-recursions at a very early level in the structure?
>
> And what makes TWC snappier than TW5?
>
> <:-)
>
>

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

[twdev] Re: Making a formulas/computing plugin; seeking feedback & advice

2017-12-12 Thread @TiddlyTweeter

Ciao Evan

Sounds interesting. I'm very keen to use TW to do basic accounting. So far 
none of the existing solutions are quite there. I think its partly a design 
issue. One needs a framework of thinking that embraces what basic 
accounting ledger work involves. Its not just about smart columns. Its also 
about being able to (1) factor out trends (budgets, averages etc.) (2) be 
able to extract/present/print data in a way an accountant would be happy 
with. My 2 cents. 

You might want to look at Jed's work that tries to take some of that into 
simple expense tracking http://ooktech.com/TiddlyWiki/ExpenseReports/. The 
discussion 
 
around it may be interesting to.

Here's my progress after two days' tinkering:  
> https://evanbalster.com/tiddlywiki/formulas.html 
> 
>

I'd love to look but the site is not resolving for me. And both FF & Chrome 
throw a certificate error.

Best wishes
Josiah

Evan Balster wrote:
>
> For perhaps a year or two now I've had my own ideas about how to approach 
> making something like "spreadsheet formulas for TiddlyWiki", something I 
> know many other folks are interested in.
>
> Currently I use a macro-based facility in my accounting wiki.  I'm also 
> aware of Tobias Beer's "let filter".  Just today I became aware of the 
> impressive MathCell project...  However, I feel somewhat strongly that 
> "formulas" should be a general-purpose idiom on the level of filters, 
> transclusion and macros — that is, they should be possible to use in 
> WikiText, as attribute values and potentially also in filters.
>
> Right now I'm dipping a toe in the water of TiddlyWiki module development, 
> and I'll be interested in guidance and feedback as I approach this task.  
> This is my first JavaScript project (!) and my first dive into TiddlyWiki 
> core logic.  However, it's not my first dataflow compiler project so I'm 
> making quick progress.
>
>
> Here's my progress after two days' tinkering:  
> https://evanbalster.com/tiddlywiki/formulas.html
>
> No operator parsing yet, but formulas are functional.  They can process 
> transclusions, filters and variables, and basic arithmetic and summing 
> functions are provided.  I decided to go with a "mushroom bracket" syntax 
> like the below for the wiki parser:
>
> (= add([tag[Expense]get[value]], {{Soda-Pop!!value}}) =)
>
> There's also an <$eval> widget that exposes a few more options.
>
>
> I'm trying to keep the syntax and behavior close to that of formulas in 
> Excel/Google Sheets while preserving TiddlyWiki's native idioms for data.  
> (If the plugin is paired with a suitable spreadsheet UI, there could be a 
> case for a "range" syntax in the future — but for now it's focused on 
> fetching from Tiddlers.)
>
> Probably my biggest misgiving at this point is that my approach has had me 
> re-inventing some source processing.  The plugin has its own (small) 
> compiler, and I'm left wondering if it would be more sensible to have the 
> widget "eval" its children and defer more to the wiki parser.
>
>
> Anyway, very interested in feedback about syntax, bugs and code review.  
> I'll be particularly interested to see if Jeremy has any good tips on 
> architecture.
>
> -- Evan
>

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

[twdev] Re: Making a formulas/computing plugin; seeking feedback & advice

2017-12-12 Thread @TiddlyTweeter

Ciao Evan

I looked at your TW. I can't really comment fruitfully further other than 
say it looks like its in a good direction. I'm not a programmer so am 
useless on giving code guidance :-(. 

I can be helpful on what an accounting app could look like. Some of that is 
covered in the post I made to Jed I gave link to in my last post. And I'll 
more than happily comment on anything when I can see what an end outcome 
for accounting might look like.

Very best wishes
Josiah
 
 
Evan wrote: 

>  Here's my progress after two days' tinkering:  
>>> https://evanbalster.com/tiddlywiki/formulas.html 
>>> <https://www.google.com/url?q=https%3A%2F%2Fevanbalster.com%2Ftiddlywiki%2Fformulas.html=D=1=AFQjCNFVx3tbZHBO1f6OD6SOaOBolcbF4Q>
>>>
>>
@TiddlyTweeter replied:

> I'd love to look but the site is not resolving for me. And both FF & 
>> Chrome throw a certificate error.
>>
>
PMario helped out:

> I used http:// ... 
>

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

[twdev] TWX / Or TW5+ -- Infinite Markup Options?

2017-10-25 Thread @TiddlyTweeter

I'm writing this here for lack of anywhere else. Its not up to Github
standard so I can't post it there. But I think the issue is real and its
more than the usual TW problem solving.

I have been using BJ's excellent "Flexity" Plugin
for some weeks now. Its basically
opened my eyes to ..

(1) The central role of Parsing in TW.

(2) The flex you can get when you can switch OFF some of the extant
parsing rules and replace them with alternative markup.

(3) The ease of using Regular Expressions (via BJ's method) to create
totally new systems of markup very economically & efficiently without
having to edit JavaScript.

WHAT is my point?

My point is that IF the current architecture of parsing could be opened up
so that it were much easier to add "User Content Types" via markup mediated
by a simple cascade of regular expressions (NOT via individual Javascript
modules as is) for many use cases it could open the way for TW to become a
near "Universal Markup Engine".

Over the next few weeks I hope to release a fully honed TW application for
screenplays that uses the pure, standard, *Fountain Markup* system. But
even without that yet complete I'm sensing that better, easier interface
with the TW Parsers--and an easier way to add new parsing rules without
recourse to JavaScript could be seriously healthy step for TW or TWX.

Best wishes
Josiah

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

[twdev] Re: Why "sharing of tiddlers" is a linchpin for success

Exactly why TW in the wild inclines to the "centrifugal". 

The "centripetal" is MISSING. That lack maybe part causes the fragmentation 
you are talking of.

I don't think this is about waiting around more ... I mean how many years 
you (everyone reading) been here already?

GIVE me a format. Lets get on with it :-)

Josiah

Mat wrote:
>
> This should also answer your request for:
>
> IF I, say converted David's list, WHAT would be the best format (basically 
>> fields defined and filled for every Tiddler?) that is optimal for sharing? 
>> Where's the list :-)?
>>
>
> ...i.e; I have no idea. Nobody can know this yet. It may depend on how the 
> sharing is implemented. It may also depend on *what people want to do 
> with it: *For example, Twitter has that fixed number of characters limit 
> so if, for some reason, sharing typically ends up as tweets then that would 
> of course affect what is "best format". Just not possible to know at this 
> stage.
>


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

[twdev] Re: Why "sharing of tiddlers" is a linchpin for success


>
> Mat: Nobody can know this yet.


I disagree. I DO think it is important a few people, TW "experts", examine 
it to make sure its broad enough. But to say "Nobody can know" is just 
silly.
 

> Twitter has that fixed number of characters limit so if, for some reason, 
> sharing typically ends up as tweets then that would of course affect what 
> is "best format". Just not possible to know at this stage.
>

FYI, Twitter in now 280. It will fit fine. I'd make sure in my case. IF 
somebody else made another 500 I could use that were longer that 280 total, 
those I'd edit in Tweet. Easy.

It may also depend on *what people want to do with it: *


No. A definition of what data is essential to adequately capture a resource 
should be as wide as seems doable. That leaves end users free to do what 
they want. They don't define it. They use it.

As I said, lets get on with it.

Josiah

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/827e903a-f633-49d0-87b9-0ab9d16c57b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: Why "sharing of tiddlers" is a linchpin for success

Jed Carty wrote:
>
> I tried to start a listing of plugins that I was hoping to extend to other 
> tiddlywiki resources that is similar to what you are describing but then I 
> got distracted and I don't think anyone else really started using it. What 
> I made is here: http://inmysocks.tiddlyspot.com/#Plugin%20twCard
>

Its a really good resource. 

I agree that getting it really used likely needs other steps. Part of the 
issue is, I think, "what are we doing" -- I mean is this an exercise in 
one-off excavation? Or is it a viable, sustainable thing?

Part of MY interest is to document the mess (since David did it already). 
Get it over with and maybe help develop a shared data structure such that 
data resources are more easily found.

One thing that goes on that is rarely mentioned is Erwan's aggregator. What 
I seen of it its quite a neat idea. Under subscribed and not that 
developed, but it works. I think there is mileage in the approach?

J.

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

[twdev] Re: Why "sharing of tiddlers" is a linchpin for success

Ciao Mat
Ciao Mat

I think concrete examples help.

My use case. I like to try promote TW (though promotion is not on your
list :-) on Twitter because its effective and Twitter I know well. There is
an infinite listening audience there. I am doing 7,000% less than I could
because every bl**dy TW resource I want to point to I have to research,
find the address for documentation and the install, know if the author
needs acknowledging on Twitter (i.e. are on Twitter or not) etc, find them
there, craft a post, check it.

*PLEASE give me standardly laid out tiddler for every resource worth
posting about ...*

1 - download address
2 - documentation address(es)
3 - support address
4 - author address(es)
5 - data of release or version # if available
6 - description

Then recycling info over Twitter would be a doddle and we could begin to
dance it.

Ideally I'd like to generate a resource list from a Tiddler set of, say,
600 resources, output it to a Twitter robot poster and leave it get on with
it for six months at a time. Then I can concentrate on responding to
questions about them, not the hand-crafting of them.

As is its unviable. *And a consequence is TW is not getting the important
exposure it deserves.*

Right now I'm looking to use David Gifford's TiddlyToolmap, since its the
most comprehensive list around. But that is huge work as the entries don't
come up in a browser in any standard way (as there is NO standard way
defined for listing a resource). That is NOT usable for a wider audience
who need a standard approach so it doesn't get confusing. So I still have
to check every entry and re-write it. That's too much to do often.

Regarding your own depiction of example scopes ... IMO I think its
important to define the Final Usage of "Data" as precisely as possible in
order to layout what you talking about in practice--down to the level of
fields and whatnot. I think your list may be currently too broad...

Mat ...

- contribute code to e.g Github (probably via an API)
- co-develop TW stuff without e.g Github
- collectively build repositories (for e.g plugins)
- collectively build documentation
- discuss TW stuff
- discuss non-TW stuff

Delimited basic resource finding I suspect is critical across the board at
the moment? (Not saying no to anything else, just trying to find a viable
handle to work forward from.)

Just thoughts
Josiah

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

[twdev] Re: Why "sharing of tiddlers" is a linchpin for success

Ciao Mat

Further to my last, and hopefully on-point.

IF I, say converted David's list, WHAT would be the best format (basically 
fields defined and filled for every Tiddler?) that is optimal for sharing? 
Where's the list :-)?

This immediately brings up the issue of legacy. IMO getting legacy a bit 
more ordered is a good step? The other route is automation "in-future" with 
smart new methods. But I do think the fragmentation of resources we have 
now IS a large part of what we have now so there needs to be some enfolding 
the old into a new approach?

Just thoughts
Josiah

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

[twdev] Re: Why "sharing of tiddlers" is a linchpin for success

2018-06-11 Thread @TiddlyTweeter


>
> Mat: maybe I'm naive and disregard fundamental problems?
>

I think you are Hot On -- EXCEPT on the question of legacy. On which you 
don't seem to see the issue.

The future will come not just with a shiny new system (I am in favour of) 
it will also be because of a BRIDGE to the past. 

My concern is HOW to document the past work (that is huge) so that it can 
be included. As IS FOUND now. Not requiring a user to change anything.

So I see this as about two things ...

(1) shiny new system

(2) a data STRUCTURE under which old stuff can be organised.

I hope this is clear.
Josiah

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

Re: [twdev] Re: Should TiddlyWiki consider moving to GitLab?

Ciao PMario

I emailed David about this thread ... he replied ...

*I would hope that the people to whom you wrote would feel free to use the 
> info in my toolmap to create similar things according to the criteria they 
> set.*
>

A notable point about Dynalist is that its exportable as OPML. Just about 
the simplest format imaginable. It would be easy to migrate to anything. 
The really hard work on these resources is getting a starting point. That 
is there. Needs perfecting, but its there.

PMario wrote:
>
> It's not this single project I'm aiming at. I want to have the possibility 
> to cover all projects listed there, where it makes sense __and__ If their 
> authors want to!
>

IMO the issue is bang-for-buck. 

Meaning "what resources are the least work to garner and hone for the 
objective?" I think TiddlyToolMap is a pretty much number one because of 
its scope. Its weak in few areas (like setup), but not many compared to 
everything else.

Best wishes
Josiah

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/33cd1f22-37c7-42f3-9c29-2826c584b464%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Seeking Thoughts On ... embed / object / iframe in TW

Thanks Andreas, that is helpful info.

On Friday, 8 June 2018 14:53:32 UTC+2, Andreas Hahn wrote:
>
> Hi Josiah, 
>
> from what I can tell, in certain browsers, the use of the  tag 
> disallows the javascript contexts of both sites to communicate via 
> messages. This would be the desired behaviour when embedding things into 
> your tiddlywiki, as  where it is allowed are also allowed to 
> inject javascript into your wiki, effectively taking it over, should it 
> be a malicious site. 
>
>
> /Andreas 
>
>

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

Re: [twdev] Re: Should TiddlyWiki consider moving to GitLab?


>
> PMario ...
> eg: GifMex'es tw-dynalist is a great resource:  
> https://dynalist.io/d/zUP-nIWu2FFoXH-oM7L7d9DM ... But he had to tell the 
> community, that he's on holyday, so the list won't be extended for several 
> days! ... That's a problem. ... Not the holydays, but the "helpnessless" of 
> the community. ...
>

I want to comment more about this in some detail because its important to 
functional dynamics.

And to get away from the idea somehow you people on GitHub know what you 
are doing beyond GitHub. There is little evidence you do! :-).

I been around TW now long enough to see an innovation when its there. I 
seen serious initiatives on Reddit, on Stack Exchange start and stall. I 
complained endlessly when I started about "documentation".

Gifford's "Out Of The Blue" initiative on TiddlyToolMap emerged from his 
own frustration with not being able to find things. And on that he 
put-his-finger-on-the-issue ... *its NOT lack of information, documentation 
or resources that is the main issue, it is FINDING them.*

He has given the start of HOW to find what you need when you need it. His 
work, far more than anything I have ever seen, illustrates that issue and 
begins to solve it. 

His solution is clunky, imperfect & limited to his time available. It has 
to be. One person handling masses of info. 

I love he is imperfect, limited and can't avoid being clunky. Because he 
DID it.

So whilst "you" (no pointing) may see a need for all this to be under an 
umbrella, until such time as you provide both the mechanism and people to 
do it, I'd say people like David are still our best bet. 

So, unless you have a better way formed, better to just say "it's really 
good!" Which it is.

FYI, I am aware he is time limited and agreed to handle Twitter 
announcements for him.

Side thoughts, but not entirely irrelevant
Josiah

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

[twdev] Seeking Thoughts On ... embed / object / iframe in TW

My case: I would like to make a TW that often shows in a box other sites. 

People warn me: 

*That is dangerous. If you don't know what you are doing a cracker could 
eat you.*I'd like to be clearer about security of object v. iframe ... 

I notice that HTML5 iframe has sandboxing options. 

I have no idea if object (being used for pages, NOT video or audio or 
images) is a safe idea for windowing of remote sites in general. 

Before I go on with this I'd appreciate any general comments, thoughts 
about basic steps I need to look at. Nothing huge, just a pointer or two.

Many thanks for any help
Josiah 

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

Re: [twdev] Re: Should TiddlyWiki consider moving to GitLab?

Ciao Jeremy and all

This is a comment slightly from a weird position (probably) from your point 
of view. I'm not thinking here as a developer. I'm thinking as a social 
anthropologist.

I am reading several discussions at the moment about proposals for 
innovation in development process, documentation and addressing user needs 
better.

I am, frankly, feeling some of this effort could be wasted because IMO the 
single biggest danger with TW is *yet more fragmentation*. The GitHub side 
is the most integrated and consistent at the moment. 

Out in the world of end-users some of us are struggling to 
join-the-informational-dots of the scattered resources so everyone knows 
what is where. just finding things, plugins, tutorials, example TW etc is 
almost a full-time job.

On the dev end my concern is: could the desire to improve actually have 
unintended consequences that actually increase fragmentation?

Just thoughts
Josiah

Jeremy Ruston wrote:
>
> *My point wasn't about access control. It was that I am not in favour of 
> splitting the TW5 repo up* (e.g. moving each translation to its own 
> repo). The reason is that it becomes harder for users of the repo to 
> manage, making sure that they have cloned the right repos, and that they 
> are all synced together. The current state will always be in sync, but it 
> is hard to, say, reconstruct what the repos looked like on 11th May 2016. 
> This is a somewhat controversial area but this "monorepo” philosophy is 
> widely practiced for large scale projects (e.g. Google stores billions of 
> lines of code in a single repo).
>

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

[twdev] Needed: A Basic Data Format For Sharing

2018-06-16 Thread @TiddlyTweeter

David Gifford's TiddlyToolMap
has succinctly illustrated
THE way to solve much of the fragmentation of resources TiddlyWiki lays in
adopting structures for shared info on (a) resources; (b) documentation.

TiddlyToolMap emerged from David's own frustration of not being able to
find what he needed at the time he needed it.

His solution was simple: collect on a list, with basic categories, links to
major useful innovations.

Its imperfect, not comprehensive, somewhat messy when looking at items as
there is no standard of presentation, and it includes nothing about whether
a solution will all work in all TW generations.

BUT the key points are:

- largely it works;

- its the only attempt of its kind currently alive;

- he is happy its taken on, as he says: *I would hope that ... people
... would feel free to use the info in my toolmap to create similar things
according to the criteria they set.*

- most IMPORTANT, it is being picked up on in the wild as a major
resource repository ... see, for instance, this German blog post:
https://toolblog.de/2018/06/16/die-ultimative-liste-fuer-tiddlywiki/?

TiddlyToolMap is a VERY good example of "auto-marketing".

It fills a need, and despite being very crude in structure, and sometimes
painful to use, it DOES "hit the spot" of "Wider Use". It appeals. Is
increasingly used. And addresses the lack of a full Resource Base elsewhere.

It is for these reasons I ask you help to develop a BASIC DATA FORMAT FOR
RESOURCES (i.e. a list of minimal fields that can capture and organise
plugins, macros and documentation) so that David's resource could be
exported in a FORM that can be used and developed and NOT get lost.

Yes?

Please feel free to ask questions if anything I wrote needs clarifying.

Best wishes
Josiah

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

[twdev] Re: GitHub CDN

2018-05-29 Thread @TiddlyTweeter

Fascinating about that is the huge detail the developer gives about what 
happens if he dies.

https://github.com/jsdelivr/jsdelivr/wiki/What-to-do-if-I-die-aka-The-bus-factor

I do think that kind of forward thinking is excellent.

On Tuesday, 29 May 2018 21:20:31 UTC+2, Mat wrote:
>
> Apropos the current hullaballo around external databases, here is one 
> using github which should be interesting considering the TW projects use of 
> github. 
>
> https://github.com/jsdelivr/jsdelivr
>
> <:-)
>

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

[twdev] Re: Improving TiddlyWiki 5 web server functionality

2018-06-23 Thread @TiddlyTweeter

Most welcome ...
 

> * A new module for serving static file attachments over HTTP
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/b16dc823-1e44-491a-b395-537ca64d17b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: Needed: A Basic Data Format For Sharing

2018-06-20 Thread @TiddlyTweeter

Ciao TonyM,

TonyM wrote:
>
> I have being looking closely at the optimum way to represent all resources 
> us TiddlyWiki enthusiasts use in the process of developing a Community 
> resource website, also within my own network of wikis I have built informal 
> standards around storing such things in Tiddlers. This is not yet 
> exhaustive but that is where I am headed.
>
> Basing everything on a tiddler model makes sense because they immediately 
> become shareable, and can carry the required tags to make them work.
>

I agree on the end-sharing part. But I'm not so convinced on single TW's 
dynamic in creating the "feeder resource". Mark S., over in the other 
thread I started on thi 
s 
suggested something like a MediaWiki where its a shared dedicated resource 
base/lister. That makes sense, I think. 

Right now I'm personally interested in trying to leverage David's data into 
a format I can use more easily to Tweet to the Twitter TiddlyWiki group 
where I'm pretty sure posting more entries from it would be welcomed.

And I think that illustrates my main point. 

That David's list has had great effects. And helping him, or branching it 
into other formats, could be great for (a) Existing Users; (b) More 
actively Promoting TW and the huge range of what it can do. 

So whilst I do see sense in Tiddlerising it, I'm interested too in simply 
fieldising it in a way that can be used in various ways. The two things are 
not at odds.

I suppose my point is this is about knowledge and information management 
> and we have the perfect tool for this, tiddlywiki all we need to do is 
> promote some defacto standards and share them.
>

Right. I guess some kind of "standard format" for resource listing would 
eventually be ideal. But with a collaborative framework for additions too. 
Something like that.

Best wishes
Josiah

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

Re: [twdev] Performance note: Adding variables to selective refresh

2018-01-10 Thread @TiddlyTweeter

Ciao Evan

*Interesting test. The difference is visible.*

I'm wondering if simple users like me could ever get to benefit from a 
"test your TW Efficiency" plugin to better isolate issues?

A specific emergent USE CASE is that TW is getting more "grid-layout 
friendly". I'm sure users will tend towards having many more Tiddlers open. 
Personally
* for very short Tiddlers I'd like to have hundreds open simultaneously 
that I can dynamically filter down to just what I need to see (the filtered 
out remaining in memory but hidden).*
Your thread alerted me that decent performance might be possible on that 
but also I need to be more aware of what is going on to ensure it. Dunno 
how else to explain this. But I hope you get the general idea: performance 
and utility are related. I'd rather not be inhibited opening zillions of 
Tiddlers, but IME its an issue.

Best wishes
Josiah

Evan Balster wrote:
>
> The test-case mentioned in my last E-mail can be seen here:  
> https://evanbalster.com/tiddlywiki/formulas.html#Harmonic%20Lattice
>
> Try moving the "interpolation" slider around with and without $noRefresh 
> enabled, and note the difference in framerate.
>

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

Re: [twdev] Re: TiddlyWiki 5 Dev Hangout #104 will be on Wednesday 17th January at 3pm GMT

2018-01-17 Thread @TiddlyTweeter

*Hangout #104*

I enjoyed it. It was lively. It was really informative.

PMario was *particularly excited*--wonderful voice when happy and in his 
stride. 

It was nice to hear *Abraham chip in* as he's done great work outside the 
fold. 

*Evan looks too young* to be so clever ... lucky bastard.

*Jeremy's monotone* is seriously deep. The Leonard Cohen of software?

Josiah


On Wednesday, 17 January 2018 16:04:41 UTC+1, Jeremy Ruston wrote:
>
> The hangout is about to start.
>
> Watch at http://youtu.be/ts1jx-_ih2A
>
> Or join in at 
> https://hangouts.google.com/hangouts/_/ytl/wM9j-qa30GbkJyh30N0dsA5AXPM4Klj3ALqXFZoYmFk=?hl=en_US
>
> Best wishes
>
> Jeremy.
>
>
> On 17 Jan 2018, at 10:48, PMario  wrote:
>
> hi,
> I'll be online.
> -m
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywikide...@googlegroups.com .
> To post to this group, send email to tiddly...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywikidev/114ef251-1bf4-4120-81c9-08df8038015e%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

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

[twdev] Re: Timer plugin, and iterative computation in TiddlyWiki

2018-01-15 Thread @TiddlyTweeter

I hope this comment doesn't stop the clock

Evan Balster wrote ...

>
> Elsewhere in the wiki you'll find an "auto-map" also based on the formula 
> plugin:  https://evanbalster.com/tiddlywiki/formulas.html#Auto-Map  This 
> was implemented before element-wise calculations were possible in formulas, 
> so the algorithm is entirely ineffective, but this draft serves as an 
> example of a much heavier iterative algorithm (with many, many more 
> setfield widgets).
>

Seriously good. Very promising. Auto-mapping. Give the cells a link and you 
are there.

Josiah, x

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

[twdev] Re: My First Release Plugin

2018-01-21 Thread @TiddlyTweeter

>
> Diego Mesa wrote:
>
> Just want to mention, I've used the excellent tinka plugin:
>
> https://tinkaplugin.github.io/
>
> to package and edit plugins.
>
> I have also noticed it seems to conventional to include minimal 
> documentation, but I am not so sure why. I always have to end up refering 
> to another website to look up details about a plugin I;ve already 
> installed. I would suggest just bundling much more thorough documentation 
> and (at least some) examples will all plugins - just my opinion though!
>

Some people do include more documentation in their plugins to good effect.

Part of the issue is, I think, that its not so easy to KNOW what is needed. 
A developer in midst of something that is now transparent to them is not 
necessarily able to fully grasp what is needed by an end user. On the one 
hand you want only what is enough. On the other its in everyone's interest 
that there is enough documentation. 

I do think some superb plugins are UNDERUSED because they are not so well 
documented.

Josiah

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

[twdev] Re: My First Release Plugin

2018-01-31 Thread @TiddlyTweeter

This plugin is not Yet Published or Working on this site
erm... that's a bit confusing! :-)

J, x

On Wednesday, 31 January 2018 08:43:21 UTC+1, TonyM wrote:
>
> Folks,
> Almost there,
>
> I have used Tinka to create the plugin
>
> The Pre-release in on this site http://tiddlywiki.psat.com.au/mymenus/
>
>
> As mentioned previously my current plugin content list is attached
>
> You will notice the $:/PSaT/MyMenus/manager 
>  is 
> not in bold
>
> I discovered the menu item that should appear in the sidebar tab does not 
> display until I edit it.
>
> Why would it not work until edited?
>
> Can anyone help me with this please?
>
> Tony
>
>
>
> On Thursday, January 18, 2018 at 11:37:25 AM UTC+11, TonyM wrote:
>>
>> Hi Developer folks,
>>
>> I am using tinka to build my My First Release Plugin. I am a little 
>> unclear about the importance of naming standards,
>>
>> My Current design has tiddlers with the Prefix $:/PSaT/PluginName/various 
>> tiddler names
>>
>> PSaT is the initials of my Business name People, System and Things.
>>
>> Is it fine to keep these in this naming standard? even although the 
>> plugin will be at $:/plugins/PSaT/PluginName?
>>
>>
>> Must I create before packaging even if the other content is using the 
>> above prefix?
>> $:/plugins/PSaT/PluginName/readme
>> $:/plugins/PSaT/PluginName/licence
>>
>> I am trying to do what is correct.
>>
>> Thanks
>> Tony
>>
>

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

[twdev] Re: My First Release Plugin

2018-01-31 Thread @TiddlyTweeter

Ciao Tony. 

I have never published a plugin. Sorry to say.

Josiah

TonyM wrote:
>
> But the statement is somewhat true, it remains version 0.0.x the key menu 
> does not load automatically in the sideBar and I need to resolve the above 
> to proceed.
>
> Any ideas? Have you published a plugin before?
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/6e01fcb4-d336-44f6-82bc-d795524307d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Proposing more sane fault tolerance for "unclosed" tags & markup

2017-12-20 Thread @TiddlyTweeter

Ciao Evan, Jeremy & Tobias

Jeremy Ruston wrote:
>
> An alternative that I have seen in other markup implementations is to 
> treat line break as closing all open inline formatting elements. 
>

Right. That behaviour is what I have see too. I suspect that's because the 
simpler versions parse only a line at a time and just substitute HTML for 
inline markup shorthand using regex that matches pairs sequentially. 

That would also have significant impact on backwards compatibility, but 
> might be easier to implement. 
>

Right. How much and often it would break back compatibility I'm unsure of.

IMO all the lightweight markups got a bit out of control (see: CommonMark & 
Babelmark 2 [A Markdown comparator]). They are easy. But parsers tended to 
make it too easy to get away with fouling the footpath with malformed 
markup by, typically, second guessing closing tags when only opening tags 
had been created.

I think Tobias' point is worth attention ...

> Rather than try and be smart or "graceful" about it,
> we should *stop all parsing completely* and throw an error ...

Why? Because if you try to automate on all anomalies you end up with an 
over complex smorgasbord to maintain. 

I think the one issue behind the problem is NOT just about poor final 
render in edge cases. Its also about tolerance (or not) of user behaviours 
on their original marking-up that code ends up over-supporting.

Best wishes
Josiah

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

[twdev] Re: Idea: input text-field with integrated "confirm" button

2018-07-28 Thread @TiddlyTweeter

Ciao Mat

I fully agree with you. What you propose would simplify the current 
situation to good benefit for many use cases.

Here is a USE CASE: I create a series of several hundred Tiddlers of Film 
Title data. Once created a film student will often want to revise the 
content of various fields (e.g. YearReleased, Synopsis, AspectReatio, 
LogLine etc) of a Tiddler without entering the full editor. Handling other 
Tiddlers in order to help process the data on a larger data set like that 
can get over-complicated. Far better for this type of app. to have one 
Tiddler per record and no dependencies.

Would ...

-- simplify user code

-- make the life a "tweaker" easier.

My 2 cents
Josiah

Mat wrote:
>
> This is a proposal to extend the EditTextWidget or possibly introduce a 
> new widget to be a simple-to-use unit for user input.
>
> *Problem*
> The EditTextWidget does not work for modifying the *current* tiddler nor 
> for macros due to tiddler refresh after each entered character. And the 
> possible "circumventional solutions" put a lot of burden on the user and 
> forces use of additional tiddlers.
>

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

[twdev] Re: Merge some advanced search into search

2018-07-28 Thread @TiddlyTweeter

Ciao Mat

Interesting discussion.

Mat wrote:When hacking, I find it annoying to constantly have to pull up
> the "advanced search"... but it just struck me; Can't standard search
> simply also be a "filter search"?
>

Even though its not exactly the same territory, the thread touching into
PMario's "advanced-search-plus", does have some relevant observations:
https://groups.google.com/forum/#!msg/tiddlywiki/tWo3S6sEwTs/QIzQhC7PCAAJ
that relate to functionality, not just a different layout.

I thought Diego Mesa's post about "simple search everywhere bar" was also
interesting with its idea of an *intelligent recognition* of the search
type.

I spent, myself, a couple of days, looking at how I actually search. These
are my conclusions on you idea of replacing the standard search with an
enhanced version ...

1 -- ADD a Toggle button the right to switch between "Title ONLY search"
and "Title OR/AND content search"

2 -- REMOVE any distinction between System, Shadow or Standard searches.
All search will be ALL. Typing the needed address, or part address, for a
"tweaking user" will give most everything they ever need, especially in
combination with (1).

3 -- INTELLIGENT FILTER. The Search to detect IF it starts "[" and then
search in Filter Mode.

4 -- SAVE SEARCH??? More a question than a complete answer, but to add a
"Save Search" button to the right of the search, that results in a dropdown
similar to the current Advanced Filtered Version, though in this case for
ANY search, might be worth a thought.

Best wishes
Josiah

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

[twdev] Re: TiddlyDesktop: Any chance for new revision?

2018-07-25 Thread @TiddlyTweeter

Ciao Mohammad

Mohammad Rahmani wrote:
>
> Is there any chance to have a new revision of Tiddlydesktop in the near 
> future?
> The issue with fullscreen is very demanding and I hope you could resolve 
> this in the new revision.
>

To improve the chances this will happen you should also go to 
https://github.com/Jermolene/TiddlyDesktop/issues/148 and either add you 
own comment and/or add a "thumbs up" to what others have written. These 
"votes" matter in indicating to Jeremy where there is demand for a "fix" or 
"new feature".

TiddlyDesktop has its own GitHub which is well worth following if TD 
interests you: https://github.com/Jermolene/TiddlyDesktop. Its quite 
manageable as its not huge. Personally I think TD is brilliant.

FWIW, one thing I think would be very good in TD is that all addressing of 
wiki be able to use relative pathing. This would increase its portability 
and enable it to run as a self-contained app more easily.

Best wishes
Josiah

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

[twdev] Re: TiddlyWiki for Mobile

2018-07-14 Thread @TiddlyTweeter

I think it a good question. A very good question.

*To answer properly I'd like to take some time to think into it more. *

There are several issues to un-bundle. For instance, your comment about the
"More" menu is spot-on, but can also be a PITA on desktop too. So some
issues on Mobiles are also issues on Desktop. The limited screen space on
mobiles simply highlight those existing problems more.

Another issue, quite central, is whether TW on Android should aim to
replicate the motherload? Whilst JD has done a great job in the CSS for
Mobile, there is a bigger issue about whether for Mobile the actual
functioning, the code of doing stuff, needs tweaks.

*Jed's three points* I think are accurate. And excellent to work from. But
the implication of them he gives is far too negative. I think his facts are
spot-on, but his view of what they imply is very partial.

IMO, Android is important to support WELL. Not least for wider adoption of
TW since its one of the most widely used OS on the planet.

Best wishes
Josiah

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

[twdev] Re:

2018-07-11 Thread @TiddlyTweeter

Erm ... this thread seems to have no title! :-)

On Wednesday, 11 July 2018 12:28:11 UTC+2, Adam Antios wrote:
>
> Having spent a lot of time trying to use TiddlyWiki on Android and after 
> seeing that a lot of people have the same issues I can't help but wonder 
> what are the plans regarding the development of a full working solution 
> exlusively targeting phones?
>
> Is there any reason why this has not been implemented yet? Is there any 
> technical difficulty or is it just not a priority?
>

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

[twdev] Re: Proposing a plaintext parse & render mode for attributes & more

2018-01-12 Thread @TiddlyTweeter

FWIW, I've been avidly using BJ's Flexitype plugin--especially the version 
that allows sequences of Regular Expressions to be run before the main 
parser kicks in. It's perfect for many use cases where you need develop a 
specialised markup (e.g. screenplays). Or cases where you want to extract 
strings from huge texts. 

I found it stable and incredibly useful.

Best wishes
Josiah

BJ wrote:
>
> For reference, I have a plugin that does some of this:
>
> http://bjtools.tiddlyspot.com/#Flexitype%20Demos 
> 
>
>

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

[twdev] Re: Are all preinstalled themes based on Vanilla?

2018-04-05 Thread @TiddlyTweeter

Its good news in the sense that TW is not burdened with 9 complete CSS 
distinct themes yet benefits from variations.

Its perhaps not so clear that to revamp the full presentation CSS you need 
to take over Vanilla.

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

[twdev] Re: [TW5] Is there a simple way to realise a share button?

2018-04-10 Thread @TiddlyTweeter

There has been a lot of work done on this. Its not been wrapped into a 
plugin which is why you probably did not find it. 

Basically a lot of "share mechanisms" utilise "URL posting". If what you 
need is that I suggest you look to Riz's Network poster for a basic model 
that should be easy to modify for further networks. 
https://ibnishak.github.io/Tesseract/pluginsandmacros/socialmacros/index.html

Best wishes
Josiah

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

[twdev] Re: TiddlyWiki ControlPanel Appearance Bug

2018-06-28 Thread @TiddlyTweeter

Ciao Adam

Do you mean this behaviour? ...



Adam Antios wrote:
>
> In the TiddlyWiki if you go to Settings -> Appearance -> Toolbars there is 
> a bug, which is that the text appearing there is longer than the width of 
> the tiddler.
>

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

[twdev] Re: TiddlyWiki ControlPanel Appearance Bug

2018-06-28 Thread @TiddlyTweeter

eek the image left ... I meant ... do you mean this behaviour? ...



Adam Antios wrote:
>>
>> In the TiddlyWiki if you go to Settings -> Appearance -> Toolbars there 
>> is a bug, which is that the text appearing there is longer than the width 
>> of the tiddler.
>>
>

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

[twdev] Re: TiddlyWiki ControlPanel Appearance Bug

2018-06-28 Thread @TiddlyTweeter

FYI, because of your post, I entered an issue on GitHub Issue about this 
here: https://github.com/Jermolene/TiddlyWiki5/issues/3344

Best wishes
Josiah

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

[twdev] Re: Big list of TWs

2018-09-30 Thread @TiddlyTweeter

joearms wrote:
>
> Is their (somewhere) a "big list" of TW5's - or a web site where one 
> coulpe register a TW?
>

Did you look through TiddlyWiki ToolMap: 
https://dynalist.io/d/zUP-nIWu2FFoXH-oM7L7d9DM

Josiah

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

[twdev] Re: Big list of TWs

2018-10-01 Thread @TiddlyTweeter

Ciao Mohammad

It appears out of date because it is underused. Very few plugin writers 
sign up to it.

Josiah
 

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

[twdev] Re: Looking for a tutorial on how to write a plugin

2019-01-16 Thread @TiddlyTweeter

Joe

Very useful is the Tinka plugin maker. It is very well thought through and 
gives much useful support to do them.

https://tinkaplugin.github.io/

Josiah

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

[twdev] Re: New Feature PR: shuffle[] filter operator for deterministically randomizing list orders

2019-01-21 Thread @TiddlyTweeter

Ciao Matt,

It think it is a neat tool with good potential usage. I think it should be 
a plugin. Not in the core. Mainly because most users are unlikely to need 
it.

My two cents
Josiah

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

[twdev] Re: Is there an english high level description of how wiki text ends up as HTML?

2018-12-18 Thread @TiddlyTweeter

Caro, you are right. Apologies.

I will post separately about my issue on this.

J.  

TonyM wrote:
>
> I think your comment is little unfair. I listed the key components to 
> learning what Joe wanted, ultimately supported by the content that Mario 
> was able to post.
>


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

Re: [twdev] Relation of filter expressions to boolean logic

2018-12-20 Thread @TiddlyTweeter

J & J,

"Reverse Polish" I understand.

This thread is interesting for highlighting, I think, how an explanandum 
can clarify the variety of explanans.

josiah

joearms wrote:
>
>B C +A
>
> is pretty neat - it eliminates the parentheses OR becomes whitespace and 
> AND becomes +
>
> It's a Reverse Polish Monad Filter (RPMF)
>

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

Re: [twdev] Relation of filter expressions to boolean logic

2018-12-20 Thread @TiddlyTweeter

Joe

FYI I'm not a programmer and don't want to be one :-). 

But I found your probing is very illuminating.

Given you are a highly achieved programmer I find it interesting even you 
need to grapple the TW.

I think there is a kind of "implicit" TW zeitgeist or weltanschauung in TW 
that is both very happily bracing and quite askance (oblique) to other 
stuff. Once we get into it I think we tend forget its divergences.

THB I think Jeremy does not fully know himself quite how far he has got and 
how good it is.

One thing I'm kinda interested in is "comparing Wiki". IMO we are 
underselling TW. Its a different world.

Just thoughts
Josiah


joearms wrote:
There is method in my madness :-)

I'm trying to relate stuff I don't know (ie the tiddlywiki) to stuff I do 
know
(ie regular programming languages)

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

[twdev] Re: Looking for the Rosetta Stone

2018-12-20 Thread @TiddlyTweeter

Joe, spot on

... info is there but all over the place. Us lingerers kinda figure out how 
to find it but we should get our act together to make better sense of it 
and connect it up so it can be found easily. 

... concerning copyright. Probably an easier issue. Plugins often carry 
copyright/usage terms. I never seen one that was restrictive. Its more 
likely it doesn't occur to most users to put terms on each tiddler. How 
about a general TW flag "you can use it" covering all usage unless at 
tiddler level there is a (c) when a writer needs specific terms?

Josiah

On Thursday, 20 December 2018 21:08:42 UTC+1, joearms wrote:
>
> Thanks - seems to me that everything I want to know is out there somewhere 
> but not organised 
> at one place and in an order that makes sense to me.
>
> I retrospect it would be nice every tiddler has a copyright/reuse field so 
> I know If I can
> reuse the tiddler without infringing on usage rights.
>
> /Joe
>
> On Thursday, 20 December 2018 19:06:34 UTC+1, Diego Mesa wrote:
>>
>> The great Eric Shulman explained it beautifully here:
>>
>> https://groups.google.com/d/msg/tiddlywiki/3NdhzmCD-Rs/yoxtHnBCAAAJ
>>
>> The bottom line is reveal is a IF statement like this:
>>
>> <$reveal type="match" default=<> text=<> >
>> This content is shown if variable1 and variable2 match
>> 
>>
>> On Thursday, December 20, 2018 at 12:03:06 PM UTC-6, joearms wrote:
>>>
>>>
>>>
>>> On Thursday, 20 December 2018 18:59:56 UTC+1, Diego Mesa wrote:

 Joe,

 Coming from other languages, in my mind the "reveal" widget is the 
 closest thing to an IF. Wikify is a unique construction to TW. Also note 
 that the great Evan Balster wrote a "Condition" Plugin:

>>>
>>> Goodness - I haven't got to reveal yet. I wouldn't have guessed it was 
>>> an IF statement :-) 
>>>
>>> /Joe
>>>

 http://evanbalster.com/tiddlywiki/formulas.html#Condition%20Plugin

 which exposes <$if>, <$else-if> and <$else> widgets.


>>> Nice
>>>  
>>>
 On Thursday, December 20, 2018 at 8:40:24 AM UTC-6, joearms wrote:
>
>
>
> On Thursday, 20 December 2018 14:57:39 UTC+1, Mohammad Rahmani wrote:
>>
>> Joe,
>>
>>  have you seen:
>>   https://tiddlywiki.com/#Widgets
>>
>
> Yes - I wanted to know the most important :-)
>  
>
>>
>> These are list of widgets in TW core:
>>
>> The below five widgets are my choice for programming TW and I think 
>> these are 
>>
>>1. list
>>2. set (and vars)
>>3. reveal (for conditional operation)
>>4. wikify
>>5. import (scope of variable and private methods)
>>
>>
>>
> Thanks 
>  
>
>> Other widgets are important for example
>>
>>- creating/deleteing tiddlers
>>- field operation
>>- creating htmls elements (radio, select, editbox, ...)
>>- ...
>>
>>
>> There are expert people over there can explain in more details.
>>
>>
>> -- Mohammad
>>
>

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

[twdev] Re: Looking for the Rosetta Stone

Joe & Mario

My sense of this is 

1 - Joe, I doubt any of the stuff (i.e. Tiddler text like you see in blogs) 
you've encountered and want to recycle is in anyway problematic. 
WHY? The creator never thought to (c) it. If they had it would be likely 
the PAGE would gave a CLEAR copyright statement.

2 - Plugins do tend to have copyright terms. These get automatically 
transported when you install them.

IN BRIEF ... I would not worry about it.

Josiah

On Wednesday, 26 December 2018 19:56:10 UTC+1, joearms wrote:
>
> Thanks Mario, 
>
> that was good to know.
>
> What concerns me more are TWs I've found "in the wild" - can I quote from 
> them if I can't get permission from the author
> and if there are no apparent rights in the TW file
>
> Cheers
>
> /Joe
>
> On Tuesday, 25 December 2018 15:14:32 UTC+1, PMario wrote:
>>
>> Hi Joe, 
>>
>> Everything used from tiddlywiki.com is licensed, based on the following 
>> definitions from 2 CLAs
>>
>> see: https://github.com/Jermolene/TiddlyWiki5/tree/master/licenses
>>
>> more specific for individuals: 
>> https://github.com/Jermolene/TiddlyWiki5/blob/master/licenses/cla-individual.md#2-grant-of-rights
>>   
>>
>> TiddlyWiki *code* uses: BSD 3-cause
>> TiddlyWiki *docs* uses: CC-BY 
>>
>> Every contributor needs to sign the CLA prior to merging the 
>> pull-request. Signing the CLA is an "active" process. So it can't happen by 
>> accident. The list of contributors can be seen at the end of the CLA.
>>
>> Every plugin, that can be included with the TW plugin manager has to use 
>> the same licenses. 
>>
>> 3rd party plguins should have their own licenses, which are completely up 
>> to the author. If a plugin itself uses external libraries, the used 
>> licenses can add up. 
>>
>> see: 
>> https://wikilabs.github.io/editions/markdown-it/#%24%3A%2Fplugins%2Fwikilabs%2Fmarkdown-it
>>  
>> ... where my plugin uses BSD 3-clause and the underlying library uses MIT.
>>
>> I personally don't include the license text. I include links only. ... 
>> Because for some of my plugins the license text would be bigger then the 
>> "real" plugin content. 
>>
>> If licenses are defined within a VCS (version control system), it's easy 
>> to verify, which license was active at any given time. If 3rd party plugins 
>> are hosted, without VCS, it will be difficult, since the author can change 
>> the library text at any time. So the latest active plugin could have had a 
>> different license 2 years ago.
>>
>> I personally would *not* want to contribute to the "EDLs (Edit 
>> description lists)" because I consider it "bloat of metadata". I'm in favor 
>> of having an "audit-able" system, but it needs to come "naturally". So it 
>> has to be part of the underlying system, without the need to make the core 
>> more complicated.  
>>
>> IMO a system with much potential for TiddlyWiki is the DAT-protocol and 
>> DAT-filesystem. see: DAT-project  
>>
>> It uses a "copy on write" storage system, that is "naturally" versioned. 
>> So it's easy to create valid links to licenses, which also include the 
>> whole "prose text". ... 
>>   
>> just some thoughts. 
>>
>> have fun!
>> mario
>>
>>

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

[twdev] Re: My new blog (pre release)

joearms wrote:
>
> The tiddler to add a tweet link at the bottom of every tiddler  is here:
>
>
> https://github.com/joearms/joearms.github.io/blob/master/tw/share/tiddlers/My%20Footer.tid
>

Joe, I think your default Tweet system is boring :-).

On Twitter l, like most everyone, ignores crude links.

 In TW you could create an explanatory text to be included prior to the 
resource address without having to type it manually in the Twitter 
submission box/window.

Josiah

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

[twdev] Re: My Blog is now a TW

Ciao Riz & Joe

1 - Riz. Great practical comment. Some time ago you did some really neat 
experiments for static output that was more "integrative" looking than 
tw.com. Tw.com static can come over as a series of pages, not an integrated 
site.

2 - The Google Indexing issue is perhaps worth further exploration? TW can 
add headers that mildly encourage/improve it for the dynamic version?

3 - The issue of "static site" via node generation I find somewhat 
confusing, ultimately. What I really want is to be able to auto-generate 
with "some JS dynamism".

4 - Tiddlyspot is not indexed by Google, as far as I know, so zillions of 
TW we don't know about.

Just thoughts
Josiah

On Thursday, 27 December 2018 09:39:16 UTC+1, Riz wrote:
>
> Hi Joe,
>
> I see you are enjoying your TW5 quite well. Here is a thought for your 
> consideration. The basic TW5 you download from GitHub or tiddlywiki.com 
> is a good fit for several things. Unfortunately the idea of using 
> Tiddlywiki itself as a blog has a major downside. The unique structure and 
> data storage of TW5 doesn't fly well with the search engine optimisation 
> guidelines of most search engines. Here's an experiment. The most popular 
> website using Tiddlywiki is obviously tiddlywiki.com itself. Now search 
> Google for "Tiddlywiki HelloThere". You will see that large part of links 
> point to tiddlywiki.com/static/, which are not Tiddlywiki files, but 
> static HTML generated by Tiddlywiki.
>
> Ergo, if you are serious about using TW5 for blogging, use it not as blog 
> itself, but as a static site generator, a role for which Tiddlywiki is one 
> of the best fits. 
>
> There was a "blog edition Tiddlywiki" as a part of core. However I cannot 
> find it in github right now.
>
> Sincerely,
> Riz
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/19ed9e44-a338-4d45-861a-7153cbd832b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: Looking for the Rosetta Stone

Mario

Appreciate your detail on this but it misses something.

Say a person writes a Tiddler in a TW of "text to be read". What is the 
problem copying it if the "site" indicates NO copyright conditions?

Josiah

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

[twdev] Re: My Blog is now a TW

For email users: I updated my last post on a point about a TW "static" 
downside.

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

Re: [twdev] What are 5 most important widgets to learn?

I watched with great interest replies to Joe. 

They tell me a lot I did not know that is USEFUL to know.

Jeremy Ruston wrote:
>
> My take on the 5 most important widgets to learn would be...
>

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

[twdev] Re: Hiding the TW (at first)

Joe. FYI I don't use node raw. I use BOB.exe which is basically node 
wrapped down to TW needs. Its rather good for anything where you need 
automation on button press.

Regarding doing an XML switcheroo I think Jeremy's 
https://tiddlywiki.com/prerelease/editions/xlsx-utils/ is well worth a 
look. Its best when you have a standardised structure.

J.

On Wednesday, 26 December 2018 19:52:44 UTC+1, joearms wrote:
>
> What I want is to programmatically create a TW from the following:
>
> A large amount of documentation in XML
> A large amount of code
>
> Basically one XML file per code file.
>
> This I want to turn into a TW and add a lot of fancy stuff (code Xref, 
> annotations etc.)
>
> With some back-end support I could (I think) turn this into a fully blown 
> IDE - 
>
> This might take a while :-)
>
>>

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

[twdev] Re: adding a remote tiddler from github

2018-12-16 Thread @TiddlyTweeter

Do you have an addess?

On Sunday, 16 December 2018 11:43:26 UTC+1, joearms wrote:
>
> I'd like some feedback on some tiddlers I've been writing.
>
> If I publish the tidders on github (ie the individual tiddlers and NOT an 
> entire TW)
> is there a syntax that can be used that can yank in and view the tiddler 
> from any other
> TW?)
>
> I realise this breaks security - but would be very convenient - can the 
> remote tiddler be run in a 
> iframe? or some other trusted mode?
>
> Cheers
>
> /Joe
>

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

[twdev] Re: Hiding the TW (at first)

2018-12-25 Thread @TiddlyTweeter

The neat thing, for most purposes on "hiding" in TW is its CSS structure. 
What folk sometimes (somewhat incorrectly) call "Read Only" is mostly just 
changing some CSS rules.

One thing I'd myself like to understand much better is how to combine 
"startup actions" that are informed by auto-detection of the environment 
(e.g. smartphone) with application of specific CSS layouts and "hidings".

josiah

joearms wrote:
>
> I want to turn off most of the advanced features of the TW ...
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/b2b68bbc-72e0-49ab-a786-1dca991bd5d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: Is there an english high level description of how wiki text ends up as HTML?

2018-12-14 Thread @TiddlyTweeter

TonyM 

> I am not sure how important it is for you to learn how the wiki text is 
> translated to HTML, more that "what WikiText results in what output?" 
> Please clarify!
>

I'm emboldened by Joe since he knows what he is doing, which I often don't.

Its very important.

One issue is knowing when you are passing "literal text" when to what or 
"Wikitext" (WHAT is that, BTW?)

The  rest of your reply is interesting for basically saying: find out 
yourself :-)

J. x


> One thing to keep in mind is exploring your TiddlyWiki's own internal 
> workings is a great way to learn and discover. In part due to TiddlyWiki's 
> Open source status and in part because it is designed to allow its user 
> interface and working to be freely modified you can actually be on a desert 
> island with no internet and teach yourself about tiddlywiki. Of course this 
> can sometimes be time consuming when some good documentation would help.
>
> The challenge for a new user, like for any system, is getting and 
> understanding the keywords that describe something. For example the "magic 
> tags" you mention, are most likely system tags thus if you look here 
> https://tiddlywiki.com/#SystemTags you will see a short explanation for 
> each, many of these will also be the magic tiddlers you speak of.
>
> Learning about the page, view and edit templates and how they work is also 
> useful, because then you can track how something appears in front of you. 
>
> The way the toolbars and buttons work is also a key area to learn, because 
> it enables so much, including customising or making your own buttons.
>
> I am now reworking my "TWInternals" Tiddler to remove a dependency on a 
> plugin and I will let you know here where to find it. This tiddler 
> basically lets you peek into a range of internal tiddlers and settings, and 
> can act both as a reference and a step by step exploration to learn more.
>
> Regards
> Tony
>
>
>
>
> On Monday, December 10, 2018 at 12:12:06 AM UTC+11, joearms wrote:
>>
>> I'd like an overview of how wikitext ends up as HTML
>>
>> 1) macros are expanded
>> 
>>
>> ?) html is output
>>
>> or is it
>>
>> 1) wikitext is parsed
>>  
>>
>> etc.
>>
>> I have no idea - is this documented somewhere?
>>
>> In particular, how is the interaction with 'magically named tiddlers' 
>> managed.
>>
>> I am aware that giving tiddlers special names and special tags changes 
>> what happens
>> when the tiddler wikitext is expanded - but I have never found an 
>> exhaustive list
>> of the magic tiddlers and magic tags and what they do and in particular 
>> when they do what they do.
>>
>> Is there such a list?
>>
>> Cheers
>>
>> /Joe
>>
>>

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

[twdev] Re: Tiddler in live edit preview mode behaves differently to in view mode

2018-12-15 Thread @TiddlyTweeter

"Fieldmanger" is great during the Xmas period :-)

More seriously: I like your questions. They bring "us" back to what TW 
looks like on entry to someone who knows what they are doing. 

J, x

joearms wrote:
>
> Solution:
>
Wrap the button code in a fieldmanger ... 
>

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

[twdev] Re: Silent and Noisy errors

2018-12-15 Thread @TiddlyTweeter

Right. Its much worse for computer illiterate users like me who have no 
clear idea what is right and wrong in the lingo format.

I just assume that live feedback on coding errors would bloat TW beyond 
reasons for it.

Josiah

On Friday, 14 December 2018 19:48:01 UTC+1, joearms wrote:
>
> I just spent a good half an hour scratching my head.
>
> I made the following error
>
> I wrote:  `<>`
>
> Instead of:
>
> `<>`
>
> (I know it should be a small "p" and not a big "P" - but errors like this  
> (silent errors)
> are extremely difficult to spot. I call errors like this `quiet errors`.
>
> I have no idea how the filter mechanisms are implemented but it would be 
> extremely helpful if all programming errors if they can be detected be 
> converted into "noisy errors"
>
> Noisy errors stop the program execution with a huge red error text telling 
> you what went wrong. Quiet errors just swallow up the error and say nothing.
>
> As a general design principle, I believe that all plugins etc should 
> generate noisy errors if they detect an error condition.
>
> Cheers
>
> /Joe
>

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

[twdev] Re: Preparing TW for the next step

2018-11-29 Thread @TiddlyTweeter

I agree *very much* with Jed. 

In particular, Mr Ruston's concern with backwards compatability is ace and 
a neat near 9.95 out of 10. I hope your angle won't mess that up. It could.

I also agree that the dev side is not so populated. There simply are not 
enough commited devs. (I'll never be one)

IMO you have to prove relevance. 

Erwan and Tobias are red herrings--they mainly not here--that is not 
aversion to TW--merely off doing their own thing.

I DO think a more open context could help cope with the many standing PRs. 
BUT not a free-for-all.

SO somewhere is "middle-ground" I hope.

Not sure this makes sense. But I'd say that mr JR is "long in the tooth" ... 
and 
still basically responds to strong knocks on heaven's door. 
https://www.youtube.com/watch?v=gazW7MOqHzQ

Josiah

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

[twdev] Re: Where is the source code that implements the "tm-new-tiddler" message?

2019-01-12 Thread @TiddlyTweeter

It is interesting how much you like the Salt Mines.

On Saturday, 12 January 2019 10:40:47 UTC+1, joearms wrote:
>
>
>
> I want to find the source code that implements the "tm-new-tiddler" 
> message?
>
> Why do I want it?
>
> I've been looking at the documentation for
> tm_new_tiddler at 
> https://tiddlywiki.com/#WidgetMessage%3A%20tm-new-tiddler
>
> Having read this I could not understand what the paramObject was so I 
> experimented a bit and tried this:
>
> <$button>
> <$action-sendmessage $message="tm-new-tiddler" title="Comment" 
> tags="comment" text=<>
> parent = {{!!title}}
> foo = "this"
> bar = "that"
> paramObject = " 'abc':'two' "
> />
> New Comment
> 
>
> When I click this a new tiddler is created with fields 
> parent,paramObject,foo and bar
>
> Very strange - the documentation make no mention of that I can add 
> arbitrary additional fields to the command and I still haven't a clue what 
> paramObject is
>
> So I thought to myself "if all else fails read the code" - trouble is I 
> can't find it.
>
>
> Cheers
>
> /Joe
>
>
>  
>

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

[twdev] Re: My Blog is now a TW

2019-01-04 Thread @TiddlyTweeter

Ciao Joe

Right. You can search Google and find good things. Many of those would be 
on Github or privately hosted. But I don't think Tiddlyspot TW are 
currently actively indexed by Google. Unless I'm seriously mistaken. That 
includes a lot of, many, useful TW 5. Some older TW Classic do seem to be 
indexed on it but they won't help you.

Josiah

joearms wrote:
>
> iddlyTweeter wrote:
>>
>>
>> 4 - Tiddlyspot is not indexed by Google, as far as I know, so zillions of 
>> TW we don't know about.
>>
>
> Is that true? - when I get stuck I Google for solutions to my problems - 
> this often works when the
> "search" inside my local TW fails. I've found a lot of good TW content via 
> Google.
>
>>

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

[twdev] Re: [TW5] [TW-jsoneditor] Json Editor for Tiddlywiki Open Beta v0.0.5

2019-04-02 Thread @TiddlyTweeter

Ciao Joshua

Brilliant piece of work! 

It works well and looks good too.

I have in mind to maybe use it for a food nutrition database. That will 
take me time---but this looks like it will do the job properly.

Best wishes
Josiah

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

[twdev] Re: rudimentary find-on-page support for TD

Simon Huber wrote:
>
> I've created this little demo here: 
> http://find-on-page-test.tiddlyspot.com/
>
> It allows to find words on the page using a very simple action-widget
>
>  what I've noticed is that matches on tags are found but the selection 
> isn't visible.
>
 
Right. I'm doubtful its workable without visual feedback. I tried. I failed.

Josiah

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

[twdev] Re: rudimentary find-on-page support for TD

Just NOTING TiddlyDesktop is an awesome install at 250Mb before you even do 
anything.

On Wednesday, 27 February 2019 14:27:01 UTC+1, @TiddlyTweeter wrote:
>
> Back to topic ... I'll experiment with your search tool in TD and report 
> back.
>
> A dopo
> Josiah
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/559b8a13-1145-46d5-8e6f-ef3e64dabb5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: rudimentary find-on-page support for TD

Back to topic ... I'll experiment with your search tool in TD and report 
back.

A dopo
Josiah

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/8c6ef525-1113-43de-95b7-449513f280b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: rudimentary find-on-page support for TD

Anyone who wants to help JR on TD gets my vote. 

Its a superb solution for desktop users.

MY main concern has been to encourage *a fully portable build* of it (i.e. 
that you can use relative addressing to wiki). That would permit 
repackaging of the app with content wiki. I would definitely use it  ...

Josiah

On Wednesday, 27 February 2019 13:33:04 UTC+1, Simon Huber wrote:
>
> Simon,
>>
>> Jeremy is the author of tiddlydesktop. It uses a cutdown browser to 
>> opperate, I know he was reluctant to add more and more such that it would 
>> become a browser but you may be able to persuade him to add this if its 
>> practical to do so in a future release.
>>
>> Regards
>> Tony
>>
>
> Hi Tony, yeah I know about this little interest conflict. But 
> search-on-page is not a browser-only thing. An address bar would be I 
> guess, this is just functionality for the notebook/application itself 
>

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

[twdev] Re: a video widget that plays videos without interruption