[cp-patches] Patch: FYI: a handy launch configuration

[Tom Tromey]

I'm checking this in.

This adds a launch configuration called "ClasspathSwingActivityBoard"
(I pick these long goofy names to avoid name clash in the workspace;
at least with builder launch configs eclipse is still picky about
this; there is an eclipse.org PR for it).

This new launcher will run the swing activity board using the metal
plaf.  It requires that you have a jamvm project set up, per my
earlier message.

I don't want to go overboard and add too many built-in launchers.
But, I thought this one would be useful as it is a GUI application and
it is useful in an area that is seeing heavy hacking at the moment.

Note that right now these are CDT launch configs, and you may need the
CDT for them to work.  This is sub-optimal.  Andrew Overholt had a
good idea earlier -- if we had an eclipse extension that taught
eclipse how to recognize the workspace jamvm as a JRE, then we could
make java launch configs.  This doesn't present a huge advantage at
the moment, but it will once JDWP is wired into the VM...

Tom

2005-09-08  Tom Tromey  <address@hidden>
 
        * 
examples/gnu/classpath/examples/swing/ClasspathSwingActivityBoard.launch:
        New file.

Index: examples/gnu/classpath/examples/swing/ClasspathSwingActivityBoard.launch
===================================================================
RCS file: 
examples/gnu/classpath/examples/swing/ClasspathSwingActivityBoard.launch
diff -N examples/gnu/classpath/examples/swing/ClasspathSwingActivityBoard.launch
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ examples/gnu/classpath/examples/swing/ClasspathSwingActivityBoard.launch    
1 Jan 1970 00:00:00 -0000
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<launchConfiguration type="org.eclipse.cdt.launch.localCLaunch">
+<stringAttribute key="org.eclipse.cdt.launch.DEBUGGER_ID" 
value="org.eclipse.cdt.debug.mi.core.CDebugger"/>
+<stringAttribute key="org.eclipse.cdt.launch.protocol" value="mi"/>
+<booleanAttribute key="org.eclipse.cdt.debug.mi.core.STOP_ON_SOLIB_EVENTS" 
value="false"/>
+<stringAttribute key="org.eclipse.cdt.launch.DEBUGGER_START_MODE" value="run"/>
+<listAttribute key="org.eclipse.cdt.debug.mi.core.SOLIB_PATH"/>
+<booleanAttribute key="org.eclipse.debug.core.appendEnvironmentVariables" 
value="true"/>
+<booleanAttribute key="org.eclipse.cdt.launch.ENABLE_REGISTER_BOOKKEEPING" 
value="false"/>
+<booleanAttribute key="org.eclipse.cdt.debug.mi.core.AUTO_SOLIB" value="true"/>
+<booleanAttribute key="org.eclipse.cdt.launch.DEBUGGER_STOP_AT_MAIN" 
value="true"/>
+<booleanAttribute key="org.eclipse.cdt.launch.use_terminal" value="true"/>
+<stringAttribute key="org.eclipse.cdt.launch.PROJECT_ATTR" value="jamvm"/>
+<booleanAttribute key="org.eclipse.cdt.launch.ENABLE_VARIABLE_BOOKKEEPING" 
value="false"/>
+<stringAttribute key="org.eclipse.cdt.debug.mi.core.DEBUG_NAME" value="gdb"/>
+<stringAttribute key="org.eclipse.cdt.launch.PROGRAM_NAME" value="src/jamvm"/>
+<stringAttribute key="org.eclipse.cdt.launch.PROGRAM_ARGUMENTS" 
value="-Dswing.defaultlaf=javax.swing.plaf.metal.MetalLookAndFeel 
gnu.classpath.examples.swing.Demo"/>
+<stringAttribute key="org.eclipse.cdt.debug.mi.core.GDB_INIT" value=""/>
+</launchConfiguration>