[tw5] Popup images?

[Leon Gomez]

Is there any way to pop up, open or enlarge images to their natural size 
(ideally within the tiddler)?

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4e453341-67c0-4a25-a5dc-bfbdff25941c%40googlegroups.com.

Re: [tw5] $:/info tiddlers not updating

[TonyM]

Tt

I am afraid I can't quite catch your thoughts here.

I know this post changed direction but I have proven to myself a hack that I 
can already make use of and with little effort can help the community make more 
of tiddlywiki. 

To be clear I am not changing any existing plugin, more coopting the 
mechanisium for other purposes. Which will in fact satisfy a number of issues 
raised and on github.

Regards
Tony

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b7144dda-43a1-4806-bf2b-296dc534bc85%40googlegroups.com.

Re: [tw5] Re: Save directly Tiddlywiki 5 file to GitHub

[Richard Campbell]

Jeremy - if this is useful, feel free to copy and host it from 
tiddlywiki.com directly.

I was wondering the same thing about per-tiddler github saving, but wonder 
about the performance as github isn't really designed as a full database 
(e.g. file lookups are always a two request process). Something like 
firebase might be better, and firebase perhaps could help enable 
collaborative/shared tiddlers.

Cheers,

.ric


On Saturday, September 7, 2019 at 4:35:02 AM UTC-4, Jeremy Ruston wrote:
>
> Hi Richard
>
> Good stuff, thanks for sharing. I’ve wondered about using a similar 
> approach to load at startup individual tiddler files from a tiddler folder 
> stored on GitHub.
>
> Best wishes
>
> Jeremy
>
> On 7 Sep 2019, at 01:29, Richard Campbell > 
> wrote:
>
> I'm late to this conversation, but have a small github pages site which 
> can be used to download a (normal) github repo index.html file using their 
> GET blob api. You can enter your username, repo, and a PAT (currently it 
> assumes the tiddlywiki file is "index.html".)   The location and PAT are 
> stored in local storage, nothing stored in github or on any other site. 
>
> https://netrc.github.io/tiddlyGithub/
>
> Once you've entered the username/repo/PAT, the download just takes a 
> second or so (on good connection!).  Then of course the GitHub saver works 
> nicely in the background to save all changes.
>
> Richard
>
>
>
> On Friday, May 3, 2019 at 5:05:20 AM UTC-4, Jeremy Ruston wrote:
>>
>> Hi Cameron
>>
>> Can you show a screenshot of the control panel settings prior to clicking 
>> “save changes”?
>>
>> It may also be worth precisely listing the steps you took so that I can 
>> try to duplicate your result.
>>
>> Best wishes
>>
>> Jeremy.
>>
>> On 3 May 2019, at 00:36, camero...@gmail.com wrote:
>>
>> Hi Jeremy,
>>   Thanks for reading my comment. I am actually using Chrome, and when I 
>> follow along with the intended workflow it removes my github auth token and 
>> also the save feature just downloads index.html in-browser. If you follow 
>> my link or look at the attached image you can also see that all the styling 
>> and formatting is messed up, I'm using empty.html downloaded from 
>> prerelease as the basis and no nonstandard tiddlers are added. I understand 
>> this is prerelease so I am not depending on it I was just excited to use 
>> tiddlywiki in a  new way. I'm willing to provide more debugging 
>> information, but I am a bit of a novice so I don't know where to start.
>>
>> 
>>
>>
>>
>> On Thursday, May 2, 2019 at 4:10:30 PM UTC-4, Jeremy Ruston wrote:
>>>
>>> Hi Cameron
>>>
>>> Firstly, are you using Firefox? I think it doesn’t support 
>>> XMLHttpRequests from files loaded from a file:// URI. I used Chrome in most 
>>> of my testing.
>>>
>>> The intended workflow is to load the wiki via the 
>>> https://username.github.io/index.html URI, and then save changes 
>>> directly back to GitHub. The challenge is that GitHub pages doesn’t update 
>>> instantly, it takes a few minutes for a pushed HTML file to be accessible. 
>>> So, care has to be taken not to reload the wiki from GitHub pages before 
>>> the changes have been processed. To be cautious, one might want to check 
>>> the wiki in a separate tab to see when it has refreshed.
>>>
>>> Best wishes
>>>
>>> Jeremy.
>>>
>>> On 2 May 2019, at 20:54, camero...@gmail.com wrote:
>>>
>>> Hi, 
>>>
>>> I've been trying to get this working but I feel that I am missing 
>>> something. i can get my repository to host to github pages but when I use 
>>> my local browser to open the tiddlywiki (index.html) I've got in the git 
>>> repo I then cannot save it. Is the workflow (once it works) to navigate to 
>>> the file on your hard drive, make edits, save it then git commit, push, 
>>> etc? Every time I try to make modifications they are either not saved 
>>> because I used the hosted tiddlywiki at github.io to try to make 
>>> changes or I get a n XHMLHttpRequest error code: 409 if I try to edit the 
>>> on-disk index.html in my browser and use the tiddlywiki save function. I 
>>> note that I do have an earlier version of this index.html file being served 
>>> in my github pages. What could I be missing?
>>>
>>> On Thursday, April 4, 2019 at 7:20:36 AM UTC-4, Mohammad wrote:

 Referring to: https://github.com/Jermolene/TiddlyWiki5/issues/3890

 And the nice https://github.com/38911BytesFree/TiddlyWiki

 To save Tiddlywiki directly to GitHub Pages, is it possible to 


