+++ /dev/null
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
- <name>org.tizen.web.simulator.help</name>
- <comment></comment>
- <projects>
- </projects>
- <buildSpec>
- <buildCommand>
- <name>org.eclipse.pde.ManifestBuilder</name>
- <arguments>
- </arguments>
- </buildCommand>
- <buildCommand>
- <name>org.eclipse.pde.SchemaBuilder</name>
- <arguments>
- </arguments>
- </buildCommand>
- </buildSpec>
- <natures>
- <nature>org.eclipse.pde.PluginNature</nature>
- </natures>
-</projectDescription>
+++ /dev/null
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: Tizen Simulator Help
-Bundle-SymbolicName: org.tizen.web.simulator.help;singleton:=true
-Bundle-Version: 1.0.0
-Bundle-Vendor: Intel
+++ /dev/null
-bin.includes = META-INF/,\
- plugin.xml
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8"?>
-<project name="org.tizen.simulator.help" default="build.jars" basedir=".">
-
- <property name="p2.build.repo" value="file:${buildDirectory}/buildRepo"/>
- <property name="basews" value="${ws}"/>
- <property name="baseos" value="${os}"/>
- <property name="basearch" value="${arch}"/>
- <property name="basenl" value="${nl}"/>
- <property name="bundleId" value="org.tizen.simulator.help"/>
- <property name="bundleVersion" value="1.0.0"/>
- <property name="p2.publishonerror" value="false"/>
-
- <!-- Compiler settings. -->
- <property name="javacFailOnError" value="false"/>
- <property name="javacDebugInfo" value="on"/>
- <property name="javacVerbose" value="false"/>
- <property name="logExtension" value=".log"/>
- <property name="compilerArg" value=""/>
- <property name="compilation.prereq.log" value="${buildDirectory}/prereqErrors.log"/>
- <property name="javacSource" value="1.3"/>
- <property name="javacTarget" value="1.2"/>
- <condition property="dir_bootclasspath" value="${java.home}/../Classes">
- <os family="mac"/>
- </condition>
- <property name="dir_bootclasspath" value="${java.home}/lib"/>
- <path id="path_bootclasspath">
- <fileset dir="${dir_bootclasspath}">
- <include name="*.jar"/>
- </fileset>
- </path>
- <property name="bootclasspath" refid="path_bootclasspath"/>
- <property name="bundleJavacSource" value="${javacSource}"/>
- <property name="bundleJavacTarget" value="${javacTarget}"/>
- <property name="bundleBootClasspath" value="${bootclasspath}"/>
-
- <target name="init" depends="properties">
- <condition property="pluginTemp" value="${buildTempFolder}/plugins" >
- <isset property="buildTempFolder"/>
- </condition>
- <property name="pluginTemp" value="${basedir}"/>
- <condition property="build.result.folder" value="${pluginTemp}/org.tizen.simulator.help_1.0.0" >
- <isset property="buildTempFolder"/>
- </condition>
- <property name="build.result.folder" value="${basedir}"/>
- <property name="temp.folder" value="${basedir}/temp.folder"/>
- <property name="plugin.destination" value="${basedir}"/>
- <condition property="p2.publish.parts" value="true" >
- <istrue value="${p2.gathering}"/>
- </condition>
- <property name="compilation.problem.marker" value="${build.result.folder}/compilation.problem"/>
- <condition property="compilation.problem.marker.exists" value="true" >
- <and>
- <available file="${compilation.problem.marker}"/>
- <isfalse value="${p2.publishonerror}"/>
- </and>
- </condition>
- </target>
-
- <target name="properties" if="eclipse.running">
- <property name="build.compiler" value="org.eclipse.jdt.core.JDTCompilerAdapter"/>
-
- </target>
-
- <target name="build.update.jar" depends="init" description="Build the plug-in: org.tizen.simulator.help for an update site.">
- <delete dir="${temp.folder}"/>
- <mkdir dir="${temp.folder}"/>
- <antcall target="build.jars"/>
- <antcall target="gather.bin.parts">
- <param name="destination.temp.folder" value="${temp.folder}/"/>
- </antcall>
- <jar destfile="${plugin.destination}/org.tizen.simulator.help_1.0.0.jar" basedir="${temp.folder}/org.tizen.simulator.help_1.0.0" filesetmanifest="merge"/>
- <delete dir="${temp.folder}"/>
- </target>
-
- <target name="build.jars" depends="init" description="Compile classes and build nested jars for the plug-in: org.tizen.simulator.help.">
- <delete file="${compilation.problem.marker}" quiet="true"/>
- </target>
-
- <target name="checkCompilationResults" if="compilation.error.occured">
- <echo file="${compilation.problem.marker}" message="org.tizen.simulator.help_1.0.0${line.separator}compilation.error.occured=${compilation.error.occured}"/>
- <eclipse.logCompileError bundle="org.tizen.simulator.help_1.0.0" log="${compilation.prereq.log}">
- </eclipse.logCompileError>
- </target>
-
- <target name="build.sources" depends="init">
- </target>
-
- <target name="publish.bin.parts" depends="init" if="p2.publish.parts" unless="compilation.problem.marker.exists">
- <mkdir dir="${build.result.folder}/org.tizen.simulator.help_1.0.0"/>
- <copy todir="${build.result.folder}" failonerror="true" overwrite="true">
- <fileset dir="${basedir}">
- <include name="META-INF/MANIFEST.MF"/>
- <include name="plugin.xml"/>
- <include name="fragment.xml"/>
- </fileset>
- </copy>
- <antcall target="apitools.generation">
- <param name="target.folder" value="${build.result.folder}"/>
- <param name="projectLocation" value="${basedir}"/>
- <param name="binary.folders" value="/home/bob/src/tizen/org.tizen.simulator.help"/>
- <param name="projectName" value="${bundleId}_${bundleVersion}"/>
- </antcall>
- <eclipse.gatherBundle
- metadataRepository="${p2.build.repo}"
- artifactRepository="${p2.build.repo}"
- buildResultFolder="${build.result.folder}"
- baseDirectory="${basedir}"
- />
- </target>
-
- <target name="gather.bin.parts" depends="init" if="destination.temp.folder">
- <mkdir dir="${destination.temp.folder}/org.tizen.simulator.help_1.0.0"/>
- <copy todir="${destination.temp.folder}/org.tizen.simulator.help_1.0.0" failonerror="true" overwrite="true">
- <fileset dir="${basedir}">
- <include name="META-INF/"/>
- <include name="plugin.xml"/>
- </fileset>
- </copy>
- <antcall target="apitools.generation">
- <param name="target.folder" value="${destination.temp.folder}/org.tizen.simulator.help_1.0.0"/>
- <param name="projectLocation" value="${basedir}"/>
- <param name="binary.folders" value="/home/bob/src/tizen/org.tizen.simulator.help"/>
- <param name="projectName" value="${bundleId}_${bundleVersion}"/>
- </antcall>
- </target>
-
- <target name="build.zips" depends="init">
- </target>
-
- <target name="gather.sources" depends="init" if="destination.temp.folder">
- <antcall target="copy.src.includes">
- <param name="source.destination.folder" value="${destination.temp.folder}/org.tizen.simulator.help_1.0.0"/>
- </antcall>
- </target>
-
- <target name="gather.individual.sources" depends="init">
- <antcall target="copy.src.includes">
- <param name="source.destination.folder" value="${destination.temp.folder}"/>
- </antcall>
- </target>
-
- <target name="copy.src.includes" depends="init">
- </target>
-
- <target name="gather.logs" depends="init" if="destination.temp.folder">
- </target>
-
- <target name="clean" depends="init" description="Clean the plug-in: org.tizen.simulator.help of all the zips, jars and logs created.">
- <delete file="${plugin.destination}/org.tizen.simulator.help_1.0.0.jar"/>
- <delete file="${plugin.destination}/org.tizen.simulator.help_1.0.0.zip"/>
- <delete dir="${temp.folder}"/>
- <delete file="${compilation.problem.marker}" quiet="true"/>
- </target>
-
- <target name="refresh" depends="init" if="eclipse.running" description="Refresh this folder.">
- <eclipse.convertPath fileSystemPath="/home/bob/src/tizen/org.tizen.simulator.help" property="resourcePath"/>
- <eclipse.refreshLocal resource="${resourcePath}" depth="infinite"/>
- </target>
-
- <target name="zip.plugin" depends="init" description="Create a zip containing all the elements for the plug-in: org.tizen.simulator.help.">
- <delete dir="${temp.folder}"/>
- <mkdir dir="${temp.folder}"/>
- <antcall target="build.jars"/>
- <antcall target="build.sources"/>
- <antcall target="gather.bin.parts">
- <param name="destination.temp.folder" value="${temp.folder}/"/>
- </antcall>
- <antcall target="gather.sources">
- <param name="destination.temp.folder" value="${temp.folder}/"/>
- </antcall>
- <delete>
- <fileset dir="${temp.folder}">
- <include name="**/*.bin${logExtension}"/>
- </fileset>
- </delete>
- <zip destfile="${plugin.destination}/org.tizen.simulator.help_1.0.0.zip" basedir="${temp.folder}" filesonly="true" whenempty="skip" update="false"/>
- <delete dir="${temp.folder}"/>
- </target>
-
- <target name="apitools.generation" if="generateAPIDescription">
- <apitooling.apigeneration projectName="${projectName}" project="${projectLocation}" binary="${binary.folders}" target="${target.folder}" extramanifests="${extraManifests}" allownonapiproject="${allowNonApiProject}" />
- </target>
-
-</project>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html>
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <title>Application Demos for Tizen Simulator</title>
- <!--
- <link rel="stylesheet" type="text/css" href="scripts/content.css" />
- -->
-</head>
-
-<body>
- <h2>Introduction of Tizen API Demo Application</h2>
- <p> Each feature of the Tizen API Demo application is briefly
- presented in the following paragraphs.</p>
-
- <h3>Accelerometer</h3>
- <p>Accelerometer API can access accelerometer sensor values and
- functionalities are provided via deviceapis.accelerometer interface.</p>
-
- <p>Application can subscribe to accelerometer device to receive
- notifications about device acceleration changes.</p>
-
- <p>X,Y and Z Axis values are show in the middle and when you can
- click and drag with mouse, those value will change concurrently.</p>
-
- <p>Also, we can click the "Shake" button to simulate the device is
- shaken along the X axis.</p>
-
- <h3>Device Orientation</h3>
- <p>This example simulates a device orientation change event.</p>
-
- <p>Switch between portrait and landscape icon from the Device
- panel, as you can see, the platform screen is rotated accordingly.</p>
-
- <h3>Device APIs</h3>
- This page shows the result of deviceapis.listAvailableFeatures() and
- deviceapis.listActivatedFeatures().
-
- <h3>Geo Positioning</h3>
- <p>Geographical data can be configured from the "Geo Location"
- panel and web simulator will pass the geo location data to the
- application.</p>
- <p>As shown in the video, we change the value of Latitude from the
- "Geo Location" panel and the map in the panel is updated instantly for
- reference. Then click the "Update Map" button in our application, the
- map in the center is updated accordingly with correct geographical
- data, just like the map on the Geo Location panel.</p>
-
- <h3>Camera</h3>
-
- <p>The example shows the emulated camera window for the device.
- Click capture to take a picture or use "Record Start" and "Record
- Stop" to record video.</p>
-
- <h3>Device Interaction</h3>
- <p>This example demonstrates a few device notification mechanisms
- provided by WAC 2.0 DeviceInteraction API. As shown in the "Device &
- Network Setting", you can turn on/off device vibrator and backlight
- and adjust audio volume.</p>
- <p>If backlight is off, the whole device is dimmed to simulate this
- effect.</p>
- <p>One of the most prominent case of DeviceInteraction module is to
- test startNotify. If the device volume is above 0, a device beeper is
- played when startNotify is invoked. If the device volume is set to 0
- and vibrator is active, then the device will render a shake-like
- movement. If the vibrator is also off, backlight will be switched on
- for a specified duration.</p>
- <h3>Contact</h3>
- <p>This example demonstrates the usage of pim.contact API. Start by
- getting an Address Book and you can add/update/delete/find contacts in
- that Address Book.</p>
-
- <h3>Filesystem</h3>
-
- <p>Filesystem example showcases the capability of Filesystem API.
- You can traverse the file system hierarchy by clicking through the
- folders or back button. You can also execute copy/paste/delete
- operations by clicking corresponding buttons. In addition, a simple
- editor is provided for you to create/edit text files.</p>
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Debugging with the Tizen Simulator</title>
-</head>
-
-<body>
- <h2>Debugging with the Tizen Simulator</h2>
- More to come...
-</body>
-</html>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html>
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <title>Tizen Simulator Design</title>
-
-</head>
-
-<body>
- <h2>Tizen Web Simulator Design</h2>
- More to come...
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
- <head>
- <title>Tizen API Coverage</title>
- </head>
-
- <body>
- <h2>Tizen API Coverage</h2>
- Below is a summary of the Tizen APIs supported in this release. Some APIs are supported
- with a Javascript backend and others are provided by Google Chrome.
- <h3>Supported Tizen APIs</h3>
- The following APIs are implemented by the simulator in JavaScript.
- <ul>
- <li>Tizen</li>
- <li>Alarm</li>
- <li>Application</li>
- <li>Calendar</li>
- <li>Call</li>
- <li>Contact</li>
- <li>Filesystem</li>
- <li>Geocoder</li>
- <li>LBS</li>
- <li>Media Content</li>
- <li>Messaging</li>
- <li>NFC</li>
- <li>System Information</li>
- <li>Time</li>
- <li>Power</li>
- </ul>
- <h3>Non-supported Tizen APIs</h3>
- The following APIs are not supported by the current version of the simulator. Support for these APIs
- is under development.
- <ul>
- <li>Bluetooth</li>
- </ul>
-
- <h3>W3C/HTML5 Specifications</h3>
- <h4>Widget</h4>
- <ul>
- <li>The config.xml of a widget is parsed by the simulator and the information is shown
- in the "feature configuration" panel.</li>
- </ul>
- <h4>Content (documents, graphics, multimedia)</h4>
- <ul>
- <li>HTML5 audio</li>
- <li>HTML5 video</li>
- <li>HTML5 Forms</li>
- <li>Session History API</li>
- <li>HTML5 2D Canvas</li>
- <li>Inline SVG</li>
- </ul>
- <h4>CSS3</h4>
- <ul>
- <li>CSS3 2D Transforms</li>
- <li>CSS3 3D Transforms</li>
- <li>CSS3 Animations</li>
- <li>CSS3 Transitions</li>
- <li>iframe sandbox attribute</li>
- <li>HTML5 2D Canvas</li>
- <li>CSS3 Colors</li>
- </ul>
- <h4>Device/OS Integration</h4>
- <ul>
- <li>W3C Geolocation API (via Javascript backend)</li>
- <li>Orientation and Acceleration (via Javascript backend)</li>
- <li>Browser onLine State</li>
- <li>W3C Vibration API (via Javascript backend)</li>
- <li>Web Audio</li>
- <li>Web Notifications</li>
- <li>Sensors (via Javascript backend)</li>
- </ul>
- <h4>Network & Communication</h4>
- <ul>
- <li>The WebSocket API</li>
- <li>Web Messaging</li>
- <li>XMLHttpRequest Level 2 (Partial)</li>
- <li>Cross-Origin Resource Sharing (CORS)</li>
- <li>Server-Sent Events</li>
- </ul>
- <h4>Storage</h4>
- <ul>
- <li>Web Storage</li>
- <li>File API</li>
- <li>File API: Directories and System</li>
- <li>File API: Writer</li>
- <li>HTML5 Application Cache</li>
- <li>Web SQL Database</li>
- <li>Indexed DB API</li>
- </ul>
- <h4>Performance</h4>
- <ul>
- <li>Web Workers</li>
- <li>Page Visibility API (via Javascript backend)</li>
- <li>Animation Timing Control</li>
- </ul>
- </body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<base href=".." />
-<title>Using the Simulator with Eclipse</title>
-</head>
-
-<body>
- <h2>Getting started with the Tizen Web Simulator</h2>
-
- <h3>Install Google Chrome</h3>
- <p>The Tizen Web Simulator runs on the Google Chrome browser.
- To use the Tizen Web Simulator you must first download and install Google Chrome on your development platform:
- <a href="http://www.google.com/chrome/">http://www.google.com/chrome/</a>
- </p>
- <h4>Configure Simulator Preferences</h4>
- The Tizen SDK attempts to discover the location of Google Chrome on your system. You may need to set the
- location manually in the Preferences. For details, see <a href="gettingstarted/simulatorpreferences.html">Simulator Preferences</a>.
-
- <h3>Launch your application in the Simulator</h3>
- <p>The web simulator Eclipse plugin is an Eclipse launch configuration type. You can launch
- it by doing one of the following:</p>
- <ul>
- <li>Right-click your web project. Select "Run As->Tizen Web Simulator Application".</li>
- <li>If the simulator has been launched before, click the Run icon in the toolbar or
- from the menu select Run->Run Last Launched (Ctrl+F11).</li>
- <li>For first-time launch, create a run configuration. From the menu, select
- "Run->Run Configurations...". Configure the "Tizen Web Simulator Application" properties and then run it.</li>
- </ul>
- <p>
- <a href="images/simulator_launch.png"><img src="images/simulator_launch.png" style="width:700px"/></a>
- </p>
-
- <p>When started, the simulator loads the file specified in the "Content" field of the config.xml file.
- This is usually index.html.</p>
- <p>The simulator renders your application using the Chrome/Webkit backend. All of the same development
- features of Chrome are available in the simulator, including Web Inspector (press F12 to access).</p>
-
- <p>The advantages of using the Tizen Simulator include:
- <ul>
- <li>Ability to set device screen size and orientation</li>
- <li>Ability to run applications that use the Tizen API</li>
- <li>Ability to send events and messages to your application for debugging purposes.
- These include messages, geolocation data, and sensor input such as accelerometer events.</li>
- </ul>
- </p>
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
- <head>
- <title>Implemented Tizen API</title>
- </head>
-
- <body>
- <h2>Implemented Tizen API</h2>
- In this release, the following Tizen APIs are implemented by the simulator:
- <ul>
- <li>Tizen</li>
- <li>Alarms</li>
- <li>Application</li>
- <li>Calendar</li>
- <li>Call</li>
- <li>Contact</li>
- <li>Filesystem</li>
- <li>Geocoder</li>
- <li>LBS</li>
- <li>Media Content</li>
- <li>Messaging</li>
- <li>NFC</li>
- <li>System Information</li>
- <li>Time</li>
- <li>Power</li>
- <li>W3C Geolocation</li>
- <li>W3C Sensors</li>
- <li>W3C Battery</li>
- <li>W3C Vibration</li>
- <li>W3C Page Visibility</li>
- </ul>
- </body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<base href=".." />
-<title>Tizen Simulator Features</title>
-</head>
-
-<body>
- <h2>Tizen Simulator Features</h2>
-
- <h3>Loading application address bar</h3>
-
- <p>When the simulator is started from the Tizen IDE, the path to
- your application's main content file is loaded into the
- application address bar. You can change which file or project
- is being run by editing this field.</p>
-
- <h3>Basic panel operation</h3>
- <h4>Expand/Collapse</h4>
- <p>Each panel can be opened or closed by clicking the small
- arrow on the left side of the panel bar.</p>
- <h4>Reorder</h4>
- <p>Each panel can be moved and reordered by dragging the drag area
- on the right side of the panel bar.</p>
- <h4>Show/Hide</h4>
- <p>Each panel can be showed or hid by clicking the panel-setting button
- on the right side of the application address bar.</p>
-
- <h2>Tizen Simulator</h2>
-
- <h3>Simulator Panels</h3>
- <p>
- <img src="images/simpanel-resolution-and-orientation.png"
- style="float:right; margin: 0px 20px 0px 20px;" />
- <h4>Resolution and Orientation</h4>
- <p>In this panel you can change the target device you are
- emulating. The drop down box on the top shows current device's
- resolution and all four device resolutions supported by the Tizen
- emulator are also supported by the simulator.
- In addition, you can switch its orientation between
- portrait mode and landscape mode. If your application has
- subscribed to this event, it should receive the event and
- the subscribed callback is invoked.</p>
- <br clear="right" />
- </p>
- <p>
- <img src="images/simpanel-platform-api.png"
- style="float:right; margin: 0px 20px 0px 20px;" />
- <h4>Platform API</h4>
- <p>The platform API panel allows you to select which platform you are on.
- Currently, only the Tizen API is supported.</p>
- <br clear="right" />
- </p>
- <p>
- <img src="images/simpanel-system-summary.png"
- style="float:right; margin: 0px 20px 0px 20px;" />
- <h4>System Summary</h4>
-
- <p>The System Summary panel provides a summary of system
- configuration settings, what device you are simulating, and
- other notes that are of interest in the emulated environment.</p>
- <br clear="right" />
- </p>
- <p>
- <img src="images/simpanel-accelerometer.png"
- style="float:right; margin: 0px 20px 0px 20px;" />
- <h4>Accelerometer</h4>
-
- <p>The accelerometer panel allows you to click and drag with your
- mouse to manipulate the physical position of the device.
- Accelerometer events are sent into the running application, allowing
- you to debug accelerometer change events. A "Shake" button
- simulates a back and forth movement along the X axis.</p>
-
- <br clear="right" />
- </p>
- <p>
- <img src="images/simpanel-messaging.png"
- style="float:right; margin: 0px 20px 0px 20px;" />
- <h4>Messaging</h4>
- <p>The messaging panel enables sending and receiving email, SMS,
- and MMS types of messages.</p>
- <p>SENDING</p>
- <p>This section can be used to test if the application can handle incoming
- messages properly. For example, an application can use the following Tizen API
- to receive an email message:
-
- <p> tizen.messaged.getMessageService (messaging.email, <br \>
- successCallback, errorCallback)</p>
-
- <p>Sending a message with <i>email</i> type from the panel should be
- received by the application.</p>
- <p>You can compose a new message by providing a
- sender's address, message type, and message content. After clicking the
- "Send" button, the application should receive the new message. A default "From"
- is given to all sent messages.</p>
-
- <p><b>NOTE:</b> To simulate the 'sync' scenario, as described in the Tizen Web API documentation,
- email messages sent to an application are intentionally withheld
- until the application invokes 'sync' or 'syncFolders' (INBOX) from the
- email messagingService's MessageStorage.</p>
- <p>SMS and MMS messages are kept synchronized all the time. When an
- application starts, all folders are synchronized.</p>
-
- <p>RECEIVING</p>
- <p>Messages sent from the application will be received and listed in
- the Receiving area of the panel.</p>
-
- <p>Recipients: The recipients field shows all recipients from the application sending
- the message. Multiple recipients are separated by ",". The message field shows message
- contents sent from the applications.</p>
- <br clear="right" />
- </p>
- <p>
- <img src="images/simpanel-geo-location.png"
- style="float:right; margin: 0px 20px 0px 20px;" />
-
- <h4>Geo Location</h4>
-
- <p>The Geo Location panel enables your application to debug APIs
- to retrieve geographical data from the device. The panel
- provides an input interface to configure the geographical data
- being sent from the device. Additionally, a map is shown in
- response to the change of the data so that you can correlate
- geo location data with a real map.</p>
- <br clear="right" />
- </p>
- <p>
- <img src="images/simpanel-time.png"
- style="float:right; margin: 0px 20px 0px 20px;" />
- <h4>Time Zone</h4>
-
- <p>The Time Zone panel displays a timezone which can be
- manipulated for an application to test Time APIs.</p>
-
- <p>You can change current time locale by selecting a different option.</p>
- <br clear="right" />
- </p>
- <p>
- <img src="images/simpanel-feature-configuration.png"
- style="float:right; margin: 0px 20px 0px 20px;" />
- <h4>Feature Configuration</h4>
-
- <p>The Feature Configuration panel displays a graphical
- representation of the config.xml file.</p>
-
- <br clear="right" />
- </p>
- <p>
- <img src="images/simpanel-device-and-network-config.png"
- style="float:right; margin: 0px 20px 0px 20px;" />
- <h4>Device and Network Settings</h4>
-
- <p>Tizen SystemInfo provides various APIs to retrieve device and
- networking information. This panel allows you to specify
- device status and see if the application can retrieve device
- status correctly from the Tizen SystemInfo API. The application can also
- add listeners for system status change notifications.</p>
- <p>In the "Config" section, you can turn on/off vibrator and lock/unlock
- the screen. If something is required, the CPU load can also be manually specified.</p>
- <p>In the "CPU" section, you can manually specify the CPU load.</p>
- <p>In the "Storage" section, the default setting of the STORAGE mode is "INTERNAL".</p>
- <p>In the "Display" section, it shows some information about device status, such as 'Resolution',
- 'DPI', and 'Physical width/height'. In addition, the brightness can also be set according to your
- preference.</p>
- <p>In the "Device" section, more information about device, sunch as 'IMEI', 'Version'.</p>
- <p>In the "Network", "WiFi Network", "Cellurlar Network", and "Ethernet Network" sections, you
- can select various network parameter and settings.</p>
- <p>In the "SIM" section, you can also set 'SIM' informations.</p>
-
-
- <br clear="right" />
- </p>
- <p>
- <img src="images/simpanel-sensors.png"
- style="float:right; margin: 0px 20px 0px 20px;" />
- <h4>Sensors</h4>
-
- <p>The sensors panel provides three slide bars to configure the ambient magnetic field in X, Y and Z.</p>
-
- <br clear="right" />
- </p>
- <p>
- <img src="images/simpanel-call.png"
- style="float:right; margin: 0px 20px 0px 20px;" />
- <h4>Call</h4>
-
- <p>The Call panel provides a control panel for simulating sending and
- receiving calls. These calls can be tracked by CallHistory related
- methods using the Tizen Call APIs.</p>
- <p>You can make a call from "LOCAL PARTY"(simulator) to "REMOTE PARTY"
- or accept/reject a call placed by the "REMOTE PARTY". They can also
- pick a reason to simulate a failed call from the "Reason" drop down
- menu.</p>
- <p>When you clicks "End", the "call" functionality will be closed.</p>
- <br clear="right" />
- </p>
- <p>
- <img src="images/simpanel-battery.png"
- style="float:right; margin: 0px 20px 0px 20px;" />
- <h4>Battery</h4>
-
- <p>The Battery panel allows you to test an application that
- uses the battery API.</p>
- <p>
- "Total time" shows either the time (in minutes) needed to charge the
- battery from empty to full capacity (if "Is Charging" is checked), or
- the time until the battery will be empty (if "Is Charging" is not checked).</p>
- <p>
- "Battery Level" and "Remaining Power" indicates the remaining battery capacity (with percentage
- and in minutes, respectively). For example, if the total time is set into '600 minutes', it means
- that the simulator will take 600 minutes to fully charge the battery from empty to fill. Currently,
- it has been charged to 75.42% capacity and has been charged for 452.52 minutes.</p>
- </p>
- <br>
- <p>
- <img src="images/simpanel-application.png"
- style="float:right; margin: 0px 20px 0px 20px;" />
- <h4>Application</h4>
- <p>The Application panel provides control of install/uninstall/update methods and a list of the applications
- in the simulator.</p>
- <br clear="right" />
- </p>
- <br>
- <p>
- <img src="images/simpanel-nfc.png"
- style="float:right; margin: 0px 20px 0px 20px;" />
- <h4>NFC Adapter</h4>
- <p>The NFC Adapter panel allows you to turn power on/off and poll NFC adapter. It also
- enables sending and receiving NFC tag/peer data.</p>
- <P>Power</p>
- <P>Turn on/off power.</P>
- <P>Polling</p>
- <P>Turn on/off polling.</P>
- <p>NFC data sending and receiving</p>
- <p>At first, select Tag or Peer to attach to, then you can set up more detailed data and the click "Attach"/"Detach"
- button to attach or detach.</p>
- <br clear="right" />
- </p>
- <br>
- <p>
- <img src="images/simpanel-power-mananger.png"
- style="float:right; margin: 0px 20px 0px 20px;" />
- <h4>Power Manager</h4>
-\r
- <p>The Power Manager panel provides a control and display panel for power resource states.</p>
- <p>The RESOURCES section shows the current resource states, according to resource property values
- (CPU.load, DISPLAY.brightness).</p>
- <p>CPU and Display state ranges define, as follows:<br>
- CPU.load [0, 1]<br>
- Low[0, 0.5],<br>
- High (0.5, 1]<br>
- Display.brightness [0, 1]<br>
- Off [0, 0],<br>
- Dim (0, 0.5],<br>
- Normal (0.5, 0.7],<br>
- Bright (0.7, 1]</p>
- <p>Power Management Rules defines power management rules and developers can change these rules.If the state
- rule is "Allow", requesting for this state is granted in an application. Or, if the state rule is "Deny",
- requesting for this state is not granted in an application.</p>
- <br clear="right" />
- </p>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Simulator Preferences</title>
-</head>
-
-<body>
- <h2>Simulator Preferences</h2>
- <p>The Tizen Web Simulator provides a few configuration options, set in
- the Preferences dialog (from the top-menu, select Window, Preferences).
- Select Tizen SDK, Web, Simulator in the left pane.</p>
-
- <a href="../images/simulator_pref.png"><img src="../images/simulator_pref.png" style="width:700px"/></a>
- <h3>Google Chrome Settings</h3>
- <h4>Google Chrome location</h4>
- <p>Enter the full path to the Google Chrome program. When first started, the Tizen SDK will attempt to discover the location. However, it may
- be necessary to enter or modify this value manually.</p>
- <p>In Linux the path is often /opt/google/chrome/google-chrome. <br \>
- In Windows the path is often C:\Users\<user name>\AppData\Local\Google\Chrome\Application\chrome.exe.</p>
-
-
- <h4>Extra parameters</h4>
- The simulator is started with a few default parameters including:
- <table border="0" cellspacing="10" padding="0">
- <tr><td width="10px"> </td><td>--allow-access-from-files</td><td>Allow the simulator Javascript
- APIs to access files on the disk (such as config.xml and the application icon).</td></tr>
- <tr><td width="10px"> </td><td>--disable-web-security</td><td>Allow the simulator to do cross
- domain requests (such as access map location on another server).</td></tr>
- </table>
- If you wish to add any additional startup parameters, enter them here.
- <h4>Profile data location</h4>
- <p>Enter the full directory path for the simulator to store user preferences and web application data.</p>
-
- <p><b>NOTE: </b>Instead of using default value for this parameter, it is HIGHLY recommended that Linux users specify this parameter, since the total length of the directory path in Linux is very limited for this parameter. Possible consequence for using default value is only one application being able to be launched at the same time.</p>
- <p>There is no such restriction in Windows version.</p>
-
- <h3>Simulator Settings</h3>
- <h4>Simulator location</h4>
- <p>Set whether to use the default version of the simulator or another, custom version.</p>
- Internal: Use the simulator that is part of the Tizen SDK <br />
- External: Use a custom build or other simulator version. Enter the full path to the "index.html" file for
- that version of the simulator. </p>
- <h4>Launch simulator in Google Chrome application mode</h4>
- Selecting this option will launch the simulator without the Google URL bar or tabs at the top. It will
- appear as if the simulator is a stand-alone application. It has no effect on simulator features.
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Using the Tizen Simulator by itself</title>
-
-<!--
- <link rel="stylesheet" href="styles/style.css">
- <script type="text/javascript" src="jquery.js"></script>
- <link rel="stylesheet" type="text/css" href="scripts/content.css" />
- -->
-<style type="text/css">
-#code {
- background-color: #EFF3F2;
- border: 1px solid #E0E8E5;
- border-collapse: collapse;
- border-spacing: 0;
- color: #444444;
- font-family: Monaco, "Courier New", Courier, monospace;
- font-size: 100%;
- overflow: auto;
- padding: 1em;
-}
-</style>
-</head>
-
-<body>
-
- <h1>Using the Simulator by itself</h1>
- <div>
-
- <h2>Install Google Chrome (or Chromium)</h2>
- <p>
- The Tizen Simulator runs on the Google Chrome or Chromium browser. To
- use the Tizen Simulator you must first download and install Google
- Chrome on your development platform: <a
- href="http://www.google.com/chrome/">http://www.google.com/chrome/</a>
-
- 1. Use in Eclipse 2. Use as stand-alone
- <h2>Launch web simulator</h2>
- <p>After you install Google Chrome (download from
- www.google.com/chrome/) and Web Simulator to your local host, you can
- launch it and see how it works.</p>
- <b>NOTE : </b>Since Chrome doesn't allow new windows bringing its own
- startup options after chrome starts, be sure to close all Chrome
- instances and start Chrome manually. There a few command line switches
- that must be included to grant Web Simulator local file access and to
- achieve optimized visual effects. They are
- <ul>
-
- <p></p>
- <li>--allow-file-access-from-files<br> <i>By default,
- file:// URIs cannot read other file:// URIs. This is an override
- for developers who need the old behavior for testing.</i></li>
- <p></p>
- <p></p>
- <li>--disable-web-security<br> <i>Don't enforce the
- same-origin policy. (Used by people testing their sites.)</i></li>
- <p></p>
- <p></p>
- <li>--start-maximized<br> <i>Start the Web Simulator
- maximized for best effect</i></li>
-
- <p></p>
- <li>--app=<file:///my/path/to/Ripple-UI/pkg/web/index.html><br>
- <i>Runs Web Simulator in "app mode": with no browser toolbars.</i></li>
- <p></p>
- </ul>
-
- Other useful switches are:
- <ul>
- <li>--user-data-dir<br> <i>Specifies the directory that
- user data is kept in. Defaults to ~/.config/google-chrome</i>
-
- </li>
- </ul>
-
- <h3>Mac</h3>
- <ul>
- <li>Make sure your default browser is Google Chrome, not Safari.</li>
- <li>Open the terminal and open the Google Chrome with file
- access: The syntax is<br>
- <p>open <Path to Chrome.app> --args
- --allow-file-access-from-files --disable-web-security
- --start-maximized --app=<uri to Web Simulator>
- [--user-data-dir=<path to user data directory>]</p>
- </li>
-
- </ul>
- <div id="code">
- <pre>tizen$ open /Applications/Google\ Chrome.app --args --allow-file-access-from-files --disable-web-security --start-maximized --app=file:///Users/tizen/Desktop/web/index.html --user-data-dir=/Users/tizen/simulator-profile-data/</pre>
- </div>
-
- <h3>Windows</h3>
- <ul>
- <li>lanuch "cmd.exe" and open the Google Chrome with file
- access: The syntax is<br>
-
- <p><path to chrome.exe> --allow-file-access-from-files
- --disable-web-security --start-maximized --app=<uri to Web
- Simulator> [--user-data-dir=<path to user data directory>]</p>
- </li>
- </ul>
- <div id="code">
- <pre>C:\>C:\app\Google\Chrome\Application\chrome.exe --allow-file-access-from-files --disable-web-security --start-maximized --app=file:///C://tizen/web/index.html --user-data-dir=C://tizen/simulator-profile-data/</pre>
-
- </div>
-
- <h3>Linux</h3>
- <ul>
- <li>open a terminal and open the Google Chrome with file access:
- The syntax is<br>
- <p>$ <path to google-chrome> --allow-file-access-from-files
- --disable-web-security --start-maximized --app=<uri to Web
- Simulator> [--user-data-dir=<path to user data directory>]</p>
- </li>
-
- </ul>
- <div id="code">
- <pre>$ google-chrome --allow-file-access-from-files --disable-web-security --start-maximized --app=file:///home/tizen/web/index.html --user-data-dir=/home/tizen/simulator-profile-data/</pre>
- </div>
-
- </div>
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html>
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <title>Troubleshooting</title>
-</head>
-
-<body>
-<h2>Troubleshooting</h2>
-Enter details here...
-</body>
-</html>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Known Issues</title>
-<style type="text/css">
-#code {
- background-color: #EFF3F2;
- border: 1px solid #E0E8E5;
- border-collapse: collapse;
- border-spacing: 0;
- color: #444444;
- font-family: Monaco, "Courier New", Courier, monospace;
- font-size: 100%;
- overflow: auto;
- padding: 1em;
-}
-</style>
-</head>
-
-<body>
- <h2>Known Issues</h2>
- <p>There are a few known issues when running application in Web
- Simulator, and they are listed below and we are wokring on either a
- better solution or workarounds</p>
-
- <ul>
- <li>Application will be loaded twice during refresh. <br><br /></li>
-
- <li>Using instanceof to check if the return restult is Array or Date
- wouldn't work.<br /> workaround: use the following snippet to
- type-check Date and Array.
- <div id="code">
-<pre>
-isValidDate = function (d) {
- if (Object.prototype.toString.call(d) !== "[object Date]")
- return false;
- return !isNaN(d.getTime());
-}
-
-isValidArray = function (a) {
- return (Object.prototype.toString.call(a) === "[object Array]");
-}
-</pre>
- </div>
- <p />
- </li>
-
- </ul>
- <div></div>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <base href="." />
- <title>Tizen Web Simulator</title>
- </head>
-
- <body>
- <h2>Tizen Web Simulator</h2>
- <a href="images/simulator1.png"><img src="images/simulator1.png" style="float:right; margin: 0px 20px 20px 20px; width:500px; " /></a>
- <br>
- The Tizen Web Simulator is a light-weight tool for developing mobile web applications.
-
- <h3>Features:</h3>
- <ul>
- <li>Supports running and debugging modern HTML5 web applications</li>
- <li>Simulates Tizen Web APIs via JavaScript backend</li>
- <li>Includes configuration panels for sending the application events and messages to debug features
- such as Geo Location, Accelerometer, Messaging, and more.</li>
- <li>Runs on Google Chrome</li>
- </ul>
- <p>For detailed feature descriptions and screenshots, see
- <a href="gettingstarted/simulatorfeatures.html">Simulator Features</a>.
- </p>
-
- <!--
- <h4>Contents</h4>
- <ul>
- <li><a href="#gettingstarted">Getting Started</a></li>
- <li><a href="appdemos.html">Tizen API Demos</a></li>
- <li><a href="debugging.html">Debugging with the Simulator</a></li>
- <li><a href="design.html">Simulator Design</a></li>
- <li><a href="knownissues.html">Known Issues and Release Notes</a></li>
- </ul>
- -->
-
- <p>The Tizen Web Simulator is based on the <a href="https://github.com/blackberry-webworks/Ripple-UI">Ripple-UI Framework</a> and is licensed under Apache Software License v.2.0.</p>
- </body>
-</html>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8"?>
-<?eclipse version="3.4"?>
-<plugin>
- <extension
- point="org.eclipse.help.toc">
- <toc
- file="toc.xml"
- primary="true">
- </toc>
- <toc
- file="tocgettingstarted.xml">
- </toc>
- </extension>
-
-</plugin>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-
-<toc label="Tizen Web Simulator Guide" topic="html/toc.html">
- <topic href="html/toc.html" label="Overview">
- </topic>
- <topic label="Getting Started">
- <anchor id="gettingstarted"/>
- </topic>
-</toc>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-
-<toc label="Getting Started" link_to="toc.xml#gettingstarted">
- <topic label="Starting the Simulator" href="html/gettingstarted/configandstartup.html" />
- <topic href="html/gettingstarted/simulatorfeatures.html" label="Simulator Features" />
- <topic href="html/gettingstarted/TizenAPI.html" label="Tizen API Coverage" />
- <topic href="html/gettingstarted/simulatorpreferences.html" label="Simulator Preferences" />
-</toc>
projects / sdk / ide / websimulator-eplugin.git / commitdiff
