Ok this helps a lot.

On Apr 8, 12:06 pm, Apurv Gupta <apurv.gu...@gmail.com> wrote:
> You can't update appData using server side templates. You should do this
> interaction on the canvas view.One option [which requires upcoming view
> param support in NavigateToApp] is to set these as parameters to canvas
> view, and perform the action there.
>
> On Wed, Apr 8, 2009 at 8:43 PM, Christopher (adoring husband) <
>
> markite...@gmail.com> wrote:
>
> > Ok thanks so much for the help. I'm starting to get it. I know
> > templates will be super easy once i see how to do what im trying to
> > do.
>
> > How would I update a person's appdata from the app. For example: a
> > user clicks a button and a new value is stored for a given key.
>
> > thanks!
>
> > On Apr 5, 9:28 pm, Apurv Gupta <apurv.gu...@gmail.com> wrote:
> > > On Mon, Apr 6, 2009 at 3:35 AM, Markitecht <markite...@gmail.com> wrote:
>
> > > > So if i'm reading this right, *no* javascript will be allowed on
> > > > profile views in the future.
>
> > > > How can the app make calls to the datastore?
>
> > > > Where is 'newFetchPersonAppDataRequest' replaced, for example?
>
> > > <os:PersonAppDataRequest key="keyname" method="appdata.get"
> > > userId="@owner"/>
>
> > > > I'm very new to templates and wish to get my (successful and highly
> > > > popular) app back on track. Losing installs is no fun.
>
> > > > thanks,
> > > > Christopher
>
> > > > ps. from docs:
> > > > "2.1.1 Limitations
> > > > An OST implementation can fetch, inject, cache, and store data
> > > > requests for the application before any client side code executes. OST
> > > > does not represent a full replacement for JavaScript. OST assumes that
> > > > applications can fallback to JavaScript whenever a combination of
> > > > application and container cannot make use of a given OST feature."
>
> > > > ...seems like a contradiction to be depracating *any* use of
> > > > javascript immediately before OST can sufficiently replace the
> > > > necessary functionality.
>
> > > > pps. does any of this seem super weird to anyone? Goog has such
> > > > consistent policies about backward-compatibility. OS developers jumped
> > > > through hoops, contributed to the community for months before being
> > > > able to publish apps and were super patient as goog wrestled with the
> > > > launch of OS on Orkut. Now we lose Profile views? and can't use .js or
> > > > Flash at all when we get them back (provided we can get up to speed on
> > > > this template thing)? I don't mean to be a bother, but this appears
> > > > strangely out of step with how Goog usually does business, especially
> > > > with regard to the developer community.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Orkut Developer Forum" group.
To post to this group, send email to opensocial-orkut@googlegroups.com
To unsubscribe from this group, send email to 
opensocial-orkut+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/opensocial-orkut?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to