/jEdit/tags/before_bsh-2-0b4/doc/FAQ/faq-plugins.xml

# · XML · 231 lines · 206 code · 20 blank · 5 comment · 0 complexity · 61d435307caf244b2edb4c1815bac630 MD5 · raw file

  1. <!-- jEdit buffer-local properties: -->
  2. <!-- :indentSize=4:noTabs=false:maxLineLen=72:tabSize=4: -->
  3. <!-- :xml.root=faq.xml: -->
  4. <!-- jEdit FAQ -->
  5. <!-- Copyright (C) 2003 John Gellene, Kris Kopicki -->
  6. <sect1 id="plugins"><title>Plugin Questions</title>
  7. <para>
  8. This section deals with questions concerning the use of jEdit's
  9. plugins. Plugins are applications that share jEdit's memory space
  10. and user interface and provide a wide variety of functions and
  11. services.
  12. </para>
  13. <qandaset defaultlabel="qanda">
  14. <qandadiv id="plugin-general"><title>General plugin questions</title>
  15. <qandaentry>
  16. <question id="plugins-latest-official">
  17. <para>
  18. Where can I get information on the latest available
  19. <quote>official</quote> plugins?
  20. </para>
  21. </question>
  22. <answer>
  23. <para>
  24. To get a listing of the latest plugins available for downloading from
  25. jEdit Plugin Central, use the <guimenuitem>Plugin Manager</guimenuitem>
  26. feature on jEdit's <guimenu>Plugin</guimenu> menu. You can also get more
  27. detailed descriptions of the plugins from the <ulink
  28. url="http://plugins.jedit.org">Plugin Central</ulink> web site.
  29. </para>
  30. </answer>
  31. </qandaentry>
  32. <qandaentry>
  33. <question id="plugins-latest-beta">
  34. <para>
  35. Where can I get information on new plugins under development?
  36. </para>
  37. </question>
  38. <answer>
  39. <para>
  40. Many plugin developers make beta versions of their plugins available for
  41. downloading on the <ulink url="http://community.jedit.org">jEdit
  42. Community</ulink> web site. Check the <quote>Plugin beta
  43. versions</quote> section of the web site's <quote>Downloads</quote>
  44. area.
  45. </para>
  46. </answer>
  47. </qandaentry>
  48. <qandaentry>
  49. <question id="plugin-install-manual">
  50. <para>
  51. How do I install a plugin manually, without using the Plugin Manager?
  52. </para>
  53. </question>
  54. <answer>
  55. <para>
  56. Copy the plugin's jar archive file (or files, if there are more than one)
  57. to the <filename>/jars</filename> subdirectory of either (a) the directory in
  58. which jEdit is installed, or (b) your user settings directory (which you can find
  59. by evaluating the BeanShell expression
  60. <userinput>jEdit.getSettingsDirectory()</userinput>.
  61. </para>
  62. </answer>
  63. </qandaentry>
  64. <qandaentry>
  65. <question id="plugin-loading">
  66. <para>
  67. Why can't plugins be loaded dynamically (i.e. not having to restart)?
  68. </para>
  69. </question>
  70. <answer>
  71. <para>
  72. There are plans to support such a feature in jEdit 4.2, however it will
  73. likely require a different plugin API, so existing plugins will need to
  74. be updated to take advantage of it.
  75. </para>
  76. </answer>
  77. </qandaentry>
  78. <qandaentry>
  79. <question id="plugins-developing">
  80. <para>
  81. How do I write a plugin?
  82. </para>
  83. </question>
  84. <answer>
  85. <para>
  86. Writing a plugin requires a working knowledge of Java and some
  87. familiarity with jEdit's Plugin API. There is a tutorial on
  88. plugin development in the jEdit User's Guide. The source
  89. code distribution for jEdit also includes the source for
  90. an example plugin, <application>Quick Notepad</application>, which
  91. is discussed in the tutorial.
  92. </para>
  93. <para>
  94. To learn more about plugin development, take a look at the source
  95. code for other plugins, particularly those whose features or user
  96. interface you might use as a model. The <ulink
  97. url="mailto:devel@jedit.org">jedit-devel mailing list</ulink> and
  98. the message boards at <ulink url="http://community.jedit.org">jEdit
  99. Community</ulink> are also available for specific questions.
  100. </para>
  101. </answer>
  102. </qandaentry>
  103. <qandaentry>
  104. <question id="plugin-irc">
  105. <para>
  106. Is there an IRC (Internet Relay Chat) plugin for jEdit?
  107. </para>
  108. </question>
  109. <answer>
  110. <para>
  111. Yes. Open the Plugin Manager, then select <guimenuitem>Install
  112. plugins</guimenuitem>. You will find the
  113. IRC plugin which you can select for installation.
  114. </para>
  115. </answer>
  116. </qandaentry>
  117. <qandaentry>
  118. <question id="plugin-console-execute">
  119. <para>
  120. Is it possible to execute your application from within jedit?
  121. </para>
  122. </question>
  123. <answer>
  124. <para>
  125. Yes. You can use the System shell of the Console plugin to run you application.
  126. The only limitation is that the plugin does not provide access to the
  127. application's standard input stream, so you will not be able to provide
  128. command-line input once the application is running. If the application requires
  129. such input, it will hang and you will have to terminate its process. Details are
  130. available in the help documentation for the Console plugin.
  131. </para>
  132. </answer>
  133. </qandaentry>
  134. <qandaentry>
  135. <question id="plugin-cvs">
  136. <para>
  137. Can I work with CVS under jEdit? Is there a plugin for CVS? How can I send a
  138. command from jEdit so as to use CVS from within jEdit?
  139. </para>
  140. </question>
  141. <answer>
  142. <para>
  143. GruntSpud and jEditCvs are two such plugins. Under Windows and the WinCVS
  144. Open Source package, you can specify <userinput>jedit.exe</userinput> as your default
  145. viewer and editor to automate the opening of file.
  146. </para>
  147. </answer>
  148. </qandaentry>
  149. <qandaentry>
  150. <question id="plugin-debugger">
  151. <para>
  152. Is there a debugger plugin?
  153. </para>
  154. </question>
  155. <answer>
  156. <para>
  157. A plugin based on the version 1.4 of the JSwat debugger application is currently
  158. available for download using jEdit's Plugin Manager feature. The Debugger plugin
  159. is also available.
  160. </para>
  161. </answer>
  162. </qandaentry>
  163. <qandaentry>
  164. <question id="plugin-antfarm-cmdlineprop">
  165. <para>
  166. Using AntFarm, how do I pass a command-line property to my build
  167. (for example, <userinput>ant build -Dtarget=test</userinput>)?
  168. </para>
  169. </question>
  170. <answer>
  171. <para>
  172. In general, you would need to run Ant from a command line to pass specific
  173. parameters. The AntFarm plugin currently does allow you specify the target
  174. to be built from its graphical display, so the example given in the question
  175. could be run using the plugin.
  176. </para>
  177. </answer>
  178. </qandaentry>
  179. <qandaentry>
  180. <question id="plugins-xslt">
  181. <para>
  182. Any development on integrating an XSL parser? It would be great to have the
  183. possibility to do XSL + XSLT -> XHTML development in the same environment as
  184. other development.
  185. </para>
  186. </question>
  187. <answer>
  188. <para>
  189. There is currently one plugin available called XSLT. The XSLT plugin provides
  190. features for: transforming XML using XSL transformation stylesheets; evaluating
  191. XPath expressions on XML and displaying results; and indenting XML.
  192. </para>
  193. </answer>
  194. </qandaentry>
  195. <qandaentry>
  196. <question id="plugins-ssh">
  197. <para>
  198. Is there a plugin to enable opening of files across networks using SSH?
  199. </para>
  200. </question>
  201. <answer>
  202. <para>
  203. Yes, the FTP plugin privides this functionality as of version 0.5. You will
  204. need to have Java 1.4 or newer to use it. Prior versions of java can still be
  205. used with the plugin, however you will only be able to use the FTP protocol.
  206. </para>
  207. </answer>
  208. </qandaentry>
  209. </qandadiv>
  210. </qandaset>
  211. </sect1>