1. Have GitHub Saver plugin? or
2. Update the current classic TW to TW5?


 --Mohammad


>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "TiddlyWiki" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to tiddl...@googlegroups.com.
>>> To post to this group, send email to tiddl...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/tiddlywiki.

[tw5] Re: Search in the output of a Transclude Tiddlers (JavaScript macro & TemplateTiddler)

[Mohamed Amin]

OK, I figure it out, it seem that there was a typo or syntax error in my 
"Wikify widget call",
thanks to <> Macro 
 as it was my main tool for 
debugging this issue.



On Sunday, September 8, 2019 at 4:38:35 AM UTC+2, Mohamed Amin wrote:
>
> Hello,
>
> Appreciate your support as my head is spinning now ;)
>
> My problem here is that I don't know how to assign some text (transcluded 
> from a JavaScript & TemplateTiddler) to a Variable.
>
> Attached is an Experimental example (a simple Account Management) :-
> 1- It has some "Account Tiddlers" which contains ONLY fields (Acc01, 
> Acc02, .. Acc05)
> 2- All "Account Tiddlers" are "Transcluded" using a Template Tiddler 
> "accTemp" (with {{||accTemp}})
> 3- There are 2 JavaScrip Macros (TW5MyJavascriptMacro001 & 
> TW5MyJavascriptMacro002) to calculate "Age of current Password" and 
> different "Worning Message"
>
> Till this point everything is working fine, 
>
> What I failed to do is to search through the "Account Tiddlers", for 
> example "Query 01" return a result when I search for "Acc03" , while the 
> other Queries are NOT.
>
> I tried to use SetWidget, WikifyWidget and Macro but I failed, so please 
> check the attached file and let me know what I miss there.
>
> Thanks in Advance
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/51da87f0-6603-4848-bdae-df0ea29a3363%40googlegroups.com.

Re: [tw5] FEATURE REQUEST: instruction text for Tiddler Manager

[@TiddlyTweeter]

>
>  help button that links to some more extensive new docs at 
> https://tiddlywiki.com/#UsingTiddlerManager 
> 
> .
>

Ciao JR

That does not resolve?

TT

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/073135cf-422a-40a9-b5d8-31344e835f36%40googlegroups.com.

Re: [tw5] $:/info tiddlers not updating

[@TiddlyTweeter]

TonyM

I'd suggest that export to JSON of ONLY what is needed would likely help 
well, if not better. A newbie would not know what you are talking about :-).

BUT, an issue, too, in the background, is we respect plugin authors and 
tend to avoid, in public, partially using them. 

I think that is one of the reasons complete "app. packages", combining 
plugins or parts of them, plus hacks are RARE publicly on TW. 
Though obviously huge in private practice.

So there is a communal aspect in play too.

Askance thoughts
TT

