You could probably do something like what you want just using Javascript in a gadget. You can use wave.Participant.getID() to get the current participant and then decide how your draw the gadget based on settings you have for that user.
The problem that you would have is that the state for that gadget would have to contain the settings for all users, unless you stored user settings in an AppEngine DB, and retrieved those via AJAX, then only the data that was applicable to all users would be in the Gadget state. Regards, Zac Shenker On Wed, Sep 9, 2009 at 3:56 AM, rja <[email protected]> wrote: > > I wasn't trying to write a Robot, but as I mentioned, I was trying to > write a Gadget, but use the appengine to create it dynamically. > > I'm trying to detect the identity of that user, using the userService. > > I agree that the approach you outlined doesn't work, because it twists > the idea of a wave as a collaboration medium. Which is why I was > thinking of using a Gadget. > > I think the idea of a custom view for every user, is important, > specially in a massively collaborative environment like Google Wave, > because if you don't give a user the ability to do that, you can't get > around the problem that every Wave user faces today - There's too much > information, modifications to a Wave are impossible to track without > playback, and in general, you just get lost. > > Imagine any game that works within Wave. You would ideally want every > user to see something that is specific to them. > > Imagine a specification that is getting reviewed within Wave. You > would want the ability to turn on and off annotations/review-comments, > without doing so for every single user on the wave. And you would > probably want your settings to be saved for next time. > > At this time, the only extensions that Wave supports, are Robots and > Gadgets. Robots are like any other people on a wave. So that doesn't > work. Gadgets are rich elements that go inside a wave, allowing you a > custom experience. Ideally I'd prefer to have some control with a > third type of extension - like maybe something called > "WaveUIExtension" which allows me to customize the View of a wave, but > I think that will probably be a long time coming, if at all. > > Until then, a Gadget, which renders the rich view, but based on the > personalized preferences of a user, will meet my needs. But at this > time, a gadget doesn't seem to be personalize-able. My question is, > whether my understanding is correct. And whether there is another way > of achieving the same goal. > > > On Sep 6, 8:52 pm, Zac Shenker <[email protected]> wrote: > > The robot will get run as a result of the callback from an event it is > > registered for. As a result you will not receive any user context. > > Probably the best way that I could think of to build what you are > thinking > > of would be as follows: > > 1. Each user has a Wave with just them and the Robot as participants > > 2. The robot can display gadgets and information relevant to each > particular > > user > > 3. Whenever any Wave is updated the Wave decides how all the User Waves > > should be changed. > > 4. Unfortunatley you would see changes being made by the robot rather > than > > the person they were from. > > > > Personally I see this as going a bit against the collaboration concepts > of > > Wave, where all users contribute to the same Wave, instead you what every > > user to see something different? > > > > Regards, > > Zac Shenker > > > > On Sun, Sep 6, 2009 at 10:26 PM, rja <[email protected]> wrote: > > > > > Hi, > > > > > So I'm trying to create a gadget, that's personalized for every user. > > > Imagine a gadget version of Rosy Etta, where the text typed by one > > > user in English, shows up in French for another user whose preferred > > > language is French, and in German for yet another user. > > > > > However, when exposing a dynamic XML (created in appengine) that pulls > > > the current user's nickname using appengine's User service > > > (com.google.appengine.api.users - I'm using Java), even though I'm > > > logged into both my Google Account as well as my Wave sandbox, the > > > "userService.getCurrentUser()" call always returns null. > > > > > I'm guessing it might be because the gadget isn't requested directly > > > by my browser, but the request is made by proxy via the Wave server. > > > > > In any case, how would I customize the view of a component in the wave > > > (whether gadget, or anything else) based on the user? Any ideas? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
