WebOS Internals - User contributions [en]

Tutorials webOS Debugging 101

2009-10-12T22:25:05Z

G33kgirl:

If you're results are not what you expected use JavaScripts try/catch/finally block statements to localize the problem. The first thing you want to do is get as close as possible to where you believe the error is occuring. If you're not sure where, start at the beginning.

Add mojo.logs to your code and evaluate them in putty.

Mojo.Log.error("****V" + " my variable: " + this.variable );

putty.exe
(for emulator)
ip address "localhost" port 5522
connection type: ssh

when command line opens type root
no password just hit enter

type: cat /var/log/messages | grep payment

"payment" is the string you are searching for with grep

after you log in to putty:
mojo.log.error writes to /var/log/messages

cat: types the file out
grep: searches it for the string following grep and prints out those lines
| (vertical bar): says pass the output of cat over to grep

SIDE NOTE: if you copy text into the clipboard, you can paste it into putty by right-clicking in putty.

Portal:webOS Applications

2009-09-27T15:44:03Z

G33kgirl: Add text and link to wiki formatting page

__notoc__
{{preware}}
{{portal-header
|The Instructions on [[Tutorials_webOS_Hello_World|building WebOS Mojo applications]] of your own are simple and straight forward.
}}
{{portal-header
|If you are looking for [[Portal:Patches_to_webOS|patches to modify existing webOS applications]] those are found in '''[[Portal:Patches_to_webOS|Patches to webOS]]'''.
}}
{{portal-three-columns
|column1=
* [[Portal:webOS_Applications_All|All]]
* [[Portal:webOS_Applications_Business|Business]]
* [[Portal:webOS_Applications_Communications|Communications]]
* [[Portal:webOS_Applications_Entertainment|Entertainment]]

|column2=
* [[Portal:webOS_Applications_Food|Food]]
* [[Portal:webOS_Applications_Games|Games]]
* [[Portal:webOS_Applications_Lifestyle|Lifestyle]]
* [[Portal:webOS_Applications_News|News]]

|column3=
* [[Portal:webOS_Applications_Social Networking|Social Networking]]
* [[Portal:webOS_Applications_Tutorial|Tutorial]]
* [[Portal:webOS_Applications_Utilities|Utilities]]
* [[Portal:webOS_Applications_Productivity|Productivity]]
}}
{{portal-two-columns
|column1=
== Tutorials ==

* [[Tutorials_webOS_Getting_Started|Getting Started Developing]]
* [[Tutorials_webOS_Hello_World|Building Your First Application]]
* [[Tutorials_webOS_Porting_Older_App|Porting older javascript apps]]
* [[Tutorials_webOS_IPKG_Installer|IPKG Installer]]
* [[Tutorials_webOS_Installing_An_Ipk|Installing an IPK]]
* [[Komodo|Komodo Specific Tutorials]]
* [[Tutorials_webOS_Loading_Existing_Apps_Into_An_Eclipse_Project|Loading Existing apps into an Eclipse Project]]
* [[Tutorials_webOS_Using Cookies|Using Cookies To Move Variables]]
* [[Tutorials_webOS_Debugging 101|Common Ways to Debug Your Application]]
* [[Tutorials_webOS_Getting_JSON_From_An_External_MySQL_Database|Getting JSON From An External MySQL Database]]
* [[Tutorials_Differences_between_Emulator_and_Pre|Diffences between Emulator and Pre]]

== Want to write a tutorial and Add it? ==

Just name the article like

"Tutorials webOS " + name

Ex: Tutorials_webOS_Getting_Started 
(spaces are the same thing as underscores)

==Need help formatting your text for wiki? ==
Find easy to use markup examples with visual representations on our formatting help pages.

[[Help:Formatting | Wiki Formatting Help]]

|column2=
== Policies about adding Applications ==

Your application can be any progress (Completed/Beta/Design Phase), just make sure you have a temporary name. For example if your application is called "Testing This":

<source lang="text">
{{portal-application-item
|name=Asteroids
|article=Asteroids
|user=AWESOM-O
|site=http://domain.com/asteroids/
|description=This is a short description, leave screenshots
and other details for the application page.
}}
</source>

Place this under the [[Portal:webOS Applications All|All webOS Application Portal]], and the category it goes under (for instance "Games" if it is a game). You can always change the applications name just make sure it is not taken and let us know on the [[Admin_Changes|Admin Changes]] page so we can delete the old application page (so others can use it).

}}
==Development Projects==
webOS Mojo and Multiple language projects being developed as open source by the community.

* [[Application:Preware|Preware]]: A mojo app with backend plugin to run ipkg and fetch over the air installs and updates from the Preware ipkg feed.
* [[On Screen Keyboard]]
* [[My notification|My notification]] : a Mojo app to enable the changing of system sounds and wallpaper.
* [[EBook-Reader]]: a Mojo app for reading text-oriented books on line.

== Development Proposals ==
These proposals for webOS applications lack a formal project at this time.
* [[Splash Application|Splash Application]]
* [[Proposal_to_install_Homebrew_apps_on_/media/internal_%28USB_partition%29]]

Help:Style Guide

2009-09-27T15:23:36Z

G33kgirl: added example text to give user visual reference of wiki code

== One Column ==
{{article-one-column-blue
|header1 = Example Once Column Layout
|column1 =
Example One Column Layout - Lorem ipsum dolor sit amet, test link adipiscing elit. Nullam dignissim convallis est. Quisque aliquam. Donec faucibus. Nunc iaculis suscipit dui. Nam sit amet sem. Aliquam libero nisi, imperdiet at, tincidunt nec, gravida vehicula, nisl. Praesent mattis, massa quis luctus fermentum, turpis mi volutpat justo, eu volutpat enim diam eget metus. Maecenas ornare tortor. Donec sed tellus eget sapien fringilla nonummy. Mauris a ante. Suspendisse quam sem, consequat at, commodo vitae, feugiat in, nunc. Morbi imperdiet augue quis tellus.
}}
<pre>
<source lang="text">
{{article-one-column-blue
|header1=Header
|column1=
Some text
}}
</source></pre>

