Yeah... there's no search/alias matching those strings, so it doesn't add them to the menu.
 
Hmm...  I'm in favor of keeping it as an optional add-on, if it can be completely self-contained in an XML file.
 
 
Dan,
 
Instead of adding snippets to the menu, how about creating a popup window (similar to qsfind) with the list of current snippets?  I can see a window popping up with both the list of current snips and options to create/edit snippets.
 
BTW, I'd also _really_ like to see the calendar be completely self-contained in its own XML file.
 
Maybe we should create another subdirectory for user add-ons/plug-ins that we could put items like this, the calendar, etc. in.
 
Thoughts?
 
Glenn
----- Original Message -----
Sent: Tuesday, May 07, 2002 10:24 AM
Subject: [DQSD-Users] here's one...

my MRUmenu.txt looks like this...
 
tam
sfdqs
editsnippet('test2.html')
openSearchWindow('snippets')
snippet
 
well my menu has:
5 tam
4 sfqds
1 new snippet
 
 
perhaps the mrumenu code needs to ignore snippet stuff.  especially if snippets become standard.
 
since DQSD is primarily (not only) a search utility, and snippets help compile a set of search results in one window i have hanged my tune and vote to keep it.
 
just my 2 cents... now i'm broke ;)
 
JB
 

Reply via email to