Re: [tw5] Re: Links vs Tiddlers

[John D]

Hi @Victor,

Personally, I create a tiddler for each bookmark. When I have several
similar urls to save, for example a list of online IDE, then I create only
one tiddler for the list. This way it reduces clutter but still allows me
to tag and filter each link.

Here's my wiki : vaforis.github.io

Currently it has over 600 tiddlers and I didn't notice any lags. Each
tiddler has a link and a quick description of the url.
I created it a while ago, so this is not very efficient .. if I wanted to
redo it, I'd use fields to set the content and use a template to display
the content, it would probably shave off quite a bit of space.

Le mar. 22 juin 2021 à 16:37, Victor Dorneanu  a écrit :

> > *If you are asking if the above approach (an individual tiddler per
> link with summary pages) is better or worse than a manual page with a bunch
> of links you update as you find them then I would say, based on
> consideration for the workflow involved, quality of life interaction/steps,
> and also the fact that many users here have stated they have massive
> tiddlywiki's with little performance hit, that I would stick with what you
> have and not be too concern with the size.*
>
> That's exactly what I'm asking for. I think it should concern to much
> about the size.
>
> > *But if i consider these resources important enough to hold a place in
> my Digital Garden (having presumably read or at least skimmed the
> articles), then i typically have something more to say about them.*
>
> Exactly! I also use to annotate my bookmarks; at least I have a small note
> there. Just having a link there has no value for me.
>
> > *In light of your recent article on Note Taking in 2021
>  (excellent piece,
> b/t/w, what really set my own wheels turning
> , along with a good
> few others), i don't guess i'm telling you anything new, Victor... But
> anyway: thanks again for sparking a bit more introspection into this
> process i too often run, but still don't think critically enough about!*
>
> Thank you very much! I'm planning to add more posts regarding my workflow.
> On Tuesday, June 22, 2021 at 3:11:11 PM UTC+2 ludwa6 wrote:
>
>> Hey @Victor: That's a good question- simple, but profound- one that all
>> of us here must answer for ourselves some non-zero number of times most
>> days.
>>
>> The answer to this for me is a followup Q: What version of my future self
>> (i.e. in what context) do i imagine would find this resource to be most
>> useful?
>> If the answer to that Q comes to me easily enough, then tiddler content
>> -description, crossref link(s), tag(s)- then the NoteMaking tends to flow
>> quite naturally.
>>
>> If OTOH it does not... Well then i've got yet another note w/ a set of
>> links that i may very likely never bother to click.  Take for example your
>> note on 4-Day Work Week ,
>> which links to one canonical definition from Wikipedia, and two articles on
>> the topic that i know nothing about beyond the title, where it was
>> published, and possibly when (date is URL-encoded on one link, but not on
>> the other).  If i'm only interested in the simplest form of NoteTaking
>> -i.e. resource curation, the Librarian role- then maybe that serves the
>> need.  But if i consider these resources important enough to hold a place
>> in my Digital Garden (having presumably read or at least skimmed the
>> articles), then i typically have something more to say about them.
>>
>> In light of your recent article on Note Taking in 2021
>>  (excellent piece, b/t/w,
>> what really set my own wheels turning
>> , along with a
>> good few others), i don't guess i'm telling you anything new, Victor... But
>> anyway: thanks again for sparking a bit more introspection into this
>> process i too often run, but still don't think critically enough about!
>>
>> /walt
>>
>> On Tuesday, June 22, 2021 at 11:22:29 AM UTC+1 Victor Dorneanu wrote:
>>
>>> Hi,
>>>
>>> since I was not able to find such a thread, I've decided to create a new
>>> one. I just want to read your opinions when it's better to just have links
>>> (inside a tiddler) and when one should create tiddlers for them (as
>>> bookmarks).
>>>
>>> I'll try to describe my current problem. At the moment I use this
>>> Bookmarks plugin
>>>  to
>>> organize my bookmarks. Examples:
>>>
>>>- List of bookmarks for Tiddlywiki 
>>>- List of bookmarks for Golang 
>>>
>>> As I discover more sites/resources I'd add them as a bookmark and
>>> they'll be automatically listed on those pages. However, doing so will also
>>> increase the size of my Tiddlywiki instance. I use nodeJS and call 
>>> *tiddlywiki
>>> tw5 --build 

