| Re: [nebula-dev] XViewer Widget problems? |
|
Thanks Don, I didn’t mean to sound like I was
complaining about the lack of documentation, just pointing out that it was not
a source. I began by stepping through the example in the debugger to see where
things are happening and familiarizing myself with the code. I have already
done exactly as you described and I’m in the process of modifying the test
packages to resemble my project requirements. I started by changing columns and
column data and realized that the XViewerColumn class, which is not part of the
org.eclipse.nebula.widgets.xviewer.test package (actually it is in the org.eclipse.nebula.widgets.xviewer
package) contains direct references to the test data. I did not expect this
coupling between the test classes and what I thought was the XViewer implementation?
What I’m trying to determine in this exercise is the coupling and
cohesion of the design and was hoping for a clean cut between the XViewer implementation
and the specific requirements of a project wanting to use the XViewer. Am I
looking at this all wrong? I understand we can override most operations to make
them behave the way we need to. But I would think this to be the exception in
most cases and by implementing a set of defined XViewer interface/abstract
classes and extending a known set of classes would be the way it was intended
to be used. I’m trying to determine how it was envisioned to be used and
follow that approach or is it just a hunk of code and anyone can go in and
change any and all classes they feel fit to. I would hope it is more of the
former than the latter but I don’t know enough about the history to make
a call either way. Would you mind sharing your thoughts on this? Thanks Michael Stapleton Sr. Software Engineer - Echostar Broadcasting Corporation (307) 633-5448 From:
nebula-dev-bounces@xxxxxxxxxxx [mailto:nebula-dev-bounces@xxxxxxxxxxx] On Behalf Of Dunne, Donald G The .test package has all the code you would
need to get started. You can right-click on XViewerTest -> Run As
-> Java Application to see the example. After that, just copy all the
classes in that package to your own project and start modifying as needed. Yes, documentation is not as desired,
maybe if someone has some time/resources/expertise in tech writing, they could
come up with better docs. We decided an example was the best method
of communication given the resources. Also, we're happy to answer questions as
they come up. Don From:
nebula-dev-bounces@xxxxxxxxxxx [mailto:nebula-dev-bounces@xxxxxxxxxxx] On Behalf Of Stapleton, Mike Hi, I am new on the nebula mailing list and got on it because of
problems trying to use the XViewer widget. I am working with the XViewer source
I downloaded from the Nebula sight. It looks to also contain the XViewer test
code. I am trying to figure out what parts belong in the API and which parts
are internal and are not part of the API so I can use it as intended. Does
anyone on the team have any XViewer examples that I could examine for this
purpose. I have the test code but it does not make a good candidate for an
example. It uses internal libraries that probably only exist for testing, has hard coded data right in the classes
to mention just a few problems. It is difficult to tell what
interfaces should be implemented in order to use the XViewer and which should
be only accessed by XViewer code.
The test example seems highly coupled especially the code addressing columns?
Documentation is scarce to say the least so any help on this issue would be appreciated. Michael Stapleton Sr. Software Engineer - Echostar Broadcasting Corporation (307) 633-5448 |