Ø
Wouldn't using Agile2D mean
using things like AWT's Image, Font, and Color
representations?
Ø
If Agile2D implements the
Graphics2D interface, this would bring in a lot of AWT's
resources, and applications would
Ø
have
duplicate representations of images, fonts, etc., not to mention the resource
leaks in AWT.
Yes. I proposed the usage of Java2D as a temporary solution. Surfacing
the features of XRENDER/GDI+ in SWT will take time (if ever), isn’t it?
Ø
BTW, why is GDI+ not hardware
accelerated if it came out at least 5 years after the DirectDraw API?
Ø
Oh well, I'm MS will make it
faster, especially if doing so would reduce windows stability ;-) (directX anyone?)
AFAIK, in next version of Windows (Longhorn?)
MSFT will abandon GDI’s Device Driver Interface
altogether and will instead re-implement GDI on top of DirectDraw/Direct3D. So
the graphics cards vendors will have to provide only DirectX drivers.
I also believed they will do the same with GDI+ (so it will gain
hardware acceleration after all).
But there are rumours that they will abandon GDI+
altogether, so I don’t know what to think anymore:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=Xns93299E8D31A01kevwpeckyahoocom%40207.46.248.16&rnum=1&prev=/groups%3Fq%3Dgdi%2Blonghorn%26hl%3Den%26lr%3D%26ie%3DUTF-8%26selm%3DXns93299E8D31A01kevwpeckyahoocom%2540207.46.248.16%26rnum%3D1
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=%23WNXtjtzCHA.1728%40TK2MSFTNGP12&rnum=29&prev=/groups%3Fq%3D%2522kevin%2Bpeck%2522%26start%3D20%26hl%3Den%26lr%3D%26ie%3DUTF-8%26scoring%3Dd%26selm%3D%2523WNXtjtzCHA.1728%2540TK2MSFTNGP12%26rnum%3D29
-----Original Message-----
From: Randy Hudson
[mailto:hudsonr@xxxxxxxxxx]
Sent: Tuesday, April 15, 2003 5:10 PM
To: platform-swt-dev@xxxxxxxxxxx
Subject: RE: [platform-swt-dev]
Java2d features in SWT
Wouldn't using Agile2D mean using things like AWT's
Image, Font, and Color representations? If Agile2D implements the
Graphics2D interface, this would bring in a lot of AWT's resources, and
applications would have duplicate representations of images, fonts, etc., not
to mention the resource leaks in AWT.
Agile2D's
OpenGL implementation on a hardware-accelerated Thinkpad is already slower than
Sun's Java2D implementation, which is *not* hardware accelerated by default. For
machines without OpenGL hardware, it could be slower still.
BTW,
why is GDI+ not hardware accelerated if it came out at least 5 years after the
DirectDraw API? Oh well, I'm MS will make it faster, especially if doing
so would reduce windows stability ;-) (directX anyone?)
|
|
"Steve Northover"
<Steve_Northover@xxxxxxxxxx>
Sent
by: platform-swt-dev-admin@xxxxxxxxxxx
04/15/2003 09:24 AM
Please
respond to platform-swt-dev
|
To: platform-swt-dev@xxxxxxxxxxx
cc: platform-swt-dev@xxxxxxxxxxx,
platform-swt-dev-admin@xxxxxxxxxxx
Subject: RE:
[platform-swt-dev] Java2d features in SWT
|
Perhaps a better approach might be to write an SWT binding for Agile2D?
|
|
"Ivan Markov"
<ivan.markov@xxxxxxxxx>
Sent by: platform-swt-dev-admin@xxxxxxxxxxx
04/14/2003 12:24 PM
Please respond to platform-swt-dev
|
To: platform-swt-dev@xxxxxxxxxxx
cc:
Subject: RE:
[platform-swt-dev] Java2d features in SWT
|
I've never worked with GDI+ so take this with a grain of salt, but..
I've read on the GDI/GDI+ newsgroups that GDI+ is still not
hardware accelerated; the majority of the rasterizing operations are implemented
in software and are very slow, the reason being that GDI+ is implemented
on top of GDI, which, aside from AlphaBlend() doesn't know much about alpha
channels.
Has this situation changed recently?
For me, Java2D<->org.eclipse.swt.graphics.GC interop
seems the better solution, especially considering that Java2D had more time to
mature and they are starting to implement certain operations in hardware (with
Direct3D) recently..
/Ivan
-----Original
Message-----
From: Randy Hudson [mailto:hudsonr@xxxxxxxxxx]
Sent: Monday,
April 14, 2003 6:42 PM
To: platform-swt-dev@xxxxxxxxxxx
Subject: [platform-swt-dev] Java2d features in SWT
http://www.eclipse.org/newsportal/article.php3?id=2707&group=eclipse.tools.gef
The community has offered to write JNI support for GDI+ on win32, and Xc/Xr
support (I don't know what that is) on Linux. However, the proposal was
to add this support to GEF. IMO, the proper home for these would be in
SWT.
Would the SWT team be willing to investigate providing real GDI+ support or a
subset of GDI+ that would be "portable". Win32 wrappers for
GDI+ on SWT have already been posted to Eclipse.org, but the cross-platforms
issues must be addressed. There have been numerous requests for anti-aliasing,
font rotation, thick dashed lines, transformations, transparency, etc.
thanks,
Randy