Re: [tw5] Re: TiddlyWiki SO cool ...

[John D]

I can share mine : https://curatedvideos.github.io/
This wiki, as the name suggests, curates videos and channels from high
quality content creators.

Le ven. 25 juin 2021 à 23:47, TW Tones  a écrit :

> TT,
>
> I*ts sad we can't easily find wikis "in the wild." I don't actually know
> what has been made!*
>
> I too would like to see more in the wild however for myself a lot of my
> wikis are for personal organisation, and many are in different states of
> completion. They are a work in progress, the privacy or perfectionism
> desires stop them being visible to the world. I presently tend to share
> components rather than full wikis.
>
> One of my key realisations with tiddlywiki is it can be used as continuous
> improvement development platform, it responds to the way it grows, its past
> and the futures I imagine. Tiddlywiki is revolutionary and evolutionary.
>
> Tones
>
>
> On Thursday, 24 June 2021 at 18:51:36 UTC+10 TiddlyTweeter wrote:
>
>> Ciao cj.v ...
>>
>> Thanks for the detailed reply.
>> I basically agree with most everything you wrote.
>>
>> One of the slightly odd things with TiddlyWiki is we got masses of great
>> wikis about doing code in TiddlyWiki easily available.
>> BUT very few listed wikis of end-product applications.
>> That is likely much to do with fact TW design eschews being tracked by
>> Google et al.
>> Its sad we can't easily find wikis "in the wild." I don't actually know
>> what has been made!
>> That is an impediment to being able to do a decent SHOWCASE of variant
>> uses and applications suited to specific end purposes (other than coding TW
>> for the pleasure of it) :-(
>>
>> Best wishes
>> TT
>>
>> On Wednesday, 23 June 2021 at 16:47:43 UTC+2 cj.v...@gmail.com wrote:
>>
>>> Although I'm no fan of social media (Twitter, Instagram, Tik Tok, etc.
>>> etc.), my answer would be YouTube, Blogs and all social media options.
>>>
>>> Via titles that equal use cases, and not titles about the product (well,
>>> with loads of metadata some somebody looking for TiddlyWiki, or TW, can
>>> find these social media jewels.)
>>>
>>> So draw folk to the videos and such via problems that need to be solved,
>>> or approaches to doing certain things.
>>>
>>> For example, thinking of the discussion about notetaking and notemaking.
>>>
>>> Instead of a social media something like "Notetaking with TiddlyWiki",
>>> draw folk in with something like "Agile Notetaking" (well, some title that
>>> draws folk, in the spirit of whatever draws people to viral videos.)
>>>
>>> So flood the media with marketing not of the product itself, but of the
>>> full breadth and depth of solutions that coincidentally are handled with
>>> TiddlyWiki align with whatever plugins when they apply.
>>>
>>> As another example, my Le P'tit Aurèle
>>>  project.  If I were to (when the
>>> project is ready) blitz social media with stuff related to that project, it
>>> would all be with titles that fall under an umbrella of "Constructing
>>> Comprehensive yet User-Friendly Multilingual Dictionaries"  (well,
>>> something sexier that can go "viral").  And every "post" to whatever social
>>> media would have a "by the way, this was built with TiddlyWiki."
>>>
>>> If there are a ridiculous number of videos out there on how to do
>>> real-world good stuff and they all of the things done happen to be done
>>> with TiddlyWiki, I think that would grab some attention.
>>>
>>> Something like that ...
>>>
>>>
>>>
>>>
>>> On Wed, Jun 23, 2021 at 6:15 AM TiddlyTweeter 
>>> wrote:
>>>
 Ciao cj.v...

 Yeah. In the practicalities of dealing with code I think it is easy to
 forget/set-aside certain things,

 The FREEDOM TW brings to dealing with information design and use is not
 shouted enough.

 I'd love if the tool were more widely used.
 I'm thinking a bit here out loud.

 How can we communicate better to potential end users its fundamental
 benefits?

 Best wishes
 TT
 On Wednesday, 23 June 2021 at 03:47:15 UTC+2 cj.v...@gmail.com wrote:

