WebOS Internals - User contributions [en]

Application:MetaDoctor

2010-04-29T00:56:32Z

Pre101: /* Mac OS X 10.6 */ Corrected md5sum port package name

= What is the Meta Doctor? =

The Webos Internals Meta Doctor is a set of shell scripts which can modify a copy of the Palm webOS Doctor to bypass the "First Use" application and allow the phone to run without having been activated on a cell network.

It can reach into Palm's distributed Doctor jar file and make changes which prevent the first use app from running, as well as applying other tweaks to the OS.

= Step 1: Setting up Meta-Doctor=

== Linux ==

=== Installing required software ===

# Open terminal from the ( Applications > Accessories ) menu. (If using Cygwin Method: Go to Start>Programs>Cygwin>Cygwin Bash Shell and skip to Number 3)
# If you have git installed, skip this step. If you do not have git installed, type: <pre>sudo apt-get install git-core</pre> and follow the directions to install git.
# Now type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre>
# If you do not have patch installed, you will need to install patch. (If using Cygwin method: Skip this step and jump to number 7) On an Ubuntu system type: <pre>sudo apt-get install patch</pre>
# If you do not have java installed, do so. To install java, choose ( Applications > Ubuntu Software Center ) and type '''java 6 runtime''' in search - it is easiest to search for java to find it - then follow the on screen instructions. It should be pretty simple.
# Download and install the Palm Novacom software from http://developer.palm.com. Download the version for Ubuntu [https://cdn.downloads.palm.com/sdkdownloads/1.3.1.314/sdkBinaries/palm-novacom_1.0.46_i386.deb here] and install it. (If you choose to install the full SDK instead, and are running the 64-bit version of Ubuntu 9.x you will have difficulty installing the SDK and the instructions on the download site are wrong. Read [https://developer.palm.com/distribution/viewtopic.php?f=31&t=2308 this thread] and [http://forums.precentral.net/showpost.php?p=2021966&postcount=108 this post] for help.)
# Open a terminal and navigate to the meta-doctor directory where the meta-doctor was copied to in step 3 above. (If using Cygwin method: You should already be in a terminal and just do the cd command) For example: <pre>cd meta-doctor</pre>
# Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre>
# Download the latest webosdoctor file using the download paths found at [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versions] .The wr version is the German/UK GSM version. An example download command would be: <pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/sr1ntp1351rod/webosdoctorp100ewwsprint.jar</pre>
# Rename the file that you download to include the version number for future reference (examples: webosdoctorp100ewwsprint-1.3.5.1.jar, webosdoctorp100eww-wr-1.1.3.jar, or webosdoctorp100ewwbellmo-1.2.1.jar). An example command to do that would be:<pre>mv webosdoctorp100ewwbellmo.jar webosdoctorp100ewwbellmo-1.3.5.1.jar</pre>

=== Running Meta-Doctor ===

# Navigate to the meta-doctor directory in the terminal
# If you would like Meta-Doctor to apply patches to webOS in order to add or change functionality from the factory install, open the Makefile in a text editor (For Cygwin method see notes at bottom of this section about this step)<pre>gedit Makefile</pre>and uncomment (remove the leading # characters from) the options you would like to use.
# Type one of the following:
#: <pre>make all-sprint</pre>
#: <pre>make all-wr</pre>
#: <pre>make all-bellmo</pre>
#: <pre>make all-telcel</pre>
#: <pre>make all-verizonwireless</pre>
#: depending on the carrier in question.

This should begin a process within the terminal that should take 10 minutes max.

'''*Cygwin notes*'''

gedit doesn't work in cygwin. Instead, open the file in WordPad. You can find the Makefile in <cygwin install folder>\home\<username>\meta-doctor

For example <pre>C:\cygwin\home\johndoe\meta-doctor</pre>

Then follow the rest of the instructions in number 2 about uncommenting options.

=== Error conditions ===

If an error message appears with unknown in a file name, check the file rename in step 8 above.

=== If the build fails ===

If the make command fails, you can use <pre>make clobber</pre> to clean up the build directory. After this you can re-run the command.

== Mac OS X 10.6 ==

In general, follow the Linux install instructions, with the following changes:

#If you haven't, install MacPorts first. [http://www.macports.org/].
#Install gnutar:
#<pre>sudo port install gnutar</pre>
#Install md5sum:
#<pre>sudo port install md5sha1sum</pre>
#Install wget:
#<pre>sudo port install wget</pre>

After the make process, run the Doctor with: <pre>java -jar webosdoctorp100eu-wr-1.4.1.jar</pre> (adapt for your flavor).

==Using a Virtual Machine==

If you do not have a Linux system, you will need to run the meta-doctor in a virtual machine. For windows users there are two options. For Mac users, follow option 1.

===Running in VMware or VirtualBox===

# Download [http://www.ubuntu.com/getubuntu/download Ubuntu 9.10].
# Download a virtual machine program, either vmware or virtualbox. A virtual machine is simply a program that allows you to piggyback a second operating system on top of your native OS without dual booting or actually having a Linux machine.
#: I ended up using VirtualBox instead, because I found the VMware to be very confusing on what to actually download. The Virtual box website is very simple and straight forward. Here is a link for the virtualbox download for Windows: [http://download.virtualbox.org/virtualbox/3.0.10/VirtualBox-3.0.10-54097-Win.exe VirtualBox-3.0.10-54097-Win]
# Now install virtualbox just like you would install any other application, nothing fancy here.
# Start up virtualbox and follow either of these instructions to install Ubuntu
## http://www.helpdeskgeek.com/linux-tips/how-to-install-ubuntu-in-virtualbox/
## http://www.psychocats.net/ubuntu/virtualbox

