WebOS Internals - User contributions [en]

User talk:Eain

2009-07-29T20:06:35Z

Eain:

Hey your edit doesn't work because the straight linux pkg doesn't have the required install file or else you would have to use make. so i fixed it

[[User:Epyon22|Epyon22]] 19:49, 29 July 2009 (UTC)Epyon22

Whoops! Sorry about that!

Patch Browser Global Search Addons

2009-07-29T19:35:41Z

Eain: added clarification at the end to include reboot mention

For this example I am going to add a reddit.com option to the global search. Feel free to use whatever site you want -- just make sure to change the names accordingly :)

'''NOTE''' Make sure you put all your addons BEFORE twitter, if they are after it will not work properly!!

'''0. [[Portal:Accessing_Linux|Access Linux]], then enable write access:'''

<pre><nowiki>mount -o remount,rw /</nowiki></pre>

'''1. Edit the following file:'''
/usr/lib/luna/system/luna-applauncher/app/controllers/global-search-assistant.js

Find this code and modify it as such (be sure to use the correct search link):

<pre><nowiki>
this.URLs = {
'google':$L("www.google.com/m/search?client=ms-palm-webOS&channel=iss&q="),
'wikipedia':$L("http://en.wikipedia.org/wiki/Special:Search/"),
'reddit': $L("http://www.reddit.com/search?q="),
'twitter': $L("http://search.twitter.com/search?q=")

};
</nowiki></pre>

Be sure to note the comma at the end of the line beginning with 'twitter'. URL codes for additional search engines found [[global-search-addons-collection | here]].

'''2. In the same file -- you must also add "$('reddit').removeClassName('selected');" to this function:'''

<pre><nowiki>
clearSearch: function() {
if (this.delayShowAppsConatactsTimeout)
window.clearTimeout(this.delayShowAppsConatactsTimeout);
this.currentFilter = "";
this.searchExplicitlyExpanded = false;
this.noMatches = false;
this.hideContactsDiv();
this.launcherIconsDiv.hide();
this.dialDiv.hide();
this.numberDiv.hide();
this.webDrawer.showWeb = false ;
this.controller.modelChanged(this.webDrawer);
this.expandedSearchDrawer.showExpanded = false;
this.controller.modelChanged(this.expandedSearchDrawer);
this.searchApps.clear();
$('google').removeClassName('selected');
$('map').removeClassName('selected');
$('wikipedia').removeClassName('selected');
$('reddit').removeClassName('selected');
$('twitter').removeClassName('selected');
$('web').removeClassName('selected');
if (this.controller.get('searchterm')) {
this.controller.get('searchterm').mojo.setText("");
this.controller.get('searchterm').mojo.blur();
}
this.gpsInfo = undefined;
},
</nowiki></pre>

'''3. Edit the following file:'''
/usr/lib/luna/system/luna-applauncher/app/views/global-search/expanded-searches-div.html

Modify the code to add a new div:
<pre><nowiki>
<div id='expanded_searches_drawer' x-mojo-element="Drawer">
<div class="palm-row" id="google" name="search-identifier" x-mojo-tap-highlight="persistent">
<div class="palm-row-wrapper">
<div class="search-google"></div>
</div>
</div>
<div class="palm-row" id="map" name="search-identifier" x-mojo-tap-highlight="persistent">
<div class="palm-row-wrapper">
<div class="search-maps"></div>
</div>
</div>
<div class="palm-row" id="wikipedia" name="search-identifier" x-mojo-tap-highlight="persistent">
<div class="palm-row-wrapper">
<div class="search-wikipedia"></div>
</div>
</div>
<div class="palm-row" id="reddit" name="search-identifier" x-mojo-tap-highlight="persistent">
<div class="palm-row-wrapper">
<div class="search-reddit"></div>
</div>
</div>
<div class="palm-row" id="twitter" name="search-identifier" x-mojo-tap-highlight="persistent">
<div class="palm-row-wrapper">
<div class="search-twitter"></div>
</div>
</div>
<div id='web_drawer' x-mojo-element="Drawer">
<div class="palm-row last" id="web" name="search-identifier" x-mojo-tap-highlight="persistent">
<div class="palm-row-wrapper">
<div class="title search-url truncating-text" id="webtext">#{filterText}</div>
</div>
</div>
</div>
</div>
</nowiki></pre>

'''4. Edit the following file:'''
/usr/lib/luna/system/luna-applauncher/stylesheets/global-search.css

Add the following class to the css file:
<pre><nowiki>
.palm-group.search .search-reddit {
width: 100%;
height: 52px;
background: url(../images/search-reddit.png) center center no-repeat;
}
</nowiki></pre>

'''5. Finally, you need to create a png image (ideally 200x44, but any size up to 300x44 should work) with a transparent background and the logo of your choice. Add it to the path below making sure the name matches the css class, reboot, and enjoy!'''
/usr/lib/luna/system/luna-applauncher/images

'''6. Remount file system as read-only:'''

<pre><nowiki>mount -o remount,ro / </nowiki></pre>

'''7. Disconnect and reboot your Pre with Orange-Sym-R

Here is the image I used:

[[Image:Reddit.png]]

(See [[Global Search Addons Collection | all available 'universal search' images and search links]].)

And here is the end result!

[[Image:global-search.jpg]]

Next steps

2009-07-28T23:54:35Z

Eain: /* Finishing */

''The old, manual setup of Optware and users can be found [[Setting_up_optware_feed | here]].''

=Automated Setup of Optware, Users and Access=
The webOS community asks that users who have obtained access to the Linux subsystem install a standard set of software to ensure everyone has the necessary tools in place to use the resources the community is providing.

In particular, this includes the Optware package manager. Palm's webOS uses the ''ipkg'' package manager internally. The community has a version of ''ipkg'' called ''ipkg-opt'' which accesses the Optware library of over 1300 Linux programs available for installation on the Pre.

Palm has indicated that they have no intention of using the /opt directory, so we direct our installs to /opt/bin rather than /bin to avoid being overwritten by future Palm software upgrades.

In addition, the standard package creates a non-root user, installs ''sudo'', and includes an SSH program (''dropbear'') and an sftp program.

For your convenience, we've packaged all this up into a simple script.

==Optware Setup==

'''If you're attempting to install these packages to your emulator, you must first add sufficient space by [[Adding_Disks_to_the_Emulator|enabling a virtual disk]].'''

After completing the process of obtaining access to your Pre, do the following:

'''Type each line exactly as it appears. Copying and pasting is probably a good idea.'''

''Note to Windows Putty users: To paste in putty, simply right-click and the program pastes into the terminal whatever you have copied to the clipboard.''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/optware-bootstrap.sh
sh optware-bootstrap.sh
</source></div>

Follow the on-screen instructions.

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh]

==Quilt setup==