On Sunday, 8 September 2019 09:57:05 UTC+2, TonyM wrote:
>
> Observation
>
> The fact that in the normal turn of events a shadow tiddler remains a 
> shadow tiddler until edited, then if you remove the plugin that defined 
> that tiddler, the edited tiddler remains, is actually a bonus. Of course 
> there will be cases where you want them deleted such as when removing test 
> data. However it also allows you to edit tiddlers you want to keep in the 
> wiki, and on deleting the plugin tiddler, the tiddlers you never edited 
> will be removed from the wiki, is a useful way to selectively incorporate 
> tiddlers from a repository and remove those you do not need, helping 
> develop leaner wikis.
>
> Regards
> Tony
>
> On Sunday, September 8, 2019 at 4:33:54 PM UTC+10, TonyM wrote:
>>
>> Folks,
>>
>> I built a Tiddler bundle to display info plugins in Control panel > 
>> Plugins > Info
>>
>> Attached, just remove the .txt extension before dropping on a test wiki. 
>> Then if you follow the instructions in my last post you can make your own 
>> info bundle.
>>
>> Only one core tiddler is changed for this 
>> example $:/core/ui/ControlPanel/Plugins although others will look as if 
>> they came with the core given I reused the naming standards.
>>
>> Regards
>> Tony
>>
>> On Saturday, September 7, 2019 at 10:54:42 PM UTC+10, TonyM wrote:
>>>
>>> Jeremy,
>>>
>>> For give me for being a bit of a hacker. I have played with making my 
>>> own tiddlers with a plugin-type of info, 
>>> which I note is NOT documented here 
>>> https://tiddlywiki.com/#Plugin%20Fields (perhaps this is understandable)
>>>
>>> However I found if I started to import multiple tiddlers, and renamed 
>>> $:/import to tiddlername (Capturing the import json), and modified the 
>>> tiddler type to info (deleting the status field) I created myself a hidden 
>>> plugin - not listed in plugins, containing the batch of tiddlers I almost 
>>> imported. Reloading I had all the shadow tiddlers appearing. Of course If I 
>>> edit a tiddler it looses its bold font in the "info plugin", and overwrites 
>>> the shadow.
>>>
>>> Disabling and reloading they are gone, but listed in the new info plugin 
>>> in italics and they open new empty tiddlers. The edited tiddlers from when 
>>> the plugin was active remain in the wiki as regular tiddlers, and can 
>>> actually be deleted, perhaps must be.
>>>
>>> Not only has this suddenly shed light on the plugin mechanism but I have 
>>> found away to capture importing tiddlers even from multiple JSON and 
>>> storing them in abeyance and made available when needed by enabling the 
>>> plugin. This has exposed a method by which I can load test data into a 
>>> wiki, or configuration settings. 
>>>
>>> This info plugin can be dragged and dropped to another wiki. 
>>> Interestingly after importing If I open the "info" plugin (not a plugin 
>>> title), the import mechanism offers to import the tiddlers. If it does so I 
>>> expect It will create standard tiddlers that would override if it where a 
>>> plugin.
>>>
>>> Anyway there is a lot of potential here, even if we were to create a new 
>>> tiddler type of say "bundle", that used my proposed import but not get 
>>> replaced as per the idea documented here;
>>> Suggested Import mechanisium refactor for hackability #4231 
>>> 
>>>
>>> I can explain further the value in such an mechanism if you wish, but 
>>> perhaps the possibilities are obvious to you.
>>>
>>>- Packed data tiddlers
>>>- Restorable and removable data with a click save and reload to add 
>>>or remove
>>>- Canned sets of config tiddlers to toggle multiple tiddler states
>>>- Ability to drag and drop to other wikis, a bundle defined in one 
>>>wiki to another
>>>- A method by which to host and distribute json files of tiddlers 
>>>(which are not active in the source wiki) without needing to upload 
>>>independant files to the host.
>>>- A method by which a developer can commit tiddlers into a plugin 
>>>bundle and selectively overwrite tiddlers to release a new version. Once 
>>>happy commit these changes back into the plugin. 
>>>- A way to distribute macros (excluding javascript plugin code) 
>>>which can be selectively activated and deactivated. Especially good for 
>>>designer tools.
>>>
>>> Apart from the import hackability I expect we would need a mechanism to 
>>> 

[tw5] Re: Announcement: Tiddler Commander 1.2.4

[@TiddlyTweeter]

Though I could not myself do this kind of thing ... integrating 
https://flibbles.github.io/tw5-relink/ with TC was a great idea!

I am very impressed at the way this leverages and integrates  good tools 
together to be able to inter-work. 

So the normal user can just get on and do amazing things too!

TT

Mohammad wrote:
>
> ... This is an effort to integrate Tiddler Commander with Relink plugin.
>
> Demo:https://github.com/kookma/TW-Commander
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/34f437c4-55f6-405a-b30b-bb05d2aedff4%40googlegroups.com.

Re: [tw5] $:/info tiddlers not updating

[TonyM]

Observation

