Hi people, I came to my senses (hopefully) and made httpinst a standard search XML, instead of keeping it in a separate js include file. The benefits are:
- Automatic help system puts up a nice help box on httpinst ? - No customization of search.htm/installer necessary (I changed them both back) - Users can get rid of the functionality by disabling/deleting the XML I really missed the help functionality. Also, considering the recent discussion on 'losing all canned searches' [1], maybe we should put all the required searches in a coresearches directory...? That way, we could guarantee the function of the bar, even if people were to empty the searches directory. That might be worth looking into for the next release cycle, since we'll have to rework the search parsing on startup anyway. Feedback most welcome, Kim [1] http://sourceforge.net/tracker/index.php?func=detail&aid=850134&group_id=420 81&atid=432066 ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ DQSD-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-devel
