[twdev] Shadow Tiddler behaviours

[SylvainComte]

Hello Tony,

I did not answer because I have not enough theorical background to say what 
will happen. I have a practical case of multiple copies of a shadow tiddlers 
working in the same wiki : see my i18n macro used in several plugins of
http://sycom.gitlab.io/TiddlyWiki-Plugins/

BUT it doesn't overwrite a core plugin AND I did not investigate what happens 
here, which version is retained or anything like this since I'm sure the 
tiddler is the same. By construction.

Cheers

Sylvain
@sycom

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/646dcf3d-db9b-4e5b-9210-40565fddba74%40googlegroups.com.

[twdev] Requesting input on concept: ToC-Content-tree

[SylvainComte]

Another use case could be a "book generator"? This thread on GG is an 
inspiration : https://groups.google.com/forum/tiddlywiki/uPzz3rA7wWg

I had to edit templates to achieve this. But a toc-content may work well.

Sylvain
@sycom

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/fd4338ce-de31-4920-af1a-708b30a46108%40googlegroups.com.

Re: [twdev] Re: RFC - i18n : a translation macro

[SylvainComte]

Great!

I do have an explanation for issues I didn't understand. The documentation 
(https://tiddlywiki.com/#Macro%20Definitions%20in%20WikiText and 
https://tiddlywiki.com/#Macro%20Definition%20Syntax) is clear about enclosing 
default value with quotes, but I didn't go back there for a while and I forgot.

The same doc tells that parameters are space separated. No commas there. Should 
it be updated?

I will iterate the macro soon with those enrichments 

Greetings

Sylvain
@sycom

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/18b3159d-c6c7-4fa1-8059-aabcbef3c735%40googlegroups.com.

[twdev] RFC - i18n : a translation macro

[SylvainComte]

Maybe with another title? :-)

This could be useful for more international plugins. 

I'd be glad to have advices and adapt this for more users.

Cheers

Sylvain
@sycom

Le lundi 14 octobre 2019 18:58:06 UTC+2, SylvainComte a écrit :
>
> Hello,
>
> as discussed on github (see #4179 
> <https://github.com/Jermolene/TiddlyWiki5/issues/4179> for a background) 
> I made a i18n macro that could be useful for translating plugins without 
> using lingo / languages.
>
> For those who care or have time, please test it on demo site (
> https://sycom.frama.io/TiddlyWiki-Plugins/dev/i18n.html) and tell me what 
> you think. Here or on github issue.
>
> cheers
>
> *Sylvain*
> @sycom
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/dfd7b634-ba3b-49ff-b574-aa8574a6c7d0%40googlegroups.com.

[twdev] Re: Worth considering: Ease of installing plugins VS. pressure to include in core

[SylvainComte]

Or may be it could become something like this

[image: 3375224700_c7bf7c3791_b.jpg]
Just kidding of course, but I have ome questions with this approach

* What are essential functions for the core? Who will decide of this? As 
all of us have already experienced this, there are almost as many visions 
of what a minimal wiki should be...
* What if my modules combination has some incompatibility issues? For a 
"simple" user with no coding skills, who will fix this?
* Are we sure we can't make the existing core thiner before we put it in 
pieces

The success of TiddlyWiki has always been a good balance between "ready to 
use"-ness, personalization, and hackability.

Edgy to preserve with this Lego game maybe... 

Warm regards

Sylvain
@sycom


Le vendredi 13 septembre 2019 22:03:16 UTC+2, Mohammad a écrit :
>
> A modular approach!
>
> * core (minimum essential tools)
> * themes
> * languages
> * plugins
> ** highlight.js
> ** katex
> ** codemirror
>
> 
>
> url: 
> https://medium.com/5000-things/learning-from-lego-a-step-forward-in-modular-web-design-d8ff953f45a8
>
> On Friday, September 13, 2019 at 10:29:44 PM UTC+4:30, Mat wrote:
>>
>> Just a thing I've been reflecting over:
>>
>> *The easier it is to install plugins*, either permanently install them 
>> or - perhaps even more importantly - to do a temporary use+delete install...
>>
>> *...the less the need and pressure to include functionality in the core / 
>> std distro.*
>>
>> The coming "dynamic loading of plugins 
>> " is a 
>> very welcome step in this direction. I can't tell if this is an 
>> implementation of the request to Provide a mechanism to register plugins 
>> after boot . Another 
>> addition was the implementation of making tag pills work for multi-tiddler 
>> DnD imports. A more general idea would be a handle to DnD filtered lists 
>> . A further step 
>> would be to Extend Download button to offer adding plugins 
>> . And eventually 
>> we'll hopefully be able to solve the Big One, i.e a library that serves a 
>> federated collection of plugins.
>>
>> Apropos this, if installing and removing plugins were totally painless, 
>> would it be possible to excise features from the core / standard distro? 
>> Just curious.
>>
>> <:-)
>>
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/62434530-dda3-4645-aef4-932d9229e735%40googlegroups.com.

[twdev] Re: Plugin and Macro publishing standards

[SylvainComte]

Hello all,

pretty interesting thread indeed. I'm not sure to be the most capable 
person on this subject but this last message reminds me of my first time 
developing plugin.

> Plugins are the work of an "auteur" and we respect that. Perhaps too 
> much? 

Actually they are. Sometimes because of the "auteur" but in most cases in 
my humble opinion, because he's the only one that can fully understand what 
he did. Even when documenting the code, each author has a very own plugin 
structure. In my case, it has no consistency from one plugin to another. 
Just can imagine anybody looking at it would consider it's a mess...
I wish I had some kind of instructions about plugin structure, good 
practices (and bad ones) when I made the first (and the others) ;-)
I'm also aware that this is some very useful freedom for contributors. 
World is not black nor white...

