Oops, looks like I garbled the response, here it is again
--
Great to meet you and glad you like the Viewer.
1) The id is meant to be a unique identifier and is used for storing/loading
the table customizations between instances of an application. It also provides
for the column name to be the same, like "Description", but the values shown
different.
In these cases, you would want to know the full id of the column (if there is
one). However, in the simplest case, you are correct, it shouldn't show. I
made a code fix such that if the name and id are the same, it doesn't show in
the Header or Customization dialog. Hope that helps.
2) I could not reproduce this problem. Can you send an example of the problem
using the test code provided. Also, if you have a fix and want to send the
patch, it would speed things up.
3) We have subclassed the XViewerTextFilter to provide extra capabilities.
Here's an example. You should just be able to implement "select" to do
whatever you want.
public class XBranchTextFilter extends XViewerTextFilter {
public XBranchTextFilter(XViewer viewer) {
super(viewer);
}
@Override
public boolean select(Viewer viewer, Object parentElement, Object element) {
if (element instanceof TransactionRecord) {
return true;
}
if (element instanceof ArrayList<?>) {
return true;
}
return super.select(viewer, parentElement, element);
}
}
And then make sure that your Xviewer overrides the getXViewerTextFilter method
@Override
public XViewerTextFilter getXViewerTextFilter() {
return new XBranchTextFilter(this);
}
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Chris Merrill
Sent: Tuesday, October 19, 2010 1:52 PM
To: [email protected]
Subject: [nebula-dev] XViewer questions
First, a little introduction: I've been upgrading part of our UI this week and
came across XViewer. I've incorporated it as a replacement for TreeViewer and
it is working great for us! The quick text-filtering and searching, as well as
the drag-n-drop column reordering were on our feature list and I'm happy to
call them done without doing much real work :>
I've followed a little of the process of getting the builds fixed and am
looking forward to being able to get a JAR or plugin, rather than including the
source in our tree.
I've got a few questions that I haven't been able to resolve yet:
1) The "id" passed into the columns - what is it's purpose? In the example, it
is something like "xviewer.test.complete" and shows in the column tooltip as
well as the column descriptions in the customization dialog. That example value
seems somewhat unnatural for the end-user (depending on your end-user base), so
I'm guessing that I'm just not understanding how it should be used. I tried
"turning it off" (by passing in null or empty strings) but judging by the
results, that was obviously not an intended use-case :>
2) We highlight certain rows by changing the background color. When I do a
search, any cells which are:
a) not highlighted by the search, and
b) in a row with the changed background color, and
c) blank
will end up with the changed background color removed - e.g. the background
changes to white.
Not a serious problem, but a little ugly. Is it a known problem?
3) using the supplied text filter (XViewerTextFilter) I found that the
filtering was a bit over-aggressive for our needs. If a non-leaf-node did not
contain the search text, then the node would not be displayed, even if one (or
more) leafs under that node did contain the search text. Am I not using that
correctly, or is that by design? I subclassed XViewerTextFilter to allow
parent nodes of leafs that match the search to be displayed, but it did not
seem like it was designed to be subclassed (all fields private), so perhaps I
am not approaching this correctly?
Thanks for any help you can offer!
Chris
--
------------------------------------------------------------------------ -
Chris Merrill | Web Performance, Inc.
[email protected] | http://webperformance.com
919-433-1762 | 919-845-7601
Web Performance: Website Load Testing Software & Services
------------------------------------------------------------------------ -
_______________________________________________
nebula-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/nebula-dev
_______________________________________________
nebula-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/nebula-dev
_______________________________________________
nebula-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/nebula-dev
