PageRenderTime 74ms CodeModel.GetById 10ms RepoModel.GetById 1ms app.codeStats 0ms

/jEdit/tags/jedit-4-5-pre1/doc/FAQ/faq-plugins.xml

#
XML | 172 lines | 167 code | 0 blank | 5 comment | 0 complexity | 7d3c31913a92a10aba3f03f153ff82d1 MD5 | raw file
Possible License(s): BSD-3-Clause, AGPL-1.0, Apache-2.0, LGPL-2.0, LGPL-3.0, GPL-2.0, CC-BY-SA-3.0, LGPL-2.1, GPL-3.0, MPL-2.0-no-copyleft-exception, IPL-1.0
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <section id="plugins">
  3. <title>Plugin Questions</title>
  4. <!-- jEdit buffer-local properties: -->
  5. <!-- :indentSize=4:noTabs=false:maxLineLen=80:tabSize=4: -->
  6. <!-- :xml.root=faq.xml: -->
  7. <!-- jEdit FAQ -->
  8. <!-- Copyright (C) 2003 John Gellene, Kris Kopicki -->
  9. <para>This section deals with questions concerning the use of jEdit's
  10. plugins. Plugins are applications that share jEdit's memory space and user
  11. interface and provide a wide variety of functions and services.</para>
  12. <qandaset defaultlabel="qanda">
  13. <qandadiv id="plugin-general">
  14. <title>General plugin questions</title>
  15. <qandaentry>
  16. <question id="plugins-latest-official">
  17. <para>Where can I get information on the latest available
  18. <quote>official</quote> plugins?</para>
  19. </question>
  20. <answer>
  21. <para>To get a listing of the latest plugins available for
  22. downloading from jEdit Plugin Central, use the
  23. <guimenuitem>Plugin Manager</guimenuitem> feature on jEdit's
  24. <guimenu>Plugin</guimenu> menu. You can also get more
  25. detailed descriptions of the plugins from the <ulink
  26. url="http://plugins.jedit.org">Plugin Central</ulink> web
  27. site.</para>
  28. </answer>
  29. </qandaentry>
  30. <qandaentry>
  31. <question id="plugins-latest-beta">
  32. <para>Where can I get information on new plugins under
  33. development?</para>
  34. </question>
  35. <answer>
  36. <para>We encourage plugin developers to join the
  37. <email>jedit-devel@lists.sourceforge.net</email> mailing
  38. list. There, you will find the greatest concentration of
  39. people who are also familiar with the core and its
  40. plugins.</para>
  41. </answer>
  42. </qandaentry>
  43. <qandaentry>
  44. <question id="plugin-install-manual">
  45. <para>How do I install a plugin manually, without using the
  46. Plugin Manager?</para>
  47. </question>
  48. <answer>
  49. <para>Copy the plugin's jar archive file (or files, if there
  50. are more than one) to the <filename>/jars</filename>
  51. subdirectory of either (a) the directory in which jEdit is
  52. installed, or (b) your user settings directory (which you
  53. can find by evaluating the BeanShell expression
  54. <userinput>jEdit.getSettingsDirectory()</userinput>.</para>
  55. </answer>
  56. </qandaentry>
  57. <qandaentry>
  58. <question id="plugins-developing">
  59. <para>How do I write a plugin?</para>
  60. </question>
  61. <answer>
  62. <para>Writing a plugin requires a working knowledge of Java
  63. and some familiarity with jEdit's Plugin API. There is a
  64. tutorial on plugin development in the jEdit User's Guide.
  65. The source code distribution for jEdit also includes the
  66. source for an example plugin, <application>Quick
  67. Notepad</application>, which is discussed in the
  68. tutorial.</para>
  69. <para>To learn more about plugin development, take a look at
  70. the source code for other plugins, particularly those whose
  71. features or user interface you might use as a model. The
  72. <ulink url="mailto:jedit-devel@lists.sourceforge.net">jedit-devel mailing
  73. list</ulink> and the message boards at <ulink
  74. url="http://community.jedit.org">jEdit Community</ulink> are
  75. also available for specific questions.</para>
  76. </answer>
  77. </qandaentry>
  78. <qandaentry>
  79. <question id="plugin-irc">
  80. <para>Is there an IRC (Internet Relay Chat) plugin for
  81. jEdit?</para>
  82. </question>
  83. <answer>
  84. <para>Yes. Open the Plugin Manager, then select
  85. <guimenuitem>Install plugins</guimenuitem>. You will find
  86. the IRC plugin which you can select for installation.</para>
  87. </answer>
  88. </qandaentry>
  89. <qandaentry>
  90. <question id="plugin-console-execute">
  91. <para>Is it possible to execute my application from within
  92. jEdit?</para>
  93. </question>
  94. <answer>
  95. <para>Yes. You can use the System shell of the Console
  96. plugin to run your application.</para>
  97. </answer>
  98. </qandaentry>
  99. <qandaentry>
  100. <question id="plugin-cvs">
  101. <para>Can I work with cvs/svn/git/hg/bzr/Perforce
  102. under jEdit? Is there a plugin for my favorite SCCS system?
  103. How can I send a command from jEdit to cvs/svn without
  104. leaving my editor?</para>
  105. </question>
  106. <answer>
  107. <para>The SVNPlugin supports Subversion browsing, diffing
  108. (via JDiff) and other common operations.</para>
  109. <para>With *NIX (or cygwin), the Console plugin
  110. documentation has some ideas on how to use jEdit as the
  111. <literal>VISUAL</literal> editor when called from the
  112. cvs/svn/hg command-line tools, all of which can be run from
  113. the Console dockable.</para>
  114. <para>The ProjectViewer plugin has some support for reading
  115. the "entries" in your working directory, and will use that as a filter for importing. CVS/SVN support is built-in, and p4, bzr, git, and hg are also supported via plugins. </para>
  116. <para>The P4Plugin adds Perforce support to ProjectViewer,
  117. and has some other advanced features for working with
  118. Perforce repositories.</para>
  119. <para>You can use jEdit as your default editor from WinCVS:
  120. specify <userinput>jedit.exe</userinput> as your default
  121. viewer and editor to automate the opening of file.</para>
  122. <para>GruntSpud and jEditCvs are not maintained, but do
  123. offer CVS support on jEdit 4.2final.</para>
  124. </answer>
  125. </qandaentry>
  126. <qandaentry>
  127. <question id="plugin-debugger">
  128. <para>Is there a debugger plugin?</para>
  129. </question>
  130. <answer>
  131. <para> The GdbPlugin provides gdb/mi support for C/C++
  132. programs. Also, the Console BeanShell can be used to debug Java classes in the current running JVM. </para>
  133. <para>A plugin based on the version 1.4 of the JSwat
  134. debugger application is currently available for download
  135. using jEdit's Plugin Manager feature. </para>
  136. <para>The developers would like to come up with a common
  137. debugger plugin that can be shared between java, gdb, and python, but such a thing does not exist at this time.
  138. </para>
  139. </answer>
  140. </qandaentry>
  141. <qandaentry>
  142. <question id="plugins-xslt">
  143. <para>Any development on integrating an XSL parser? It would
  144. be great to have the possibility to do XSL + XSLT -&gt;
  145. XHTML development in the same environment as other
  146. development.</para>
  147. </question>
  148. <answer>
  149. <para>There is currently one plugin available called XSLT.
  150. The XSLT plugin provides features for: transforming XML
  151. using XSL transformation stylesheets; evaluating XPath
  152. expressions on XML and displaying results; and indenting
  153. XML.</para>
  154. </answer>
  155. </qandaentry>
  156. <qandaentry>
  157. <question id="plugins-ssh">
  158. <para>Is there a plugin to enable editing of remote files
  159. over FTP or SSH?</para>
  160. </question>
  161. <answer>
  162. <para>The FTP plugin allows remote editing of files over the
  163. <literal>SFTP://</literal> and <literal>FTP://</literal>
  164. protocols. <literal>HTTP://</literal> is supported natively
  165. in jEdit. The <literal>FTPS://</literal> and
  166. <literal>FISH://</literal> protocols are not supported
  167. yet.</para>
  168. </answer>
  169. </qandaentry>
  170. </qandadiv>
  171. </qandaset>
  172. </section>