> Why don't you package the Snippets add-on (similar to the googlespell example) > so that it can be independently packaged, downloaded, and installed from SF? If it were a separate set of XML files, this would work fine. Unfortunately it alters search.htm and helpmenu.js. Given that, if it's not part of the base code, it has to be updated with every release. To dqsd's credit, that is far too frequent to make it practical. The RSS news feed stuff might be possible as an add-on. I honestly haven't had a chance to try it.
Does JS support overloaded functions? It's perhaps the only way I can think of effectively doing things like this. > Go for it. Forking is...never the best solution, IMHO. This is why I've kept my current fork pretty much to myself. -Dan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Glenn Carr Sent: Monday, August 19, 2002 3:35 PM To: [EMAIL PROTECTED] Subject: Re: [DQSD-Users] dsdq and knowledge management ? > As it relates to DQSD, I've found the DQSD direction to > be focused on pure searching. I maintain a separate "build" > of DQSD with an add-on I wrote that I call Snippets. > Snippets allow you to save chunks of web pages (without > knowing HTML). When I introduced it originally, some felt > it was outside the scope of DQSD. Dan, Why don't you package the Snippets add-on (similar to the googlespell example) so that it can be independently packaged, downloaded, and installed from SF? Your example was one reason I went through the pain of experimenting with the GoogleSpell add-on. If there's missing functionality that needs to be added to DQSD which is generic enough for all searches/add-ons to take advantage of, then it makes sense to add the functionality. _But_, if core functionality is modified to support a single add-on or search, then we're setting a bad precendent. One that will result in DQSD having various chunks of code in the core source which are only used by a single add-on/search. IMO, some of the core code already matches that description (calendar) and should be moved to an add-on. > I've since though of integrating various features into DQSD. > I've done a lot of (unrelated) work with RSS new feeds, and I > have considered adding the feature to DQSD to show a news > ticker during idle time. RSS is really the first fruit of a > semantic web coming to harvest. However, the DQSD direction > of sticking to the bread and butter searching leaves me a > little uninterested in working on such things. Again, I'd recommend trying to add it as an add-on. > If there were enough interest I'd love to fork DQSD into > something less constrictive. At the same time, I'd hate to > do it too. Go for it. Glenn ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Dqsd-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-users http://sourceforge.net/mailarchive/forum.php?forum_id=8601 ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Dqsd-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-users http://sourceforge.net/mailarchive/forum.php?forum_id=8601
