|
Re: Benefits of draw2D over drawing with SWT [message #186871 is a reply to message #186564] |
Thu, 07 July 2005 06:37 |
Eclipse User |
|
|
|
Originally posted by: none.unknown.com
"Brad Reynolds" <bradleyjames@gmail.com> wrote in message
news:daeo19$a1a$1@news.eclipse.org...
> I'm looking to implement a custom drawn control. Like many others I
> need a Table that fulfills the requirements of my employer and the
> native SWT Table won't fulfill our requirements. I've looked at the
What are these requirements?
> Table implemented in GEF and decided that I didn't need the overhead of
> GEF for a Table. I also looked at KTable (a SWT Table implementation)
> and although it seemed like it got the job done I like having the
> framework that draw2D provides. So I'm playing around with implementing
> our own Table. I like the JFace approach in that the MVC layer is
> outside of the base component and not built into the core widget and was
> hoping to develop a Table that followed this same pattern.
>
> I like what draw2D provides but I want to make sure that I'm not
> overlooking some part of SWT that isn't exposed in draw2D that I will
> need later on. My assumption has been that draw2D is a framework that
> utilizes SWT that doesn't limit my visibility to SWT abilities. It
All GC-releated functionality (painting, clipping, advanced graphics) is
supported.
> looks like it exposes most of what SWT does in draw2D specific classes
> but also adds layouts, update manager for drawing efficiency, and base
> implementations of widgets like Buttons and Labels.
>
> Is there something that I'm missing or misunderstanding? Am I making
> any incorrect assumptions? Any advice is greatly appreciated.
>
> Thanks,
> Brad
|
|
|
|
Powered by
FUDForum. Page generated in 0.03706 seconds