On Saturday, 22 December 2018 00:15:11 UTC+1, TonyM wrote:
>
> Joe,
>
> I empathise with you learning journey, having come to tiddlywiki in a 
> similar way, as an IT Professional with coding in my past. Perhaps this 
> perspective can help with the conceptualisation.
>
> In case it helps, filters and the filter runs are somewhat like command 
> line filters piping selecting etc... but in Tiddlywiki the primary purpose 
> (but not the only one) is the manipulation of tiddlers, and lists of 
> tiddlers so they lean towards handing tiddler titles, of course you can 
> list fields in the current tiddler, or throughout the whole wiki, or 
> generate virtual titles (EG Range operator)
>
> Tiddler titles are in effect the key to a tiddler, and tiddlers are the 
> standard unit of data, "the records in the database". But of course these 
> records also provide the user interface and bootstrap the whole wiki in a 
> file model.
>
> You said "equivalent to queries in predicate logic", I tend to think of it 
> as the previously defined but forgotten 4th Generation programming 
> languages  
> <https://en.wikipedia.org/wiki/Fourth-generation_programming_language>
>
> In effect we are normally processing sets at a time, even if that set has 
> zero 1, or many members, tags on a tiddler are just a subset as are fields. 
> the special design in tiddlywiki is, changes in these lists are 
> automatically reflected in what you see and it does this economically by 
> using trees to identify the effected tiddlers.
>
> TiddlyWikis tag line is "a non-linear personal web notebook", and this 
> explains somewhat its structure and concept, but I now consider "tiddlywiki 
> a platform" on which to build almost any algorithm, and deploy it almost 
> anywhere.
>
> For 3Generation language coders there is a need to in someways forget a 
> little of how we conceptualise programming, because tiddlywiki is handling 
> the relationship and changes in tiddlers across the whole wiki, provides 
> the tools for list / set management and more. Of course if you want to be a 
> developer, rather than a TiddlyWiki Super User, you may need to revert to 
> the regular programming language models, but then you need to learn about 
> the way in which tiddlywiki achieves its magic. See 
> https://tiddlywiki.com/dev/ especialy 
> https://tiddlywiki.com/dev/#TiddlyWiki%20Architecture
>
> Of course if you are across object oriented coding you can in some ways 
> treat tiddlers as objects, or a html developer think of it as website 
> design (A lot of html and css works out of the box in TiddlyWiki, unless it 
> needs javascript), if you have database skills you can build databases 
> using tiddlers or datatiddlers, if you are a user interface designer you 
> can use tiddlywikis logic, tiddlers, html and css. If you are a javascript 
> designer, you could build widgets and filter operators and create plugins 
> that bring in open source javascript solutions to tiddlywiki - one of the 
> best already is codemirror but there are many more in math and 
> visualisation as examples.
>
> If you want to be involved in core development perhaps building a widget 
> and a filter operator would be a good start, I would be happy to provide 
> some ideas if you want a project.
>

Writing a widget is on my lists of things to do :-) - subject to the 
condition that it is clearly described and well-documented and 
contains beautiful code (which makes it tricky)

At the moment I'm staring at the documentation and writing zillions of 
small test cases to
test my understanding.

In my opinion, the examples are too tough - the macro definitions *start* 
with parametrised macros 
at which I think "what about macros with zero parameters" the notations 
$var$ and $(var)$ and
<<var>> are used in ways that are unfamiliar to me - is this eager or lazy 
evaluation? what is the scope
of variables? what is the visibility of a macro? is it public/private, are 
their global variables etc.

The way of programming by creating a bundle or tiddlers whose net effect is 
to do something
is also unfamiliar (rather than just writing one module that does 
everything)


> However there is so much more than can be done without going into core 
> development, because this is a platform of almost infinite possibilities.
>

It's great
 

>
> Welcome to the community, I see by your questions, you are likely to be a 
> productive member.
>

Thanks for those kind words :-)

/Joe
 

>
> Regards
> Tony
>
>
> On Thursday, 20 December 2018 22:21:15 UTC+11, joearms wrote:
>>
>> There is method in my madness :-)
>>
>> I'm trying to relate stuff I don't know (ie the tiddlywiki) to stuff I do 
>> know
>> (ie regular programming languages)
>>
>> /Joe
>>
>>
>>
>> On Thursday, 20 December 2018 11:58:31 UTC+1, @TiddlyTweeter wrote:
>>>
>>> J & J,
>>>
>>> "Reverse Polish" I understand.
>>>
>>> This thread is interesting for highlighting, I think, how an explanandum 
>>> can clarify the variety of explanans.
>>>
>>> josiah
>>>
>>> joearms wrote:
>>>>
>>>>    B C +A
>>>>
>>>> is pretty neat - it eliminates the parentheses OR becomes whitespace 
>>>> and AND becomes +
>>>>
>>>> It's a Reverse Polish Monad Filter (RPMF)
>>>>
>>>

-- 
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 [email protected].
To post to this group, send email to [email protected].
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/70eeb977-de80-43ee-8893-6dfe34d22a7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to