Just following up on this need [1]. There is an implementation team that has an immediate need for this and I will be recommending they use this solution ahead of it being truly being incorporated into the spec. I see no harm in implementing this. Consumers that don't support it simply don't get the events and providers who don't support it, simply don't send the events. The harm is it additive to the spec. These feels straightforward and could include just a 1 liner in delegated UI section to reference the re-sizing in [2]
Anyone see any problems with this approach? Can we queue this up for Core topic? [1] http://open-services.net/bin/view/Main/OslcCoreIssues [2] http://open-services.net/bin/view/Main/OslcCoreUiPreview#Preview_sizing Thanks, Steve Speicher | IBM Rational Software | (919) 254-0645 Steve K Speicher/Raleigh/IBM wrote on 11/22/2010 08:17:20 AM: > From: Steve K Speicher/Raleigh/IBM > To: oslc-core <[email protected]> > Cc: Patrick Streule/Zurich/IBM@IBMCH > Date: 11/22/2010 08:17 AM > Subject: Need for window resize for Delegated UIs > > I wanted to get this on the backlog / feature list for future Core work and topics. > > Namely, the current delegated UI spec [1] allow only for a one time > declarative sizing of the dialog. If the dialog needs to dynamically change, > unfortunately there is no way to communicate the resizing information. > Though, this exists in the UI Preview spec [2] . So I'd propose that the > same approach be applied. > > [1] - http://open-services.net/bin/view/Main/OslcCoreSpecification? > sortcol=table;up=#Delegated_User_Interface_Dialogs > [2] - http://open-services.net/bin/view/Main/OslcCoreUiPreview? > sortcol=table;up=#Preview_sizing > > Thanks, > Steve Speicher | IBM Rational Software | (919) 254-0645
