I keep waiting for someone else to write this plugin idea which will basically let you search a specially formatted text file for notes and data by keyword or tag.-mouser (May 31, 2008, 01:32 AM)
my suggestion:
wait for the Information Reference plugin, and don't waste your time setting these aliases up manually.
I keep waiting for someone else to write this plugin idea which will basically let you search a specially formatted text file for notes and data by keyword or tag.-mouser (May 31, 2008, 01:32 AM)
the biggest problem with this plugin idea is that it threatens to be so complicated that it never gets coded, so we need to figure out a nice reasonable set of ideas.i agree
I think the only reason to support some note taking is because it would be easy and would be well suited for people who do NOT already use a proper notetaking application.
(ps. for those who use a notetaking application -- what would be nicer is a plugin for FARR that interfaces to their existing note taking application!)-mouser (June 01, 2008, 04:02 PM)
I think it makes sense to start with a very basic textfile search capability first and then expand it if and when demand occurs.i agree
When the user inputs "info tag1" FARR would output "data1 data2 data3" (or "data1 \n data2 \n data3")i think it would be better to have the whole line i.e. : tag1 data1 data2 data3 (or "tag1\n data1 \n data2 \n data3")
I think it makes sense to start with a very basic textfile search capability first and then expand it if and when demand occurs.
Two rather non-complex systems could be:
1. comma separated data. Example:
tag1 data1 data2 data3
tag2 data4 data5 data6
When the user inputs "info tag1" FARR would output "data1 data2 data3" (or "data1 \n data2 \n data3")
Mousers example ("info phone hospital") in comparison adds one level of complexity. But how often is that needed? I suspect that it for much lookup usage is enough to output all the info related to a "first level tag" i.e. "info hospital" would display adress, phone number, email etc in FARR. Two drawbacks with the more complex example is that the user must memorize all the second level categorizes and must create all his/her new data in a very well formed and consistent way. I definitely prefer something less complex and less (human) memory hungry.-Nod5 (June 02, 2008, 07:36 AM)