wish to provide
per gadget url preferences you can just ignore they siteid and return or
persist the preferences for all gadgets coming from that url.
From: daviesd davi...@oclc.org
To: dev@shindig.apache.org,
Date: 07/27/2011 03:22 PM
Subject:Re: Example implementation
container code changing the id of the site.
-daviesd davi...@oclc.org wrote: -
To: dev@shindig.apache.org
From: daviesd davi...@oclc.org
Date: 08/02/2011 12:02PM
Cc: Dan Dumont/Westford/IBM@Lotus
Subject: Re: Example implementation for user prefs?
Dan,
Have you seen an timing issues
: daviesd davi...@oclc.org
To: dev@shindig.apache.org,
Date: 07/28/2011 11:55 AM
Subject:Re: Example implementation for user prefs?
Jesse,
I think you are correct that it should be per instance. That's where the
siteid would come into play. At least that's how I'm reading
developerWorks Profile
From: daviesd davi...@oclc.org
To: dev@shindig.apache.org,
Date: 07/28/2011 11:55 AM
Subject:Re: Example implementation for user prefs?
Jesse,
I think you are correct that it should be per instance. That's where the
siteid would come into play
developerWorks Profile
From: daviesd davi...@oclc.org
To: dev@shindig.apache.org,
Cc: Ryan J Baxter/Westford/IBM@Lotus
Date: 07/29/2011 10:41 AM
Subject:Re: Example implementation for user prefs?
In our implementation the siteid SHOULD be unique and specific to an
instance
implementation for user prefs?
Dan,
Nice! I'm still using 3.0.0-beta2, so hadn't seen this yet. Was there an
earlier thread on how to use this? Can you explain how I hook into this
and
provide a server-side implementation? And does this mean when I call
navigateGadget that I should now
To: dev@shindig.apache.org,
Date: 07/27/2011 03:22 PM
Subject:Re: Example implementation for user prefs?
Dan,
Nice! I'm still using 3.0.0-beta2, so hadn't seen this yet. Was there an
earlier thread on how to use this? Can you explain how I hook into this
and
provide a server-side
Subject:Re: Example implementation for user prefs?
Dan,
Nice! I'm still using 3.0.0-beta2, so hadn't seen this yet. Was there an
earlier thread on how to use this? Can you explain how I hook into this
and
provide a server-side implementation? And does this mean when I call
needed when doing the gadget render, not the metadata request.
No patch needed.
From: Dan Dumont/Westford/IBM@Lotus
To: dev@shindig.apache.org,
Date: 07/27/2011 03:35 PM
Subject:Re: Example implementation for user prefs?
http://opensocial-resources.googlecode.com/svn
davi...@oclc.org
To: dev@shindig.apache.org,
Date: 07/28/2011 11:55 AM
Subject:Re: Example implementation for user prefs?
Jesse,
I think you are correct that it should be per instance. That's where the
siteid would come into play. At least that's how I'm reading it (and now
preferences are supposed to be stored per user/per application instance).
-Original Message-
From: daviesd [mailto:davi...@oclc.org]
Sent: Wednesday, July 27, 2011 11:59 AM
To: dev@shindig.apache.org
Subject: Re: Example implementation for user prefs?
Actually, I was lazy and went
...@us.ibm.com
Phone: 978-899-3041
developerWorks Profile
From: Henry Saputra henry.sapu...@gmail.com
To: dev@shindig.apache.org,
Date: 07/28/2011 09:13 PM
Subject:Re: Example implementation for user prefs?
Hmm I cant seem to find if user preference is per application
instance. I
...@us.ibm.com
Phone: 978-899-3041
developerWorks Profile
From: Henry Saputra henry.sapu...@gmail.com
To: dev@shindig.apache.org,
Date: 07/28/2011 09:13 PM
Subject:Re: Example implementation for user prefs?
Hmm I cant seem to find if user preference is per application
Actually, I was lazy and went with the approach of layering userprefs on top
of appdata as follows:
container.rpcRegister('set_pref', function(rpcArgs, data) {
var prefName = rpcArgs['a'][1];
var prefKey = 'up_' + prefName;
var prefValue = rpcArgs['a'][2];
Can you write this up a patch so we can make this the default
implementation? This is something I've been meaning to do for months.
On Wed, Jul 27, 2011 at 8:58 AM, daviesd davi...@oclc.org wrote:
Actually, I was lazy and went with the approach of layering userprefs on
top
of appdata as
Subject: Re: Example implementation for user prefs?
Actually, I was lazy and went with the approach of layering userprefs on top
of appdata as follows:
container.rpcRegister('set_pref', function(rpcArgs, data) {
var prefName = rpcArgs['a'][1];
var prefKey = 'up_' + prefName
: daviesd davi...@oclc.org
To: dev@shindig.apache.org,
Date: 07/27/2011 01:09 PM
Subject:Re: Example implementation for user prefs?
Paul,
Sure. Give me a few days, I just got back from vacation. I'll have to
figure
out whether the container token will be sufficient for this, as I had
are going to be providing a default preference persistence impl, it
would be great if you could hook into this :)
From: daviesd davi...@oclc.org
To: dev@shindig.apache.org,
Date: 07/27/2011 01:09 PM
Subject:Re: Example implementation for user prefs?
Paul,
Sure
.
If you are going to be providing a default preference persistence impl,
it
would be great if you could hook into this :)
From: daviesd davi...@oclc.org
To: dev@shindig.apache.org,
Date: 07/27/2011 01:09 PM
Subject:Re: Example implementation for user prefs?
Paul
preferences you can just ignore they siteid and return or
persist the preferences for all gadgets coming from that url.
From: daviesd davi...@oclc.org
To: dev@shindig.apache.org,
Date: 07/27/2011 03:22 PM
Subject:Re: Example implementation for user prefs?
Dan,
Nice! I'm
: Example implementation for user prefs?
Dan,
Nice! I'm still using 3.0.0-beta2, so hadn't seen this yet. Was there an
earlier thread on how to use this? Can you explain how I hook into this
and
provide a server-side implementation? And does this mean when I call
navigateGadget that I should
So with some research it looks like I'm supposed to be implementing my own
server module. Is that pretty much accurate?
Yes -- you'll need to implement both the client side UI for editing preferences
and the server side API for persisting them. I actually just did that work
though for the
On Tue, Jul 26, 2011 at 5:17 AM, Ciancetta, Jesse E. jc...@mitre.orgwrote:
So with some research it looks like I'm supposed to be implementing my own
server module. Is that pretty much accurate?
Yes -- you'll need to implement both the client side UI for editing
preferences and the server
So with some research it looks like I'm supposed to be implementing my own
server module. Is that pretty much accurate?
Again, any advice or RTFMs (with a link to the respective FMs) is
appreciated.
Thanks,
Mat
On Fri, Jul 22, 2011 at 10:20 AM, Mat Schaffer m...@schaffer.me wrote:
So I
If you want the user pref to be persisted in the database you need to
implement the server handler for it.
I remember Doug Davies has tried to add persistent layer for user
pref. Maybe he could share his progress.
Including him in the email.
- Henry
On Mon, Jul 25, 2011 at 3:42 PM, Mat
So I noticed that UserPref items don't work on the sample container which
makes sense after finding this thread:
http://markmail.org/message/tlwtlo4mrnrpz4w5
Is there any good example of best-practice for implementing user prefs in my
containing application? Do I just make my own
26 matches
Mail list logo
