Laboratoire ICAR » Plateforme TXM

	  <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>

	  <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins">

		    <accessrules>

			      <accessrule kind="accessible" pattern="**"/>

		    </accessrules>

	  </classpathentry>

	  <classpathentry kind="src" path="src"/>

	  <classpathentry kind="output" path="bin"/>

	  <classpathentry exported="true" kind="lib" path="lib/jython-standalone-2.7.0.jar"/>

	  <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>

	  <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins">

		    <accessrules>

			      <accessrule kind="accessible" pattern="**"/>

		    </accessrules>

	  </classpathentry>

	  <classpathentry kind="src" path="src"/>

	  <classpathentry kind="output" path="bin"/>

	  <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>

	  <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins">

		    <accessrules>

			      <accessrule kind="accessible" pattern="**"/>

		    </accessrules>

	  </classpathentry>

	  <classpathentry kind="src" path="src"/>

	  <classpathentry kind="output" path="bin"/>

	  <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>

	  <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins">

		    <accessrules>

			      <accessrule kind="accessible" pattern="**"/>

		    </accessrules>

	  </classpathentry>

	  <classpathentry kind="src" path="src"/>

	  <classpathentry kind="output" path="bin"/>

	  <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>

	  <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins">

		    <accessrules>

			      <accessrule kind="accessible" pattern="**"/>

		    </accessrules>

	  </classpathentry>

	  <classpathentry kind="src" path="src"/>

	  <classpathentry kind="output" path="bin"/>

	  <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>

	  <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins">

		    <accessrules>

			      <accessrule kind="accessible" pattern="**"/>

		    </accessrules>

	  </classpathentry>

	  <classpathentry kind="src" path="src"/>

	  <classpathentry kind="output" path="bin"/>

	  <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>

	  <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins">

		    <accessrules>

			      <accessrule kind="accessible" pattern="**"/>

		    </accessrules>

	  </classpathentry>

	  <classpathentry kind="src" path="src"/>

	  <classpathentry kind="output" path="bin"/>

<p>Cooccurrence Matrix</p>

	  <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>

	  <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins">

		    <accessrules>

			      <accessrule kind="accessible" pattern="**"/>

		    </accessrules>

	  </classpathentry>

	  <classpathentry kind="src" path="src"/>

	  <classpathentry kind="output" path="bin"/>

<p>Prototype of aligned edition browser</p>

	  <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>

	  <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins">

		    <accessrules>

			      <accessrule kind="accessible" pattern="**"/>

		    </accessrules>

	  </classpathentry>

	  <classpathentry kind="src" path="src"/>

	  <classpathentry kind="output" path="bin"/>

<p>Progression - inspired by Weblex.</p>

	  <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>

	  <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins">

		    <accessrules>

			      <accessrule kind="accessible" pattern="**"/>

		    </accessrules>

	  </classpathentry>

	  <classpathentry kind="src" path="src"/>

	  <classpathentry kind="output" path="bin"/>

<p>Diagnostic function</p>

  <contexts>

    <context id="overallHelp">

      <description>Help for Practically Macro plugin</description>

      <topic href="doc/overall.html" label="Practically Macro"/>

    </context>

    <context id="editDialogHelp">

      <description>Help for Practically Macro edit dialog</description>

      <topic href="doc/macroEdit.html" label="Practically Macro macro editing"/>

    </context>

    <context id="managingMacrosHelp">

      <description>Help for Practically Macro edit dialog</description>

      <topic href="doc/macroManage.html" label="Practically Macro macro management"/>

    </context>

  </contexts>

	  <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>

	  <classpathentry kind="src" path="src"/>

	  <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>

	  <classpathentry kind="output" path="bin"/>