Optionally, you can then install the ''quilt'' patch manager which allows multiple-file patches. (Yes, the pun was intentional. Quilt manages multiple patches.) This installation process has also been packaged into a simple script. It will install quilt, and all of its dependencies, and create a local clone of the WebOS-Internals patch repository. [[Applying_Patches | Applying Patches]] provides a more thorough guide on the use of quilt.

'''Again, type each line exactly as it appears. Copying and pasting is probably a good idea.'''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/quilt-bootstrap.sh
sh quilt-bootstrap.sh
</source></div>

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh]

==Finishing==

To finish off, turn Developer Mode back to "Off" (which will reboot your Pre).

Once you are finished, you may SSH into your Pre with an SSH client like [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty]:
*Find your IP address with [http://checkmyip.com/ CheckMyIP.com]
*SSH to that IP address on port 222
**If you're doing this over EVDO, there may be a lot of latency. Be patient.
*Log in with the username and password you created during the Optware installation
**Many operations cannot be carried out with the permissions of that username. You'll need to [[Basic_Linux_Use#sudo|sudo]] those operations with the new username's password

Next steps

2009-07-28T23:51:20Z

Eain: Changed font size to fit properly

Next steps

2009-07-28T23:47:48Z

Eain: Added formatting, finishing steps, clarified SSHing in

''The old, manual setup of Optware and users can be found [[Setting_up_optware_feed | here]].''

=Automated Setup of Optware, Users and Access=
The webOS community asks that users who have obtained access to the Linux subsystem install a standard set of software to ensure everyone has the necessary tools in place to use the resources the community is providing.

In particular, this includes the Optware package manager. Palm's webOS uses the ''ipkg'' package manager internally. The community has a version of ''ipkg'' called ''ipkg-opt'' which accesses the Optware library of over 1300 Linux programs available for installation on the Pre.

Palm has indicated that they have no intention of using the /opt directory, so we direct our installs to /opt/bin rather than /bin to avoid being overwritten by future Palm software upgrades.

In addition, the standard package creates a non-root user, installs ''sudo'', and includes an SSH program (''dropbear'') and an sftp program.

For your convenience, we've packaged all this up into a simple script.

==Optware Setup==

'''If you're attempting to install these packages to your emulator, you must first add sufficient space by [[Adding_Disks_to_the_Emulator|enabling a virtual disk]].'''

After completing the process of obtaining access to your Pre, do the following:

'''Type each line exactly as it appears. Copying and pasting is probably a good idea.'''

''Note to Windows Putty users: To paste in putty, simply right-click and the program pastes into the terminal whatever you have copied to the clipboard.''

<div style="font-size:140%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/optware-bootstrap.sh
sh optware-bootstrap.sh
</source></div>

Follow the on-screen instructions.

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh]

==Quilt setup==

Optionally, you can then install the ''quilt'' patch manager which allows multiple-file patches. (Yes, the pun was intentional. Quilt manages multiple patches.) This installation process has also been packaged into a simple script. It will install quilt, and all of its dependencies, and create a local clone of the WebOS-Internals patch repository. [[Applying_Patches | Applying Patches]] provides a more thorough guide on the use of quilt.

'''Again, type each line exactly as it appears. Copying and pasting is probably a good idea.'''

<div style="font-size:140%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/quilt-bootstrap.sh
sh quilt-bootstrap.sh
</source></div>

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh]

==Finishing==

To finish off, turn Developer Mode back to "Off" (which will reboot your Pre).

