Building features on top of Wave itself is definitely something we like to do. User profiles, settings, avatars etc fit well here (it's what Google Wave does too).
However I agree with James we probably need some basic infrastructure outside of waves to bootstrap such a system. Basic password resetting is a good example, as is some admin functionality like account management. Implementing profile waves is a big task, but password reset and user management pages sound feasible. Go for it! Alex On 28 October 2010 08:28, Vega <[email protected]> wrote: > I am not sure how much effort would take to support gadgets in WIAB - > probably not too much. Implementation of admin gadget should not be > too hard, if needed I can do it. > > On Oct 27, 3:31 pm, x00 <[email protected]> wrote: > > Content management could work through extensions, and ultimately a > > fully blown wave application framework. But I don't see that as the > > remit of WIAB at the moment. > > > > Potentially in the future all content could be float atop of wave like > > services, bar the infrastructure itself. > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" 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/wave-protocol?hl=en.
