Summary: | [ViewMgmt] [RCP] Support for passing input data to views | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Brandon Brockway <brockway> |
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | bokowski, cbeth, frydzewski, Matthew_Hatem, njohnston, pwebster, robbinsj, wsm879 |
Version: | 3.0.1 | Keywords: | api, helpwanted |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All | ||
Whiteboard: |
Description
Brandon Brockway
2005-01-11 18:13:59 EST
Note that arbitrary properties can already be passed to a view, or any other extension instance via the data parameter of setInitializationData. See the Javadoc for IExecutableExtension for more details. In addition, arbitrary subelements could be put under the <view> element. These get passed in via the config parameter of setInitializationData. The PDE compiler may complain about such subelements since they don't satisfy the extension point schema, but it will work. Other usecases for passing initialization data to a view are more dynamic than what you propose, e.g. if views are showing a document, the app wants to pass the input element (similar to the way editors work). This use case would not be covered by a static configuration. Nick, Correct, static data specified in a view's extension can be obtained in the setInitializationData() method but it's difficult to target subsets of this data to specific instances of a multi view, especially views that have null for their secondary identifier. Additionally, this data is static and can only be changed by updating the plug-in (plugin.xml or plugin.properties). I'm looking for a more dynamic system and a better way to set per instance data on a multi view. Currently, I only have use cases for setting this data once per instance, and displaying multiple instances on one page, but ideally you should be able to update or change the data while the view is active. The two solutions I proposed were just examples and starting points for discussion. They were the most obvious solutions and I don't expect either to be implemented. I agree with you that a generalized way of passing data/input/configuration to a view should be similar to the support for editors. I'm mostly concerned with the implementation satisfying the three requirements I listed in the description to this bug. Thanks. Adding RCP tag as I assume this is for an RCP app, not a regular IDE plug-in. Is there a plan to add this enhancement in 3.2? This is an important feature for our product. Hi Beth, sorry this is not currently on the plan for 3.2. If this is important to you, please coordinate with Steve Wasleski. Reassigning bugs in component areas that are changing ownership. I will try to find time for this in 3.4. In 3.3 part properties were added to both editors and views. Initially they can be accessed through IWorkbenchPart3. Also properties were added to perspective folders, although these were propogated all the way to the presentation. Maybe the part properties could be used if they could be set: 1) in the view definition, there could be a default 2) when calling showView and/or creating the view reference, maybe properties could be pre-set. Of course this depends on justifying that the view initial configuration is a property of the view :-) PW Ran out of time for 3.4. Remy is now responsible for watching the [ViewMgmt] category. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. |