Souk21
> @TW Tones The goal is indeed to make it the more hackable/customizable I > can. > Thank you for the tip, I didn't know about this drag n' drop feature :) > > Done the right way the community can build a library of "commands" that >> are practical for any user, and or designer and we can share them saving >> development time. Can we make it respond to existing methods? >> > > Yes! It's exactly what I had in mind. > What do you think could be a good way to allow this ? > Once I understand how to make my own and "package" a command using your tool, I will have a better idea, I am glad you support this approach. > Should we centralize all the commands in a repo ? > That would be the ideal, but still not essential. Not every one (like me) are so used to submitting items to a repo, or using GitHub. > What do you mean by 'respond to existing methods' ? > There are a range of methods to achieve things in tiddlywiki, I am talking about gradually supporting them using your tool. An example may be someone wanting add a new custom field to tiddlers with a given tag etc.. > It would be nice to find alternatives for most node js tiddlywiki commands >> (where relevant) >> > > I'm not too familiar with node.js commands yet (I've only used --listen so > far), could you point me towards the relevant ones? > > I do not use node from the command line myself, however there are opportunities to use "node" commands to achieve various results, my though is can we provide those same similar operations in tiddly-wiki such as exporting static html files and more via "Command Palette". > Being able to write commands that interact with the server such as bob >> would be nice. Using a server message. >> > > That is definitely in my todo list. The problem is I'm really new to > server things. > Making my firefox extension talk with tiddlywiki's node server was a big > accomplishment for me haha > My idea for the palette messaging the server was to be able to send a > message to the server so it commits my notes repo and pushes it. > I think for that kind of basic usage I could work it out. > Is there any more 'advanced' usages that you can think of? > And yes, the big questions are how should we deal with passing arguments > to the server, and how should we deal with responses from the server. > Great to know you already have some ideas here. This can be developed in time. > > > Could we get this to past the resulting "command" into edited text fields >> for quick coding from stored patterns. Perhaps even a separate but similar >> tool >> > > I'm not sure I understand. Are you talking about 'saving' a search/filter > operation as a command easily? > Sorry, what I mean is ctrl-p operates at the whole of wiki level. eg ctrl-P "wel" opens the welcome tiddler. I am wondering if we could do the same when in a text field editing content so ctrl-p in a text field would insert [[Welcome]] into the tiddler, not unlike the current editor toolbar button (link Icon) to insert a wikitext link but making use of Command Palette features. > > > On TiddlyDesktop the actions and links can actually open file explorers, >> apps and run batches, interacting with the local OS, so there is great >> potential for desktop management tools or text based search and execute. >> Work flow tools that help actually do the work. >> > > Interesting! I didn't try TiddlyDesktop yet, but that's good to keep in > mind > > > Perhaps it is already possible but I would love to be able to type say >> showcode and clicking the result would set a tag, field or config tiddler >> to yes for a given tiddler (currentTiddler) we have methods to identify the >> current tiddler navigated from. >> > > I'm sorry I'm not sure I got this one. > Basically adding a way to add tags to the current tiddler by typing into command pallet. Thanks again, Like all good innovations in tiddlywiki, they open numerous new possibilities as does your solution. 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b3609027-2bdc-470a-a894-e989a274864co%40googlegroups.com.