> I mostly avoid things that the visitor might mistake to be the plugin 
> when it is not.

I think this is a good practice I do not apply now. But i definitely shall 
(and will)

Speaking from macro, shouldn't they be "self-documented" ? For "classic" 
macro (i.e. non JavaScript) the documentation regarding usage parameters 
etc. could be directly included in the tiddler. Just as you have self 
documented functions in your favourite terminal function (`myfunction 
-help` you know)...

Cheers,

Sylvain
@sycom


Le jeudi 12 septembre 2019 13:55:45 UTC+2, @TiddlyTweeter a écrit :
>
> TonyM wrote:
>>
>> The social pressure placed on me with people like Mohammad and those of 
>> you beforehand publishing great content, is for me to publish more of my 
>> tools and utilities, has led me to build and automate a process to publish 
>> content.
>>
>> I am starting this thread to solicit suggestions for such standards for 
>> publishing. I often see github, demo and source wikis published for a 
>> plugin. What should these contain?
>>
>
>  ... 
>
> One of the issues here is I have a lot of wiki macro solutions that do not 
>> need to be plugins, they can be installed without save and reload so they 
>> can be "dropped" on any wiki and used, for exploratory purposes.
>>
>> I can try and build me own solution but I would prefer to do so based on 
>> the wisdom and experience of the community so this post.
>>
>
> I'm not sure my wisdom is orthodox :-). I'd say that JSON format is the 
> premier format for sharing work, regardless of whether its a plugin or 
> humble macro.
>
> The plugin mechanism is very good for fact of shadow tiddlers & 
> recuperation from change errors. The plugin format is also good for being 
> consolidated, in the sense you can remove it in one go. The addressing 
> contains it.
>
> As I have mentioned before I think there is a social-psychological aspect 
> to "plugins" that maybe sometimes inhibit breaking them down for reuse. 
> Plugins are the work of an "auteur" and we respect that. Perhaps too much?
>
> Best wishes
> TT
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/32bd08a8-b6fb-4a5b-8cbc-1b296a14d040%40googlegroups.com.

[twdev] Re: Want to translate your plugins or documentation? Try the i18n macro

[SylvainComte]

Great,

Love to know it's useful.

If you're fluent in another language than fr-FR or en-GB. Or have corrections 
for existing ones, I'll be glad to update online documentation. Starts here 
http://sycom.gitlab.io/TiddlyWiki-Plugins/#i18n%20macro

Cheers

Sylvain
@sycom

-- 
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/8b38bdaa-60cb-49d0-94d0-e16a8722740e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] How to support multiple languages in my plugin?

[SylvainComte]

Hi,

You may use my <> macro ;-) (work in progress)

http://sycom.gitlab.io/TiddlyWiki-Plugins/#i18n%20macro

Cheers

Sylvain
@sycom

-- 
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/363e0fb7-1bd7-49e3-ad7f-90c6cf150fa4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] difference between "tiddlywiki" (using node) and "node tiddlywiki.js" (using node and local copy of tiddlywiki repo) ?

[SylvainComte]

Hello,

in an attempt to build a new plugin, I discovered that when I do

> node tiddlywiki.js path/to/my/wiki --build index

Using node and a local copy of tiddlywiki5 repository, my wiki and my 
plugin are perfectly built.

But when I do

> tiddlywiki path/to/my/wiki --build index

Using node and a npm install of tiddlywiki, my wiki is built but my plugin 
is not here. No error thrown by the console and none of the files of my 
plugins are in the wiki...

Does anyone have a hint on what happens here ?

cheers,

Sylvain

-- 
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/8e3ac60e-63b6-4281-b359-0b6fbe74bef3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] geoTiddlers and maps within your TiddlyWiki with Leaflet Map Plugin

[SylvainComte]

Hello, 

Very few words to let you know about Leaflet Map Plugin 
.
 


It is still very young and I'm a very non-professional dev, so you may want 
to have a look at source code  
(framasoft gitlab instance. But there is also a clone on github) or even post 
issues  on it's repo.

good mapping

Sylvain

-- 
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/0cdf8611-199c-4eaf-9f0c-0a0996b666ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.