On 6 May 2011, at 03:35, Zhenhua (Gerald) Guo wrote:
>> The other requirement I can see is to hold height and width parameters in
>> the Widget object and push these into the view as these are obtained from
>> the metadata in W3C widgets rather than using callbacks to set the iframe
>> size dynamically.
>
> I am not familiar with W3C widget. In gadget, there is API to adjust
> iframe height. It can be called any time after the initialization.
> So if there is anything similar in W3C Widget, callbacks may also be
> needed to set height.
Its not part of the W3C spec, but could be added as a proprietary <feature>
extension.
>
>
> Gerald
>
>>
>> S
>>
>>>
>>> -Matt
>>>
>>>>
>>>> public URL renderWidget(User user, RegionWidget regionWidget){
>>>> }
>>>>
>>>> Or is it a bit more complex than that..?
>>>>
>>>> At the site level we also need some sort of palette or menu system for
>>>> adding widgets based on what's available in available containers. The
>>>> actual metadata is mostly quite similar - titles, authors, icons etc.
>>>> Wookie exposes metadata on all available widget in its REST API. Some
>>>> user stories for how we envisage users discovering and adding
>>>> widgets/gadgets to the workspace would be useful here.
>>>>
>>>>>
>>>>> -Matt
>>>>>
>>>>> On 5/4/11 5:23 PM, "Matt Franklin (JIRA)" <[email protected]> wrote:
>>>>>
>>>>>> Implement User Prefs
>>>>>> --------------------
>>>>>>
>>>>>> Key: RAVE-27
>>>>>> URL: https://issues.apache.org/jira/browse/RAVE-27
>>>>>> Project: Rave
>>>>>> Issue Type: Technical task
>>>>>> Reporter: Matt Franklin
>>>>>>
>>>>>>
>>>>>> Implement persistence of user prefs, container services and RPC
>>>>>> callbacks
>>>>>>
>>>>>> --
>>>>>> This message is automatically generated by JIRA.
>>>>>> For more information on JIRA, see:
>>>>>> http://www.atlassian.com/software/jira
>>>>>
>>>>
>>>
>>
>>
