From: <ko...@us...> - 2010-09-30 20:00:44
|
Revision: 18683 http://jedit.svn.sourceforge.net/jedit/?rev=18683&view=rev Author: kog13 Date: 2010-09-30 20:00:38 +0000 (Thu, 30 Sep 2010) Log Message: ----------- Added documentation Modified Paths: -------------- plugins/ClojureShell/tags/1.0/ClojureShell.props plugins/ClojureShell/tags/1.0/build.xml plugins/ClojureShell/tags/1.0/docs/users-guide.xml plugins/ClojureShell/trunk/ClojureShell.props plugins/ClojureShell/trunk/build.xml Added Paths: ----------- plugins/ClojureShell/tags/1.0/docs/ Modified: plugins/ClojureShell/tags/1.0/ClojureShell.props =================================================================== --- plugins/ClojureShell/tags/1.0/ClojureShell.props 2010-09-30 19:46:50 UTC (rev 18682) +++ plugins/ClojureShell/tags/1.0/ClojureShell.props 2010-09-30 20:00:38 UTC (rev 18683) @@ -4,7 +4,7 @@ plugin.clojure.shell.ClojureShellPlugin.author=Damien Radtke plugin.clojure.shell.ClojureShellPlugin.description=Provides a Console shell \ that maintains a Clojure Read-Eval-Print-Loop. -#plugin.clojure.shell.ClojureShellPlugin.docs=index.html +plugin.clojure.shell.ClojureShellPlugin.docs=index.html plugin.clojure.shell.ClojureShellPlugin.longdescription=description.html plugin.clojure.shell.ClojureShellPlugin.name=Clojure Shell plugin.clojure.shell.ClojureShellPlugin.usePluginHome=false Modified: plugins/ClojureShell/tags/1.0/build.xml =================================================================== --- plugins/ClojureShell/tags/1.0/build.xml 2010-09-30 19:46:50 UTC (rev 18682) +++ plugins/ClojureShell/tags/1.0/build.xml 2010-09-30 20:00:38 UTC (rev 18683) @@ -13,7 +13,7 @@ none: if you supply your own html file as this template does. xsltproc: if you plan on using docbook --> - <property name="docs-proc.target" value="none" /> + <property name="docs-proc.target" value="xsltproc" /> <!-- jEdit installation properties. --> <!-- mark:properties --> @@ -23,11 +23,6 @@ <!-- If you want any extra files to be included with your plugin's jar, such as custom images, you need to specify them here. --> <selector id="packageFiles"> - <and> - <or> - <filename name="**/GroovyRepl.html" /> - </or> - </and> </selector> <!-- Add your plugin's specific dependencies here --> Modified: plugins/ClojureShell/tags/1.0/docs/users-guide.xml =================================================================== --- plugins/PythonShell/trunk/docs/users-guide.xml 2010-09-30 19:46:50 UTC (rev 18682) +++ plugins/ClojureShell/tags/1.0/docs/users-guide.xml 2010-09-30 20:00:38 UTC (rev 18683) @@ -1,7 +1,7 @@ <?xml version="1.0"?> <book> <bookinfo> - <title>Python Shell</title> + <title>Clojure Shell</title> <author> <firstname>Damien</firstname> <surname>Radtke</surname> @@ -9,17 +9,16 @@ </bookinfo> <chapter id="overview"><title>Overview</title> <para> - The Python Shell plugin maintains an interactive Python environment within jEdit. + The Clojure Shell plugin maintains an interactive Clojure environment within jEdit. This can be useful for running quick tests, or simply to play around with the language to get a better feel for its syntax. </para> <para> - To use the plugin, open up the Console dockable and select the Python shell. + To use the plugin, open up the Console dockable and select the Clojure shell. Once selected, it will attempt to start up the Read-Eval-Print-Loop, and if successful, - the Python information message and prompt will be displayed. If not successful, - you will need to tell the plugin where to find Python; this can be done by going to - Plugins -> Plugin Options -> Python Shell. This should only be necessary if the Python - executable can not be found on your system path. + the Clojure prompt will be displayed. If not successful, the Clojure provider plugin + may need to be configured. Refer to that plugin's documentation for information + on how to configure it. </para> </chapter> <chapter id="actions"><title>Evaluating Code</title> @@ -29,9 +28,9 @@ code without having to manually copy and paste it. </para> <para> - These actions can be found in Plugins -> Python Shell. Using these actions, you can + These actions can be found in Plugins -> Clojure Shell. Using these actions, you can use the shell to evaluate the active buffer, any selected text within that buffer, - or an external Python script. + or an external Clojure script. </para> <para> Any variables or functions defined in the shell will persist until the loop is Modified: plugins/ClojureShell/trunk/ClojureShell.props =================================================================== --- plugins/ClojureShell/trunk/ClojureShell.props 2010-09-30 19:46:50 UTC (rev 18682) +++ plugins/ClojureShell/trunk/ClojureShell.props 2010-09-30 20:00:38 UTC (rev 18683) @@ -4,7 +4,7 @@ plugin.clojure.shell.ClojureShellPlugin.author=Damien Radtke plugin.clojure.shell.ClojureShellPlugin.description=Provides a Console shell \ that maintains a Clojure Read-Eval-Print-Loop. -#plugin.clojure.shell.ClojureShellPlugin.docs=index.html +plugin.clojure.shell.ClojureShellPlugin.docs=index.html plugin.clojure.shell.ClojureShellPlugin.longdescription=description.html plugin.clojure.shell.ClojureShellPlugin.name=Clojure Shell plugin.clojure.shell.ClojureShellPlugin.usePluginHome=false Modified: plugins/ClojureShell/trunk/build.xml =================================================================== --- plugins/ClojureShell/trunk/build.xml 2010-09-30 19:46:50 UTC (rev 18682) +++ plugins/ClojureShell/trunk/build.xml 2010-09-30 20:00:38 UTC (rev 18683) @@ -13,7 +13,7 @@ none: if you supply your own html file as this template does. xsltproc: if you plan on using docbook --> - <property name="docs-proc.target" value="none" /> + <property name="docs-proc.target" value="xsltproc" /> <!-- jEdit installation properties. --> <!-- mark:properties --> @@ -23,11 +23,6 @@ <!-- If you want any extra files to be included with your plugin's jar, such as custom images, you need to specify them here. --> <selector id="packageFiles"> - <and> - <or> - <filename name="**/GroovyRepl.html" /> - </or> - </and> </selector> <!-- Add your plugin's specific dependencies here --> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |