Mojo Storage Cookie - Revision history

Darkmagister at 02:18, 12 December 2011

2011-12-12T02:18:36Z

G33kgirl at 21:09, 7 September 2009

2009-09-07T21:09:44Z

G33kgirl at 20:09, 7 September 2009

2009-09-07T20:09:17Z

G33kgirl at 19:52, 7 September 2009

2009-09-07T19:52:46Z

G33kgirl at 19:51, 7 September 2009

2009-09-07T19:51:05Z

G33kgirl at 19:45, 7 September 2009

2009-09-07T19:45:49Z

Rboatright: 2

2009-08-30T12:30:41Z

Rboatright: 2

2009-08-30T05:24:10Z

Rboatright: create

2009-08-30T05:21:47Z

create

Rboatright: cookies

2009-08-30T05:20:47Z

New page

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

Typical uses for a cookie include User configuration for a game or other app, login info, etc.

When you want to use a cookie, the processes starts out the same no matter if you have already used a cookie or now.

You must set a variable to a cookie object. This is simple:

this.cookie = new Mojo.Model.Cookie('reversi');

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

If the cookie already exists, this.cookie is linked to it. If it does not exist, a new cookie is created.

this.cookie now has two important methods available. .get and .put

If you call .get, if the cookie exists, and has data in it, you get the object that was stored in the cookie returned to you. If the cookie does NOT have data in it, the .get returns undefined.

So, you can do:

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

What can we store in a cookie? A cookie can store one object. You can store a string "abc". You can store a number 123, you can store the contents of a variable. That variable can contain an array which might have many values, but the VARIABLE is one object.

You can also store a javascript object. For example:

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

now, we can store myObject in a cookie using the other call to the cookie we created earlier:

this.cookie.put(myObject)

stores myObject into the cookie.

Now, we can retrieve the object with

someOtherObect = this.cookie.get()

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

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

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.

SImple

@@ Line 91: / Line 91: @@
 <br>More information on Mojo Cookies can be found here:<br>
-http://developer.palm.com/palm-sdk/jsdoc/symbols/Mojo.Model.Cookie.html
+https://developer.palm.com/content/api/reference/mojo/classes/mojo-model-cookie.html
 <br>http://www.webos-internals.org/wiki/Tutorials_webOS_Using_Cookies

← Older revision		Revision as of 21:09, 7 September 2009
Line 88:		Line 88:

	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.		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.
		+
		+
		+	<br>More information on Mojo Cookies can be found here:<br>
		+	http://developer.palm.com/palm-sdk/jsdoc/symbols/Mojo.Model.Cookie.html
		+	<br>http://www.webos-internals.org/wiki/Tutorials_webOS_Using_Cookies

← Older revision		Revision as of 20:09, 7 September 2009
Line 58:		Line 58:
	}		}
	\|}		\|}
−
−
−	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''.
−
−	~~<br>''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.~~
−	}

@@ Line 31: / Line 31: @@
 ====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.
 <br>''Example: putting the contents of "myObject" into the cookie "myCookie"''
@@ Line 38: / Line 37: @@
 ====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.
 <br>''Example: retrieving a cookies content and placing it in an object''
@@ Line 46: / Line 44: @@
 someOtherObject.name will now be "Fred"    someOtherObject.city will be Somewhere.
 Side note:

@@ Line 6: / Line 6: @@
 ===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.
+Set a variable to a new cookie object.
 <br>''Example: Setting a variable to a cookie object''
   myCookie = new Mojo.Model.Cookie('reversi');
@@ Line 15: / Line 17: @@
 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
+"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.
@@ Line 89: / Line 86: @@
 <br>''Example: removing "myCookie"''
   myCookie.remove.
 ===Javascript Object Notes===