===Using WUBI===

Windows users have another option to avoid using a virtual machine. They can use the meta doctor without harming your current installation of windows using simple Ubuntu installer called WUBI. Also no need for moding any partitions or installing any boot loaders. It will just appear as program in your installed software list and when you do not want it anymore simply uninstall it while in windows through Control Panel. It is easy and there is no virtual machine headaches of trying to configure USB, Network and File sharing with host computer... To access it you just reboot and choose Ubuntu from dual boot screen.

# download [http://www.ubuntu.com/getubuntu/download Ubuntu 9.10]
# burn that file to a cd or mount to virtual drive
# Run cd in windows (the wubi.exe file inside the disk, it also comes up in auto run)
# Click on '''Install Inside windows'''.
#: This will install Ubuntu while running Windows without the need of making a partition I would recomand making the install image the full recommended 30 gigs if you have the hard drive space and think you are interested in actually using the Ubuntu OS, otherwise the minimum recommended by Wubi should be just fine.
# Restart your computer and you can dual boot to Windows or Ubuntu

The nice thing about this is that it will allow you to uninstall Ubuntu right from Windows as if it was never there and remove the dual boot, not to mention the fact you do not need to partition your drive.

If you are still wondering what Wubi is the fallowing link should explain it to you better.
[https://wiki.ubuntu.com/WubiGuide Wubi Guide]

'''Note:'''
this will only work with the cd image found at the Ubuntu Download link. The dvd image of 9.04/9.10 is a live cd/installer and does not have the option to install inside windows using Wubi

==Using Cygwin==

Windows users can alternatively use [http://www.cygwin.com/ Cygwin] to run Meta-Doctor. This can often be simpler and faster than installing a full-blown Virtual Machine.

Simply install Cygwin, and include the following additional packages:

# Python
# Make
# Patch
# Git
# Zip
# Unzip
# wget

(use View "Full" to find these specific packages more easily)

After you have installed these packages, you can follow the [[Application:MetaDoctor:#Linux | Linux instructions]]

= Step 2: Running the patched webOS Doctor =

The updated doctor version has the same name as the original, but is in a new folder: ''meta-doctor/build/pre-p100eww-sprint-1.3.5.1/webosdoctorp100ewwsprint-1.3.5.1.jar''.
If you are running in Ubuntu or Cygwin, you can just run the new jar file now.

If you are running Ubuntu using VM, you will need to copy the new jar out of the VM into your live desktop to run the jar in your native OS.

''Windows host:''

[http://ubuntuexperiment.wordpress.com/2008/11/12/sharing-folders-between-host-and-guest-os-in-virtualbox/ VirtualBox folder Sharing]

[http://www.howtogeek.com/howto/ubuntu/how-to-share-folders-with-your-ubuntu-virtual-machine-guest/ VMWare folder Sharing]

''Mac OSX host:''

[http://davidherron.com/blog/topics/628-virtualbox-running-ubuntu-accessing-host-file-system-mac-os-x VirtualBox folder Sharing]

: ''NOTE: this only applies to WUBI Users''
You should be able to run the JAR as if you had Linux installed natively because in a sense you do (as long as Java is installed and you run the Jar using Java) but if you rather run it in windows

Using terminal the following command in a Wubi installation of Ubuntu will copy the JAR file to the host Windows OS :<pre>cp /meta-doctor/build/pre-p100eww-sprint-1.2.1/webosdoctorp100ewwsprint-1.2.1.jar /host/webosdoctorp100ewwsprint-1.2.1.jar</pre>
This will place the Jar either in your Windows C:\ drive or whatever drive you installed Wubi to.

== Once the Doctor is running ==

# Select your language
# Accept the license agreement
# Connect your Pre to your PC via USB and select "Next" when it becomes available

After completion the device will reboot and present you with the activation set-up.

If your PC does not recognize your Pre and you cannot go past step 3 above, try the following steps:

# With the USB cable connected, completely power off the Pre (hold down the power button until the option to power off appears)
# Hold down the Up button on the volume rocker
# While holding the Up button, power on the Pre
# "Next" should now be enabled - proceed with the recovery
{{tux|Tux_with_Pre.png|float:right;}}
The above steps will put the Pre into bootloader recovery mode and should allow the PC to recognize your device and proceed with the restore. In this mode the screen will display a giant USB logo instead of the usual Palm startup logo.

When the process finishes, the Pre will reboot and your new modified image will have been installed.

----

After the doctor completes, you will need to run the "First Run" application. To do this, you will need an active internet connection. Either WiFi or Cellular. If you do not have WiFi and cannot connect to the Palm Profile servers, you might have a problem with your programming. This Meta Doctor (or webOS Doctor in general) could possibly erase the modem's programming. To resolve you will need to perform the following steps:

'''Note:''' This has only been confirmed to resolve Sprint CDMA issues, YMMV.

'''Note 2:''' You should try to update your profile first. Open the phone app, open the App Menu and select ''Preferences'' then select ''Update Network Settings''. If you get an error, then procede with these instructions.
*'''1.''' Open the Phone App.
*'''2.''' Enter ''##MSL#'' (MSL= 6 digit lock code. Get this from Sprint.)
*'''3.''' Verify your MDN and MSID are incorrect. If they are incorrect, continue. If they are correct, this is not your problem and you should not continue.
*'''4.''' Select ''Edit''.
*'''5.''' Select the first box (MDN) and enter your 10-digit cellular number.
*'''6.''' Select the second box (MSID) and enter your 10-digit MSID (Get this from Sprint).
*'''7.''' Select ''Save''.
*'''8.''' Backswipe out of the the view.
*'''9.''' You should now be able to open complete '''Note 2''' above without any errors.

You should now be able to run the ''First Use'' application without any problems.

=If the Doctor will not run=
Go [http://www.webos-internals.org/wiki/How_To_Recover here] if you have further problems connecting your Pre to the running Meta'ed Doctor.

=Miscelaneous=

==How to change a provider's DB-entry so 3G data can be used on the Pre==

[http://forums.precentral.net/gsm-pre/211728-modifying-webos-carrier-network-settings.html#post2002079 This post] and [http://forums.precentral.net/palm-pre/209222-few-questions-about-german-palm-pre-6.html this thread] describe various ways to adjust the provider's data base in the Pre, so the 3G datacom works on non-supported networks. webOS 1.3.1 allows setting of the providers data directly from the activation screen for providers that are present in the DB. Some report that they are not able to do that and that they cannot get 3G datacom working on 1.3.1

Application:MetaDoctor

2010-04-28T17:38:26Z

Pre101: /* Mac OS X 10.6 */ Added wget to install list

= What is the Meta Doctor? =

The Webos Internals Meta Doctor is a set of shell scripts which can modify a copy of the Palm webOS Doctor to bypass the "First Use" application and allow the phone to run without having been activated on a cell network.

It can reach into Palm's distributed Doctor jar file and make changes which prevent the first use app from running, as well as applying other tweaks to the OS.

= Step 1: Setting up Meta-Doctor=

== Linux ==

=== Installing required software ===

# Open terminal from the ( Applications > Accessories ) menu. (If using Cygwin Method: Go to Start>Programs>Cygwin>Cygwin Bash Shell and skip to Number 3)
# If you have git installed, skip this step. If you do not have git installed, type: <pre>sudo apt-get install git-core</pre> and follow the directions to install git.
# Now type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre>
# If you do not have patch installed, you will need to install patch. (If using Cygwin method: Skip this step and jump to number 7) On an Ubuntu system type: <pre>sudo apt-get install patch</pre>
# If you do not have java installed, do so. To install java, choose ( Applications > Ubuntu Software Center ) and type '''java 6 runtime''' in search - it is easiest to search for java to find it - then follow the on screen instructions. It should be pretty simple.
# Download and install the Palm Novacom software from http://developer.palm.com. Download the version for Ubuntu [https://cdn.downloads.palm.com/sdkdownloads/1.3.1.314/sdkBinaries/palm-novacom_1.0.46_i386.deb here] and install it. (If you choose to install the full SDK instead, and are running the 64-bit version of Ubuntu 9.x you will have difficulty installing the SDK and the instructions on the download site are wrong. Read [https://developer.palm.com/distribution/viewtopic.php?f=31&t=2308 this thread] and [http://forums.precentral.net/showpost.php?p=2021966&postcount=108 this post] for help.)
# Open a terminal and navigate to the meta-doctor directory where the meta-doctor was copied to in step 3 above. (If using Cygwin method: You should already be in a terminal and just do the cd command) For example: <pre>cd meta-doctor</pre>
# Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre>
# Download the latest webosdoctor file using the download paths found at [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versions] .The wr version is the German/UK GSM version. An example download command would be: <pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/sr1ntp1351rod/webosdoctorp100ewwsprint.jar</pre>
# Rename the file that you download to include the version number for future reference (examples: webosdoctorp100ewwsprint-1.3.5.1.jar, webosdoctorp100eww-wr-1.1.3.jar, or webosdoctorp100ewwbellmo-1.2.1.jar). An example command to do that would be:<pre>mv webosdoctorp100ewwbellmo.jar webosdoctorp100ewwbellmo-1.3.5.1.jar</pre>

=== Running Meta-Doctor ===

# Navigate to the meta-doctor directory in the terminal
# If you would like Meta-Doctor to apply patches to webOS in order to add or change functionality from the factory install, open the Makefile in a text editor (For Cygwin method see notes at bottom of this section about this step)<pre>gedit Makefile</pre>and uncomment (remove the leading # characters from) the options you would like to use.
# Type one of the following:
#: <pre>make all-sprint</pre>
#: <pre>make all-wr</pre>
#: <pre>make all-bellmo</pre>
#: <pre>make all-telcel</pre>
#: <pre>make all-verizonwireless</pre>
#: depending on the carrier in question.

This should begin a process within the terminal that should take 10 minutes max.

'''*Cygwin notes*'''

gedit doesn't work in cygwin. Instead, open the file in WordPad. You can find the Makefile in <cygwin install folder>\home\<username>\meta-doctor

For example <pre>C:\cygwin\home\johndoe\meta-doctor</pre>

Then follow the rest of the instructions in number 2 about uncommenting options.

=== Error conditions ===

If an error message appears with unknown in a file name, check the file rename in step 8 above.

=== If the build fails ===

If the make command fails, you can use <pre>make clobber</pre> to clean up the build directory. After this you can re-run the command.

== Mac OS X 10.6 ==

In general, follow the Linux install instructions, with the following changes:

#If you haven't, install MacPorts first. [http://www.macports.org/].
#Install gnutar:
#<pre>sudo port install gnutar</pre>
#Install md5sum:
#<pre>sudo port install md5sum</pre>
#Install wget:
#<pre>sudo port install wget</pre>

After the make process, run the Doctor with: <pre>java -jar webosdoctorp100eu-wr-1.4.1.jar</pre> (adapt for your flavor).

==Using a Virtual Machine==

If you do not have a Linux system, you will need to run the meta-doctor in a virtual machine. For windows users there are two options. For Mac users, follow option 1.

===Running in VMware or VirtualBox===

# Download [http://www.ubuntu.com/getubuntu/download Ubuntu 9.10].
# Download a virtual machine program, either vmware or virtualbox. A virtual machine is simply a program that allows you to piggyback a second operating system on top of your native OS without dual booting or actually having a Linux machine.
#: I ended up using VirtualBox instead, because I found the VMware to be very confusing on what to actually download. The Virtual box website is very simple and straight forward. Here is a link for the virtualbox download for Windows: [http://download.virtualbox.org/virtualbox/3.0.10/VirtualBox-3.0.10-54097-Win.exe VirtualBox-3.0.10-54097-Win]
# Now install virtualbox just like you would install any other application, nothing fancy here.
# Start up virtualbox and follow either of these instructions to install Ubuntu
## http://www.helpdeskgeek.com/linux-tips/how-to-install-ubuntu-in-virtualbox/
## http://www.psychocats.net/ubuntu/virtualbox

===Using WUBI===

Windows users have another option to avoid using a virtual machine. They can use the meta doctor without harming your current installation of windows using simple Ubuntu installer called WUBI. Also no need for moding any partitions or installing any boot loaders. It will just appear as program in your installed software list and when you do not want it anymore simply uninstall it while in windows through Control Panel. It is easy and there is no virtual machine headaches of trying to configure USB, Network and File sharing with host computer... To access it you just reboot and choose Ubuntu from dual boot screen.

# download [http://www.ubuntu.com/getubuntu/download Ubuntu 9.10]
# burn that file to a cd or mount to virtual drive
# Run cd in windows (the wubi.exe file inside the disk, it also comes up in auto run)
# Click on '''Install Inside windows'''.
#: This will install Ubuntu while running Windows without the need of making a partition I would recomand making the install image the full recommended 30 gigs if you have the hard drive space and think you are interested in actually using the Ubuntu OS, otherwise the minimum recommended by Wubi should be just fine.
# Restart your computer and you can dual boot to Windows or Ubuntu

The nice thing about this is that it will allow you to uninstall Ubuntu right from Windows as if it was never there and remove the dual boot, not to mention the fact you do not need to partition your drive.

If you are still wondering what Wubi is the fallowing link should explain it to you better.
[https://wiki.ubuntu.com/WubiGuide Wubi Guide]

'''Note:'''
this will only work with the cd image found at the Ubuntu Download link. The dvd image of 9.04/9.10 is a live cd/installer and does not have the option to install inside windows using Wubi

==Using Cygwin==

Windows users can alternatively use [http://www.cygwin.com/ Cygwin] to run Meta-Doctor. This can often be simpler and faster than installing a full-blown Virtual Machine.

Simply install Cygwin, and include the following additional packages:

# Python
# Make
# Patch
# Git
# Zip
# Unzip
# wget

(use View "Full" to find these specific packages more easily)

After you have installed these packages, you can follow the [[Application:MetaDoctor:#Linux | Linux instructions]]

= Step 2: Running the patched webOS Doctor =

The updated doctor version has the same name as the original, but is in a new folder: ''meta-doctor/build/pre-p100eww-sprint-1.3.5.1/webosdoctorp100ewwsprint-1.3.5.1.jar''.
If you are running in Ubuntu or Cygwin, you can just run the new jar file now.

If you are running Ubuntu using VM, you will need to copy the new jar out of the VM into your live desktop to run the jar in your native OS.

''Windows host:''

[http://ubuntuexperiment.wordpress.com/2008/11/12/sharing-folders-between-host-and-guest-os-in-virtualbox/ VirtualBox folder Sharing]

[http://www.howtogeek.com/howto/ubuntu/how-to-share-folders-with-your-ubuntu-virtual-machine-guest/ VMWare folder Sharing]

''Mac OSX host:''

[http://davidherron.com/blog/topics/628-virtualbox-running-ubuntu-accessing-host-file-system-mac-os-x VirtualBox folder Sharing]

: ''NOTE: this only applies to WUBI Users''
You should be able to run the JAR as if you had Linux installed natively because in a sense you do (as long as Java is installed and you run the Jar using Java) but if you rather run it in windows

Using terminal the following command in a Wubi installation of Ubuntu will copy the JAR file to the host Windows OS :<pre>cp /meta-doctor/build/pre-p100eww-sprint-1.2.1/webosdoctorp100ewwsprint-1.2.1.jar /host/webosdoctorp100ewwsprint-1.2.1.jar</pre>
This will place the Jar either in your Windows C:\ drive or whatever drive you installed Wubi to.

== Once the Doctor is running ==

# Select your language
# Accept the license agreement
# Connect your Pre to your PC via USB and select "Next" when it becomes available

After completion the device will reboot and present you with the activation set-up.

If your PC does not recognize your Pre and you cannot go past step 3 above, try the following steps:

# With the USB cable connected, completely power off the Pre (hold down the power button until the option to power off appears)
# Hold down the Up button on the volume rocker
# While holding the Up button, power on the Pre
# "Next" should now be enabled - proceed with the recovery
{{tux|Tux_with_Pre.png|float:right;}}
The above steps will put the Pre into bootloader recovery mode and should allow the PC to recognize your device and proceed with the restore. In this mode the screen will display a giant USB logo instead of the usual Palm startup logo.

When the process finishes, the Pre will reboot and your new modified image will have been installed.

----

After the doctor completes, you will need to run the "First Run" application. To do this, you will need an active internet connection. Either WiFi or Cellular. If you do not have WiFi and cannot connect to the Palm Profile servers, you might have a problem with your programming. This Meta Doctor (or webOS Doctor in general) could possibly erase the modem's programming. To resolve you will need to perform the following steps:

'''Note:''' This has only been confirmed to resolve Sprint CDMA issues, YMMV.

'''Note 2:''' You should try to update your profile first. Open the phone app, open the App Menu and select ''Preferences'' then select ''Update Network Settings''. If you get an error, then procede with these instructions.
*'''1.''' Open the Phone App.
*'''2.''' Enter ''##MSL#'' (MSL= 6 digit lock code. Get this from Sprint.)
*'''3.''' Verify your MDN and MSID are incorrect. If they are incorrect, continue. If they are correct, this is not your problem and you should not continue.
*'''4.''' Select ''Edit''.
*'''5.''' Select the first box (MDN) and enter your 10-digit cellular number.
*'''6.''' Select the second box (MSID) and enter your 10-digit MSID (Get this from Sprint).
*'''7.''' Select ''Save''.
*'''8.''' Backswipe out of the the view.
*'''9.''' You should now be able to open complete '''Note 2''' above without any errors.

You should now be able to run the ''First Use'' application without any problems.

=If the Doctor will not run=
Go [http://www.webos-internals.org/wiki/How_To_Recover here] if you have further problems connecting your Pre to the running Meta'ed Doctor.

=Miscelaneous=

==How to change a provider's DB-entry so 3G data can be used on the Pre==

[http://forums.precentral.net/gsm-pre/211728-modifying-webos-carrier-network-settings.html#post2002079 This post] and [http://forums.precentral.net/palm-pre/209222-few-questions-about-german-palm-pre-6.html this thread] describe various ways to adjust the provider's data base in the Pre, so the 3G datacom works on non-supported networks. webOS 1.3.1 allows setting of the providers data directly from the activation screen for providers that are present in the DB. Some report that they are not able to do that and that they cannot get 3G datacom working on 1.3.1

Komodo Macro

2010-03-15T06:33:09Z

Pre101: Cleanup

Macros show up in the toolbox panel on the right-hand side of the Komodo window. They can be used to automate almost everything in Komodo, and all the Komodo add-on functionality is exposed to the macros.

Since users are used to writing JavaScript for their Mojo applications all macros are written in JavaScript (Python is also allowed, but not documented).

If you do not see the panel: '''View''' > '''Tabs & Sidebars''' > '''Toolbox'''.[[Image:Komodo_Toolbox_Macro.png|frame|right|Add a new Macro to the Toolbox]]

== Macro Basics ==

To create a new macro simply add your code to the starting script below

<source lang="javascript">
komodo.assertMacroVersion(2); // Macro Version
if(komodo.view && komodo.view.scintilla)
{
komodo.view.scintilla.focus(); // Sets focus
}
[... Your Script Here ...]
</source>

== Deploy Functions ==

The deploy functions will automatically toggle and animate the add-on to prevent conflicts. The functions automatically use the active project to perform operations.

<source lang="javascript">
// Emulator Functions
ko.extensions.webos.emulator.packageInstallLaunch();
ko.extensions.webos.emulator.packageInstallInspect();
ko.extensions.webos.emulator.remove();
ko.extensions.webos.emulator.launch();
ko.extensions.webos.emulator.close();
// Device Functions
ko.extensions.webos.device.packageInstallLaunch();
ko.extensions.webos.device.remove();
ko.extensions.webos.device.launch();
ko.extensions.webos.device.close();
</source>

The above functions can optionally be passed an object with onSuccess and onFailure property functions.

<source lang="javascript">
{
onSuccess:function()
{
// This means the function worked
},
onFailure:function()
{
// This means the function failed, the UI will show this also.
}
}
</source>

For more customization you must use the base Palm functions listed below.

== Macro Functions ==

All functions are asynchronous, with onSuccess and onFailure callbacks. These are written to make more complicated tasks very simple to write into a macro.

=== Check If Connected ===

The first thing you need to determine is if the emulator or device is connected.

==== Is Emulator Connected ====

<source lang="javascript">
ko.extensions.webos.palm.isEmulatorConnected({
onSuccess:function()
{
// Emulator was found
},
onFailure:function()
{
// Emulator was not found
}
});
</source>

==== Is Device Connected ====

<source lang="javascript">
ko.extensions.webos.palm.isDeviceConnected({
onSuccess:function()
{
// Device was found
},
onFailure:function()
{
// Device was not found
}
});
</source>

=== Palm Commands ===

You may have never used the Palm command line since you are used to the add-on, but the following are what the quick buttons rely on:

==== Generate Application ====

This function is documented only to show the complete list of commands. It is recommended that you use the new project option in the emulator as this will only create the src/ contents.

<source lang="javascript">
ko.extensions.webos.palm.generateApplication({
appInfo:{}, // The appinfo.json object
path:"", // Absolute file path. "C:\Folder" for instance
onSuccess:function()
{
// Created a application at path
},
onFailure:function()
{
// Failed to create application template
}
});
</source>

==== Package Application ====

Package an application simply creates the ipk and places it into either the bin/release or bin/debug based on the framework_config.json settings.

<source lang="javascript">
ko.extensions.webos.palm.packageApplication({
onSuccess:function()
{
// Created the ipk package file
},
onFailure:function()
{
// Failed to create package
}
});
</source>

==== Install Application ====

Install an application to the device or emulator. There are currently two options.

<source lang="javascript">
ko.extensions.webos.emulator.cmdName
ko.extensions.webos.device.cmdName
</source>

Once you pick a device or emulator to install to you must select an ipk. If you do not select an IPK it is automatically populated with the current project's ipk based off framework_config.json and appinfo.json.

<source lang="javascript">
ko.extensions.webos.palm.installApplication({
device:ko.extensions.webos.emulator.cmdName,
path:"", // OPTIONAL: Absolute path to ipk file.
onSuccess:function()
{
//
},
onFailure:function()
{
// Test
}
});
</source>

==== Launch Application ====

<source lang="javascript">
ko.extensions.webos.palm.launchApplication({})
</source>

==== Close Application ====

<source lang="javascript">
ko.extensions.webos.palm.closeApplication({})
</source>

==== Remove Application ====

<source lang="javascript">
ko.extensions.webos.palm.removeApplication({})
</source>

=== Editing "appinfo.json" ===

Need to read in the appinfo.json or save property changes through commands. Like all commands these are asynchronous, meaning they won't cause Komodo to freeze while they are being run.

==== Getting the Object ====

To get the active project's "appinfo.json" into an object simply call the function below:

<source lang="javascript">
ko.extensions.webos.project.getAppInfo({
onSuccess:function()
{
// this.json contains the object while this.text contains the contents
alert(this.json.version); // or any other property.
},
onFailure:function()
{
// this.errorCode == 1, this.error == "Error: Failed to load appinfo.json"
// this.errorCode == 2, this.error == "Error: Failed to parse appinfo.json"
alert(this.error);
}
});
</source>

==== Saving the Object ====

The "appinfo" property contains either the full appinfo.json or partial properties. Make sure that overwrite = false or the entire appinfo.json will be overwritten.

<source lang="javascript">
ko.extensions.webos.project.setAppInfo({
overwrite:false, // Completely overwrites file
appinfo:{},
onSuccess:function()
{
// this.json contains the object while this.text contains the contents
alert(this.json.version);
},
onFailure:function()
{
// this.errorCode == 1, this.error == "Error: Failed to load appinfo.json"
// this.errorCode == 2, this.error == "Error: Failed to parse appinfo.json"
alert(this.error);
}
});
</source>

=== Editing "framework_config.json" ===

Need to read in the "framework_config.json" or save property changes through commands. Like all commands these are asynchronous meaning they won't cause Komodo to freeze while they are being run.

==== Getting the Object ====

[Will type up shortly]

==== Saving the Object ====

[Will type up shortly]

=== Useful Macros ===

If you find a useful macro list it below.

Testing Feeds

2010-01-14T06:06:23Z

Pre101:

Setting up the WebOS Internals testing feeds on your webOS 1.3.5+ device:

1. Gain access to the shell, either through novaterm/ssh or via the terminal application available through the regular WebOS Internals Feed

2. Execute the following script:

<pre>
cd /media/cryptofs/apps/etc/ipkg
echo "src/gz webosinternals-testing http://ipkg.preware.org/feeds/webos-internals/testing/all" >webos-internals-testing.conf
echo "src/gz webosinternals-testing-armv7 http://ipkg.preware.org/feeds/webos-internals/testing/armv7" >>webos-internals-testing.conf
</pre>

3. Once Preware is launched, selected the Update Feeds menu.

Testing Feeds

2010-01-14T05:44:31Z

Pre101: New page: Setting up the WebOS Internals testing feeds on your webOS 1.3.5+ device: 1. Gain access to the shell, either through novaterm/ssh or via the terminal application available through the r...

Portal:Community

2009-11-27T05:42:00Z

Pre101:

There is a large community of developers around the Palm Pre.

* [[Contact|Contact]]
* [[Meetups|Meetups]]

== IRC ==
{{tux|Tux_Chat.png|float:right;}}
You can join us anytime on our [[wikipedia:Internet Relay Chat|IRC]] channels.

* [irc://chat.freenode.net/webos #webos] for general Palm Pre topics
* [irc://chat.freenode.net/webos-internals #webos-internals] for discussion of the operating system
* [irc://chat.freenode.net/webos-watercooler #webos-watercooler] for off-topic discussion

We are located on the freenode network, accessible from http://webchat.freenode.net/

Come and join us

=== Guidelines ===
{{tux|Tux_Mad.png|float:right;}}
See [[WebOS-Internals IRC Channel Policy]].

* For pastes greater than 2 lines, use a pastebin such as [http://webos.pastebin.com/ webos.pastebin.com].
* Keep the language civilized. Don't try to debate. WebOS is cross platform and the [[Portal:Tools|tools]] supported by webOS-Internals are also.

== Other Web Sites ==
* [http://developer.palm.com/distribution/index.php webOSdev Forum] Palm's official developer forum
* [http://webos101.com webOS 101] webOS Programming wiki focusing on app development
* [http://www.webosschool.com/ webOS School] On-line webOS programming courses

Application:Preware

2009-11-03T21:47:44Z

Pre101: Added bug report

{{application
|name=Preware
|type=webOS
|version=Version: Beta 0.9.5 (22 Oct 2009)
|tag=Utilities
|screenshot=Application_Preware_List.png
|description=

== Summary ==
{{icon|Icon_Preware.png|float:right;}}
Preware is a package management application for the Palm Pre. Preware allows the user to install any package from any of the open standard package repositories on preware.org (or any other location that hosts an open standard package repository). Preware relies on a custom written service developed from community research which allows the mojo app to talk to the built-in ipkg tool.

This application was the result of extensive community-based design in [[IPKG Service]] and [[Preware Design]].

For application management, Preware can access more applications, and has more features, than any other on-device package installer.

And since it is open source, and has a completely open development process supported by a team of world-class WebOS Internals developers, it will continue to get better much faster than any other package management application.

Preware is the open application installer that has been written specifically to support a homebrew ecosystem where any developer can upload any application to any submission site, and that application can then be installed by any user. Developers no longer need to upload their applications to multiple submission sites, and users are no longer excluded from accessing applications from any open standard package repository.

=== Key Features ===

* Install / Remove / Update Homebrew Applications including advanced applications with special requirements.
* Install / Remove / Update WebOS Themes
* Install / Remove / Update WebOS Patches
* Advanced applications and Patches that run scripts require your consent prior to installation. Preware offers to show you the script before you make the decision to let it install.

== Usage ==

=== Preferences ===

[[Image:Preferences.png|160px|bottom]] You can select preferences in the top left corner of the pre to bring up the preferences screen. On the Preferences screen you can specify the look of the application, the frequency that feeds are updated, and what Preware will show you by default.

=== Feed Management ===

[[Image:preware_feeds.png|160px|bottom]][[Image:preware_add_feed.png|160px|bottom]] In the preferences section on the top bar on the right side is a button that takes you to the feeds screen. On the feeds screen you can select which feeds are loaded and which ones are not. Simply select the on or off button for that feed. (If you are not interested in feeds you can disable the two feeds for themes to speed up the updating of feeds) Preware comes with the following feeds by default.

* Canuck-software
* Optware
* PimpmyPre
* Precentral
* Precentral Themes
* Prethemer
* Preware
* Preyourmind
* Webos-internals
* Webos-patches

You also have the ability to add other feeds that follow the standard feed layout used by Preware. In the new feed section add a name for the feed, and the URL to the feed then tap add feed.

=== Package Updates ===
=== Applications ===
=== Themes ===
=== Patches ===
=== Installed Packages ===
=== List of Everything ===

== Status ==

This is beta software. Even so, as of 27 August 2009 it is the only over-the-air installer for the palm capable of installing advanced palm applications such as the [[On_Screen_Keyboard|on screen keyboard]] or the terminal application. Also as of 27 August 2009 it is the only application supporting installation from all existing palm homebrew feeds. As of 17 September 2009 it also supports installation of themes. As of 8 October 2009 it also supports installation of webos patches.

== License ==

Please be aware that org.webosinternals.preware and org.webosinternals.ipkgservice are licensed under the GPLv2.

They cannot be used by a closed source application. If you want to use them in a non-GPLv2 but otherwise open source application, please contact the authors.

== Operating notes ==

=== Limitations ===

No known limitations.

=== Known bugs ===

When selecting a patch with dependencies, if you view those dependencies then install them, when Preware returns you to the original patch's screen it will still have the 'install' button showing even though it is installed successfully. Swiping back and returning will show the correct status.

== Installation ==

You do not need to access the Linux command line or "root your Pre" to install or use Preware.

You can use one of the stand-alone Preware Installers at http://get.preware.org/ to install Preware.

If that fails, please use the [http://forums.precentral.net/homebrew-apps/206905-webos-quick-install-v2-7-beyond.html WebOS Quick Install] tool to install the Package Manager Service and the Preware application directly from the WebOS Internals feed.

No other application installer tool is sophisticated enough to install the custom Package Manager Service that Preware requires. Preware can install it, but you need a way to bootstrap Preware first, so you need to use our stand-alone Preware Installers or WebOS Quick Install for the very first installation of Preware.

You need to have your Pre in developer mode when using the stand-alone Preware Installer or WebOS Quick Install for the very first installation of the Package Manager Service and Preware. Once you have Preware correctly installed, you never need to use developer mode again with Preware (it does the required steps in the background for you whenever it needs to).

Note that Preware works just as well on the Emulator as it does on a real device, and is installed in exactly the same way.

=== Preware Installer Installation Steps ===
* Put your device in Developer Mode
* Run the Preware Installer
* Press INSTALL.
* Launch Preware, and follow the Updating steps below.

=== WebOS Quick Install Installation Steps ===
* Put your device in Developer Mode
* Run WebOS Quick Install
* Press the third button on the right
* Choose WebOS Internals Feed (all) from the dropdown list at the top.
* Select ''Package Manager Service'' from the list.
* Press DOWNLOAD.
* Press INSTALL.
* Press the third button on the right
* Choose WebOS Internals Feed (all) from the dropdown list at the top.
* Select ''Preware'' from the list.
* Press DOWNLOAD.
* Press INSTALL.
* If WebOS Quick Install offers to install the Package Manager Service automatically to enable tweaking, do not agree. It will install the wrong version. You must install it as detailed above.

=== Updating ===

To update Preware or the Package Manager Service, simpy use Preware version 0.9.0 or later.

Make sure you update the Package Manager Service first, and the Preware application second. As of Preware 0.9.4, this restriction will be enforced automatically.

If you are updating to Preware version 0.9.3 or later and you have previously used the autopatch-feed package, please follow these [http://forums.precentral.net/webos-patches/208312-autopatch-transitioning-webos-patches-feed.html] directions for the update.

=== Removal ===

Why would you ever want to remove Preware?

To remove Preware, use WebOS Quick Install's Device Management page and unselect the Package Manager Service and the Preware application.

=== Recent enhancements ===

0.9.5: A package is removed if the user cancels installation. More verbose status and error messages.

0.9.4: Added support for package dependencies.

0.9.3: Adds the webos-patches feed, and feed management support.

0.9.1: Adds the All category, plus other miscellaneous fixes.

0.9.0: Now supports themes, restart flags and the new memory-reduction service methods.

0.8.5: Massive speed improvement on loading, now supports package types and adding feeds.

0.8.2: More preferences added and now functional, with listing and update frequency options.

0.8.1: Preferences scene implemented. Upstart job stops on removal.

0.8.0: Now supports Descriptions and Screenshots.

0.7.7: Addition of ipkglog and config list, and if ipkgservice fails at start it notifies people, and if it fails after postinst it considers it complete anyways

0.7.6: Fixed the superfluous update subscription message windows

0.7.5: Fixed update subscription oddity.

0.7.4: Fixed remounting of root filesystem for post-install and pre-remove scripts on the Pre.

0.7.1: Fixed buttons and title on script view screen.

0.7.0: Initial support for post-install and pre-remove scripts, including secure informed user consent. Does not work properly with dependencies yet, so please install dependencies one at a time.

0.6.7: Fixed bug in category drop-down list.

0.6.6: Fixed bug in package size reporting.

0.6.5: Updated icon and other graphical annotations.

0.6.4: Categories drop-down bug fixed. Preware category updated.

0.6.2: Categories now work to some extent. Still a bug in the drop down box.

0.6.1: Sorting by name or date is now available. Application details screen is much more organized.

0.6.0: No user visible changes. Preparation for the secure informed user consent functionality.

0.5.1: Filtering is now available on the list screens. Just start typing ...

== Repository ==

Preware and the Package Manager Service are housed in the applications/preware and services/ipkservice git repositories at http://git.webos-internals.org/

For commit permission to the open source project, contact rwhitby on #webos-internals or email [[mailto:support@webos-internals.org support@webos-internals.org]]

== Alternative Installation (ADVANCED/CLI Method)==

Really, unless you *really* know what you are doing, you should use the WebOS Quick Install installation instructions above.

This method is for '''LINUX EXPERTS ONLY''' and depends on the ipkg.preware.org/feeds/webos-internals repository. You must install the [[Application:Terminal]] application first to set up the feeds correctly.

=== Installing via IPKG ===

Really, unless you *really* know what you are doing, you should use the WebOS Quick Install installation instructions above.

If you have never configured the ipkg feed perform the following, then follow directions below:
<source lang="text">
mount -o remount,rw /

mkdir -p /var/etc/ipkg/
ln -s /etc/ipkg/arch.conf /var/etc/ipkg/
echo "src/gz webosinternals http://ipkg.preware.org/feeds/webos-internals/all" > /var/etc/ipkg/webos-internals.conf

echo "src/gz webosinternals-armv7 http://ipkg.preware.org/feeds/webos-internals/armv7" >> /var/etc/ipkg/webos-internals.conf
</source>

If you have already configured the ipkg feed, perform the following:
<source lang="text">
mount -o remount,rw /

/usr/bin/ipkg -o /var update
/usr/bin/ipkg -o /var install org.webosinternals.ipkgservice
/usr/bin/ipkg -o /var install org.webosinternals.preware
sh /var/usr/lib/ipkg/info/org.webosinternals.ipkgservice.postinst
luna-send -n 1 palm://com.palm.applicationManager/rescan {}

mount -o remount,ro /
exit
</source>

=== Updating via IPKG ===

Really, unless you *really* know what you are doing, you should use the Preware update instructions above.

If you are already running Preware 0.9.0 or later, you should use the Preware update instructions above.

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

/usr/bin/ipkg -o /var update
/usr/bin/ipkg -o /var upgrade
sh /var/usr/lib/ipkg/info/org.webosinternals.ipkgservice.postinst
luna-send -n 1 palm://com.palm.applicationManager/rescan {}

mount -o remount,ro /
exit
</source>

}}