Passingby!
Tony!
I agree there is limited documentation on TW5 and some of them in
tiddlywiki.com are not good for learning purpose and may target developer
or advanced users.
If we could improve the documentation, then I think the learning curve will
be short.
For the Javascript and TWC, I
Passingby,
I empathise with your feelings, this happened to me initially, feeling also
that TW5 "had too long a learning curve", rather than the quicker "steeper"
learning curve (common misuse of the "learning curve" phrase avoided here,
the horizontal on this curve is time, and the vertical
On Thursday, July 5, 2018 at 12:09:15 PM UTC-6, Jed Carty wrote:
>
> There is a huge usability gain, you don't need to know any javascript to
> make something new and useful with tiddlywiki.
>
I was a hobby level programmer in javascript. I remember many years ago in
TWC using Eric Schulman's
Folks,
Jed and Mark, I agree with your apparently conflicting positions here,
here is something I have realised recently.
TiddlyWiki is mostly designed to act on its own elements, tags, tiddlers,
fields etc... and it does this in the way any "High Level" programming
language does, it treats
Perhaps I am unique, but it took me a much longer time to learn javascript
than it did to learn wikitext, so I very much disagree that javascript is
only a little harder than wikitext. And usability isn't functionality, so
if a specific thing can be implemented isn't relevant to it. The things
I would say there's a usability *loss*.
As soon as you get beyond simple list loops, there's no clear way forward.
Also, there's tons of documentation on JS. Standard procedures and
techniques.
Take a look at recent post
https://groups.google.com/forum/#!topic/tiddlywiki/IpKqoJbs35c and
There is a huge usability gain, you don't need to know any javascript to
make something new and useful with tiddlywiki. I made most of my earlier
plugins that I still use before I knew any javascript.
If it were just a neat javascript page that you used javascript to make
things in than I never
There's lots of great stuff about TW5.
But the kit the user is given is incomplete compared to JS. If it was a
complete kit, that would be one thing. The string operations are anemic.
No logic operators. Ahem, nothing for creating new tiddlers from regular
expressions (#2963).
There's a post
Jeremy!
I really appreciate your great work. I love TW5 and I use it in my daily
work more than any other tools! We know you put a lot of time and
distribute what you did free of charge and people use it some of them even
don't know who brought this amazing tool to them.
One suggestion here
Thank you Mark!
I actually do most the job with the current TW5 features and it is amazing
in preparing semantic content.
Cheers
Mohammad
On Thursday, July 5, 2018 at 7:24:41 PM UTC+4:30, Mark S. wrote:
>
> Well, it can be used to write your own widgets, which I found really
> complicated
> On 5 Jul 2018, at 15:54, 'Mark S.' via TiddlyWiki
> wrote:
>
> I'm not sure what was gained by giving TW5 it's own tree, since the DOM based
> approach obviously worked in TWC.
Well, that’s 7 years of my life wasted!
But seriously, do you not see any advantages of TW5 over TWC? To me,
Here's a link to an interesting post on the subject by Eric S.
https://groups.google.com/forum/#!topic/tiddlywiki/M6wADVDjyTE
-- Mark
On Thursday, July 5, 2018 at 7:54:41 AM UTC-7, Mark S. wrote:
>
> Well, it can be used to write your own widgets, which I found really
> complicated and
Well, it can be used to write your own widgets, which I found really
complicated and confusing, and not well-documented.
It's easier to write your own javascript Macros or Filters. The easiest
way to do that is to find a simple one (like the "now" macro) , clone it,
and then modify it to use
Hello Mario,
Thank you for your reply!
I was playing with JavaScript and was curious to see how can I add JS code
to Tiddlywiki.
I understood JS code are not allowed to directly interact with the DOM
objects!
I appreciate if you introduce me some simple cases (tutorial) for learning
how JS
Hi Mohammad,
In short: No.
I think it would be easier, if you describe, what you want to achive. So we
may have a solution, or could provide help.
more details:
Your code directly manipulates the "redered output" in the DOM and also
keeps program state in the DOM. This is similar to
15 matches
Mail list logo
