I will Josiah! I am working on a wiki to document the possible OOP in Tiddlywiki using KISS principle.
--Mohammad On Thursday, January 23, 2020 at 12:53:28 PM UTC+3:30, TiddlyTweeter wrote: > > Ciao Mohammad > > I think what is interesting is you are bringing out how you can use > "\define" cascade order intelligently to reduce code redundancy and > leverage function. > > In a way it is obvious--more experienced users use it already implicitly. > But I think an explicit more formal approach could be very helpful! > > It would be interesting to see a more complex example. As TonyM commented, > I think you'd need a methodology to keep track of it. > > Best wishes > TT > > On Thursday, 23 January 2020 07:38:00 UTC+1, Mohammad wrote: >> >> From: https://en.wikipedia.org/wiki/Method_overriding >> >> Assume you have a tiddler called *Parent* with the below contents >> >> \define a() This is a >> \define b() This is b >> \define main() >> <<a>>. <<b>> >> \end >> >> >> Now in *tiddler01 *do as below >> >> \import [[Parent]] >> <<main>> >> >> >> After saving it will display >> This is a. This is b >> >> >> and in *tiddler02 *do as below >> >> \import [[Parent]] >> \define a() This is NEW a >> <<main>> >> >> >> After saving it will display >> >> This is NEW a. This is b >> >> >> So, you can simply override the method a (in Tiddlywiki macro a). >> >> What do you think? >> >> --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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c3ff8ae8-dcce-4ba8-883b-e4a4f51e9575%40googlegroups.com.
