[Esbox-commits] r1080 - branches/work_Jeff/org.maemo.esbox.help/html/gettingstarted

Mon Dec 15 23:20:25 EET 2008

Author: jeffc
Date: 2008-12-15 23:20:25 +0200 (Mon, 15 Dec 2008)
New Revision: 1080

Removed:
   branches/work_Jeff/org.maemo.esbox.help/html/gettingstarted/ExternalizeString.html
   branches/work_Jeff/org.maemo.esbox.help/html/gettingstarted/ProfilingMaemoApplications.html
Log:
moved some topics to tasks

Deleted: branches/work_Jeff/org.maemo.esbox.help/html/gettingstarted/ExternalizeString.html
===================================================================

--- branches/work_Jeff/org.maemo.esbox.help/html/gettingstarted/ExternalizeString.html	2008-12-15 21:19:23 UTC (rev 1079)
+++ branches/work_Jeff/org.maemo.esbox.help/html/gettingstarted/ExternalizeString.html	2008-12-15 21:20:25 UTC (rev 1080)
@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<html lang="en">
-<head>
-	<meta name="copyright" content="Copyright (c) INdT 2007-2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-	<meta http-equiv="Content-Language" content="en-us">
-	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-	<title>Externalize string on C/C++ application</title>
-	<link rel="stylesheet" type="text/css" href="../help.css">
-    <style type="text/css">
-<!--
-.style1 {font-weight: bold}
--->
-    </style>
-</head>
-
-<body>
-<h2 class="style1">Extracting Strings</h2>
-
-
-<p>The Externalize Strings wizard allows you to refactor a compilation unit 
-such that strings used in the compilation unit can be translated to different languages.</p>
-<p>To externalize strings:</p>
-  <ol>
-	<li>Select a project in Project Explorer and right-click to display the popup menu and select <strong>Source > Externalize Strings</strong>.</li>
-	<p><img src="../images/extractstrings.png" alt="Externalize String" width="430" height="459"></p>
-    <li>Select the file(s) that should be externalized to enable the Externalize button, then click Externalize.</li>
-	<p><img src="../images/extractstrings1.png" alt="File that should be externalized" width="400" height="500"></p>
-    <li>A Wizard will appear showing strings that will be externalized. You can define the name of the output file, msgstr, and msgid. Click on a message string or message id to make a change.</li>
-	<p><img src="../images/extractstrings2.png" alt="Externalize Wizard" width="719" height="726"></p>
-	<li>Click Finish.</li>
-</ol>
-
-<p>A couple of files will be generated (<strong>POTFILE.in</strong> and <strong>outputName.po</strong>) which will be placed in the <strong><em>ProjectName</em>/po/</strong> directory.</p>
-<ul>
- <li>POTFILES.in contains the list of source code files that will be localized.</li> 
- <li> <em>outputName</em>.po includes translated text.</li>
-</ul>
-
-<p>The Console view will output warnings and errors.</p>
-
-<p><b>For example:</b></p>
-<p>In your source code, you probably have many strings, which eventually are shown in the user interface. For example:</p>
-
-<p><b>hildon_app_set_title ( app, "MaemoPad" );</b></p>
-
-<p>To make your strings localizable, you need to wrap the strings you want translated in gettext("String") calls. In practice, writing gettext() for every string is tedious. The common practice is to set the following #define.</p>
-
-<p><b>#define _(String) gettext (String)</b></p>
-
-<p>Thus the i18n version of the example would be:</p>
-
-<p><b>hildon_app_set_title ( app, _("MaemoPad") );</b></p>
-
-</body>
-</html>

Deleted: branches/work_Jeff/org.maemo.esbox.help/html/gettingstarted/ProfilingMaemoApplications.html
===================================================================
--- branches/work_Jeff/org.maemo.esbox.help/html/gettingstarted/ProfilingMaemoApplications.html	2008-12-15 21:19:23 UTC (rev 1079)
+++ branches/work_Jeff/org.maemo.esbox.help/html/gettingstarted/ProfilingMaemoApplications.html	2008-12-15 21:20:25 UTC (rev 1080)
@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<html lang="en">
-<head>
-	<meta name="copyright" content="Copyright (c) INdT 2007-2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-	<meta http-equiv="Content-Language" content="en-us">
-	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-	<title>Profiling C/C++ application</title>
-	<link rel="stylesheet" type="text/css" href="../help.css">
-    <style type="text/css">
-<!--
-.style1 {font-weight: bold}
--->
-    </style>
-</head>
-
-<body>
-<h2 class="style1">Profiling Maemo Applications</h2>
-
-<p><span style="font-weight: bold;"></span>Profiling is one of the most
-important techniques available for programmers to discover problems in applications. By profiling an application,
-it becomes immediately apparent where the overwhelming memory and CPU
-burdens exist, and allows you to quickly squash them. ESbox provides
-support for <a href="http://www.valgrind.org/">Valgrind</a> memory profiler and <a href="http://oprofile.sourceforge.net/news/">OProfile</a> system-wide profiler for both C/C++ and Python Projects.</p>
-
-<h3>Using Valgrind</h3>
-<p>Valgrind is a framework to build dynamic analyses tools. You can
-use Valgrind to profile your applications. It detects memory management
-(memory leaks, use of uninitialised memory, etc.) and thread bugs.
-However, Valgrind is only supported on X86/Linux, AMD64/Linux,
-PPC32/Linux and PPC64/Linux. To run Valgrind, you have to
-select an X86 Scratchbox target with the tool properly installed.</p>
-
-<p>To run Valgrind, right-click on the application (binary for C/C++
-projects or the Python script for Python projects) and select <strong>Run As &gt; Local Valgrind Memory Profiler</strong>.<br>
-<br>
-<img src="../images/valgrind.png" width="509" height="428"><br>
-</h2>
-</p>
-<p>The Valgrind tool runs your application on the X86 target and the result is
-  shown in the Valgrind view. All problems found by Valgrind are shown as a
-  tree: problem as parent nodes and details of the problems as children
-  nodes.</p>
-<p><img src="../images/profiling1.jpg"><br>
-</p>
-<p>&nbsp;</p>
-<h3>Using OProfile</h3>
-<p>OProfile is a&nbsp;system-wide profiler for Linux systems and
-can profile all running code.&nbsp;It consists of a kernel driver and a daemon for collecting sample data,
-and several post-profiling tools for turning data into information. OProfile is
-supported for ARM/Linux. It's executed on the Internet Tablet in order to
-obtain a high quality of profiling information. ESbox uses ssh to
-remotely execute OProfile and collect profiling information. So, it's
-necessary to properly install the application (OProfile installation 
-information can be found <a href="http://maemo.org/development/tools/doc/chinook/oprofile/">here</a>. ).</p>
-
-<p>To run OProfile, in the Project View right-click on the project or application 
-(binary for C/C++ projects or the Python script for Python projects) and select 
-<strong>Run As &gt; OProfile Profiler</strong>. An OProfile launch configuration will be
-automatically created for you and will be launched. If you want to create or edit a launch
-configuration for Oprofile yourself, please see 
-<a href="../tasks/CreateOprofileconfig.html">Creating a OProfile Run Launch Configuration</a>.</p>
-
-<p>After OProfile starts, ESbox launches your application on the device.
-  Then a dialog will pop up letting you decide when to stop profiling data collecting. 
-  After you click OK on the dialog, OProfile data collecting will
-  stop and the profiling result will be shown in the OProfile View.</p>
-<br>
-<img src="../images/profiling4.jpg" width="1024" height="783">
-<br>
-</body>
-</html>