== Two Columns ==
{{article-two-columns
|header1 = Example Once Column Layout
|width1=46%
|column1=
Example Two Column Layout - Lorem ipsum dolor sit amet, test link adipiscing elit. Nullam dignissim convallis est. Quisque aliquam. Donec faucibus. Nunc iaculis suscipit dui. Nam sit amet sem. Aliquam libero nisi, imperdiet at, tincidunt nec, gravida vehicula, nisl. Praesent mattis, massa quis luctus fermentum, turpis mi volutpat justo, eu volutpat enim diam eget metus. Maecenas ornare tortor. Donec sed tellus eget sapien fringilla nonummy. Mauris a ante. Suspendisse quam sem, consequat at, commodo vitae, feugiat in, nunc. Morbi imperdiet augue quis tellus.

|column2=
Example Two Column Layout - Lorem ipsum dolor sit amet, test link adipiscing elit. Nullam dignissim convallis est. Quisque aliquam. Donec faucibus. Nunc iaculis suscipit dui. Nam sit amet sem. Aliquam libero nisi, imperdiet at, tincidunt nec, gravida vehicula, nisl. Praesent mattis, massa quis luctus fermentum, turpis mi volutpat justo, eu volutpat enim diam eget metus. Maecenas ornare tortor. Donec sed tellus eget sapien fringilla nonummy. Mauris a ante. Suspendisse quam sem, consequat at, commodo vitae, feugiat in, nunc. Morbi imperdiet augue quis tellus.
}}

<pre>
<source lang="text">
{{article-two-columns
|width1=46%
|column1=
some content

|column2=
some other content
}}
</source></pre>

== Three Columns ==
{{article-three-columns
|width1=30%
|width2=30%
|column1=
Example Three Column Layout - Lorem ipsum dolor sit amet, test link adipiscing elit. Nullam dignissim convallis est. Quisque aliquam. Donec faucibus. Nunc iaculis suscipit dui. Nam sit amet sem. Aliquam libero nisi, imperdiet at, tincidunt nec, gravida vehicula, nisl. Praesent mattis, massa quis luctus fermentum, turpis mi volutpat justo, eu volutpat enim diam eget metus. Maecenas ornare tortor. Donec sed tellus eget sapien fringilla nonummy. Mauris a ante. Suspendisse quam sem, consequat at, commodo vitae, feugiat in, nunc. Morbi imperdiet augue quis tellus.

|column2=
Example Three Column Layout - Lorem ipsum dolor sit amet, test link adipiscing elit. Nullam dignissim convallis est. Quisque aliquam. Donec faucibus. Nunc iaculis suscipit dui. Nam sit amet sem. Aliquam libero nisi, imperdiet at, tincidunt nec, gravida vehicula, nisl. Praesent mattis, massa quis luctus fermentum, turpis mi volutpat justo, eu volutpat enim diam eget metus. Maecenas ornare tortor. Donec sed tellus eget sapien fringilla nonummy. Mauris a ante. Suspendisse quam sem, consequat at, commodo vitae, feugiat in, nunc. Morbi imperdiet augue quis tellus.

|column3=
Example Three Column Layout - Lorem ipsum dolor sit amet, test link adipiscing elit. Nullam dignissim convallis est. Quisque aliquam. Donec faucibus. Nunc iaculis suscipit dui. Nam sit amet sem. Aliquam libero nisi, imperdiet at, tincidunt nec, gravida vehicula, nisl. Praesent mattis, massa quis luctus fermentum, turpis mi volutpat justo, eu volutpat enim diam eget metus. Maecenas ornare tortor. Donec sed tellus eget sapien fringilla nonummy. Mauris a ante. Suspendisse quam sem, consequat at, commodo vitae, feugiat in, nunc. Morbi imperdiet augue quis tellus.
}}

<pre>
<source lang="text">
{{article-three-columns
|width1=30%
|width2=30%
|column1=
some content

|column2=
some other content

|column3=
some other content
}}
</source>
</pre>
== Code Blocks ==

To format code, use the source tag, which provides full syntax highlighting. Specify the language with the lang attribute, or if you don't want it to highlight syntax, use "text".