@@ Line 1: / Line 1: @@
-Cookies are generally used to hold small amounts of information.  A cookie may hold ONE OBJECT.  That object can be any javascript object (we will see some options later) but the cookie can hold only one.
+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 include User configuration for a game or other app, login info, etc.
+===Typical Uses For A Cookie===
-When you want to use a cookie, the processes starts out the same no matter if you have already used a cookie or now.
+===Cookie Creation, Retrieval & Disposal===
-You must set a variable to a cookie object.    This is simple:
+Here the name inside the call to Mojo.Model.Cookie names a unique cookie that will be linked to YOUR APPLICATION.
-  myCookie = new Mojo.Model.Cookie('reversi');
+If the cookie was already created, "myCookie" will now be linked to it.  However, if it does not exist, a new cookie is created.
-the name inside the call to Mojo.Model.Cookie names a unique cookie that will be linked to YOUR APP.
+"myCookie" now has three methods available
-myCookie  now has three methods available.  .get  .put  and .remove
+====What Can We Store In A Cookie?====
-If you call .get, if the cookie exists, and has data in it, you get the object that was stored in the cookie returned to you.  If the cookie does NOT have data in it, the .get returns undefined.
+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.
-So,   you can do:
+You can also store a javascript object.
- cookieObject = this.cookie.get()
+<br>''Example: creation of a javascript object named "myObject"''
-What can we store in a cookie?    A cookie can store one object.  You can store a string "abc".  You can store a number  123,  you can store the contents of a variable.  That variable can contain an array which might have many values, but the VARIABLE is one object.
+  var myObject = {"name": "Fred", "Address": "123 w 4th St", "City": "Somewhere" }
- var myObject = {"name": "Fred", "Address": "123 w 4th St", "City": "Somewhere" }
+====Putting Something Into The Cookie====
   myCookie.put(myObject)
-stores myObject into the cookie.
+====Retrieving A Cookies Contents====
-  someOtherObect = myCookie.get()
+<br>''Example: retrieving a cookies content and placing it in an object''
-now, we can just refer to that object's properties...
+Now, we can just refer to that object's properties...
 someOtherObject.name will now be "Fred"    someOtherObject.city will be Somewhere.
 To get rid of a cookie that you no longer want, call the remove method.
   myCookie.remove.
 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
   myCookie = new Mojo.Model.Cookie('score');
   myCookie.put(highScore);
@@ Line 63: / Line 100: @@
 Your app can create more than one cookie.  You could for example do:
   levelCookie = new Mojo.Model.Cookie('level');
   levelCookie.put(highScore);

@@ Line 7: / Line 7: @@
 You must set a variable to a cookie object.    This is simple:
-  this.cookie = new Mojo.Model.Cookie('reversi');
+  myCookie = new Mojo.Model.Cookie('reversi');
 the name inside the call to Mojo.Model.Cookie names a unique cookie that will be linked to YOUR APP.
-If the cookie already exists, this.cookie is linked to it.  If it does not exist, a new cookie is created.
+If the cookie already exists, myCookie is linked to it.  If it does not exist, a new cookie is created.
-this.cookie  now has two important methods available.  .get and .put
+myCookie  now has three methods available.  .get  .put  and .remove
 If you call .get, if the cookie exists, and has data in it, you get the object that was stored in the cookie returned to you.  If the cookie does NOT have data in it, the .get returns undefined.
@@ Line 34: / Line 34: @@
 now, we can store myObject in a cookie using the other call to the cookie we created earlier:
-  this.cookie.put(myObject)
+  myCookie.put(myObject)
 stores myObject into the cookie.
@@ Line 40: / Line 40: @@
 Now, we can retrieve the object with
-  someOtherObect = this.cookie.get()
+  someOtherObect = myCookie.get()
 now, we can just refer to that object's properties...
@@ Line 52: / Line 52: @@
 If the data changes, PUT IT BACK.
-SImple
+To get rid of a cookie that you no longer want, call the remove method.

@@ Line 19: / Line 19: @@
 So,   you can do:
-cookieObject = this.cookie.get()
+ cookieObject = this.cookie.get()
-if (cookieObject === undefined)  {
+ if (cookieObject === undefined)  {
       //do something that sets defaults
-} else {
+ } else {
      //  do something with the data in cookieObject.
-−
+ }
 What can we store in a cookie?    A cookie can store one object.  You can store a string "abc".  You can store a number  123,  you can store the contents of a variable.  That variable can contain an array which might have many values, but the VARIABLE is one object.