Practically Macro is an attempt to add simple editor scripting to the Eclipse platform; it is not an attempt at scripting the Eclipse platform in general.  I believe that editor scripting, while similar to general scripting, is fundamentally a different problem.  The intent of this plug-in is to enable users to record/create editor macros in a lightweight manner that can be used temporarily or easily shared with others.  I have tried to do this in a way that uses public API and public assumptions, and I've mostly been able to do so.  In my opinion, every character entered or navigation button pressed should generate a command that can be recorded.  However, Eclipse doesn't generate commands for everything, so I've done the best I can.

Eclipse 3.4 or greater; will not run correctly at 3.3.  Requires the workbench.  Shouldn't require jdt.  

Start recording a macro by typing Alt+Ctrl+R or clicking the "Record Macro" button on the main toolbar.  The Record button is only enabled when a text editor has input focus.  Once record mode is invoked, the record button will appear depressed.  

Actions that will be captured by recording a macro are Eclipse commands and keystrokes.  Mouse activity is not captured and should be avoided in the editor window.

Once you are done recording a macro, click the "Record Macro" button again.  If you have recorded any macro contents, a Save dialog will pop up allowing you to supply a name/id/description for the macro.  You can cancel if you don't want to keep the macro.  To allow the macro to be persisted across Eclipse invocations or to allow mapping the command to a keystroke, you must supply an ID.  If you only supply a name, the macro can be used during the Eclipse session only.  You can modify/add an ID later in the session. 

To play a macro, use the drop down menu on the "Play Macro" button.  You can use the "Play command..." button to execute any Eclipse command or macro that is already defined.  If there are user macros defined with ids, they will show up in a menu called "Macros".  Only the last few will be available, and they will be ordered by last used time.  If there are commands that do not have associated ids, they will show up in the submenu named "Temporary Macros", ordered by last used time.  After you have execute a macro, clicking the Play button will execute the last executed macro.

This plug-in is built on top of the Eclipse platform. Unfortunately, the Eclipse command structure is not designed with macro recording in mind.  What this means is that not all commands are recordable, and some behavior may be a little sketchy.  However, you can edit a macro after recording, so you should be able to patch up behavior that isn't desirable.  The lack of an official Eclipse strategy means that there is no guide to what commands should be recordable, so I don't impose any artificial limitations.<br>

Here are some types of actions that make sense to record as part of a macro:<br>

<ul>typing characters (see note below)</ul>

<ul>navigation characters (ex. arrows, page down)</ul>

<ul>find dialog (I've supplied my own since the standard dialog isn't public)</ul>

<ul>incremental find (with some hacking)</ul>

<ul>previously recorded macros</ul>

<ul>other commands that don't pop up dialogs (ex. file save, find next, organize imports, toggle insert mode)</ul>

<br> 

Here are some types of actions that almost certainly won't work correctly:<br>

<ul>Commands that bring up dialogs (ex. Go to line)</ul>

<ul>Wizards and other dialogs (ex. Open File)</ul>

<ul>ctrl+space intellisense</ul>

<ul>invoking code templates like "foreach"</ul>

Certain keystrokes are handled specially by the language editor.  However, these editors don't generate commands associated with their behavior, so they are difficult to interpret.  For example, in a Java file, if you type in a '<', a '>' will be inserted and the cursor will be placed between the two symbols.  Also, the editor is put into a special edit mode so that if you backspace, both characters are deleted.  However, there is no set of commands generated that accomplishes these tasks.  Instead, the editor document captures the initial '<' via a VerifyKeyListener and then does the inserts and sets the mode directly on the document.  Therefore, if you have this setting ("Automatically Close") turned on and type a '<', then the macro will not have any commands corresponding to some of these operations.  You can edit the macro afterward, but that may be inconvenient.  I've added another mode on the Options page that records keys as raw key events and plays them back.  This preserves the behavior of special characters like '<', but is more difficult to edit and may not be sharable with users on other platforms.

<br><bold>In general, I recommend running in 'Command' mode and 'typing through' special keystroke modes while recording a macro.</bold>

You can edit macros you have recorded via the Window->Preferences->PracticallyMacro Options->Editor Macro Definitions page.  From this page, you can delete existing macros or edit macros.  Select a macro and click the Edit... button.  From the edit dialog, you can reorder commands in the macro, remove commands, add new commands, and edit commands that have data associated with them (ex. the Find command).

