Mark, Thanks for the reply, I appreciate the involvement and enthusiasm you guys show for TW.
The code you provided is a great hint, and fewer resources is always a good thing. The resource usage issue is good to know, as the point of a tool like this is agile information transfer. One of the things I liked about the TWRocketDock implementation was its ability to create new tiddlers on the fly, and edit as you go. Combining this capacity with the TWO outlining capability in a separate window would be a killer research/note taking tool. The main features in Dynalist are free, including list/outline functionality we're considering here. I totally agree with you about the price of the paid product, and I won't be subscribing any time soon. That said, even some of the paid features can be accomplished in TW right now - if one has the technical aptitude. Dynalist is exactly the kind of a refined product I'm talking about being implemented in TW that would easily draw new people. I completely agree with you about a tree or outline structure being important to an app like TW (or Evernote, or ...). I think that combining TWO with capabilities like those demonstrated in the Rearranger, SlidesnStories, and SidebarExporter plugins I mentioned makes TW an Evernote and Dynalist killer (for me, at least), especially as you mentioned, when combined with TiddlyWiki in the Sky capabilities or similar access methods. I think you're absolutely right - starting with a particular end product in mind is vital for the kind of functionality I'm talking about. In fact, I'd go farther and say that a suite of "products", meaning two or three types of TiddlyWikis, each able to interact on and reference the data from the other's tiddlers would be possible, if the project were properly coordinated. This is exactly the kind of project I was alluding to. The problem with my little fantasy is that (from the perspective of a non-coder on the outside looking in), a project like TiddlyWiki, and it's resulting thousand other little plugins, is a bit like herding cats. You're right, many of these things are based on 3rd party JS libraries that are incompatible, but I'm not convinced that's the largest hurdle. Each TiddlyWiki "app" in my fantasy project could integrate the libraries necessary for that app, but the common thread between every TiddlyWiki implementation is *the tiddler*. The much more serious problem from my perspective is a lack of commonality in data structures within the tiddlers - unique field names, tag names, and schemes for handling this data in each individual plugin. I'd suggest that this is the larger hurdle in crafting a more unified "app" based on TiddlyWiki. At least that's been the primary hurdle for me while trying to incorporate pieces from various developers code. That said, I do think that getting the various developers to work together on common standards for a given "application" would largely solve the integration problems I have. I can't see any reason the data structure used in Dropboard and TiddlyMap couldn't be integrated in a common way, for example. While one may have extended sets of fields or tags that the other doesn't utilize (and vice versa), if they each began with a common set, there's great potential for interaction and interoperability on the same data set (tiddlers). That would also lead to the potential for the "application suite" of compatible TiddlyWikis customized to specific purposes as I described in my last post. In any case, thank you for that useful snippet of code and the discussion. I really do appreciate your work, and that of the other devs working in their own areas of interest. I look forward to seeing any further development of the TWO idea, as I think it is an indispensable capability for apps like TiddlyWiki. thanks again Greg On Friday, May 4, 2018 at 2:59:12 PM UTC-7, Mark S. wrote: > > Hi Greg, Tony, > > On Friday, May 4, 2018 at 9:18:58 AM UTC-7, Greg Molyneux wrote: >> >> Tony, >> >> Related to the feature set you're discussing, you might find it useful to >> look at this bit of code: >> >> https://groups.google.com/forum/#!topic/tiddlywiki/Qw5sjePXfr0 >> >> > It looks nice but it's doing something behind the scenes unnecessarily > resource intensive. Various actions work at a crawl unless you also have > the main tab on top -- in which case what is the point? > > I made a much simpler, (and uglier, admittedly) separate-window tool that > can be used for notes (but not that fancy drag/drop stuff) Just put this in > a tiddler: > > <$select tiddler="$:/state/side-edit-tiddler" tag="input"> > <$list filter="[!is[system]sort[title]]"> > <option value=<<currentTiddler>>><$text text=<<currentTiddler>>/></option> > </$list> > </$select> > > Then open the tiddler in it's own window. From the drop-down list pick the > tiddler you want to work in. Now you can take notes in a floating notepad. > > there's a reason David is using Dynalist to compile all these bits of >> shiny things for TW - it just works, and it's easy. >> > > Yeah, but for $96-$120 bucks a year it should do more than "just work" ! > It should also make coffee and give back rubs. > > The TWO mini-app is pretty easy, IMHO. Used with TiddlyWiki In the Sky it > becomes a viable substitute for SimpleNote, but providing notebook-like > structure. > > Using TWO you can set up "Notebooks" in order to categorize the > information you wish to capture. > > One of the things that bothers me about TiddlyWiki, Evernote, and > Simplenotes is that creating notes and tagging isn't really enough. There's > a lingering worry that you're going to forget that you saved stuff in the > first place. Being able to create a tree or outline structure is kind of a > way to help your mental "wiki" remember what all you've put in your actual > Wiki. But that may be just me. The "NoteStorm" app was my default TW back > with in the days of TWC. It provided some structure that helped keep your > thinking primed. > > I'd love to have a >> capable open outliner, with which I could view/relate/modify/reorganize >> data in a capable mind mapping/diagramming tool. Then take that data and >> organize tasks and projects on a kanban type board. Then take items from >> that board and reference them in my GTD TW implementaion with dates, >> resource lists, contacts, etc. All of these components exist now, but >> getting them to work well *together* is in many ways beyond my limited >> ability, and that of most non-technical users. >> > > I think you'd have to start with a specific end-product in mind, and then > get various people to agree to work on it together. But I don't know what > central target product would be compelling enough for everyone to aim for. > In addition, many of the amazing things you see don't work together because > they're based on 3rd party JS libraries, where the differences might be > nearly impossible to work out. > > -- Mark > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. 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/3b9502e8-3efc-483a-be69-f6daeb821517%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