> That would be a perfect theme song for TiddlyWiki.  Freedom for sure !
>
> I find Jon Batiste one of the coolest guys.  Wonderfully talented and
> seems like a genuinely awesome human being.
>
> On Tuesday, June 22, 2021 at 6:04:50 PM UTC-3 TiddlyTweeter wrote:
>
>> https://youtu.be/3YHVC1DcHmo
>>
>> Oh yeah
>> TT
>>
> --
 You received this message because you are subscribed to a topic in the
 Google Groups "TiddlyWiki" group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/tiddlywiki/HK3SOQdYvTs/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 tiddlywiki+...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/tiddlywiki/ea5e6f6d-f14b-4a6c-9a11-6504f80fe279n%40googlegroups.com
 

Re: [tw5] Re: TiddlyWiki toolmap submissions

[John D]

Hello oflg,

Very nice plugin, I love the simplicity of it !
If I may give a suggestion : I love your fish icon, however the text inside
is too small, maybe it would be best to either make it bigger or not in the
icon altogether ?

Best wishes,

Télumire

Le sam. 26 juin 2021 à 08:45, oflg li  a écrit :

> Hi Dave,
>
> I create a   plugin Fising
>  , a  plugin fishing tiddly with Anki
>  algorithm.
> Github repository : https://github.com/oflg/fishing.
> Demo site oflg.github.io/fishing/
>
> :)
> 在2018年2月7日星期三 UTC+8 上午10:24:27 写道：
>
>> Hi all
>>
>> Tonight I finished going through the existing sites I know about and
>> adding entries to the TiddlyWiki Toolmap (
>> https://dynalist.io/d/zUP-nIWu2FFoXH-oM7L7d9DM). Thank you, Jesus! Just
>> over 500 entries. From here on out it will just be a matter of maintaining
>> it. That seems to be the hard part: some of the sites I consulted had dead
>> links or hadn't been updated in a long time.
>>
>> *You can help me: *
>>
>> Please contact me either by replying to this thread or emailing me
>> directly at dgif...@crcna.org if:
>>
>> 1) you find items that are missing and ought to be on that list.
>> 2) you find information that needs correcting - dead links, items that
>> would be better placed in a different category, items that need better
>> descriptions, etc (Josiah aka TiddlyTweeter has been helping me a lot with
>> this - thanks a bunch!)
>> 3) you create a plugin, macro, theme, or adaptation of TiddlyWiki 5 that
>> you would like included. For example, since I started the toolmap, I have
>> been adding items I find here, like the new MyMenus. If you can tell me
>> what category it should go under, even better.
>>
>> *Two other favors I ask:*
>>
>> 1) Maybe the powers that be can pin this thread at the top of the Google
>> group as a reminder?
>>
>> 2) If you create a plugin, macro, theme, or adaptation, put something
>> like "Presenting" or "Introducing" or "New plugin" at the beginning of the
>> discussion thread, to clearly mark it so I will spot it when I check the
>> Google group, which I tend to do every 2-3 days.
>>
>> Thanks in advance for your help. Now go play with TiddlyWiki and come up
>> with some cool new stuff!
>>
>> Blessings,
>>
>> Dave Gifford
>>
> --
> 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/141a8a89-b939-4090-821b-90d7f1e768aan%40googlegroups.com
> 
> .
>

-- 
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/CADf1GSk56060Kjz%3DfxPOuKvsC2mXOBAg416WydG77hGkaiHdYw%40mail.gmail.com.

Re: [tw5] Re: Artwork for v5.2.0

[John D]

Hi everyone, here's my honest feedback, I hope it will be useful :

springer
 :
love the simplicity of it. I instantly understood what the update was
about, only thing missing is the drag feature, which I agree with saq
seems too important to be left out. One way around it maybe would be to
"drag and drop the whole image of that logo", adding a mouse cursor at the
edge of it .. this would add a lot of clutter tho. The variation @Mohamed
did, while showing all the main newelty of this update, is too cluttered
IMO. Color wise, I think it would be best to use the color palette of the
vanilla TW, since new users will see TW in the vanilla theme and might
think that the black and white logo is a way to show that now tiddlywiki as
a night mode option. While this is technically true (with the palette),
this is not part of the update so it may be a bit confusing. This goes for
the font you used too, I might be wrong but it looks like it's not the
default font used by TW. The feature slogan is a nifty touch but goes
against the brief. You could left the fields empty, use gibberish text
(lorem ipsum), or use a conceptual approach and use rectangular bars as a
placeholder (something you can see on some website, like when youtube is
loading content). I personally don't like the masked versions. This makes
the logo trapped into a shape, while all the previous splash screens (that
I know of) were either rectangular or open. The mouse cursor suggests that
it's hovering a link, while we see a field in the picture so it's a bit
confusing.
iamdar 
: the fish logo is very cute and the cloud of files is a great way to show
how tiddlers are interconnected. I can't see how this relates to this
particular update though. Maybe the fish could be added by drag and drop at
the center of the files ? It would show how we can now easily add images
inside a wiki, like dropping a fish in a pond. You could even add ripples,
but this may be too much. To be honest, I'm really not a fan of the O of
the version number though, to me it looks like you meshed up two icons
together instead of one. It also makes the numbers a bit less readable.
While it's a cool 3D effect, to my eyes it's jarring next to the flat,
non-shaded style of the fish. I also fail to see how it relates to the
update.

