Suggestions for future features

[Kathir J]

Having tags for each document (Reference: https://collatenotes.com/)
Built in web clipper (save webpages locally) - (Reference: https://collatenotes.com/)
Import data from Zim Wiki or Text files - (Reference: https://collatenotes.com/)
Google like search like ambar cloud (Reference: https://ambar.cloud/)
Function Keys support to navigate previous/next hit like Folio Views
Number of search results before search performed like table (Reference: http://table.branham.org/#/main)
Support for full text search in huge text nodes - example atleast 10,000 nodes with 100 kb of text each. Most note-taking software couldn't handle such huge content due to missing indexing
Quickest search results via indexing through Apache Lucene like docFetcher (http://www.techrepublic.com/blog/linux-and-open-source/portable-desktop-search-make-the-most-of-docfetcher/)
Please go through the menus of cherry tree software and incorporate which is easly doable.
drag and drop support between nodes

[Stephan Hradek]

Am Mittwoch, 30. August 2017 04:02:40 UTC+2 schrieb Kathir J:

Having tags for each document (Reference: https://collatenotes.com/)

It would be much nicer to give a use case than just posting a link.

What's a "document" for you? A tiddlywiki file? Are you sure you did explore everything in regards to tiddler creation? Did you check whether you can set default tags for every new tiddler?
 

Built in web clipper (save webpages locally) - (Reference: https://collatenotes.com/)

It would be much nicer to give a use case than just posting a link.

What's a "web clipper"? Are you sure, the <<snapshot>> macro isn't sufficient?
 

Import data from Zim Wiki or Text files - (Reference: https://collatenotes.com/)

It would be much nicer to give a use case than just posting a link.
 
Did you check http://tiddlywiki.com/#Importing%20Tiddlers? Why not write a converter tool yourself? IMHO this is nothing useful for the majority.

Google like search like ambar cloud (Reference: https://ambar.cloud/)

It would be much nicer to give a use case than just posting a link.

I do not want to look into this.
 

Function Keys support to navigate previous/next hit like Folio Views

It would be much nicer to give a use case than just posting a link.

 

Number of search results before search performed like table (Reference: http://table.branham.org/#/main)

It would be much nicer to give a use case than just posting a link.
 

Support for full text search in huge text nodes - example atleast 10,000 nodes with 100 kb of text each. Most note-taking software couldn't handle such huge content due to missing indexing

You shouldn't create such hge nodes.
 

Quickest search results via indexing through Apache Lucene like docFetcher (http://www.techrepublic.com/blog/linux-and-open-source/portable-desktop-search-make-the-most-of-docfetcher/)
Please go through the menus of cherry tree software and incorporate which is easly doable.

No. Why?

 

drag and drop support between nodes

Works for me. What's wrong there?
 

[Dragon Cotterill]

Quickest search results via indexing through Apache Lucene like docFetcher (http://www.techrepublic.com/blog/linux-and-open-source/portable-desktop-search-make-the-most-of-docfetcher/)
Please go through the menus of cherry tree software and incorporate which is easly doable.

No. Why?

Well I can certainly give a use case for this option. My Library TW ( http://www.kizar.co.uk/TW/library.html ) has pointers to a few gigs of external documents (.PDFs), and having an external search capability would be a boon here. This is something I have tried looking into, but to try and make it seamless for local and online searching is a huge PITA.

To be fair though, you're trying to mix two distinctly different technologies here, and the moment you try to do that there is a scope for a complete failure. I have made some headroad into this by moving my TW into a Domino database and feeding the results back using the Shared Tiddlers plugin. But this limits the search system to only being available when on-line. Which kind of defeats the purpose when it's supposed to be an "off-grid" library. :p

[Mark S.]

A web clipper is a tool for saving web pages, selected text, or images as tiddlers. It's a key feature of information systems like Evernote and Onenote. Currently you can do this with the tiddlyclip extension and plugin (http://tiddlyclip.tiddlyspot.com/) in firefox. It's unclear if this will work after coming changes in Firefox. It would be hard or impossible to have a built-in capture mechanism in TW because every browser is different, and are likely to require some 3rd party assistance. I've been using unmht to save web pages lately. You can use iframe to display MHT files in ff and then put keywords in your tiddler to help you find it.

What's <<snapshot>> ?

Mark

[@TiddlyTweeter]

TiddlyClip is rather good.

J.

[Stephan Hradek]

Am Mittwoch, 30. August 2017 16:13:11 UTC+2 schrieb Mark S.:

What's <<snapshot>> ?

I'm wondering myself ;) Honestly: Can't remember why I thought it was <<snapshot>>. I once created a "snapshot button" for my menu. It's a tiddler called "Print" looking like this:

<$button message="tm-download-file" param="$:/core/templates/static.template.html" class="btn-big-green">Save snapshot {{$:/core/images/save-button}}</$button>

Clicking it will give you a static HTML of all the currently open tiddlers.

[@TiddlyTweeter]

This thread does bring up idea we could do with a Pinned SUGGESTIONS thread?

@TiddlyTweeter