Community
Participate
Working Groups
Created attachment 183981 [details] Patch for ArrayContentProvider I have seen to many people which define their own ContentProvider even if the ArrayContentProvider would be sufficient. Perhaps we can can update ""RCP application with a view" to show the usageo of the ArrayContentProvider? Patch attached.
Created attachment 183983 [details] TableViewerColumn This includes also an update to the TableViewerColumn API of JFace.
By adding ArrayContentProvider we are losing the example usage of IStructuredContentProvider. And also the explanation in comment. I feel this information is essential for a user creating a view using the template. For the same reason we are extending LabelProvider instead of just attaching its instance. I think we can instead suggest the usage of ArrayContentProvider in the javadoc for ViewContentProvider. Similarly for ViewLabelProvider.
(In reply to comment #1) > Created an attachment (id=183983) [details] > TableViewerColumn > > This includes also an update to the TableViewerColumn API of JFace. The patch doesn't seem right to me.
Created attachment 183984 [details] TableViewerColumn Correct patch attached.
I personally think it is important to demonstrate code which does re-use commonly used parts. ArrayContentProvider does extend IStructuredContentProvider so I assume the user will see that this interface needs to be implemented.
Perhaps we can compromise and there can be a comment about ArrayContentProvider in the generated code?
A good comment would also be ok. Do you have a good proposal? The only comments I can come up with sound silly, e.g. "ArrayContentProvider" provides the same functionality as the code below.
I agree with comment 2.
Javadoc is definitely a good compromise. @Ankar: Can you change this directly or shall I create a patch? If you are looking for a patch please let me know the Javadoc additioan.
We have some major items to get done for M4, I suggest leaving this until M5.
(In reply to comment #9) > Javadoc is definitely a good compromise. > > @Ankar: Can you change this directly or shall I create a patch? If you are > looking for a patch please let me know the Javadoc additioan. Committer time is getting stretched very thin, can you look at creating a patch for this?
I find its not worth investing in Eclipse 3.x templates anymore. Closing as WONTFIX.