IMO the version with a white background looks better, the fish is a bit
drowned in that blue (no pun intended).Your second proposition, without the
fish, seems a bit better in regard to my previous point (only one logo is
best). Maybe use {} instead of [] to appeal to the json change ? I know
both are used in JSON but the [] looks more like a tiddlywiki link. Again,
not a fan of the 3D look. I do like the dotted line however, it makes it
very clear that the 0 is being dropped. It would be best to use a grab
cursor instead of a pointer, again it looks like we are about to click on a
link instead of drag a picture. I see you corrected it in your 4th
attempt, this looks much better IMO :)

brunsb 
: using brackets is a really good idea to show how tiddlywiki transit to a
json format. However if I understood correctly, this change does not
concern the typical end user that much, and I'm not sure this will be
understood for someone with no coding background. I feel like @jermolene
should clarify that point : who is the targeted audience of that logo ? Do
you want to appeal to new users or to devs ? Back to your design @brunsb :
while I think it's a good idea, I wouldn't put the red triangle. It doesn't
add anything (?) and feels out of place to me.

I like your second design
 a lot
! It is simple, very clear, we see the drag feature, the version
number. Maybe it would be best to not obfuscate the Tiddlywiki name
however. The mouse cursor should be a grab cursor.

Brian Radspinner
 : the
dashed line is a good way to represent the drag feature, I like that !
The overall composition looks a bit rough however. Your third version
 looks
much better, I'm not sure about the orange background tho.

james :
Your logo looks like it implies that TW now has 3D anaglyph capabilities,
sorry I don't get it .. the "breaking things apart and putting them back
together" concept is clever, but the way you represent it with different
colours led me to think that this is about colors, maybe printing ? Also I
fail to see how this modular idea is representative to this update, AFAIK
tiddlywiki always was modular in the sense we could add tiddlers, plugins,
etc easily.

PS : Regarding the change of name, for all 

Re: [tw5] Re: How make TW appear alive?

[John D]

Well you did ask "What does “nicely designed” mean?". Imo it only has two
meaning - following "universal" design rules and/or personal preferences.
Rather than discouraging, showing how we can make TiddlyWiki beautiful
could inspire people to be more creative, especially since TW community is
very supportive and friendly. Function is as important as design, because
no matter how useful something is, if it's not pleasing to use (ie, the UX
is bad) then it will not be used.

I agree with you, both "usefulness" and design are important. Projects like
Nico's Notebook theme or Muuri Storyview by BurningTreeC helps bring more
people aboard the TiddlyWiki train, and not only tech enthusiasts.

Here's another great wiki with an unique design that I like:
https://philosopher.life/


Le lun. 25 oct. 2021 à 02:18, Charlie Veniot  a écrit :