Once you are finished, you may SSH into your Pre with an SSH client like [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty]:
*Find your IP address with [http://checkmyip.com/ CheckMyIP.com]
*SSH to that IP address on port 222
**If you're doing this over EVDO, there may be a lot of latency. Be patient.
*Log in with the username and password you created during the Optware installation
**Many operations cannot be carried out with the permissions of that username. You'll need to [[Basic_Linux_Use#sudo|sudo]] those operations

Basic Linux Use

2009-07-28T23:38:53Z

Eain: /* sudo */

[[Image:Tux-pre.jpg|right]]

Linux at its core runs a command line shell similar to that of DOS and the Windows Command Prompt, and like the Windows/DOS Command Line, you can seriously harm your OS if you just go poking around without any idea as to what it is you're doing. The commands and programs below are the most used commands and programs throughout the tutorials on this site. Please bear in mind that Linux commands and file names are case sensitive.

== Command Line Commands ==
=== cd ===
'''Dos Eqiv:''' cd
Used to change directories. To go up a level use '..'

''Ex: "cd hello"'' would move one directory down to /hello/

''Ex: "cd .."'' would take you to the directory that is parent to your Present Working Directory. If you are in /usr/lib, this command will take you to /usr

=== pwd ===
'''Dos Eqiv:''' cd (with no parameters)
Used to show the Present Working Directory

''Ex: "pwd"'' would display your current location in the filesystem tree

=== ls ===
'''Dos Eqiv:''' dir
Used to list the contents of a directory.

''Ex: "ls"'' would list the contents of where you currently are.
''Ex: "ls /hello/"'' would list the contents of /hello/ no matter where you are.

=== cp ===
'''Dos Eqiv:''' copy
Used to copy files from one spot to another. Adding the -i flag will cause cp to ask if you want to overwrite the destination file if it already exists. Use of this flag is recommended to prevent accidental overwriting of previous backups.

''Ex: "cp -i test test.bak"'' would copy test to test.bak

''Ex: "cp -i test /var/test.bak"'' would copy test to /var/test.bak

=== mv ===
'''Dos Eqiv:''' move / rename
Used to move or rename files from one spot to another.

''Ex: "mv oldname.file newname.file"'' will rename the file oldname.file to newname.file

''Ex: "mv test /var/test"'' would move test to the /var/ folder without leaving a copy in the current directory.

=== rm ===
'''Dos Eqiv:''' del
Used to delete files and directories. Must use the -r option to delete directories.

''Ex: "rm test.file"'' would delete the test.file

''Ex: "rm test*"'' would delete all files whose name starts with 'test'

''Ex: "rm /test -r"'' would delete the folder named 'test'

'''Note:''' Adding '''-rf''' or '''-Rf''' to the rm command will "force" deletion of files, folders, and folder contents without confirmation. Please be very mindful of any instructions that suggest doing this, and '''don't rm -Rf anything unless you know what you're doing.'''

=== sudo ===
Many functions cannot be carried out unless the logged-in username has proper permissions. sudo will run a command or series of commands as root, although it may require a password.

''Ex: "sudo mount -o remount,rw /"'' would mount the file system as read-write (needed for many changes, and needs root permissions).

''Ex: "sudo vi <locked filename>"'' would edit a file whose permissions are locked-down for the current user.

== Editing Files using vi ==

The Pre's Linux operating system comes installed with a text editing program called vi. It's a very simple to use text editor.

To start with your start vi using the command 'vi' followed by the file you would like to edit.

''Ex: "vi test.html"''

''Ex: "vi /var/test.html"''

Once you start vi you will notice that you can't just start typing and have it show up in the file. vi has two modes, an Editing and a Command mode. vi always starts in the command mode. The keys you can use to switch between the two modes are show below:

===Switch to Editing Mode===
'''i''' Insert text before the cursor
'''I''' Insert text at the beginning of the current line
'''a''' Append text after the cursor
'''A''' Append text to the end of the current line
'''o''' Append text to new line after current line
'''O''' Append text to new line above current line
'''cw''' Delete from the cursor to the end of the current word and begin inserting text
'''c$''' Delete from the cursor to the end of the current line and begin appending text

===Switch back to Command Mode===
'''esc'''

Command mode is where you can chose to save a file or close it without saving along with some other various commands that are listed below. You almost always start a command in vi by using the ':' symbol, though sometimes a single character will also perform an action while in command mode.

===Saving and Quitting===
''':q''' Quit (only use if no changes have been made since the last save)
''':q!''' Quit without saving changes
''':w''' Save the file without quitting vi
''':wq''' Save the file and then quits vi

===Moving Around Within the File===
''':1''' Move to the first line. Replace 1 with any line number to jump to that line.
'''G''' Move to the last line.
'''0''' Move to the beginning of the current line.
'''$''' Move to the end of the current line.

===Special Edit Commands (use while in command mode)===
'''yy''' ''Yank'' the current line into the buffer (similar to Windows' ''copy'') or yank X number of lines ('4yy' will yank 4 lines)
'''p''' Paste the contents of the buffer below the current line (similar to Windows' ''paste'')
'''P''' Paste the contents of the buffer above the current line (similar to Windows' ''paste'')
'''dd''' Delete the current line, or delete X number of lines ('4dd' will delete 4 lines)
'''d$''' Delete everything from the cursor to the end of the current line
'''dw''' Delete everything from the cursor to the end of the current word
'''x''' Delete the character under the cursor

===Search for Text Within the File===
'''/term''' Search forward for ''term''
'''?term''' Search backward for ''term''
'''n''' Go to the next instance, if any
'''N''' Go to the previous instance, if any

''Examples:''

''/hello world'' Search forward in the file, looking for the phrase 'hello world'

''?hello world'' Search backward in the file, looking for the phrase 'hello world'

Note: For a less powerful but easier to use text editor, install nano from the [[adding-the-ipkg-repository|optware repository]]

Basic Linux Use

2009-07-28T23:37:58Z

Eain: /* Command Line Commands */

[[Image:Tux-pre.jpg|right]]

Linux at its core runs a command line shell similar to that of DOS and the Windows Command Prompt, and like the Windows/DOS Command Line, you can seriously harm your OS if you just go poking around without any idea as to what it is you're doing. The commands and programs below are the most used commands and programs throughout the tutorials on this site. Please bear in mind that Linux commands and file names are case sensitive.

== Command Line Commands ==
=== cd ===
'''Dos Eqiv:''' cd
Used to change directories. To go up a level use '..'

''Ex: "cd hello"'' would move one directory down to /hello/

''Ex: "cd .."'' would take you to the directory that is parent to your Present Working Directory. If you are in /usr/lib, this command will take you to /usr

=== pwd ===
'''Dos Eqiv:''' cd (with no parameters)
Used to show the Present Working Directory

''Ex: "pwd"'' would display your current location in the filesystem tree

=== ls ===
'''Dos Eqiv:''' dir
Used to list the contents of a directory.

''Ex: "ls"'' would list the contents of where you currently are.
''Ex: "ls /hello/"'' would list the contents of /hello/ no matter where you are.

=== cp ===
'''Dos Eqiv:''' copy
Used to copy files from one spot to another. Adding the -i flag will cause cp to ask if you want to overwrite the destination file if it already exists. Use of this flag is recommended to prevent accidental overwriting of previous backups.

''Ex: "cp -i test test.bak"'' would copy test to test.bak

''Ex: "cp -i test /var/test.bak"'' would copy test to /var/test.bak

=== mv ===
'''Dos Eqiv:''' move / rename
Used to move or rename files from one spot to another.

''Ex: "mv oldname.file newname.file"'' will rename the file oldname.file to newname.file

''Ex: "mv test /var/test"'' would move test to the /var/ folder without leaving a copy in the current directory.

=== rm ===
'''Dos Eqiv:''' del
Used to delete files and directories. Must use the -r option to delete directories.

''Ex: "rm test.file"'' would delete the test.file

''Ex: "rm test*"'' would delete all files whose name starts with 'test'

''Ex: "rm /test -r"'' would delete the folder named 'test'

'''Note:''' Adding '''-rf''' or '''-Rf''' to the rm command will "force" deletion of files, folders, and folder contents without confirmation. Please be very mindful of any instructions that suggest doing this, and '''don't rm -Rf anything unless you know what you're doing.'''

=== sudo ===
Many functions cannot be carried out unless the logged-in username has proper permissions. sudo will run a command or series of commands as root, although it may require a password.

''Ex: "sudo mount -o remount,rw /"'' would mount the file system as read-write (needed for many changes, and needs root permissions)

== Editing Files using vi ==

The Pre's Linux operating system comes installed with a text editing program called vi. It's a very simple to use text editor.

To start with your start vi using the command 'vi' followed by the file you would like to edit.

''Ex: "vi test.html"''

''Ex: "vi /var/test.html"''

Once you start vi you will notice that you can't just start typing and have it show up in the file. vi has two modes, an Editing and a Command mode. vi always starts in the command mode. The keys you can use to switch between the two modes are show below:

===Switch to Editing Mode===
'''i''' Insert text before the cursor
'''I''' Insert text at the beginning of the current line
'''a''' Append text after the cursor
'''A''' Append text to the end of the current line
'''o''' Append text to new line after current line
'''O''' Append text to new line above current line
'''cw''' Delete from the cursor to the end of the current word and begin inserting text
'''c$''' Delete from the cursor to the end of the current line and begin appending text

===Switch back to Command Mode===
'''esc'''

Command mode is where you can chose to save a file or close it without saving along with some other various commands that are listed below. You almost always start a command in vi by using the ':' symbol, though sometimes a single character will also perform an action while in command mode.

===Saving and Quitting===
''':q''' Quit (only use if no changes have been made since the last save)
''':q!''' Quit without saving changes
''':w''' Save the file without quitting vi
''':wq''' Save the file and then quits vi

===Moving Around Within the File===
''':1''' Move to the first line. Replace 1 with any line number to jump to that line.
'''G''' Move to the last line.
'''0''' Move to the beginning of the current line.
'''$''' Move to the end of the current line.

===Special Edit Commands (use while in command mode)===
'''yy''' ''Yank'' the current line into the buffer (similar to Windows' ''copy'') or yank X number of lines ('4yy' will yank 4 lines)
'''p''' Paste the contents of the buffer below the current line (similar to Windows' ''paste'')
'''P''' Paste the contents of the buffer above the current line (similar to Windows' ''paste'')
'''dd''' Delete the current line, or delete X number of lines ('4dd' will delete 4 lines)
'''d$''' Delete everything from the cursor to the end of the current line
'''dw''' Delete everything from the cursor to the end of the current word
'''x''' Delete the character under the cursor

===Search for Text Within the File===
'''/term''' Search forward for ''term''
'''?term''' Search backward for ''term''
'''n''' Go to the next instance, if any
'''N''' Go to the previous instance, if any

''Examples:''

''/hello world'' Search forward in the file, looking for the phrase 'hello world'

''?hello world'' Search backward in the file, looking for the phrase 'hello world'

Note: For a less powerful but easier to use text editor, install nano from the [[adding-the-ipkg-repository|optware repository]]

HamachiVPN

2009-07-27T20:42:50Z

Eain: /* Hamachi VPN for Palm Pre */

= Hamachi VPN for Palm Pre =

This document assumes you're familiar with the Hamachi VPN, specifically the linux version. It is geared towards a person wanting to "get it working" on the Pre. If you're not familiar, there are endless Googlable web pages that describe running Hamachi on desktop linux systems you can use for reference.

Become root:

<source lang="text">
sudo su
</source>

Make the filesystem writable:

<source lang="text">
mount -o remount,rw /
</source>

Download the hamachi binary to your pre via wget:
<source lang="text">
cd /opt/share
wget http://files.hamachi.cc/linux/hamachi-0.9.9.9-20-lnx.tar.gz
</source>

Unpack the archive:
<source lang="text">
tar zxvf hamachi-0.9.9.9-20-lnx.tar.gz
cd hamachi-0.9.9.9-20-lnx
</source>

Hamachi depends on libcrypto.so.0.9.7. The Palm Pre has libcrypto.so.0.9.8 installed. I made a symlink, and it worked. So...
<source lang="text">
ln -s /usr/lib/libcrypto.so.0.9.8 /usr/lib/libcrypto.so.0.9.7
</source>

Edit the "install" script using your favorite editor (like vi) to change the installation locations.
Also fix line 7 or you'll get an error.

I changed it to:

<source lang="text">
HAMACHI_DST=/opt/bin
TUNCFG_DST=/opt/sbin

echo
echo Copying hamachi into $HAMACHI_DST ..
</source>

Then follow the instructions in the README under Quick Start, but basically:

<source lang="text">
./install
/opt/sbin/tuncfg
hamachi-init
hamachi start
hamachi login
hamachi set-nick <your nickname>
hamachi join <network>
hamachi go-online
</source>

== Hint ==

If you use Hamachi to connect to web services running on your machines at home or elsewhere, you might make your life easier by adding some entries to the /etc/hosts file. Then you can access your servers by name instead of having to use the Hamachi 5.x.x.x IP addresses.

A simple sample entry in /etc/hosts which would allow you to access your server "beaker" at 5.1.2.3 would be:
(Add your servers below the "castle" line.)
<source lang="text">
127.0.0.1 localhost.localdomain localhost
127.0.0.1 castle
5.1.2.3 beaker
</source>

When done, make the filesystem read-only again:
<source lang="text">
mount -o remount,ro /
</source>

== Ping Test ==

When you've got hamachi up, you can try pinging one of your servers.
<source lang="text">
root@castle:/var/home/root# ping beaker
PING beaker (5.1.2.3): 56 data bytes
64 bytes from 5.1.2.3: seq=0 ttl=128 time=5.493 ms
64 bytes from 5.1.2.3: seq=1 ttl=128 time=32.257 ms
64 bytes from 5.1.2.3: seq=2 ttl=128 time=56.976 ms
64 bytes from 5.1.2.3: seq=3 ttl=128 time=74.249 ms
</source>

== Sleep/Wake and Battery Impact ==
On first testing:
* When the device went to sleep, the VPN went down.
* When the device woke up, the VPN came back up and was pingable again.

This morning, while at my workstation, and with the Pre idle in my pocket, I noticed my Pre was available/pingable on Hamachi. I am not totally sure of what the long-term battery impact might be of running Hamachi on the Pre. I'm not yet sure if it keeps the device "awake" all the time, which clearly would drain the battery. I have push GMail IMAP going, so I assume there is some kind of connection either being periodically established or constantly maintained. But I don't know enough about the networking aspects to determine at this time whether running Hamachi all the time will negatively impact the battery. Feel free to message me if you learn anything.

== Upstart script ==
This script will start Hamachi up after a reboot.

Place the following script in /etc/event.d/hamachi

<source lang="text">
description "Hamachi VPN for WebOS"
version 1.0

# don't start until the WebOS finishes it's normal boot
# that way no delay is added to the GUI startup
start on stopped finish
stop on runlevel [!2]

console output

script
/opt/bin/hamachi -c /var/home/root/.hamachi start 2>&1 /var/home/root/hamachi.log
end script

pre-start script
/opt/sbin/tuncfg
end script
</source>

HamachiVPN

2009-07-27T20:37:45Z

Eain: /* Hamachi VPN for Palm Pre */ fixed typo, updated URL

= Hamachi VPN for Palm Pre =

This document assumes you're familiar with the Hamachi VPN, specifically the linux version. It is geared towards a person wanting to "get it working" on the Pre. If you're not familiar, there are endless Googlable web pages that describe running Hamachi on desktop linux systems you can use for reference.

Become root:

<source lang="text">
sudo su
</source>

Make the filesystem writable:

<source lang="text">
mount -o remount,rw /
</source>

Download the hamachi binary to your pre via wget:
<source lang="text">
cd /opt/share
wget http://files.hamachi.cc/linux/hamachi-0.9.9.9-20-lnx.tar.gz
</source>

Unpack the archive:
<source lang="text">
tar zxvf hamachi-0.9.9.9-20-lnx-n770.tar.gz
cd hamachi-n770-0.9.9.9-20
</source>

Hamachi depends on libcrypto.so.0.9.7. The Palm Pre has libcrypto.so.0.9.8 installed. I made a symlink, and it worked. So...
<source lang="text">
ln -s /usr/lib/libcrypto.so.0.9.8 /usr/lib/libcrypto.so.0.9.7
</source>

Edit the "install" script using your favorite editor (like vi) to change the installation locations.
Also fix line 7 or you'll get an error.

I changed it to:

<source lang="text">
HAMACHI_DST=/opt/bin
TUNCFG_DST=/opt/sbin

echo
echo Copying hamachi into $HAMACHI_DST ..
</source>

Then follow the instructions in the README under Quick Start, but basically:

<source lang="text">
./install
/opt/sbin/tuncfg
hamachi-init
hamachi start
hamachi login
hamachi set-nick <your nickname>
hamachi join <network>
hamachi go-online
</source>

== Hint ==

If you use Hamachi to connect to web services running on your machines at home or elsewhere, you might make your life easier by adding some entries to the /etc/hosts file. Then you can access your servers by name instead of having to use the Hamachi 5.x.x.x IP addresses.

A simple sample entry in /etc/hosts which would allow you to access your server "beaker" at 5.1.2.3 would be:
(Add your servers below the "castle" line.)
<source lang="text">
127.0.0.1 localhost.localdomain localhost
127.0.0.1 castle
5.1.2.3 beaker
</source>

When done, make the filesystem read-only again:
<source lang="text">
mount -o remount,ro /
</source>

== Ping Test ==

When you've got hamachi up, you can try pinging one of your servers.
<source lang="text">
root@castle:/var/home/root# ping beaker
PING beaker (5.1.2.3): 56 data bytes
64 bytes from 5.1.2.3: seq=0 ttl=128 time=5.493 ms
64 bytes from 5.1.2.3: seq=1 ttl=128 time=32.257 ms
64 bytes from 5.1.2.3: seq=2 ttl=128 time=56.976 ms
64 bytes from 5.1.2.3: seq=3 ttl=128 time=74.249 ms
</source>

== Sleep/Wake and Battery Impact ==
On first testing:
* When the device went to sleep, the VPN went down.
* When the device woke up, the VPN came back up and was pingable again.

This morning, while at my workstation, and with the Pre idle in my pocket, I noticed my Pre was available/pingable on Hamachi. I am not totally sure of what the long-term battery impact might be of running Hamachi on the Pre. I'm not yet sure if it keeps the device "awake" all the time, which clearly would drain the battery. I have push GMail IMAP going, so I assume there is some kind of connection either being periodically established or constantly maintained. But I don't know enough about the networking aspects to determine at this time whether running Hamachi all the time will negatively impact the battery. Feel free to message me if you learn anything.

== Upstart script ==
This script will start Hamachi up after a reboot.

Place the following script in /etc/event.d/hamachi

<source lang="text">
description "Hamachi VPN for WebOS"
version 1.0

# don't start until the WebOS finishes it's normal boot
# that way no delay is added to the GUI startup
start on stopped finish
stop on runlevel [!2]

console output

script
/opt/bin/hamachi -c /var/home/root/.hamachi start 2>&1 /var/home/root/hamachi.log
end script

pre-start script
/opt/sbin/tuncfg
end script
</source>

Accessing Linux Using Novaterm

2009-07-27T19:23:35Z

Eain: Added clarification, removed "rooted"s.

# Download the Palm sdk from http://developer.palm.com and run it.
# Click through the installer.
#* If you are on windows, download [http://tkgeisel.com/stuff/novaterm-1.zip novaterm for windows] and unzip it into the sdk/bin directory.
# From the Pre desktop, with no applicatons open on the Pre, type in the Konami code on your Pre's keyboard. ('''upupdowndownleftrightleftrightbastart''') to access the developer mode application. You do not need to press enter. When you press the "t" of start, the developer app will become visible.
# Open the DeveloperMode application on your Pre and enable the developer mode switch, resetting the device when prompted.
# Connect to your computer via USB cable. There is no need to answer the question on your Pre regarding mounting the drive or just charging. '''Don't select anything''' (or select "Just Charge" if not selecting anything really bothers you). '''Warning: Selecting a USB mode will turn off the Pre's WiFi & Cellular connections and mess up later steps by giving you a "wget: bad address" error when you try and install additional packages.'''
# Run Novaterm.
#* on Mac and Linux open a terminal, and type in cd /opt/nova/bin
#** Then type ./novaterm
#* On Mac, if ./novaterm results: in failed to connect to server, do the folllowing
#** sudo chmod 644 /Library/LaunchDaemons/com.palm.novacomd
#** sudo launchctl load -w /Library/LaunchDaemons/com.palm.novacomd
#** ./novaterm
#* on windows, run novaterm.exe or novaterm-1.exe from the palm/sdk/bin directory. (use explorer or a command line)
# Click "Connect" with "localhost" in the field next to the button. You will be asked to log in.
# Login with username '''root''' and a blank password. (Note that if dev mode is on, you can use root and a blank password, but you can only do this while dev mode is on - rebooting turns this insecure access off again)
#* This is what you should see
#:: <pre><nowiki>
#:: root@castle:/#
#:: </nowiki></pre>
#: Assuming that worked, you are in as root. You can prove this by typing '''ls -al''' and hitting enter. You should get a directory listing.
#:: What You Should See: ==

<pre><nowiki>
root@castle:/# ls
bin dev etc lib md5sums mnt sbin tmp var
boot dspbridge home lost+found media proc sys usr
root@castle:/# uname -a
Linux castle 2.6.24-palm-joplin-3430 #1 175.1.15 armv7l unknown
root@castle:/# whoami
root
</nowiki></pre>

Congrats, you are now in as root. Tread lightly.

== Next Steps: ==

Your Linux-accessible pre is in a very sensitive and unusual state. There are several steps you should take immidiately:

* Create a new username and password so that you don't have to connect as root
* Open up ports in the pre so that you can connect to it.
* Create a secure connection so that your pre is not open to everyone in the universe. **If you do not secure the network, your device will be accessible by anyone on the internet until it is rebooted.**
* Install the Optware package manager so that you can install software onto the Pre.

All this picks up in [[Next_steps]].

== Enabling Developer Mode As A Button ==

Having to type the Konami code every time is tedious so you can make the developer mode button visible by following the instructions at [[Unhide the DeveloperMode App|Unhide the DeveloperMode App]] - '''Works with 1.1'''

Accessing Linux Using Novaterm

2009-07-27T19:20:05Z

Eain: added clarification.s

# Download the Palm sdk from http://developer.palm.com and run it.
# Click through the installer.
#* If you are on windows, download [http://tkgeisel.com/stuff/novaterm-1.zip novaterm for windows] and unzip it into the sdk/bin directory.
# From the Pre desktop, with no applicatons open on the Pre, type in the Konami code on your Pre's keyboard. ('''upupdowndownleftrightleftrightbastart''') to access the developer mode application. You do not need to press enter. When you press the "t" of start, the developer app will become visible.
# Open the DeveloperMode application on your Pre and enable the developer mode switch, resetting the device when prompted.
# Connect to your computer via USB cable. There is no need to answer the question on your Pre regarding mounting the drive or just charging. '''Don't select anything''' (or select "Just Charge" if not selecting anything really bothers you). '''Warning: Selecting a USB mode will turn off the Pre's WiFi & Cellular connections and mess up later steps by giving you a "wget: bad address" error when you try and install additional packages.'''
# Run Novaterm.
#* on Mac and Linux open a terminal, and type in cd /opt/nova/bin
#** Then type ./novaterm
#* On Mac, if ./novaterm results: in failed to connect to server, do the folllowing
#** sudo chmod 644 /Library/LaunchDaemons/com.palm.novacomd
#** sudo launchctl load -w /Library/LaunchDaemons/com.palm.novacomd
#** ./novaterm
#* on windows, run novaterm.exe or novaterm-1.exe from the palm/sdk/bin directory. (use explorer or a command line)
# Click "Connect" with "localhost" in the field next to the button. You will be asked to log in.
# Login with username '''root''' and a blank password. (Note that if dev mode is on, you can use root and a blank password, but you can only do this while dev mode is on - rebooting turns this insecure access off again)
#* This is what you should see
#:: <pre><nowiki>
#:: root@castle:/#
#:: </nowiki></pre>
#: Assuming that worked, you are in as root. You can prove this by typing '''ls -al''' and hitting enter. You should get a directory listing.
#:: What You Should See: ==

<pre><nowiki>
root@castle:/# ls
bin dev etc lib md5sums mnt sbin tmp var
boot dspbridge home lost+found media proc sys usr
root@castle:/# uname -a
Linux castle 2.6.24-palm-joplin-3430 #1 175.1.15 armv7l unknown
root@castle:/# whoami
root
</nowiki></pre>

Congrats, you are now in as root. Tread lightly.

== Next Steps: ==

Your rooted pre is in a very sensitive and unusual state. There are several steps you should take immidiately:

* Create a new username and password so that you don't connect as root
* Open up ports in the pre so that you can connect to it.
* Create a secure connection so that your pre is not open to everyone in the universe. **If you do not secure the network, your device will be accessible by anyone on the internet until it is rebooted.**
* Install the Optware package manager so that you can install software onto the Pre.

All this picks up in [[Next_steps | Next steps after rooting ]].

== Enabling Developer Mode As A Button ==

Having to type the Konami code every time is tedious so you can make the developer mode button visible by following the instructions at [[Unhide the DeveloperMode App|Unhide the DeveloperMode App]] - '''Works with 1.1'''

RTorrent

2009-07-27T17:49:56Z

Eain: /* prerequisites */

I have succsefully installed and configued rTorrent.

== prerequisites ==

1. [[Portal:Accessing Linux]]

2. [[Next steps]]

3. [[Tutorials Linux DDNS for EVDO]]

'''If you have the prerequisites taken care of, login and do the following.....'''

sudo -i

ipkg-opt install rtorrent

plus install the 3 optional components. adduser, screens....

then, create an .rtorrent.rc file.
i placed mine in my home directory. /var/home/s4mb4/.rtorrent.rc

here is the config file;

----------------------------------------
min_peers = 40

max_peers = 100

min_peers_seed = -1

max_peers_seed = 50

max_uploads = 15

download_rate = 0

upload_rate = 1

directory = /media/internal/ringtones/

session = /media/internal/ringtones/

schedule = watch_directory,10,10,load_start=/media/internal/ringtones/*.torrent

schedule = tied_directory,10,10,start_tied=/media/internal/ringtones/*.torrent

schedule = untied_directory,10,10,close_untied=/media/internal/ringtones/*.torrent

ip = my.dynamic.hostname

bind = my.dynamic.hostname

port_range = 6881-6900

check_hash = yes

use_udp_trackers = yes
------------------------------------------

start it up by running;

sudo -i

rtorrent -n -o import=/var/home/s4mb4/.rtorrent.rc

-------------------------------------------

an alternative to issuing the command above is to link or copy the .rtorrent.rc file to the directory where you launch rtorrent from. Since after login and issuing the sudo -i command i always end up at;

root@castle:/var/home/root#

i just did the following;

ln /var/home/s4mb4/.rctorrent.rc .rtorrent.rc

then just run the command;

rtorrent

------------------------------------------

more info on rtorrent and how to make it work is located here;

http://libtorrent.rakshasa.no/wiki/RTorrentUserGuide

RTorrent

2009-07-27T17:49:34Z

Eain: /* prerequisites */

I have succsefully installed and configued rTorrent.

== prerequisites ==

1. [[Portal:Accessing Linux]]

2. [[Next steps]]

3. http://www.webos-internals.org/wiki/Tutorials_Linux_DDNS_for_EVDO

'''If you have the prerequisites taken care of, login and do the following.....'''

sudo -i

ipkg-opt install rtorrent

plus install the 3 optional components. adduser, screens....

then, create an .rtorrent.rc file.
i placed mine in my home directory. /var/home/s4mb4/.rtorrent.rc

here is the config file;

----------------------------------------
min_peers = 40

max_peers = 100

min_peers_seed = -1

max_peers_seed = 50

max_uploads = 15

download_rate = 0

upload_rate = 1

directory = /media/internal/ringtones/

session = /media/internal/ringtones/

schedule = watch_directory,10,10,load_start=/media/internal/ringtones/*.torrent

schedule = tied_directory,10,10,start_tied=/media/internal/ringtones/*.torrent

schedule = untied_directory,10,10,close_untied=/media/internal/ringtones/*.torrent

ip = my.dynamic.hostname

bind = my.dynamic.hostname

port_range = 6881-6900

check_hash = yes

use_udp_trackers = yes
------------------------------------------

start it up by running;

sudo -i

rtorrent -n -o import=/var/home/s4mb4/.rtorrent.rc

-------------------------------------------

an alternative to issuing the command above is to link or copy the .rtorrent.rc file to the directory where you launch rtorrent from. Since after login and issuing the sudo -i command i always end up at;

root@castle:/var/home/root#

i just did the following;

ln /var/home/s4mb4/.rctorrent.rc .rtorrent.rc

then just run the command;

rtorrent

------------------------------------------

more info on rtorrent and how to make it work is located here;

http://libtorrent.rakshasa.no/wiki/RTorrentUserGuide

RTorrent

2009-07-27T17:48:56Z

Eain: /* prerequisites */

I have succsefully installed and configued rTorrent.

== prerequisites ==

1. [[Portal:Accessing Linux]]

2. http://www.webos-internals.org/wiki/Next_steps

3. http://www.webos-internals.org/wiki/Tutorials_Linux_DDNS_for_EVDO

'''If you have the prerequisites taken care of, login and do the following.....'''

sudo -i

ipkg-opt install rtorrent

plus install the 3 optional components. adduser, screens....

then, create an .rtorrent.rc file.
i placed mine in my home directory. /var/home/s4mb4/.rtorrent.rc

here is the config file;

----------------------------------------
min_peers = 40

max_peers = 100

min_peers_seed = -1

max_peers_seed = 50

max_uploads = 15

download_rate = 0

upload_rate = 1

directory = /media/internal/ringtones/

session = /media/internal/ringtones/

schedule = watch_directory,10,10,load_start=/media/internal/ringtones/*.torrent

schedule = tied_directory,10,10,start_tied=/media/internal/ringtones/*.torrent

schedule = untied_directory,10,10,close_untied=/media/internal/ringtones/*.torrent

ip = my.dynamic.hostname

bind = my.dynamic.hostname

port_range = 6881-6900

check_hash = yes

use_udp_trackers = yes
------------------------------------------

start it up by running;

sudo -i

rtorrent -n -o import=/var/home/s4mb4/.rtorrent.rc

-------------------------------------------

an alternative to issuing the command above is to link or copy the .rtorrent.rc file to the directory where you launch rtorrent from. Since after login and issuing the sudo -i command i always end up at;

root@castle:/var/home/root#

i just did the following;

ln /var/home/s4mb4/.rctorrent.rc .rtorrent.rc

then just run the command;

rtorrent

------------------------------------------

more info on rtorrent and how to make it work is located here;

http://libtorrent.rakshasa.no/wiki/RTorrentUserGuide

Tutorials webOS Hello World

2009-07-25T04:15:05Z

Eain: /* A couple of scripts to make development easier */ Corrected a typo

This guide assumes you have a rooted Pre, with SFTP access. If you don't, please follow the other guides on this wiki first. This guide also assumes that you have at least a basic knowledge of HTML, CSS, and maybe a little JavaScript.

'''Note:''' All of this information was acquired via referencing the applications on the Pre, dissecting the Mojo sources available on the Pre, and possibly other publicly available information. The author of this guide has no access to, or knowledge of Palm's unreleased SDK, aside from what has been made publicly available so far.

I'll start by walking you through building your first “Hello, world!” application for webOS from scratch, without copying an existing application and modifying it. Then we'll slowly get into the cooler, meatier parts of Mojo, so that you can actually start bringing your ideas to life. This guide will also cover how to “install” your newly created webOS application(s) on your [[Portal:Accessing_Linux | rooted]] Pre.

== Building your first webOS application:==

First off, a webOS application requires only three files to become functional:

* '''appinfo.json''' – This is file contains a simple JSON object, describing basic meta information about your application, such as the name, version, vendor, etc...
* '''index.html''' – This file is really the first file that is run when your application is launched. It doesn't have to be called “index.html” since you specify the name for this file in your appinfo.json file. However, I think index.html fits well, and it seems to be what most (if not, all) of the existing webOS applications are using.
* '''icon.png''' – This is the icon that will be displayed in the launcher for your application. Like index.html, the filename doesn't have to be “icon.png”, since the filename for the launcher icon is specified in your appinfo.json file.

That's it! Only three files to create a basic webOS/Mojo application... In fact, it would probably work without the launcher icon, but let's be honest... who wants an application without an icon? In a typical application (especially if you follow the Mojo framework's MVC structure) you'll have many more files and directories than this, but for simplicity's sake, we'll start with the basics.

Anyway, now let's get started building our first webOS application.

First, create a new, blank directory for your application. Note: Create this directory on your computer. We'll cover how to install your application on your Pre later.

Now for the first, and arguably the most important part of your webOS application: the appinfo.json file.

Here's the contents of a typical appinfo.json file:

<pre><nowiki>
{
"title": "Hello, world!",
"version": "0.0.1",
"type": "web",
"main": "index.html",
"id": "org.webosinternals.evanpro.app.helloworld",
"icon": "icon.png",
"vendor": "Evan Coury",
"vendorurl": "http://www.evan.pro/",
"visible": true,
"removable": true
}
</nowiki></pre>

If you're not familiar with JSON, I urge you to [*http://en.wikipedia.org/wiki/JSON read up on it]. JSON has many other valuable uses in building web applications. The appinfo.json file is really just a self-explanatory key-value pair file, defining some simple information about your application. Here are some details on each value:

{| border="1" cellpadding="10"
!width="50"| Key
!width="50"| Values
!width="50"| Required
!width="650"| Description
|-

| title
|| String/Text
|| Y
|| This is the title used in the launcher, and also in the little gray tab thing that's always at the top left... what's that called, again?
|-

| version
|| Numbers x.y
|| Y
|| Simply put, this is the current version number of your application. This will obviously be used to manage OTA updates of webOS applications, and such.
|-

| type
|| web
|| Y
|| This is the application type... So far, the only value I've seen for this is “web”, even in more complex, plug-in-based applications such as Classic. This of course hints that there could be other options for this in the future, such as “java” or “native”, or who knows what else. This guide is only going to focus on “web”, though.
|-

| main
|| index.html
|| Y
|| This is the name of the html file you want to be have run when the user launches the application from the launcher. Typically, this will always be “index.html”, but there's nothing that says it has to be.
|-

| id
|| any String
|| Y
|| Now, this is a somewhat important one. This is your “Application ID”. Typically, is what this does, is gives the operating system a programmatic way of identifying your application. This must be completely unique, and it's suggested that you stick with the reverse DNS notation used in the existing applications. (ex. org.webosinternals.evanpro.app.helloworld). As a rule of thumb, I'd suggest keeping it all lowercase, and not using anything besides a through z, 0 through 9, and dashes for your application ID. We own the webosinternals.org domain, so you can use that reversed with your IRC nickname appended if you don't own your own domain that you can use here.
|-

| icon
|| file path
|| N
|| This is, of course, the path and file name of the icon you want to appear in the launcher. Simple enough, right?
|-

| vendor
|| String
|| N
|| The name of the person / company who made the application.
|-

| vendorurl
|| String
|| N
|| The URL of the aforementioned vendor.
|-

| visible
|| boolean, default: true
|| N
|| I'm pretty sure this just indicates whether or not to show the application in the launcher. (Credit to PreGame for pointing this one out)
|-

| removable
|| boolean, default: true
|| N
|| Tells webOS if this application should removable or not.
|-

| miniicon
|| path to icon
|| N
|| Path to file for icon to be used in notification area
|-

| category
|| String
|| N
|| Default category for the application
|-

| noWindow
|| boolean, default false
|| N
|| Indicates that this is a headless application that will be only called by other apps.
|-
|}

TODO: Finish specifying which values in the appinfo.json are required and which are optional. Also mention what the default values for optional ones are. Additionally, add any new values as they're discovered.

In the empty directory you made, create a new file called appinfo.json... In it, paste my sample from above. Feel free to change the title, version, id, vendor, and vendorurl to whatever you want. (Remember what I said about the characters in the application ID, though.)

Next, either go find or make an application icon. 64 x 64 seems to be a good size for launcher icons, O'Reilly's book states that the icon's image should be about 56 x 56 pixels within the 64 x 64 png bounds. PNG's with alpha transparency obviously will look the best. Note: if your icon is smaller than 64 x 64, I believe the launcher will stretch it to 64 x 64, causing it to look fuzzy or pixelated.

If you're too lazy to find or make an icon, I've made a little hello world icon that you may use:

[[Image:Helloworld-icon.png]]

Now that we have an appinfo.json and an awesome icon, we can move onto the fun part: index.html. If you're familiar with the basics of the web (HTML / CSS / JavaScript), then this will be very simple....

We'll start with the basics... Create an index.html in the directory you created, alongside your appinfo.json and icon.png, and paste the following code into it:

<pre><nowiki>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>Hello, world title!</title>


<script src="/usr/palm/frameworks/mojo/mojo.js" type="text/javascript" x-mojo-version="1"></script>


<style type="text/css">
#content {
text-align: center;
}

#app-footer {
margin-top: 25px;
font-size: 80%;
text-align: center;
}
</style>

</head>

<body>


<div class="palm-page-header">
<div class="palm-page-header-wrapper">
<div class="title">
My First webOS App!
</div>
</div>
</div>


<button class="palm-button" id="my-awesome-button">I'm an awesome button!</button>


<div id="content">
Hello, world!<br/>
<img src="icon.png"/>
</div>


<div id="app-footer">
<hr/>
© 2009 <a href="http://www.evan.pro/">Evan Coury</a>
</div>

</body>
</html>
</nowiki></pre>

You'll notice that webOS lets you use the exact same HTML / CSS as you would if you were simply developing for a browser.

The only real distinguishing factor of this application is here:

<pre><nowiki>

<script src="/usr/palm/frameworks/mojo/mojo.js" type="text/javascript" x-mojo-version="1"></script>
</nowiki></pre>

This line tells webOS to load all of the components of the Mojo framework, including pre-built CSS classes for UI elements, and the valuable Mojo JavaScript functions, which are what will allow us to access and interact with all of the fun stuff like GPS, messaging, alerts, vibration, etc, etc.

Really, if you're just doing some HTML / CSS stuff, and don't wish to use Palm's pre-built UI styles, then you really don't even need to include Mojo... but then what's the point?

In the example, I use a couple of the pre-built CSS UI styles from Mojo. Firstly, the header...

<pre><nowiki>

<div class="palm-page-header">
<div class="palm-page-header-wrapper">
<div class="title">
My First webOS App!
</div>
</div>
</div>
</nowiki></pre>

I don't have a list of all of the palm-* CSS classes, but they're very easy to find by referencing the existing applications.

The second Mojo style I used was the button:

<pre><nowiki>

<button class="palm-button" id="my-awesome-button">I'm an awesome button!</button>
</nowiki></pre>

Other than that, everything else is just normal HTML and CSS, exactly how you would use it on the web. One thing to note is how I referenced the application icon from within the application using a simple <img> tag.

Some Protips:

* Any files you place in your application's directory are available to you to use from within your application. This includes images, CSS, JavaScript files, etc.
* You do not have to have your CSS styles in-line like the example. For example, you could create a “css” subdirectory to hold all of your CSS files. Then you can use <link rel="stylesheet" type="text/css" href="css/styles.css" /> in the <head> just like normal.
* Theoretically, the files you include (images, JavaScript, CSS) do not have to be relative paths to files in your application's directory. You can also reference remote files using absolute paths... However, be sure to note that if you reference remote files like this, your application may take longer to load, as the files need to be downloaded over EV-DO or WiFi. Also, if the Pre is unable to get a network connection, there would obviously be problems with this. I'm simply noting that it is possible, and that it does work. However, including remote JavaScript can be extremely helpful with rapid development (TODO: Add example for remote JS development).
* You may include and use jQuery (and other JS libraries, I'm sure), but make sure to include it before Mojo, and use jQuery.noConflict(); since Mojo uses Prototype (TODO: Add jQuery example).

== Installing your first webOS application:==

Now that the application has been written, you need to install it on the Pre. Fortunately, installation is quite simple:
# Rename the source directory to match the "'''id'''" tag defined in the //appinfo.json// file.
# Copy the source directory (not just the files) to ///usr/palm/applications// on the Pre so that the full path to your appinfo file looks like this: ///usr/palm/applications/YOURAPPID/appinfo.json//
# Restart the GUI using either of the following methods:
* Reboot the Pre ( '''##FF5500|Orange##''' + '''Sym''' + '''R''' ).
* Stop/restart LunaSysMgr.
* As root, from a shell, execute //initctl stop LunaSysMgr// to stop and //initctl start LunaSysMgr// to restart.
* run the following command to refresh the Launcher Cache:

<pre><nowiki>
luna-send -n 1 palm://com.palm.applicationManager/rescan {}
</nowiki></pre>

== Screenshots:==
[[Image:Helloworld-launcher.jpg]]
[[Image:Helloworld-screenshot.jpg]]

== A couple of scripts to make development easier==
I use two scripts. Say I am creating the "something" app. I'd want to use something like com.foobar.app.something. When I want to move the app over to my Pre, I run the following script from the directory above com.foobar.app.something by typing "moveapp.sh something". Here is the moveapp.sh script

<pre><nowiki>
#!/bin/sh
#moveapp.sh
APP=com.foobar.app.$1

TIMESTAMP="`date '+%Y%m%d-%H%M'`"
echo archive $APP to "$APP"_$TIMESTAMP.tgz

echo tar zcvf "$APP"_$TIMESTAMP.tgz $APP
tar zcvf "$APP"_$TIMESTAMP.tgz $APP

echo scp -P 222 "$APP"_$TIMESTAMP.tgz myaccount@192.168.23.151:new.tgz
scp -P 222 "$APP"_$TIMESTAMP.tgz myaccount@192.168.23.151:new.tgz
</nowiki></pre>

On the pre, I have included adding /media/internal/applicaitons to the application search list in /etc/palm/luna.conf. I use this script on my phone to unzip ~/new.tgz created and copied above, then rescans so you can run the new app:

<pre><nowiki>
#!/bin/sh
# unpack new app into media internal, reset the command cache, and start watching the log
MYACCOUNT=myaccount
# you should sudo this or run as root

echo "go to /media/internal/applications/..."
cd /media/internal/applications/
echo "Unpack new code from ~my
unpack $MYACCOUNT/new.tgz
tar zxvf ~$MYACCOUNT/new.tgz

echo "rescan the the launcher's cache"
luna-send -n 1 palm://com.palm.applicationManager/rescan {}

echo "tail the log file just in case"
tall -f /var/log/messages

</nowiki></pre>

== To Do List:==
* Tips for speeding up the development process with remote JS files (while we wait for the SDK).
* Deeper examples into the Mojo MVC structure (controllers, scenes, etc) and using phone-related functions (GPS, messaging, etc).

== Development notes: ==
* If you want to interact with the local file system (read text files, etc) you will need to use the serviceRequest of com.palm.applicationManager with an "open" method. However, application Manager checks the registration in command.resource.handers.json to see what applicatoins are registered to handle a particular mime type. So, you will need to add YOUR app to the list for that mime type, or some other app may be passed your file. :-( --RickB

Can this open method of the appMgr service execute shell cmds and if so how? Can we get some code samples?

------

'''Note:''' Despite the //fake// copyright notice in the sample application, the code in the preceding example(s) is released under the MIT license.