Chris,

I can only echo Saq's comments. One of tiddlywiki's key strengths is its 
diversity. When it comes to productivity using tiddlywiki people often have 
different preferences and approaches and looking at your solution it 
definitely has some great approaches.

My initial review is it looks great, and has nice functionality.

I am happy to review and comment further if requested. 

My first comments are at a very high level.

   - Try and allow you solution to be installed in such a way it is 
   somewhat independent, so people can combine your solution with others.
      - This means it can be used more often, as well as people discovering 
      novel ways to make use of it.
      - If you can "expose" macro's and methods to increase utility and 
   hackability it is always helpful.
   - I would avoid asking that any macro be placed in the tiddler 
   like <<everything>>, as this forces the use of the text field when its 
   unnecessary. 
      - Ideally I would suggest having a field such as object-type with a 
      value of omnibus
      - Then a conditional viewTemplate that shows <<everything>> if 
      object-type[omnibus]
      - If you do not want to force a tiddler to be only an omnibus you 
      could look at a simple omnibus= hide/show field
   
In a tiddler tagged $:/tags/ViewTemplate
<$list filter="[all[current]object-type[omnibus]]" variable=nul>
   <<everything>>
</$list>

Then one could have a button in the ViewToolbar to make a tiddler an omnibus

   - Set object-type field to omnibus

This would allow the text to have additional content, that displays above 
the omnibus and the tiddler to serve other functions.

Thanks for your contribution

Regards
TW Tones

On Tuesday, August 4, 2020 at 6:21:39 AM UTC+10, clutterstack wrote:
>
> Hello all,
>
> Following on from my quick adder plugin, I've built a demo of the reason I 
> wanted the quick-adding capability. 
>
> I was pretty excited about this, and I guess I still am, although it 
> converges quite a lot toward Streams and NotoWritey. It's called Omni, 
> short for Omnibus, because each one collects tiddler "passengers". Here's 
> what I said in the demo are its basic capabilities: 
>
> * Quickly add tiddlers, without needing to think of a title right away (or 
> ever)
> * Rearrange tiddlers within and between omnibuses by drag and drop
> * Drag and drop to add tiddlers to the omnibus
> * Add (existing) tags to tiddlers by drag and drop
> * Set indentation levels or styles for tiddlers within the omnibus
> * "Fold" and "unfold" tiddler transclusions 
>
> I see I Ieft out "edit tiddler text". You can see there's some overlap, 
> although there are some slightly different decisions among Streams, 
> NotoWritey, and Omni.
>
> Demo and some notes are available at
> https://clutterstack.github.io/TW5-omni/
>
> Having used this for a bit, I have come to the conclusion it needs a major 
> reworking under the hood, but there's a lot I will keep. Certainly, the 
> fact that I know Streams is much better-written is due to my having climbed 
> a learning curve writing this -- I can now read and understand Saq's code.
>
> Anyway, although this is not a production-ready plugin, maybe someone will 
> get an idea or snippet from this. The plugin repo is 
> https://github.com/clutterstack/TW5-omni.
>
> I plan to incorporate more ways to manipulate and assemble "omnibuses" 
> into my wiki. My historical problem has been that I can collect a lot into 
> a wiki but it's a bit of a black hole after that.
>
> Cheers, Chris
>

-- 
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/70c5f423-c514-43db-8a4d-54304ac21f07o%40googlegroups.com.

Reply via email to