> Oh good lord, please don't.  Good design has been part of my bread and
> butter since 1995, and I enjoy it very much in that context, but it is an
> annoying topic for me outside of work.
>
> However, that kind of stuff might be of interest to a whole bunch of other
> folk, but really should be in a separate thread.
>
> My point is: I am concerned that "pretty" becomes something too important
> in general, something that discourages anyone from demonstrating some
> wildly good stuff done with TiddlyWiki just because the community has put a
> premium on "pretty" when not all folk have the time/desire/skill to apply
> all of the theories of pretty design.
>
> There's nothing wrong with pretty design, but I look past that really
> quick because it is a fluffy distraction from the substantial stuff: what
> is it doing, why is it doing it, when is it doing it, and how is it doing
> it?
>
> Most folk may not agree, but a pretty TW does not in my mind's eye make
> for appearance of alive.
>
> All of that aside: if there's a desire to put together a gallery, be
> careful focusing on pretty.  If you're going to pitch TiddlyWiki based on
> pretty, there are all kinds of products out there that do pretty, and very
> easy for the layperson to do pretty with those products.  Might be hard for
> TiddlyWiki to compete with other products when it comes to easy-of-pretty.
> However, TiddlyWiki kills at being a platform for solutions.
>
> If you want to showcase TiddlyWiki, then find the solutions, a bunch of
> folk who want to make them pretty, go ahead and make them pretty, then
> showcase the hell out of the solutions.
>
>
>
>
> On Sunday, October 24, 2021 at 7:24:08 PM UTC-3 Télumire wrote:
>
>> http://atlas-disciplines.unige.ch/ is a beautiful example of what can be
>> done with TW.
>> I've learned about it thanks to Soren Bjornstad in his book
>> GrokTiddlywiki : https://groktiddlywiki.com/read/#Public%20Wikis
>>
>> @Charlie_Veniot while beauty is indeed subjective, it is possible to use
>> things like psychology and color theory to create a good design.
>> See https://www.nngroup.com/topic/psychology-and-ux/ for example - I can
>> provide more links if you are interested ^^
>> Le samedi 23 octobre 2021 à 16:27:01 UTC+2, hww...@gmail.com a écrit :
>>
>>> Cade:
>>>
>>> I appreciate your interesting comments, perhaps because my age has
>>> advanced to the stage that my medical data is of much greater importance to
>>> me.  Also, I have become much more cynical about medical practitioners who
>>> share data with the BigPharma oligopoly and the inevitable consequences of
>>> well-intended attempts to make all of a patient's data available on-line so
>>> that GPs and Specialist can share a holistic view of a patient.
>>>
>>> For my part, I am much more inclined to build by own repository of all
>>> my medical information and share it with just the practitioners I trust and
>>> select as care-providers.  This is particularly true now that the
>>> clinic-based GP I start with, suggests that I find my own specialists, that
>>> he can then refer me to, since the Administrative wait times are on the
>>> order of a year for a referral.
>>>
>>> In that context, I am inclined to ask you "What are the impediments to
>>> sharing the ... cardiovascular Data ..." you have.  Particularly given that
>>> you already understand fine-grained design concepts and that is should be
>>> possible to use these to anonymize a selective view of the information.
>>>
>>> Regards,
>>> Hans
>>>
>>>
>>> On Tuesday, October 19, 2021 at 11:18:29 PM UTC-4 Cade Roux wrote:
>>>
 I wish I could share the TWs we generate for our cardiovascular Data
 Mart product here.  We generate the data dictionary/manual in a TW and all
 our test outputs are in a few TWs organized by test groupings.  It
 definitely satisfies 2 and 3, as far as 1, I am still tweaking it to be
 more and more attractive and useful all the time.  We started off very
 simply because we didn't want to commit too deeply down a path which would
 limit us from retargeting our documentation to HTML or Word later.
 However, as we 

Re: [tw5] Re: Combobox idea

[John D]

Thanks @Mat! Sure, go ahead :)

Le ven. 5 nov. 2021 à 08:51, Mat  a écrit :

