Hi, i built a new $http.client widget and packaged it as a plugin.
Using this widget you can turn your tiddlers into HTTP requests. The widget will create new tiddlers when responses are received.
The client has two modes - filter, json.
In filter mode, it can turn your tiddlers into HTTP requests.
In json mode, you provide the input as a JSON array.
Detailed documentation is available through the links below:
Videos
Website
Thank you for sharing this. It looks quite powerful. I’ve read through the documentation and watched the videos. I believe I know how to use it. I don’t think I have a particular need for it now, but can imagine wanting it in the future.
To my mind, there’s one thing missing: a motivating example. I’m a coder who lives in HTTP, and have gotten relatively experienced with TiddlyWiki. So I’m sure I can come up with uses for this. But what itch did you have that you could best scratch by creating this http client? Was there a single usage you initially needed or did it grow out of a number of unrelated needs? Would you expect there to be a large number of users or only a handful? If the former, what sorts of things can you imagine them building with it? A single real-world example would help answer these questions if you can describe a fairly simple one.
Right. I’m not a programmer.
If I could I’d do a TW that communicated with the server for this group.
In a suggestive way I waddled a little further with @telumire’s input in …
Then I gave up from lack of the knack.
Would @jjkavalam’s tool let one, for instance …
I am maybe completely off track in those questions!
Please let me know if I’m an idiot.
TT