The Edit dialog also allows you to add a new macro id to a command that didn't previously have an associated id (thus turning it into a persistent command), or alter the id of an existing command.

From the Editor Macro Definitions page you can export or import macros.  Macros exported to a file can be imported via the import dialog into another eclipse (with the Practically Macro plugins installed, as well as any required plugins/commands).  

Macro scripting is provided by plugins via an extension point.  See the help for different script types on pref or edit pages for those plugins.  There is no innate scripting provided by the base Practically Macro plugin, but there is a default beanshell plugin paired with the main plugin.  

From the edit dialog, you can:<br>

<ul>reorder commands in the macro</ul>

<ul>remove commands</ul>

<ul>add new commands</ul>

<ul>edit commands that have data associated with them (ex. the Find command).</ul>

<br>The Edit dialog also allows you to add a new macro id to a command that didn't previously have an associated id (thus turning it into a persistent command), or alter (or remove) the id of an existing command.

<br>Adding new commands to the macro requires that you have some knowledge of the commands.  There is a filter above the <bold>Available Commands</bold> list that defaults to showing only edit commands (based on looking at categories).  Some commands are not appropriate to a macro, but it's impossible for me to tell what they are, so you may have to experiment.

<ul>Mark selection start - set a 'mark' at the current selection start, or at the caret pos if no selection</ul>

<ul>Mark selection end - set a 'mark' at the current selection end, or at the caret pos if no selection</ul>

<ul>Move cursor to mark - Set the editor cursor to the current mark position</ul>

<ul>Insert string - this is the workhorse command used to add text. Can contain carriage returns.</ul>

<ul>Find - perform various kinds of text searching</ul>

<ul>Styled Text commands - These are commands I've added to the system since they aren't commands by default.  Actions like "move cursor right" are supported by the StyledText widget but aren't mapped as key bindings.</ul>

<ul>Macro script - You can write whatever scripts you'd like using beanshell.  I pass in several variables for the editor that should be useful.</ul>

<br>

The Mark commands are provided as a way to maintain some state while other operations are performed without requiring scripting.  

For example, to comment a selected area, you could record a sequence of commands like:

<ol>mark selection start</ol>

<ol>move cursor right (puts cursor at end of selection</ol>

<ol>insert string "*/"</ol>

<ol>move cursor to mark</ol>

<ol>insert string "/*"</ol>

<h1>Creating new macros</h2>

Click the <bold>New</bold> button to create a new macro from scratch.

<h1>Deleting Macros</h2>

Select one or more macros to delete and click the delete button.  Macros that are mapped to keystrokes will fail to delete, as will macro contributed by plug-ins.  To delete a macro mapped to a key, you must first remove the key binding.

<h1>Editing Macros</h2>

Click the <bold>Edit</bold> button to edit an existing macro.  Macros contributed from plug-ins cannot be edited.

<h1>Copying Macros</h2>

To copy one or more macros, select them and click the <bold>Copy</bold> button.  Each macro will be copied and added to the list with a new name.  This is useful if you need another similar command, or if you want to see the contents of a macro contributed from a plug-in.

<h1>Sharing macros</h2>

Click the <bold>Export</bold> or <bold>Import</bold> buttons to export or import macros.  Macros exported to a file can be imported via the import dialog into another eclipse (with the Practically Macro plugins installed, as well as any required plugins/commands).  Macros with ids that already exist in the current Eclipse will be skipped (i.e. they will not replace the current command with that ID).  Also, from the export dialog you can copy the XML from the text box and put that directly into a plugin.xml definition with the following extension point:

<br><pre>   &lt;extension point="PracticallyMacro.defineMacro"&gt;

   &lt;/extension&gt;</pre><br>

When exporting to a file, you can export one macro or a set of macros to the same file.  If a macro uses other macros you have defined, you should export them all together.