> @Telumire - Man, that turned out quite ambitious. Looks great! Of course,
> we're way past "I found a way to quickly throw together a combobox", but IF
> one has the styles, perhaps as part of ones standard custom stylesheets,
> then it is only a matter applying it with @@.combobox.
> For the record, here's the general and simplified call:
>
> @@.combobox
> <$edit-text field=selection placeholder="type or select"/>
> <$select field=selection>
> ...options list...
> 
> @@
>
> @Telumire - I put up a combobox.tiddlyhost.com for the idea. May I
> include your stylesheet there, obviously with credits to you and a ref to
> this thread? The purpose with the page is to make it findable when one
> needs it. (I temporarily just made that page public, it is obviously not
> ready for anyone to see.)
>
> <:-)
> On Friday, November 5, 2021 at 2:00:46 AM UTC+1 Télumire wrote:
>
>> Ok I think this time I got it. Here :
>> https://Telumire.github.io/TiddlyTweaks/index.html#:%5B%5BCombobox%5D%5D
>>
>>
>>
>> Le jeudi 4 novembre 2021 à 23:17:51 UTC+1, Télumire a écrit :
>>
>>>
>>> @Eric Shulman my bad, I should have tested it a bit more. Thanks for
>>> pointing this out ! @Mat, this is because the select element is OS
>>> dependent according to this stack overflow answer :
>>> https://stackoverflow.com/a/1895485/11549574
>>>
>>> This one can be used properly inline (with a text after and before) and
>>> use a pseudo element as a select button (I left it as a red square but it's
>>> easy to customize), but there is still an issue with vertical align.. I'm
>>> still sharing it just in case, if I find something better I'll post it  :
>>>
>>> <$vars
>>>
>>> height="20px"
>>>
>>> >
>>> 
>>> .combobox{
>>> position: relative;
>>> display: inline-block;
>>> width: 150px;
>>> height:<>;
>>> background:red;
>>> margin-right:20px;
>>> }
>>>
>>> .combobox .select-btn{
>>> width:100%;
>>> cursor:pointer;
>>> opacity:0;
>>> pointer-event:all;
>>> }
>>>
>>> .combobox input{
>>> top:0;
>>> position:absolute;
>>> width:100%;
>>> }
>>>
>>> .combobox .drodown-btn{
>>> width:calc(<> + 100%);
>>> top:0;
>>> position:absolute;
>>> cursor:pointer;
>>> }
>>>
>>> .combobox .drodown-btn:after{
>>> display:block;
>>> content:"";
>>> width:calc(<> + 4px);
>>> position:absolute;
>>> inset:0 0 0 auto;
>>> background:red;
>>> pointer-events: none;
>>> }
>>> 
>>>
>>>
>>> BEFORE<$edit-text field=selection placeholder="type or select"/>AFTER
>>>
>>> before
>>> 
>>> 
>>> <$select field=selection class="select-btn" >
>>> A Tale of Two Cities
>>> A New Kind of Science
>>> The Dice Man
>>> 
>>> 
>>> <$edit-text field=selection placeholder="type or select"/>
>>> 
>>> after
>>>
>>>
>>> Le jeudi 4 novembre 2021 à 22:48:23 UTC+1, Mat a écrit :
>>>
 @Télumire, I appreciate your effort! @Eric, thank you for your shrewd
 analysis!

 Does anyone know why it is barely possible to manipulate this dropdown
 though? I do get the following to work, so the options *are*
 targettable:

 .select-btn option {background:red}

 ...but attempting to e.g position absolute, margin-left, or some such
 fails. It is as if they are immune to most styling.

 @anyone - is this because of the SelectWidget implementation, or is it
 the underlying html select / option tags? Surely people will want to style
 these? If it indeed is the underlying html tags, then is it at all possible
 to do something about it in the SelectWidget, hypothetically?

 Thanx!

 <:-)



 On Thursday, November 4, 2021 at 9:42:29 PM UTC+1 Eric Shulman wrote:

> On Thursday, November 4, 2021 at 12:31:14 PM UTC-7 Télumire wrote:
>
>> Here's the code to push the dropdown in the proper place :
>>
>
> There are layout problems with this solution.  To see the issues,
> try putting "before" and "after" text surrounding the "combobox" span:
>
>
>> *BEFORE*
>
>
>> <$select field=selection class="select-btn" >
>> A Tale of Two Cities
>> A New Kind of Science
>> The Dice Man
>> 
>> <$edit-text field=selection placeholder="type or select"/>
>>
> *AFTER*
>
>
> and compare this with the result of showing only an $edit-text widget:
>
> *BEFORE*<$edit-text field=selection placeholder="type or select"/>
> *AFTER*
>
> For the simple inline $edit-text widget, the BEFORE/AFTER text appears
> as you would expect:
> immediately preceding/following the input element and vertically
> aligned with the middle of the text
>
> However, note the placement and vertical alignment of the "combobox"
> elements:
> The edit input/select elements appear vertically aligned *below the
> baseline *of the surrounding BEFORE/AFTER text,
> and the AFTER text is immediately following the input element, rather
> 

Re: [tw5] Re: Automatically generating grocery list by clicking on cooking recipes ?

[John D]

/!\ I discovered there is a small issue with my data tiddler editor :
plugins tiddlers are also affected by the viewtemplate ! This is a bit
annoying so here's how to fix it :

