View the DQSD CVS repository here:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dqsd/
Update of /cvsroot/dqsd/dqsdweb
In directory usw-pr-cvs1:/tmp/cvs-serv9555
Modified Files:
faq.xml
Log Message:
added all the faqs
Index: faq.xml
===================================================================
RCS file: /cvsroot/dqsd/dqsdweb/faq.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** faq.xml 15 Aug 2002 13:40:50 -0000 1.4
--- faq.xml 15 Aug 2002 16:56:32 -0000 1.5
***************
*** 161,165 ****
--- 161,411 ----
</answer>
</faq>
+ <faq>
+ <question>I've written a search of my own. How do I share it with the
+world?</question>
+ <answer>E-mail it as an attachment to the <link
+href="https://lists.sourceforge.net/lists/listinfo/dqsd-users";>DQSD Users
+Group</link>.</answer>
+ </faq>
+ <faq>
+ <question>Where do I go to download searches?</question>
+ <answer>Searches can be downloaded from Source Forge at <link
+href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dqsd/dqsd/searches/";>http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dqsd/dqsd/searches/</link>.</answer>
+ </faq>
+ </category>
+ <category name="Aliases">
+ <faq>
+ <question>What is an alias?</question>
+ <answer>Aliases are simply other names for existing searches. Aliases are
+ defined in aliases.txt and/or localaliases.txt, but localaliases.txt
+is meant
+ to be the user-defined file, and it won't be overwritten on an
+install.
+ Aliases also provide substitution of '%s' (no quotes) with the actual
+search
+ string. This allows some custom searches to be added very quickly
+ just by adding the URL with '%s' in the query string. Aliases are also
+ referred to as Shortcuts.</answer>
+ </faq>
+ <faq>
+ <question>I cannot undefine some of my aliases. Why?</question>
+ <answer>There is currently no way to undefine an alias in aliases.txt without
+ removing it or commenting it out in aliases.txt (though this will
+surely be
+ fixed in an upcoming release). Be aware that this change will be
+ overwritten by later installations.<html:br/> Please also note that a
+local alias
+ overrides an alias if they have the same name.</answer>
+ </faq>
+ <faq>
+ <question>I want to create an alias to an alias. How should I do
+this?</question>
+ <answer>An alias must be defined before it can be referenced from another
+alias. For
+ example these two lines in the localaliases.txt file will show two
+shortcuts in
+ the helpbox:
+ <html:ul>
+ <html:li>dqsdcvs|http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dqsd/dqsd/
+ </html:li>
+ <html:li>dqsd|dqsdcvs
+ </html:li>
+ </html:ul>
+ <html:p>But these two lines will only show the dqsdcvs one:</html:p>
+ <html:ul>
+ <html:li>dqsd|dqsdcvs
+ </html:li>
+ <html:li>dqsdcvs|http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dqsd/dqsd/
+ </html:li>
+ </html:ul>
+ <html:p>The same two lines, but the second set sets an alias to call another
+alias that
+ hasn't been defined yet.</html:p></answer>
+ </faq>
+ </category>
+ <category name="Preferences">
+ <faq>
+ <question>How do I edit preferences for DQSD?</question>
+ <answer>Configuration settings for DQSD are defined in the preferences.js
+file. User
+ overriding settings are defined in localprefs.js. These files have
+ definitions to control the look and behavior of the toolbar. As new
+features
+ are added which require new configuration settings, new entries will
+appear in
+ the preferences.js included in DQSD releases. The preferences.js file
+ gets overwritten during the upgrade process. For this reason the user
+ should make the desired configuration changes to the localprefs.js
+file.</answer>
+ </faq>
+ <faq>
+ <question>Why are there two preference files (preferences.js and
+localprefs.js)?</question>
+ <answer>Preferences.js is included in the DQSD release bundle, therefore
+changes made
+ to the preferences.js file will be lost when a new DQSD release is
+installed.
+ Preference changes should be made to localprefs.js to be retained from
+release
+ to release.</answer>
+ </faq>
+ <faq>
+ <question>Why doesn't autocomplete work?</question>
+ <answer>Autocomplete requires two configuration settings to be specifically
+set in the
+ preference files. By default DQSD does not enable the autocomplete
+ functionality. 'autocomplete' must be set to 'true" and 'multiline'
+must be set
+ to 'false'.</answer>
+ </faq>
+ </category>
+ <category name="Styles">
+ <faq>
+ <question>How do I edit fonts, colors, etc. for DQSD?</question>
+ <answer>Style settings for DQSD are defined in the search.css file. User
+overriding
+ settings are defined in localsearch.css. These files have definitions
+to
+ control the look and styles of the toolbar. As new features are added
+which
+ require new style settings, new entries will appear in the search.css
+included
+ in DQSD releases. The search.css file gets overwritten during the
+upgrade
+ process. For this reason the user should make the desired configuration
+ changes to the localsearch.css file.</answer>
+ </faq>
+ <faq>
+ <question>Why are there two .css files (search.css and
+localsearch.css)?</question>
+ <answer>Search.css is included in the DQSD release bundle, therefore changes
+made to
+ the search.css file will be lost when a new DQSD release is installed.
+Style
+ changes should be made to localsearch.css to be retained from release
+to
+ release.</answer>
+ </faq>
+ </category>
+ <category name="Coding">
+ <faq>
+ <question>Are there any guidelines I should be aware of when making
+modifications for DQSD?</question>
+ <answer>Ground rules for checkins into CVS:
+ <html:ul>
+ <html:li>If you want to merge in some changes, just let Dave know which
+SourceForge
+ account needs CVS write access. Access is no problem if you're
+going to
+ contribute; just don't abuse it.
+ </html:li>
+ <html:li>When you do commit a change, please let Dave and the
+ <link
+href="https://lists.sourceforge.net/lists/listinfo/dqsd-users";> DQSD Users
+Group</link> know.
+ </html:li>
+ <html:li>If you're going to do major rearrangement, broadcast your intent
+to the
+ <link
+href="https://lists.sourceforge.net/lists/listinfo/dqsd-devel";> DQSD Developers
+Group</link>
+ ahead of time.
+ </html:li>
+ <html:li>If you're adding novel functionality, please consider including
+an option for
+ preferences.js to turn it off. Also please consider making the
+default "off"
+ until it's completely tested and polished.
+ </html:li>
+ <html:li>Small changes should have small diffs. Please do not use a
+wysiwyg HTML editor
+ that will introduce diffs on every line, or your checkin will be
+backed out.
+ </html:li>
+ <html:li>In the code, please mimic the prevailing convention for tabbing
+and spacing:
+ </html:li>
+ <html:ol>
+ <html:li>No tab characters in code please. Use spaces instead. (The
+exception is where
+ tabs have semantics of course). Code should be indented two
+spaces per level.
+ </html:li>
+ <html:li>Please, no space characters after a ( or before a ).
+ </html:li>
+ <html:li>Curlies for a {multiline block} should be on their own line
+and unindented
+ (just their contents are indented).
+ </html:li>
+ </html:ol>
+ <html:li>Also please mimic the prevailing convention for packaging:
+ </html:li>
+ <html:ol>
+ <html:li>Sources should be included in the distribution itself since
+this is the easiest
+ way to conform to the GPL. So all source files should be
+listed in
+ "search.nsi"; i.e., you shouldn't need CVS to get a working
+build.
+ </html:li>
+ <html:li>Please keep "build.cmd" working. In particular this means
+that DQSDTools.mak
+ needs to be kept up to date. Also, any files that are
+automatically generated
+ by the build should be deleted by "clean.cmd".
+ </html:li>
+ <html:li>Keep new sources, except for those that are being used at
+runtime, underneath src/.
+ </html:li>
+ </html:ol>
+ <html:li>Keep in mind that you are editing other people's code and that
+other people
+ will edit your stuff. Please don't be offended if your code is
+changed or even
+ disabled. Be nice!
+ </html:li>
+ <html:li>Dave may decide to turn your access off if things become
+unmanageable, or if
+ you don't make checkins for a while.
+ </html:li>
+ </html:ul></answer>
+ </faq>
+ <faq>
+ <question>How do I get started with basic Source Forge access?</question>
+ <answer>Steps to a working build of DQSD from SourceForge:
+ <html:ol>
+ <html:li>Make sure you're using Windows 2000 or better.
+ </html:li>
+ <html:li>Install cygwin from <link
+href="http://cygwin.com/setup.exe";>http://cygwin.com/setup.exe</link>.
+ </html:li>
+ <html:li>Install Microsoft Visual C++ 6.0.
+ </html:li>
+ <html:li>Install the <link
+href="http://www.microsoft.com/msdownload/platformsdk/sdkupdate/";>Microsoft
+ Internet Development SDK</link>. Move the SDK path for include
+files and libraries before the
+ standard Visual C++ header files.
+ </html:li>
+ <html:li>Install NSIS - <link
+href="http://www.nullsoft.com/free/nsis/";>http://www.nullsoft.com/free/nsis/</link>.
+ </html:li>
+ <html:li>Make sure that MSVC and NSIS are on your path
+ (you can try using Control Panel/System Properties/Environment
+Variables).
+ </html:li>
+ <html:li>From your cygwin prompt, type the following to checkout:
+ </html:li>
+ <html:ul>
+ <html:li>cd ~
+ </html:li>
+ <html:li>cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dqsd login
+ </html:li>
+ <html:li>cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dqsd co dqsd
+ </html:li>
+ </html:ul>
+ <html:li>And whenever you want to get the latest:
+ </html:li>
+ <html:ul>
+ <html:li>cd ~/dqsd
+ </html:li>
+ <html:li>cvs update -dP
+ </html:li>
+ </html:ul>
+ <html:li>Type the following to build:
+ </html:li>
+ <html:ul>
+ <html:li>cd ~/dqsd
+ </html:li>
+ <html:li>src/build.cmd
+ </html:li>
+ </html:ul>
+ <html:li>In the end, you should get a dqsd/dqsd.exe.
+ </html:li>
+ <html:li>To go back to pristine sources, run src/clean.cmd
+ </html:li>
+ </html:ol>
+ The above is for read-only access to the sources. For writable access, you'll
+ need a Source Forge account, and Dave or Glenn will have to grant proper
+ permissions to your account.<html:br/> <html:br/>
+ Alternate CVS Utilities:
+ <html:ul>
+ <html:li>WinCVS is a GUI front-end to CVS that you can use. You can pull
+the latest
+ version here: <link
+href="http://sourceforge.net/projects/cvsgui";>http://sourceforge.net/projects/cvsgui</link>.
+ </html:li>
+ <html:li>Check out Tortoise CVS. It adds the most basic/common CVS command
+functionality
+ to Explorer, so you can update, commit, add, diff, etc.. with a
+right click
+ from an Explorer window. Get it here: <link
+href="http://www.tortoisecvs.org/";>http://www.tortoisecvs.org/</link>.
+ </html:li>
+ </html:ul></answer>
+ </faq>
+ </category>
+ <category name="Add-ons">
+ <faq>
+ <question>What is an add-on?</question>
+ <answer>At times users may want to add more functionality than is possible or
+makes sense with a
+ single .XML search file. Also, it may not make sense to have this new
+feature be installed
+ for all users. If so, the ability to add add-ons allows for multiple
+files to be packaged
+ together in an optional installation package. Add-ons are installed in
+the 'addon'
+ subdirectory.</answer>
+ </faq>
+ <faq>
+ <question>When should I create an add-on rather than a search?</question>
+ <answer>When a new feature is not really a search, and/or it requires more
+than just a single XML
+ file, and/or it doesn't have general appeal (i.e., not many will use
+it) it should be an
+ optional add-on.</answer>
+ </faq>
+ <faq>
+ <question>How do I create an add-on?</question>
+ <answer>The best place to learn about creating add-ons is to look at the
+current addon
+ examples (googlespell, etc), and use them as a template for your
+own.</answer>
+ </faq>
+
</category>
+
+ <html:br/>
+ <html:center> [ <link href="doc.htm">DQSD home page</link> ]
+
+ </html:center>
+
</faqs>
+
-------------------------------------------------------
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-CVS mailing list
https://lists.sourceforge.net/lists/listinfo/dqsd-cvs
DQSD CVS repository:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dqsd/
