Attachment 91673 Details for Bug 199614 – Proposed Patch

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

[patch] Proposed Patch

199614patch.txt (text/plain), 13.11 KB, created by Ritwik Lodhiya

on 2008-03-05 12:01:54 EST

(hide)

Description:

Filename:

MIME Type:

Creator: Ritwik Lodhiya

Created: 2008-03-05 12:01:54 EST

Size: 13.11 KB

patch

obsolete

>### Eclipse Workspace Patch 1.0
>#P org.eclipse.hyades.trace.ui
>Index: ProfilingHelpContexts.xml
>===================================================================
>RCS file: /cvsroot/tptp/platform/org.eclipse.hyades.trace.ui/ProfilingHelpContexts.xml,v
>retrieving revision 1.6
>diff -u -r1.6 ProfilingHelpContexts.xml
>--- ProfilingHelpContexts.xml	29 Feb 2008 03:31:17 -0000	1.6
>+++ ProfilingHelpContexts.xml	5 Mar 2008 16:56:50 -0000
>@@ -48,7 +48,7 @@
> </context>
> 
> <context id="tbpp0007">
>-<description>This page lets you set application context preferences for profiling views.
>+<description>This page lets you set application context preferences for profiling views. You can modify labels in the profiling view to display data using the proper terms of different programming languages.
> </description>
> <topic label="Managing application context settings for profiling views" href="../org.eclipse.tptp.platform.doc.user/tasks/tsetprefappcontext.htm"/>
> </context>
>#P org.eclipse.tptp.platform.doc.user
>Index: tasks/tsetprefappcontext.htm
>===================================================================
>RCS file: /cvsroot/tptp/platform/org.eclipse.tptp.platform.doc.user/tasks/tsetprefappcontext.htm,v
>retrieving revision 1.5
>diff -u -r1.5 tsetprefappcontext.htm
>--- tasks/tsetprefappcontext.htm	25 Apr 2007 04:01:10 -0000	1.5
>+++ tasks/tsetprefappcontext.htm	5 Mar 2008 16:56:51 -0000
>@@ -12,55 +12,288 @@
> * IBM - Initial contribution
> **********************************************************************/ 
> -->
>-<HTML lang="EN-US">
>-<HEAD>
>-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
>+<html xmlns:v="urn:schemas-microsoft-com:vml"
>+xmlns:o="urn:schemas-microsoft-com:office:office"
>+xmlns:w="urn:schemas-microsoft-com:office:word"
>+xmlns="http://www.w3.org/TR/REC-html40">
>+
>+<head>
>+<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
>+<meta name=ProgId content=Word.Document>
>+<meta name=Generator content="Microsoft Word 10">
>+<meta name=Originator content="Microsoft Word 10">
>+<link rel=File-List href="tsetprefappcontext_files/filelist.xml">
> <title>Managing application context settings for profiling views</title>
>-<link rel="stylesheet" type="text/css" href="../css/book.css" >
>-</HEAD>
>-<BODY>
>+
>+<link rel=Stylesheet type="text/css" media=all href="../css/book.css">
>+<style>
>+
>+</style>
>+
>+</head>
>+
>+<body bgcolor=white lang=EN-US link=blue vlink=blue style='tab-interval:36.0pt'>
>+
>+<div class=Section1>
>+
> <h1>Managing application context settings for profiling views</h1>
>-
>-The Application context preferences dialog lists the application context
>-formatters that are available in the workbench. You can also choose
>-which formatter you want the profiling views to use if there is more
>-than one formatter available for a single application context name.
>-
>-
>-The "Application context names" table shows all context names that have
>-a formatter installed. Select one of these names to see information
>-about the installed formatter or formatters for that context name.
>-"Java" is the default application context name for data sets that do not
>-specify one.
>-
>-
>-The "Context formatters for views" table shows the names of the context
>-formatters for the selected application context name. If there is more
>-than one formatter in the list, the selected one will be used in the
>-profiling views when displaying data for the application context.
>-
>-
>-The "Handler for opening source files" table shows the names of handlers
>-for the "Open source" action for the selected application context name.
>-The "open source" action is used when you navigate from a profiling data
>-item (for example, a Java method name) to the corresponding program
>-source code. If there is more than one handler in the list, the selected
>-one will be used when you open the source file for a data item.
>-
>- 
>- 
>- 
>-
>-Related concepts<A href="../ref/reappcontext.htm"> 
>-Understanding application contexts in profiling views 
>-Overview of the Profiling Tool</A> 
>-Related tasks 
>-<A href="tecretrc.htm">Setting profiling preferences Profiling an application</A> 
>-<A href="tpfviews.htm">Using profiling views to analyze data</A> 
>-<A href="../ref/retime.htm">Viewing time measurements</A> 
>- 
>- 
>-(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.
>-
>-</BODY>
>-</HTML>
>+
>+The Application context preferences dialog lists the application context
>+formatters that are available in the workbench. The &quot;application
>+context&quot; system lets the profiling views display data using the proper
>+terms no matter what kind of data was collected. For example, the Java term
>+&quot;method,&quot; the C term &quot;function,&quot; and the FORTRAN term
>+&quot;procedure&quot; all mean to the same thing. If you collect data from a C
>+program, you want to display the data using C terms and syntax. The application
>+context system allows you to do that. You can also choose which formatter you
>+want the profiling views to use if there is more than one formatter available
>+for a single application context name. 
>+
>+The Package, Class, and Method structure used by default in Java can be
>+replaced by structure names of different languages C/C++, FORTRAN, COBOL etc) in
>+various locations, such as in the view header, formatting, and filter dialog.
>+The user also has the ability to extend the tool provide custom labels/icons
>+for existing profiling views. 
>+
>+The user can modify the language preferences by creating an extension for
>+the new context definition, the context provider declaration, and the context
>+open source action in the plugin.xml file of the
>+project. For more information, open the Context Language Sample by File
>+&gt; New &gt; Example... &gt; Context Language Sample
>+
>+The &quot;Application context names&quot; table shows all context names that
>+have a formatter installed. Select one of these names to see information about
>+the installed formatter or formatters for that context name. &quot;Java&quot;
>+is the default application context name for data sets that do not specify one. 
>+
>+The &quot;Context formatters for views&quot; table shows the names of the
>+context formatters for the selected application context name. If there is more
>+than one formatter in the list, the selected one will be used in the profiling
>+views when displaying data for the application context. 
>+
>+The &quot;Handler for opening source files&quot; table shows the names of
>+handlers for the &quot;Open source&quot; action for the selected application
>+context name. The &quot;open source&quot; action is used when you navigate from
>+a profiling data item (for example, a Java method name) to the corresponding
>+program source code. If there is more than one handler in the list, the
>+selected one will be used when you open the source file for a data item. 
>+
>+ 
>+<![if !supportLineBreakNewLine]> 
>+<![endif]>
>+
>+Related concepts<a
>+href="../ref/reappcontext.htm"> 
>+Understanding application contexts in profiling views 
>+Overview of the Profiling Tool</a>
>+
>+Related tasks 
>+<a href="tecretrc.htm">Setting profiling preferences 
>+Profiling an application</a> 
>+<a href="tpfviews.htm">Using profiling views to analyze data</a> 
>+<a href="../ref/retime.htm">Viewing time measurements</a> 
>+ 
>+ 
>+(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved. 
>+
>+</div>
>+
>+</body>
>+
>+</html>

Actions: View | Diff

Attachments on bug 199614: 91673 | 93324