Hi, I don’t know if this is the proper place to post “feature requests” using API or for Tabbles itself
About API, great work, I have some ideas as “feature requests“:
– autoTagging based on rules and patterns (filename, path, tabbles.containers)
I am interested in some auto.tagging based on “path” or “filename” patterns for example.
video.extensions => trigger (#video.tag) extensions (avi,flv,mp4,webm… etc)
analog for “file.entities” like “images” “documents”
There are databases on internet to mapping “MIME” types to “class.groups” so it is easy to implement
– Relational “Tabbles” => tabbles = tags so
We could define tag.uris => video/mp4 (easily) => #video + #mp4
another example => sports/football => #sports + #football
uris could allow “nested Tabbles” with logic
*I don’t have (yet) “deep knowledge” about Tabbles implementation of tags yet, but graph databases are great and are ready “functional programming” friendly to support more relations and ontologies of “words” and “concepts”
For example, a last example of all this:
– Tabbles path.uris to tags (path are URIs)
Imagine you have a folder with personal photos from n sources in a folder-tree based
folder, will be very useful (convert folder to tags) and
process fileNames to “search” nGrams => keywords, words
*This would be to start using “ontologies” “semantics” and controlled vocabularies
*SemanticWeb and SemanticDesktop finally “one” to the masses (visionary desire xD)
– Hashing integration batch (unique IDs for files) (hash.generator at least MD5 or MD6 and SHA-1 based algorythms (to generate unique IDs and mapping across tagging beyond even relative.paths or Tabbles listener (I see Tabbles listen for moved files even using Windows default file manager, and cleverly manages offline disk volumes via UUID) but hashing create a more flexible way of collaboration and merge databases better with “strong.Linked” relations.
Hashing will impact on database size or performance, you wonder?
(i do some research)
one of StackOverflow guys
url: blog.codinghorror DOT com/primary-keys-ids-versus-guids/
Hashing can be accomplished “manually” via commandline commands and importing “manually” to SQL database, but is not “UX friendly” and not “every user has that knowledge”
– RAMdisk and Tabbles (database, caching)
Using ramDisk is very useful to load Tabbles cache and database ( “IOPS power” ) (but “ramDisk” are “that great great unknown” for many users), to some integration “to customize easily” “Tabbles to ramdisk” will be useful
As a tip, for any users with 16GB of RAM DDR3|DDR4 or above (very common this days), I think this will be every useful “to desktop users”.
Some users could be “server admins” or “master backend superusers” but the most common maybe is “desktop or laptop workstation PC users“.
PD: I help because im a fan, yeah, but another reason is more pragmatical and practical, I could start a “file management” project by myself (ego thing, not useful), or help to improve brilliant work that exists now, and Tabbles is a software “state of art” to me, revolutionary (even too advanced to contemporary age hahaha), the thing is, here you will have a loyal entuthiast programmer and researcher with great ideas to help, and when I “get with .NET framework” even a contributor 😉
And sorry if the text is too large or cryptic (the intention is being functional programming ready :D)