"python", "text", and "javascript" are the main ones, but [http://mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi#Supported_languages all major languages] are supported.

<pre>
<source lang="text">
Code or Text
</source>
</pre>

== Application Pages (Application:Name) ==

<source lang="text">
{{application
|name=Name - Name of the Application
|version=1.0.0 - Version major.minor.build
|type=webOS - "webOS" or "Linux"
|tag=Games - Use the main list's names
|screenshot=Application_Name_Screenshot_1.png - Pay attention to naming scheme Application_ + name + _Screenshot_1.png
|description=description - Describe the app in full detail, put anything you want.
}}
</source>

== Linux Penguin Icons! ==

They must be holding a webOS device (unless they are for another purpose, chat etc). If your page could use a linux penguin (only for Linux related articles sorry), feel free to use the template and one of the many Penguins. [[Template:Tux]]

Application:Preware

2009-09-27T14:47:41Z

G33kgirl:

{{application
|name=Preware
|type=webOS
|version=Version: Beta 0.9.0 (17 Sep 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.

== 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.

== 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 ===

Preware does not individually sequence dependencies during installation, and ipkgservice only runs the postinst and prerm scripts for the requested app, so if you have a depedency for the app that you're installing, and that dependency needs a postinst or prerm script to be run, then it will fail to run them. Please install the dependency first, and then install the app that you want. This will be fixed before the 1.0.0 version.

=== Known bugs ===

No known bugs.

== Installation ==

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

Note that you *must* use version 2.01 or later of WebOS Quick Install. Version 2.0 had a bug which causes the installation of the Package Management Service to fail, and Preware then hangs on the initial "Updating" screen. A re-installation with version 2.01 should fix that.

Please use the [http://forums.precentral.net/homebrew-apps/203951-webos-quick-install-contd.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 WebOS Quick Install for the very first installation of Preware.

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.

=== Installation Steps ===
* 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.

=== Updating ===

If you are running a version of the Preware prior to 0.9.0, then you must use the WebOS Quick Install program to upgrade the Package Manager Service.

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. When dependencies are supported, this restriction will be lifted.

=== 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.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.

<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>

}}

Tutorials webOS Debugging 101

2009-09-15T04:56:52Z

G33kgirl: adding/organizing debugging help for newbies

Add mojo.logs to your code and evaluate them in putty.

Mojo.Log.error("****V" + " my variable: " + this.variable );

putty.exe
(for emulator)
ip address "localhost" port 5522
connection type: ssh

when command line opens type root
no password just hit enter

type: cat /var/log/messages | grep payment

"payment" is the string you are searching for with grep

after you log in to putty:
mojo.log.error writes to /var/log/messages

cat: types the file out
grep: searches it for the string following grep and prints out those lines
| (vertical bar): says pass the output of cat over to grep

SIDE NOTE: if you copy text into the clipboard, you can paste it into putty by right-clicking in putty.

Tutorials webOS Debugging 101

2009-09-15T04:54:46Z

G33kgirl: adding/organizing debugging help for newbies

Add mojo.logs to your code and evaluate them in putty.

Mojo.Log.error("****V" + " my variable: " + this.variable );

putty.exe
(for emulator)
ip address "localhost" port 5522
connection type: ssh

when command line opens type root
no password just hit enter

type: cat /var/log/messages | grep payment

"payment" is the string you are searching for with grep

after you log in to putty:
mojo.log.error writes to /var/log/messages

cat: types the file out
grep: searches it for the string following grep and prints out those lines
| (vertical bar): says pass the output of cat over to grep

SIDE NOTE: if you copy text into the clipboard, you can paste it into putty by right-clicking in putty.

Portal:webOS Applications

2009-09-15T04:44:31Z

G33kgirl: /* Tutorials */

__notoc__
{{preware}}
{{portal-header
|The Instructions on [[Tutorials_webOS_Hello_World|building WebOS Mojo applications]] of your own are simple and straight forward.
}}
{{portal-header
|If you are looking for [[Portal:Patches_to_webOS|patches to modify existing webOS applications]] those are found in '''[[Portal:Patches_to_webOS|Patches to webOS]]'''.
}}
{{portal-three-columns
|column1=
* [[Portal:webOS_Applications_All|All]]
* [[Portal:webOS_Applications_Business|Business]]
* [[Portal:webOS_Applications_Communications|Communications]]
* [[Portal:webOS_Applications_Entertainment|Entertainment]]

|column2=
* [[Portal:webOS_Applications_Food|Food]]
* [[Portal:webOS_Applications_Games|Games]]
* [[Portal:webOS_Applications_Lifestyle|Lifestyle]]
* [[Portal:webOS_Applications_News|News]]

|column3=
* [[Portal:webOS_Applications_Social Networking|Social Networking]]
* [[Portal:webOS_Applications_Tutorial|Tutorial]]
* [[Portal:webOS_Applications_Utilities|Utilities]]
* [[Portal:webOS_Applications_Productivity|Productivity]]
}}
{{portal-two-columns
|column1=
== Tutorials ==

* [[Tutorials_webOS_Getting_Started|Getting Started Developing]]
* [[Tutorials_webOS_Hello_World|Building Your First Application]]
* [[Tutorials_webOS_Porting_Older_App|Porting older javascript apps]]
* [[Tutorials_webOS_IPKG_Installer|IPKG Installer]]
* [[Tutorials_webOS_Installing_An_Ipk|Installing an IPK]]
* [[Komodo|Komodo Specific Tutorials]]
* [[Tutorials_webOS_Loading_Existing_Apps_Into_An_Eclipse_Project|Loading Existing apps into an Eclipse Project]]
* [[Tutorials_webOS_Using Cookies|Using Cookies To Move Variables]]
* [[Tutorials_webOS_Debugging 101|Common Ways to Debug Your Application]]

== Want to write a tutorial and Add it? ==

Just name the article like

"Tutorials webOS " + name

Ex: Tutorials_webOS_Getting_Started 
(spaces are the same thing as underscores)

|column2=
== Policies about adding Applications ==

Your application can be any progress (Completed/Beta/Design Phase), just make sure you have a temporary name. For example if your application is called "Testing This":

<source lang="text">
{{portal-application-item
|name=Asteroids
|article=Asteroids
|user=AWESOM-O
|site=http://domain.com/asteroids/
|description=This is a short description, leave screenshots
and other details for the application page.
}}
</source>

Place this under the [[Portal:webOS Applications All|All webOS Application Portal]], and the category it goes under (for instance "Games" if it is a game). You can always change the applications name just make sure it is not taken and let us know on the [[Admin_Changes|Admin Changes]] page so we can delete the old application page (so others can use it).

}}
==Development Projects==
webOS Mojo and Multiple language projects being developed as open source by the community.

* [[Application:Preware|Preware]]: A mojo app with backend plugin to run ipkg and fetch over the air installs and updates from the Preware ipkg feed.
* [[On Screen Keyboard]]
* [[My notification|My notification]] : a Mojo app to enable the changing of system sounds and wallpaper.
* [[EBook-Reader]]: a Mojo app for reading text-oriented books on line.

== Development Proposals ==
These proposals for webOS applications lack a formal project at this time.
* [[Splash Application|Splash Application]]

Portal:webOS Applications

2009-09-15T04:42:18Z

G33kgirl: /* Tutorials */

__notoc__
{{preware}}
{{portal-header
|The Instructions on [[Tutorials_webOS_Hello_World|building WebOS Mojo applications]] of your own are simple and straight forward.
}}
{{portal-header
|If you are looking for [[Portal:Patches_to_webOS|patches to modify existing webOS applications]] those are found in '''[[Portal:Patches_to_webOS|Patches to webOS]]'''.
}}
{{portal-three-columns
|column1=
* [[Portal:webOS_Applications_All|All]]
* [[Portal:webOS_Applications_Business|Business]]
* [[Portal:webOS_Applications_Communications|Communications]]
* [[Portal:webOS_Applications_Entertainment|Entertainment]]

|column2=
* [[Portal:webOS_Applications_Food|Food]]
* [[Portal:webOS_Applications_Games|Games]]
* [[Portal:webOS_Applications_Lifestyle|Lifestyle]]
* [[Portal:webOS_Applications_News|News]]

|column3=
* [[Portal:webOS_Applications_Social Networking|Social Networking]]
* [[Portal:webOS_Applications_Tutorial|Tutorial]]
* [[Portal:webOS_Applications_Utilities|Utilities]]
* [[Portal:webOS_Applications_Productivity|Productivity]]
}}
{{portal-two-columns
|column1=
== Tutorials ==

* [[Tutorials_webOS_Getting_Started|Getting Started Developing]]
* [[Tutorials_webOS_Hello_World|Building Your First Application]]
* [[Tutorials_webOS_Porting_Older_App|Porting older javascript apps]]
* [[Tutorials_webOS_IPKG_Installer|IPKG Installer]]
* [[Tutorials_webOS_Installing_An_Ipk|Installing an IPK]]
* [[Komodo|Komodo Specific Tutorials]]
* [[Tutorials_webOS_Loading_Existing_Apps_Into_An_Eclipse_Project|Loading Existing apps into an Eclipse Project]]
* [[Tutorials_webOS_Using Cookies|Using Cookies To Move Variables]]
* [[Tutorials_webOS_Debugging 101|Common ways to debug your application]]

== Want to write a tutorial and Add it? ==

Just name the article like

"Tutorials webOS " + name

Ex: Tutorials_webOS_Getting_Started 
(spaces are the same thing as underscores)

|column2=
== Policies about adding Applications ==

Your application can be any progress (Completed/Beta/Design Phase), just make sure you have a temporary name. For example if your application is called "Testing This":

<source lang="text">
{{portal-application-item
|name=Asteroids
|article=Asteroids
|user=AWESOM-O
|site=http://domain.com/asteroids/
|description=This is a short description, leave screenshots
and other details for the application page.
}}
</source>

Place this under the [[Portal:webOS Applications All|All webOS Application Portal]], and the category it goes under (for instance "Games" if it is a game). You can always change the applications name just make sure it is not taken and let us know on the [[Admin_Changes|Admin Changes]] page so we can delete the old application page (so others can use it).

}}
==Development Projects==
webOS Mojo and Multiple language projects being developed as open source by the community.

* [[Application:Preware|Preware]]: A mojo app with backend plugin to run ipkg and fetch over the air installs and updates from the Preware ipkg feed.
* [[On Screen Keyboard]]
* [[My notification|My notification]] : a Mojo app to enable the changing of system sounds and wallpaper.
* [[EBook-Reader]]: a Mojo app for reading text-oriented books on line.

== Development Proposals ==
These proposals for webOS applications lack a formal project at this time.
* [[Splash Application|Splash Application]]

Resources

2009-09-08T15:53:01Z

G33kgirl: /* Web Sites */

== Web Sites==
Here's a list of websites with forums, tutorials, and general Palm Pre information.

* [http://developer.palm.com/ Palm webOSdev] - Offical Palm Pre Developer Site
* [http://www.PreCentral.net/ PreCentral] The most active Pre-centric forums and the largest source for homebrew apps. [[PreCentral|PreCentral]] Page has more details.
* [http://www.EverythingPre.com/ EverythingPre]
* [http://www.weboshelp.net/ webOShelp] - webOS Developer Site
* [http://www.PalmPre.org/ PalmPre] - Unofficial Palm Pre Fan site


==Programming Basics==
Sites with tutorials covering programming basics (HTML, CSS, Javascript)

===HTML===
* [http://www.w3schools.com/htmL/ w3c HTML Tutorial]
* [http://www.htmldog.com/guides/htmlbeginner/ HTML Beginner Tutorial]

===CSS===
* [http://www.w3schools.com/Css/default.asp/ w3c CSS Tutorial]
* [http://www.csstutorial.net/css_tutorial_part1.php/ The CSS Tutorial]
* [http://www.htmldog.com/guides/cssbeginner/ CSS Beginner Tutorial]

===JavaScript ===
* [http://www.w3schools.com/JS/default.asp/ w3c JavaScript Tutorial]
* [https://developer.mozilla.org/en/A_re-introduction_to_JavaScript/A re-introduction to JavaScript]
* [http://www.webteacher.com/javascript/JavaScript for the Total Non-Programmer]

 

==Books==

Palm webOS
 ''The Insider's Guide to Developing Applications in JavaScript using the Palm Mojo™ Framework''
 By Mitch Allen

JavaScript: The Good Parts
 ''Unearthing the Excellence in JavaScript ''
 By Douglas Crockford

Resources

2009-09-08T15:52:43Z

G33kgirl: /* Programming Basics */

== Web Sites==
Here's a list of websites with forums, tutorials, and general Palm Pre information.

* [http://developer.palm.com/ Palm webOSdev] - Offical Palm Pre Developer Site
* [http://www.PreCentral.net/ PreCentral] The most active Pre-centric forums and the largest source for homebrew apps. [[PreCentral|PreCentral]] Page has more details.
* [http://www.EverythingPre.com/ EverythingPre]
* [http://www.weboshelp.net/ webOShelp] - webOS Developer Site
* [http://www.PalmPre.org/ PalmPre] - Unofficial Palm Pre Fan site
* howard forums - Good for a wide variety of general phone / carrier info

==Programming Basics==
Sites with tutorials covering programming basics (HTML, CSS, Javascript)

===HTML===
* [http://www.w3schools.com/htmL/ w3c HTML Tutorial]
* [http://www.htmldog.com/guides/htmlbeginner/ HTML Beginner Tutorial]

===CSS===
* [http://www.w3schools.com/Css/default.asp/ w3c CSS Tutorial]
* [http://www.csstutorial.net/css_tutorial_part1.php/ The CSS Tutorial]
* [http://www.htmldog.com/guides/cssbeginner/ CSS Beginner Tutorial]

===JavaScript ===
* [http://www.w3schools.com/JS/default.asp/ w3c JavaScript Tutorial]
* [https://developer.mozilla.org/en/A_re-introduction_to_JavaScript/A re-introduction to JavaScript]
* [http://www.webteacher.com/javascript/JavaScript for the Total Non-Programmer]

 

==Books==

Palm webOS
 ''The Insider's Guide to Developing Applications in JavaScript using the Palm Mojo™ Framework''
 By Mitch Allen

JavaScript: The Good Parts
 ''Unearthing the Excellence in JavaScript ''
 By Douglas Crockford

Resources

2009-09-08T15:52:17Z

G33kgirl: /* Books */

== Web Sites==
Here's a list of websites with forums, tutorials, and general Palm Pre information.

* [http://developer.palm.com/ Palm webOSdev] - Offical Palm Pre Developer Site
* [http://www.PreCentral.net/ PreCentral] The most active Pre-centric forums and the largest source for homebrew apps. [[PreCentral|PreCentral]] Page has more details.
* [http://www.EverythingPre.com/ EverythingPre]
* [http://www.weboshelp.net/ webOShelp] - webOS Developer Site
* [http://www.PalmPre.org/ PalmPre] - Unofficial Palm Pre Fan site
* howard forums - Good for a wide variety of general phone / carrier info

==Programming Basics==
Sites with tutorials covering programming basics (HTML, CSS, Javascript)

===HTML===
* [http://www.w3schools.com/htmL/ w3c HTML Tutorial]
* [http://www.htmldog.com/guides/htmlbeginner/ HTML Beginner Tutorial]

===CSS===
* [http://www.w3schools.com/Css/default.asp/ w3c CSS Tutorial]
* [http://www.csstutorial.net/css_tutorial_part1.php/ The CSS Tutorial]
* [http://www.htmldog.com/guides/cssbeginner/ CSS Beginner Tutorial]

===JavaScript ===
* [http://www.w3schools.com/JS/default.asp/ w3c JavaScript Tutorial]
* [https://developer.mozilla.org/en/A_re-introduction_to_JavaScript/A re-introduction to JavaScript]
* [http://www.webteacher.com/javascript/JavaScript for the Total Non-Programmer]

 
==Books==

Palm webOS
 ''The Insider's Guide to Developing Applications in JavaScript using the Palm Mojo™ Framework''
 By Mitch Allen

JavaScript: The Good Parts
 ''Unearthing the Excellence in JavaScript ''
 By Douglas Crockford

Resources

2009-09-08T15:47:25Z

G33kgirl: /* Sites */

== Web Sites==
Here's a list of websites with forums, tutorials, and general Palm Pre information.

* [http://developer.palm.com/ Palm webOSdev] - Offical Palm Pre Developer Site
* [http://www.PreCentral.net/ PreCentral] The most active Pre-centric forums and the largest source for homebrew apps. [[PreCentral|PreCentral]] Page has more details.
* [http://www.EverythingPre.com/ EverythingPre]
* [http://www.weboshelp.net/ webOShelp] - webOS Developer Site
* [http://www.PalmPre.org/ PalmPre] - Unofficial Palm Pre Fan site
* howard forums - Good for a wide variety of general phone / carrier info

==Programming Basics==
Sites with tutorials covering programming basics (HTML, CSS, Javascript)

===HTML===
* [http://www.w3schools.com/htmL/ w3c HTML Tutorial]
* [http://www.htmldog.com/guides/htmlbeginner/ HTML Beginner Tutorial]

===CSS===
* [http://www.w3schools.com/Css/default.asp/ w3c CSS Tutorial]
* [http://www.csstutorial.net/css_tutorial_part1.php/ The CSS Tutorial]
* [http://www.htmldog.com/guides/cssbeginner/ CSS Beginner Tutorial]

===JavaScript ===
* [http://www.w3schools.com/JS/default.asp/ w3c JavaScript Tutorial]
* [https://developer.mozilla.org/en/A_re-introduction_to_JavaScript/A re-introduction to JavaScript]
* [http://www.webteacher.com/javascript/JavaScript for the Total Non-Programmer]

 
==Books==


Someone please clean this page up.

Mojo Storage Cookie

2009-09-07T21:09:44Z

G33kgirl:

Cookies are generally used to hold small amounts of information. A cookie can hold only ONE OBJECT. That object can be any javascript object (we will see some options later).

===Typical Uses For A Cookie===
Typical uses for a cookie include user configuration for a game or other application, login info, passing a variable from one file to the next, etc.

===Cookie Creation, Retrieval & Disposal===
When you want to use a cookie, the processes starts out the same regardless of if you have already used the cookie or not.

====Creating A New Cookie====
Set a variable to a new cookie object.

 ''Example: Setting a variable to a cookie object''
myCookie = new Mojo.Model.Cookie('reversi');

Here the name inside the call to Mojo.Model.Cookie names a unique cookie that will be linked to YOUR APPLICATION.

If the cookie was already created, "myCookie" will now be linked to it. However, if it does not exist, a new cookie is created.

"myCookie" now has three methods available 1).get 2).put 3).remove that you can use to place data into the cookie. Retrieve data out of the cookie. And dispose of the cookie altogether.

====What Can We Store In A Cookie?====
A cookie can store only one object. But that object can contain any type of variable. For instance, you can store a string "abc". You can store a number 123. And you can store the contents of a variable. That variable can contain an array which might have many values, but the VARIABLE itself is only one object.

You can also store a javascript object.

 ''Example: creation of a javascript object named "myObject"''

var myObject = {"name": "Fred", "Address": "123 w 4th St", "City": "Somewhere" }

====Putting Something Into The Cookie====
Above we created a variable named "myObject" that holds the data. Now, we can store the variable "myObject" in the "myCookie" object we created earlier using the '.put' method.

 ''Example: putting the contents of "myObject" into the cookie "myCookie"''
myCookie.put(myObject)

====Retrieving A Cookies Contents====
When you're ready to do something with that cookie's contents you will retrieve the object with the '.get' method.

 ''Example: retrieving a cookies content and placing it in an object''
someOtherObject = myCookie.get()

Now, we can just refer to that object's properties...

someOtherObject.name will now be "Fred" someOtherObject.city will be Somewhere.

Side note:
::{| style="color:blue; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|When you call the .get method, provided the cookie exists, and has data in it. You get the object that was stored in that cookie returned to you. However, if the cookie does NOT have data in it, the .get returns ''undefined''.

 ''Example: Retrieving a cookies content & testing if the cookies holds anything''

cookieObject = this.cookie.get()
if (cookieObject === undefined) {
//do something that sets defaults
} else {
// do something with the data in cookieObject.
}
|}

#So, create an object.
#Get it.
#Check if it's undefined. If it is, define it.
#Otherwise, grab the data and go on.
#If the data changes, PUT IT BACK.

====Throwing The Cookie Away====
To get rid of a cookie that you no longer want, call the remove method.

 ''Example: removing "myCookie"''
myCookie.remove.

===Javascript Object Notes===
Simple. Now, a couple of side notes. As was said above, you can store ANY object in a cookie. So, If all you want to do is store a single high score in a cookie, you can simply do

 ''Example: ''
myCookie = new Mojo.Model.Cookie('score');
myCookie.put(highScore);

Your app can create more than one cookie. You could for example do:

 ''Example: ''
levelCookie = new Mojo.Model.Cookie('level');
levelCookie.put(highScore);
scoreCookie = new Mojo.Model.Cookie('score');
scoreCookie.put(highScore);

Instead of putting score and level into a single object as above. There is no particular advantage or disadvantage to either technique, it is a style preference. Note that in WEB programming, a site creating more than one cookie is considered impolite. This is not an issue ''inside the phone''. In any case, the cookies are tied directly to your app, and the data is not available to other apps.

 More information on Mojo Cookies can be found here: 
http://developer.palm.com/palm-sdk/jsdoc/symbols/Mojo.Model.Cookie.html
 http://www.webos-internals.org/wiki/Tutorials_webOS_Using_Cookies

Tutorials webOS Using Cookies

2009-09-07T21:08:36Z

G33kgirl:

==Using Cookies To Move Variables To Different Scenes==

This is my non-technical take on how to make cookies for the WebOS

In life if you want to make a special cookie there's an order you need to follow.

# Name your cookie
# Make your cookie and put it into a container
# Move your cookie container to the new room
# Get your cookies and share them
 
In the following example I want to move a variable stored in “this.numBalance” over to my second scene.

 The javascript file for the first scene (first-assistant.js) holds the variable (this.numBalance) I want to move and use in the next scene (second-assistant.js). The event that will push the variable to the next scene is a button click, so I would place the cookie code into my " FirstAssistant.prototype.handleClicked = function".

 Here’s the variable to be pushed to the next scene

this.numBalance = this.nBalancemodel.value;
 
Next create a cookie named this.numBalanceCookie in the cookies system and then associate the cookie with the property of the current scene. All this does is name your cookie. No values have been placed inside of it.

this.numBalanceCookie = new Mojo.Model.Cookie("numBalance");

 Next put the this.numBalance variable into the this.numBalanceCookie. In this example I'm using an if statement to first check if the variable is not empty then put its value into the numBalanceCookie.

if (this.numBalance != '') {
this.numBalanceCookie.put(this.numBalance);
}

 In the second-assistant.js file's setup function (Second Assistant.prototype.setup = function) retrieve and use the cookie’s variable.

 You need to still create a cookie named this.numBalanceCookie in this scene’s cookies system and associate it to the current scene.

this.numBalanceCookie = new Mojo.Model.Cookie("numBalance");

 Now you can retrieve the cookie’s (this.numBalanceCookie) value with the get function and place the value into a new variable (this.numBalance).

this.numBalance = this.numBalanceCookie.get();

 Now you can use the this.numBalance variable

 In this example we used two of the three methods available in the Mojo.Model.Cookie Class
 

The methods available are:

:;get()
::Returns the object stored in this cookie, or undefined if no such cookie exists
:;put()
::Creates or updates the value of this cookie.
:;remove()
::Deletes this cookie.

 More information on Mojo Cookies can be found here: 
http://developer.palm.com/palm-sdk/jsdoc/symbols/Mojo.Model.Cookie.html
 http://www.webos-internals.org/wiki/Mojo_Storage_Cookie

Mojo Storage Cookie

2009-09-07T20:09:17Z

G33kgirl:

Mojo Storage Cookie

2009-09-07T19:52:46Z

G33kgirl:

Cookies are generally used to hold small amounts of information. A cookie can hold only ONE OBJECT. That object can be any javascript object (we will see some options later).

===Typical Uses For A Cookie===
Typical uses for a cookie include user configuration for a game or other application, login info, passing a variable from one file to the next, etc.

===Cookie Creation, Retrieval & Disposal===
When you want to use a cookie, the processes starts out the same regardless of if you have already used the cookie or not.

====Creating A New Cookie====
Set a variable to a new cookie object.

 ''Example: Setting a variable to a cookie object''
myCookie = new Mojo.Model.Cookie('reversi');

Here the name inside the call to Mojo.Model.Cookie names a unique cookie that will be linked to YOUR APPLICATION.

If the cookie was already created, "myCookie" will now be linked to it. However, if it does not exist, a new cookie is created.

"myCookie" now has three methods available 1).get 2).put 3).remove that you can use to place data into the cookie. Retrieve data out of the cookie. And dispose of the cookie altogether.

====What Can We Store In A Cookie?====
A cookie can store only one object. But that object can contain any type of variable. For instance, you can store a string "abc". You can store a number 123. And you can store the contents of a variable. That variable can contain an array which might have many values, but the VARIABLE itself is only one object.

You can also store a javascript object.

 ''Example: creation of a javascript object named "myObject"''

var myObject = {"name": "Fred", "Address": "123 w 4th St", "City": "Somewhere" }

====Putting Something Into The Cookie====
Above we created a variable named "myObject" that holds the data. Now, we can store the variable "myObject" in the "myCookie" object we created earlier using the '.put' method.

 ''Example: putting the contents of "myObject" into the cookie "myCookie"''
myCookie.put(myObject)

====Retrieving A Cookies Contents====
When you're ready to do something with that cookie's contents you will retrieve the object with the '.get' method.

 ''Example: retrieving a cookies content and placing it in an object''
someOtherObject = myCookie.get()

Now, we can just refer to that object's properties...

someOtherObject.name will now be "Fred" someOtherObject.city will be Somewhere.

Side note:
::{| style="color:blue; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|When you call the .get method, provided the cookie exists, and has data in it. You get the object that was stored in that cookie returned to you. However, if the cookie does NOT have data in it, the .get returns ''undefined''.

 ''Example: Retrieving a cookies content & testing if the cookies holds anything''

cookieObject = this.cookie.get()
if (cookieObject === undefined) {
//do something that sets defaults
} else {
// do something with the data in cookieObject.
}
|}

When you call the .get method, provided the cookie exists, and has data in it. You get the object that was stored in that cookie returned to you. However, if the cookie does NOT have data in it, the .get returns ''undefined''.

 ''Example: Retrieving a cookies content & testing if the cookies holds anything''

cookieObject = this.cookie.get()
if (cookieObject === undefined) {
//do something that sets defaults
} else {
// do something with the data in cookieObject.
}

#So, create an object.
#Get it.
#Check if it's undefined. If it is, define it.
#Otherwise, grab the data and go on.
#If the data changes, PUT IT BACK.

====Throwing The Cookie Away====
To get rid of a cookie that you no longer want, call the remove method.

 ''Example: removing "myCookie"''
myCookie.remove.

===Javascript Object Notes===
Simple. Now, a couple of side notes. As was said above, you can store ANY object in a cookie. So, If all you want to do is store a single high score in a cookie, you can simply do

 ''Example: ''
myCookie = new Mojo.Model.Cookie('score');
myCookie.put(highScore);

Your app can create more than one cookie. You could for example do:

 ''Example: ''
levelCookie = new Mojo.Model.Cookie('level');
levelCookie.put(highScore);
scoreCookie = new Mojo.Model.Cookie('score');
scoreCookie.put(highScore);

Instead of putting score and level into a single object as above. There is no particular advantage or disadvantage to either technique, it is a style preference. Note that in WEB programming, a site creating more than one cookie is considered impolite. This is not an issue ''inside the phone''. In any case, the cookies are tied directly to your app, and the data is not available to other apps.

Mojo Storage Cookie

2009-09-07T19:51:05Z

G33kgirl:

Cookies are generally used to hold small amounts of information. A cookie can hold only ONE OBJECT. That object can be any javascript object (we will see some options later).

===Typical Uses For A Cookie===
Typical uses for a cookie include user configuration for a game or other application, login info, passing a variable from one file to the next, etc.

===Cookie Creation, Retrieval & Disposal===
When you want to use a cookie, the processes starts out the same regardless of if you have already used the cookie or not.

====Creating A New Cookie====
Set a variable to a new cookie object.

 ''Example: Setting a variable to a cookie object''
myCookie = new Mojo.Model.Cookie('reversi');

Here the name inside the call to Mojo.Model.Cookie names a unique cookie that will be linked to YOUR APPLICATION.

If the cookie was already created, "myCookie" will now be linked to it. However, if it does not exist, a new cookie is created.

"myCookie" now has three methods available 1).get 2).put 3).remove that you can use to place data into the cookie. Retrieve data out of the cookie. And dispose of the cookie altogether.

====What Can We Store In A Cookie?====
A cookie can store only one object. But that object can contain any type of variable. For instance, you can store a string "abc". You can store a number 123. And you can store the contents of a variable. That variable can contain an array which might have many values, but the VARIABLE itself is only one object.

You can also store a javascript object.

 ''Example: creation of a javascript object named "myObject"''

var myObject = {"name": "Fred", "Address": "123 w 4th St", "City": "Somewhere" }

====Putting Something Into The Cookie====
Above we created a variable named "myObject" that holds the data. Now, we can store the variable "myObject" in the "myCookie" object we created earlier using the '.put' method.

 ''Example: putting the contents of "myObject" into the cookie "myCookie"''
myCookie.put(myObject)

====Retrieving A Cookies Contents====
When you're ready to do something with that cookie's contents you will retrieve the object with the '.get' method.

 ''Example: retrieving a cookies content and placing it in an object''
someOtherObject = myCookie.get()

Now, we can just refer to that object's properties...

someOtherObject.name will now be "Fred" someOtherObject.city will be Somewhere.

Side note:
::{| style="color:blue; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|When you call the .get method, provided the cookie exists, and has data in it. You get the object that was stored in that cookie returned to you. However, if the cookie does NOT have data in it, the .get returns ''undefined''.

 ''Example: Retrieving a cookies content & testing if the cookies holds anything''

cookieObject = this.cookie.get()
if (cookieObject === undefined) {
//do something that sets defaults
} else {
// do something with the data in cookieObject.
}
|}

When you call the .get method, provided the cookie exists, and has data in it. You get the object that was stored in that cookie returned to you. However, if the cookie does NOT have data in it, the .get returns ''undefined''.

 ''Example: Retrieving a cookies content & testing if the cookies holds anything''

cookieObject = this.cookie.get()
if (cookieObject === undefined) {
//do something that sets defaults
} else {
// do something with the data in cookieObject.
}

#So, create an object.
#Get it.
#Check if it's undefined. If it is, define it.
#Otherwise, grab the data and go on.
#If the data changes, PUT IT BACK.

====Throwing The Cookie Away====
To get rid of a cookie that you no longer want, call the remove method.

 ''Example: removing "myCookie"''
myCookie.remove.

===Javascript Object Notes===
Simple. Now, a couple of side notes. As was said above, you can store ANY object in a cookie. So, If all you want to do is store a single high score in a cookie, you can simply do

 ''Example: ''
myCookie = new Mojo.Model.Cookie('score');
myCookie.put(highScore);

Your app can create more than one cookie. You could for example do:

 ''Example: ''
levelCookie = new Mojo.Model.Cookie('level');
levelCookie.put(highScore);
scoreCookie = new Mojo.Model.Cookie('score');
scoreCookie.put(highScore);

Instead of putting score and level into a single object as above. There is no particular advantage or disadvantage to either technique, it is a style preference. Note that in WEB programming, a site creating more than one cookie is considered impolite. This is not an issue ''inside the phone''. In any case, the cookies are tied directly to your app, and the data is not available to other apps.

Mojo Storage Cookie

2009-09-07T19:45:49Z

G33kgirl:

Cookies are generally used to hold small amounts of information. A cookie can hold only ONE OBJECT. That object can be any javascript object (we will see some options later).

===Typical Uses For A Cookie===
Typical uses for a cookie include user configuration for a game or other application, login info, passing a variable from one file to the next, etc.

===Cookie Creation, Retrieval & Disposal===
When you want to use a cookie, the processes starts out the same regardless of if you have already used the cookie or not.
====Creating A New Cookie====
Set a variable to a cookie object.
 ''Example: Setting a variable to a cookie object''
myCookie = new Mojo.Model.Cookie('reversi');

Here the name inside the call to Mojo.Model.Cookie names a unique cookie that will be linked to YOUR APPLICATION.

If the cookie was already created, "myCookie" will now be linked to it. However, if it does not exist, a new cookie is created.

"myCookie" now has three methods available
;#.get
;#.put
;#.remove

====What Can We Store In A Cookie?====

A cookie can store only one object. But that object can contain any type of variable. For instance, you can store a string "abc". You can store a number 123. And you can store the contents of a variable. That variable can contain an array which might have many values, but the VARIABLE itself is only one object.

You can also store a javascript object.

 ''Example: creation of a javascript object named "myObject"''

var myObject = {"name": "Fred", "Address": "123 w 4th St", "City": "Somewhere" }

====Putting Something Into The Cookie====
Above we created a variable named "myObject" that holds the data. Now, we can store the variable "myObject" in the "myCookie" object we created earlier using the '.put' method.

 ''Example: putting the contents of "myObject" into the cookie "myCookie"''
myCookie.put(myObject)

====Retrieving A Cookies Contents====
When you're ready to do something with that cookie's contents you will retrieve the object with the '.get' method.

 ''Example: retrieving a cookies content and placing it in an object''
someOtherObject = myCookie.get()

Now, we can just refer to that object's properties...

someOtherObject.name will now be "Fred" someOtherObject.city will be Somewhere.

Side note:
::{| style="color:blue; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|When you call the .get method, provided the cookie exists, and has data in it. You get the object that was stored in that cookie returned to you. However, if the cookie does NOT have data in it, the .get returns ''undefined''.

 ''Example: Retrieving a cookies content & testing if the cookies holds anything''

cookieObject = this.cookie.get()
if (cookieObject === undefined) {
//do something that sets defaults
} else {
// do something with the data in cookieObject.
}
|}

When you call the .get method, provided the cookie exists, and has data in it. You get the object that was stored in that cookie returned to you. However, if the cookie does NOT have data in it, the .get returns ''undefined''.

 ''Example: Retrieving a cookies content & testing if the cookies holds anything''

cookieObject = this.cookie.get()
if (cookieObject === undefined) {
//do something that sets defaults
} else {
// do something with the data in cookieObject.
}

#So, create an object.
#Get it.
#Check if it's undefined. If it is, define it.
#Otherwise, grab the data and go on.
#If the data changes, PUT IT BACK.

====Throwing The Cookie Away====
To get rid of a cookie that you no longer want, call the remove method.

 ''Example: removing "myCookie"''
myCookie.remove.

===Javascript Object Notes===
Simple. Now, a couple of side notes. As was said above, you can store ANY object in a cookie. So, If all you want to do is store a single high score in a cookie, you can simply do

 ''Example: ''
myCookie = new Mojo.Model.Cookie('score');
myCookie.put(highScore);

Your app can create more than one cookie. You could for example do:

 ''Example: ''
levelCookie = new Mojo.Model.Cookie('level');
levelCookie.put(highScore);
scoreCookie = new Mojo.Model.Cookie('score');
scoreCookie.put(highScore);

Instead of putting score and level into a single object as above. There is no particular advantage or disadvantage to either technique, it is a style preference. Note that in WEB programming, a site creating more than one cookie is considered impolite. This is not an issue ''inside the phone''. In any case, the cookies are tied directly to your app, and the data is not available to other apps.

Tutorials webOS Using Cookies

2009-09-07T17:31:13Z

G33kgirl: New page: ==Using Cookies To Move Variables To Different Scenes== This is my non-technical take on how to make cookies for the WebOS In life if you want to make a special cookie there's an order y...

==Using Cookies To Move Variables To Different Scenes==

This is my non-technical take on how to make cookies for the WebOS

In life if you want to make a special cookie there's an order you need to follow.

# Name your cookie
# Make your cookie and put it into a container
# Move your cookie container to the new room
# Get your cookies and share them
 
In the following example I want to move a variable stored in “this.numBalance” over to my second scene.

 The javascript file for the first scene (first-assistant.js) holds the variable (this.numBalance) I want to move and use in the next scene (second-assistant.js). The event that will push the variable to the next scene is a button click, so I would place the cookie code into my " FirstAssistant.prototype.handleClicked = function".

 Here’s the variable to be pushed to the next scene

this.numBalance = this.nBalancemodel.value;
 
Next create a cookie named this.numBalanceCookie in the cookies system and then associate the cookie with the property of the current scene. All this does is name your cookie. No values have been placed inside of it.

this.numBalanceCookie = new Mojo.Model.Cookie("numBalance");

 Next put the this.numBalance variable into the this.numBalanceCookie. In this example I'm using an if statement to first check if the variable is not empty then put its value into the numBalanceCookie.

if (this.numBalance != '') {
this.numBalanceCookie.put(this.numBalance);
}

 In the second-assistant.js file's setup function (Second Assistant.prototype.setup = function) retrieve and use the cookie’s variable.

 You need to still create a cookie named this.numBalanceCookie in this scene’s cookies system and associate it to the current scene.

this.numBalanceCookie = new Mojo.Model.Cookie("numBalance");

 Now you can retrieve the cookie’s (this.numBalanceCookie) value with the get function and place the value into a new variable (this.numBalance).

this.numBalance = this.numBalanceCookie.get();

 Now you can use the this.numBalance variable

 In this example we used two of the three methods available in the Mojo.Model.Cookie Class
 

The methods available are:

:;get()
::Returns the object stored in this cookie, or undefined if no such cookie exists
:;put()
::Creates or updates the value of this cookie.
:;remove()
::Deletes this cookie.

 More information on Mojo Cookies can be found here:
http://developer.palm.com/palm-sdk/jsdoc/symbols/Mojo.Model.Cookie.html

Portal:webOS Applications

2009-09-07T14:55:10Z

G33kgirl: /* Tutorials */

__notoc__
{{preware}}
{{portal-header
|The Instructions on [[Tutorials_webOS_Hello_World|building WebOS Mojo applications]] of your own are simple and straight forward.
}}
{{portal-header
|If you are looking for [[Portal:Patches_to_webOS|patches to modify existing webOS applications]] those are found in '''[[Portal:Patches_to_webOS|Patches to webOS]]'''.
}}
{{portal-three-columns
|column1=
* [[Portal:webOS_Applications_All|All]]
* [[Portal:webOS_Applications_Business|Business]]
* [[Portal:webOS_Applications_Communications|Communications]]
* [[Portal:webOS_Applications_Entertainment|Entertainment]]

|column2=
* [[Portal:webOS_Applications_Food|Food]]
* [[Portal:webOS_Applications_Games|Games]]
* [[Portal:webOS_Applications_Lifestyle|Lifestyle]]
* [[Portal:webOS_Applications_News|News]]

|column3=
* [[Portal:webOS_Applications_Social Networking|Social Networking]]
* [[Portal:webOS_Applications_Tutorial|Tutorial]]
* [[Portal:webOS_Applications_Utilities|Utilities]]
* [[Portal:webOS_Applications_Productivity|Productivity]]
}}
{{portal-two-columns
|column1=
== Tutorials ==

* [[Tutorials_webOS_Getting_Started|Getting Started Developing]]
* [[Tutorials_webOS_Hello_World|Building Your First Application]]
* [[Tutorials_webOS_Porting_Older_App|Porting older javascript apps]]
* [[Tutorials_webOS_IPKG_Installer|IPKG Installer]]
* [[Tutorials_webOS_Installing_An_Ipk|Installing an IPK]]
* [[Tutorials_webOS_Loading_Existing_Apps_Into_An_Eclipse_Project|Loading Existing apps into an Eclipse Project]]
* [[Tutorials_webOS_Using Cookies|Using Cookies To Move Variables]]

== Want to write a tutorial and Add it? ==

Just name the article like

"Tutorials webOS " + name

Ex: Tutorials_webOS_Getting_Started 
(spaces are the same thing as underscores)

|column2=
== Policies about adding Applications ==

Your application can be any progress (Completed/Beta/Design Phase), just make sure you have a temporary name. For example if your application is called "Testing This":

<source lang="text">
{{portal-application-item
|name=Asteroids
|article=Asteroids
|user=AWESOM-O
|site=http://domain.com/asteroids/
|description=This is a short description, leave screenshots
and other details for the application page.
}}
</source>

Place this under the [[Portal:webOS Applications All|All webOS Application Portal]], and the category it goes under (for instance "Games" if it is a game). You can always change the applications name just make sure it is not taken and let us know on the [[Admin_Changes|Admin Changes]] page so we can delete the old application page (so others can use it).

}}
==Development Projects==
webOS Mojo and Multiple language projects being developed as open source by the community.

* [[Application:Preware|Preware]]: A mojo app with backend plugin to run ipkg and fetch over the air installs and updates from the Preware ipkg feed.
* [[On Screen Keyboard]]
* [[My notification|My notification]] : a Mojo app to enable the changing of system sounds and wallpaper.
* [[EBook-Reader]]: a Mojo app for reading text-oriented books on line.

== Development Proposals ==
These proposals for webOS applications lack a formal project at this time.
* [[Splash Application|Splash Application]]