The fact that in the normal turn of events a shadow tiddler remains a 
shadow tiddler until edited, then if you remove the plugin that defined 
that tiddler, the edited tiddler remains, is actually a bonus. Of course 
there will be cases where you want them deleted such as when removing test 
data. However it also allows you to edit tiddlers you want to keep in the 
wiki, and on deleting the plugin tiddler, the tiddlers you never edited 
will be removed from the wiki, is a useful way to selectively incorporate 
tiddlers from a repository and remove those you do not need, helping 
develop leaner wikis.

Regards
Tony

On Sunday, September 8, 2019 at 4:33:54 PM UTC+10, TonyM wrote:
>
> Folks,
>
> I built a Tiddler bundle to display info plugins in Control panel > 
> Plugins > Info
>
> Attached, just remove the .txt extension before dropping on a test wiki. 
> Then if you follow the instructions in my last post you can make your own 
> info bundle.
>
> Only one core tiddler is changed for this 
> example $:/core/ui/ControlPanel/Plugins although others will look as if 
> they came with the core given I reused the naming standards.
>
> Regards
> Tony
>
> On Saturday, September 7, 2019 at 10:54:42 PM UTC+10, TonyM wrote:
>>
>> Jeremy,
>>
>> For give me for being a bit of a hacker. I have played with making my own 
>> tiddlers with a plugin-type of info, 
>> which I note is NOT documented here 
>> https://tiddlywiki.com/#Plugin%20Fields (perhaps this is understandable)
>>
>> However I found if I started to import multiple tiddlers, and renamed 
>> $:/import to tiddlername (Capturing the import json), and modified the 
>> tiddler type to info (deleting the status field) I created myself a hidden 
>> plugin - not listed in plugins, containing the batch of tiddlers I almost 
>> imported. Reloading I had all the shadow tiddlers appearing. Of course If I 
>> edit a tiddler it looses its bold font in the "info plugin", and overwrites 
>> the shadow.
>>
>> Disabling and reloading they are gone, but listed in the new info plugin 
>> in italics and they open new empty tiddlers. The edited tiddlers from when 
>> the plugin was active remain in the wiki as regular tiddlers, and can 
>> actually be deleted, perhaps must be.
>>
>> Not only has this suddenly shed light on the plugin mechanism but I have 
>> found away to capture importing tiddlers even from multiple JSON and 
>> storing them in abeyance and made available when needed by enabling the 
>> plugin. This has exposed a method by which I can load test data into a 
>> wiki, or configuration settings. 
>>
>> This info plugin can be dragged and dropped to another wiki. 
>> Interestingly after importing If I open the "info" plugin (not a plugin 
>> title), the import mechanism offers to import the tiddlers. If it does so I 
>> expect It will create standard tiddlers that would override if it where a 
>> plugin.
>>
>> Anyway there is a lot of potential here, even if we were to create a new 
>> tiddler type of say "bundle", that used my proposed import but not get 
>> replaced as per the idea documented here;
>> Suggested Import mechanisium refactor for hackability #4231 
>> 
>>
>> I can explain further the value in such an mechanism if you wish, but 
>> perhaps the possibilities are obvious to you.
>>
>>- Packed data tiddlers
>>- Restorable and removable data with a click save and reload to add 
>>or remove
>>- Canned sets of config tiddlers to toggle multiple tiddler states
>>- Ability to drag and drop to other wikis, a bundle defined in one 
>>wiki to another
>>- A method by which to host and distribute json files of tiddlers 
>>(which are not active in the source wiki) without needing to upload 
>>independant files to the host.
>>- A method by which a developer can commit tiddlers into a plugin 
>>bundle and selectively overwrite tiddlers to release a new version. Once 
>>happy commit these changes back into the plugin. 
>>- A way to distribute macros (excluding javascript plugin code) which 
>>can be selectively activated and deactivated. Especially good for 
>> designer 
>>tools.
>>
>> Apart from the import hackability I expect we would need a mechanism to 
>> optional delete imported or overwritten (shadow) tiddlers, so they do not 
>> remain in the wiki after the info plugin is disabled or deleted. And 
>> perhaps a method to list such pseudo plugins. I wonder if the lack of this 
>> clean up could cause problems already when people add/edit/delete plugins 
>> because the overwritten tiddlers will remain as a legacy.
>>
>> Regards
>> Tony
>>
>> On Saturday, September 7, 2019 at 11:06:37 AM UTC+10, TonyM wrote:
>>>
>>> Jeremy
>>>
>>> The idea of temporary plugin sounds interesting!
>>>
>>> Tony
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop 