replace

<$list filter="[is[current]get[type]match[application/json]]" variable=_>

by

<$list 
filter="[is[current]!is[shadow]!has[plugin-type]get[type]match[application/json]]"
variable=_>

Updated tiddler : download it here
<https://mail.google.com/mail/u/0?ui=2=bcb2aed9e5=0.1=msg-a:r-3271639119415285557=att=safe=f_kww17jjs0>

Also please note that this tool will only work with application/json data
tiddler, in the form { "key":"value", "key2":"value2" } (no nested data!)
To create a new recipe, create a new tiddler and set the type to
application/json (or clone an existing recipe).

If you only want this viewTemplate to work for data tiddler with the tag
*recipe*, change the list filter to

"[tag[recipe]is[current]!is[shadow]!has[plugin-type]get[type]match[application/json]]"



Le mar. 7 déc. 2021 à 12:28, Télumire  a écrit :

> This thread was a very interesting read and a fun coding experience,
> thanks to all of you ^^
> And @cassandra, I'm french too and happen to have an interest in cooking
> so please share your work ! :)
> Le mardi 7 décembre 2021 à 02:39:55 UTC+1, cj.v...@gmail.com a écrit :
>
>> "Je batch cook? "  Moi too, et thank le p'tit bébé Jésus parc'que-j'batch
>> mange...
>>
>> Which makes me think right away of "Le Chiac est la solution
>> <https://www.youtube.com/watch?v=iqSRvbsEcQc>" and something a gal once
>> told me:  "ma soeur va shack-é up avec son boyfriend."
>>
>> BTW: I love "development" with/in TiddlyWiki, from the
>> mostly-all-about-data-and-organization (Le P'tit Aurèle
>> <https://leptitaurele.neocities.org/>) to some pretty out-there kind of
>> "programming" (BASIC Anywhere Machine
>> <https://sites.google.com/view/basicanywheremachine>).  The stuff that
>> can be done with TiddlyWiki is really amazing.
>>
>> But collaborative "development" via forums?  Yeah, that's major heartburn
>> for this kid.
>>
>> On Monday, December 6, 2021 at 9:10:28 PM UTC-4 cassandr...@gmail.com
>> wrote:
>>
>>> Thank you all !
>>>
>>> In the order :
>>> @CJ : thank you for your help ! I can see how the type of plateform for
>>> developing can be awful to use haha. Hope my little project was interessing
>>> for you ! Cheers =D
>>>
>>> @Mat : I'm keeping the NewTids macro in my mind for future use, it does
>>> seem pretty useful ! For now, with a mix of google lens on my phone and
>>> copy pasting directly in my computer, I'm doing it pretty fast ! Just a bit
>>> of tweaking and adjusting the format is fine.
>>> I work in a field which sometime is a bit taxing mentally and I find
>>> doing simple repetitive task help me allievate the stress haha.
>>>
>>> @Stobot : thank you for the files ! I imported both yours and John D
>>> methods and while Télumire's is more completed, I really like your idea and
>>> how you formated it ! I think it can be pretty useful for a lot of
>>> situation.
>>> As a total newbie, TW was a bit hard to get into at first. I watched a
>>> serie of tutorial video and read some more to only begin to have a normal
>>> functionnal TW.
>>> Your idea of incremental tutotal could be a great way to facilitate the
>>> appropriation of the TW for beginner !
>>>
>>> @And finally Télumire/John D : thank you a lot for all your work ! I
>>> tested it and it worked just fine. It answers to all my problem and more
>>> haha.
>>> Reading the programing behind was very interessing ! I understood where
>>> it comes from (but I never could have written it as easily as you and not
>>> for a bit of time).
>>> Thank you as well for the ressources you listed. I will read it to
>>> optimize my utilisation of TW which is such a great tool but I only scraped
>>> the surface.
>>> The Data Tiddler Editor you writted was way way way too complicated for
>>> me to understand but I can really appreciate what it does ^^ !
>>> Anyway, thank you again !
>>>
>>> With thing as they are now, I guess I can do a pretty good version of
>>> the TW I imagined. I will maybe post it here when it will be a bit fuller
>>> but I'm french so all the tiddly/recipe/ingredient would be too. Not sure
>>> if it could help someone without the book (which is "Je batch cook toute
>