Greg, I truely understand what you are asking for and I believe it's achievable in principle.
I have not reached into javascript yet but not sure I need to, but I plan to put the developer hat on soon. I have contributed to others work by asking for minor changes that keep their solutions somewhat interoperable. An outliner based on heirachical tagging is a good example. The items tagged by a given tag can form a stack on drop boards kanban view. My design approach is to build solutions that sit on top of tiddlywiki not in it. This includes queue or list management, tiddler disposition, fields as 1st class citizens and designer views using a variation on an outliner. All of these should be able to live in the same wiki including with my first plugin mymenus (and other plugins) and to do this they should leverage the native way to do things. If we all write solutions on top of the native structure they should interopperate. Another way is to make solutions sit to the side of the native methods not compromising other solutions. I have only started on this journey so it will take time before I can collaborate to set design criteria to ensure such interoperability. Least of all to prove the validity of an approach. This is also a costly (in time) venture, and the results will always be presented on an open source platform with multiple ways to copy and reuse my own and others intelectual output, I am all for this but only recently discovered a possible way to earn a return. That is basicaly being an expert in the tiddlywiki eco system and always contributing to it (user and developer) but being in a position to rapidly develop bespoke or goobal solutions. I will never be in competition with the comunity only with alternative platforms out there. The truth is if we build our own development frameworks, methods, patterns in collaboration with the community we all grow, by sharing, this exists for the core but not so much for end sooutions. Yet if we are expert and tiddlywiki use grows there will always be non experts we can help, and people who want to commission solutions. Further it would be nice if we could crowd source solutions off each other with a return or prize to the solution provider, this would help fund developers translate what they know to what we share. It is easy to see the effort it takes to translate a bespoke solution into an easy to use plugin, even more so if it can opperate in the eco system without compromising interopperability. Just a bit of where my thinkng is at. Background. Sick of being an employee I am striking out on my own, I have very little income and hundreds of possible sucess vectors, I hope tiddlywiki will be one of them. This freedom must come to an end if I can not mak a "right livelihood" from tiddlywiki, my consulting, trouble shooting, cloud solutions, website design, support and hosting. Am I deluded about tiddlywiki, is my belief in it just apparent sucess that makes me feel good? Regards Tony -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/71403dc3-da20-4422-8af3-c5887139aae8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