Re: [tw5] $:/info tiddlers not updating

[TonyM]

Folks,

I built a Tiddler bundle to display info plugins in Control panel > Plugins 
> Info

Attached, just remove the .txt extension before dropping on a test wiki. 
Then if you follow the instructions in my last post you can make your own 
info bundle.

Only one core tiddler is changed for this 
example $:/core/ui/ControlPanel/Plugins although others will look as if 
they came with the core given I reused the naming standards.

Regards
Tony

On Saturday, September 7, 2019 at 10:54:42 PM UTC+10, TonyM wrote:
>
> Jeremy,
>
> For give me for being a bit of a hacker. I have played with making my own 
> tiddlers with a plugin-type of info, 
> which I note is NOT documented here 
> https://tiddlywiki.com/#Plugin%20Fields (perhaps this is understandable)
>
> However I found if I started to import multiple tiddlers, and renamed 
> $:/import to tiddlername (Capturing the import json), and modified the 
> tiddler type to info (deleting the status field) I created myself a hidden 
> plugin - not listed in plugins, containing the batch of tiddlers I almost 
> imported. Reloading I had all the shadow tiddlers appearing. Of course If I 
> edit a tiddler it looses its bold font in the "info plugin", and overwrites 
> the shadow.
>
> Disabling and reloading they are gone, but listed in the new info plugin 
> in italics and they open new empty tiddlers. The edited tiddlers from when 
> the plugin was active remain in the wiki as regular tiddlers, and can 
> actually be deleted, perhaps must be.
>
> Not only has this suddenly shed light on the plugin mechanism but I have 
> found away to capture importing tiddlers even from multiple JSON and 
> storing them in abeyance and made available when needed by enabling the 
> plugin. This has exposed a method by which I can load test data into a 
> wiki, or configuration settings. 
>
> This info plugin can be dragged and dropped to another wiki. Interestingly 
> after importing If I open the "info" plugin (not a plugin title), the 
> import mechanism offers to import the tiddlers. If it does so I expect It 
> will create standard tiddlers that would override if it where a plugin.
>
> Anyway there is a lot of potential here, even if we were to create a new 
> tiddler type of say "bundle", that used my proposed import but not get 
> replaced as per the idea documented here;
> Suggested Import mechanisium refactor for hackability #4231 
> 
>
> I can explain further the value in such an mechanism if you wish, but 
> perhaps the possibilities are obvious to you.
>
>- Packed data tiddlers
>- Restorable and removable data with a click save and reload to add or 
>remove
>- Canned sets of config tiddlers to toggle multiple tiddler states
>- Ability to drag and drop to other wikis, a bundle defined in one 
>wiki to another
>- A method by which to host and distribute json files of tiddlers 
>(which are not active in the source wiki) without needing to upload 
>independant files to the host.
>- A method by which a developer can commit tiddlers into a plugin 
>bundle and selectively overwrite tiddlers to release a new version. Once 
>happy commit these changes back into the plugin. 
>- A way to distribute macros (excluding javascript plugin code) which 
>can be selectively activated and deactivated. Especially good for designer 
>tools.
>
> Apart from the import hackability I expect we would need a mechanism to 
> optional delete imported or overwritten (shadow) tiddlers, so they do not 
> remain in the wiki after the info plugin is disabled or deleted. And 
> perhaps a method to list such pseudo plugins. I wonder if the lack of this 
> clean up could cause problems already when people add/edit/delete plugins 
> because the overwritten tiddlers will remain as a legacy.
>
> Regards
> Tony
>
> On Saturday, September 7, 2019 at 11:06:37 AM UTC+10, TonyM wrote:
>>
>> Jeremy
>>
>> The idea of temporary plugin sounds interesting!
>>
>> Tony
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b0cd46a1-5804-435e-bc20-b9d418f0e83c%40googlegroups.com.
[
{
"text": "<>\n",
"title": "$:/core/ui/ControlPanel/Plugins/Installed/Info",
"tags": "",
"modifier": "dev",
"modified": "20190908061422295",
"creator": "",
"created": "20190908054528499",
"caption": "{{$:/language/ControlPanel/Plugins/Info/Caption}} (<$count 
filter=\"[!has[draft.of]plugin-type[info]] -[prefix[$:/temp]]\"/>)"
},
{
"text": "Info",
"title": "$:/language/ControlPanel/Plugins/Info/Caption",
"tags": "",
"modifier": "dev",
"modified": "20190908054808212",