Home » Eclipse Projects » Standard Widget Toolkit (SWT) » SWT GC - Rendering quality, API, etc
| SWT GC - Rendering quality, API, etc [message #449523] |
Tue, 25 January 2005 17:58  |
Eclipse User |
|
|
|
Originally posted by: rohroh_us.yahoo.com
Swing's Java2D provides some very elaborate rendering capabilities. The
underlying native Windows OS platform provides for API that allows fairly
good rendering quality via specified rendering hints, etc. Why is it that
the SWT GC API architects did not incorporate some of this functionality
into the SWT API? It would've been a simple JNI mapping into the
corresponding Win32 API. Was their concern due to portability and
availability of these features on platforms that do not support it?
Clearly inavailability of high-quality rendering could have been handled
as gracefully degraded output. Moreover, because a very large percentage
of the Eclipse user base runs on a Windows platform, they wouldn't even
notice.
Having said that, are there any plans in store for the Eclipse SWT team to
provide a more exhaustive API for rendering? Specifically, we would like
to see:
1. Ability to specify rendering hints
2. Ability to apply transforms at the GC level
3. Add missing API (e.g. fillPolygonGradient, fill/drawCustomShape, etc)
The reason why the Eclipse IDE does so well is because the UI is very
responsive as it is modelled over a thin JNI layer over the OS API and on
Windows, the OS UI is clearly very good.
Just a thought. I think there are a lot of other users who would like to
see these new features added too.
|
|
|
| Re: SWT GC - Rendering quality, API, etc [message #449687 is a reply to message #449523] |
Fri, 28 January 2005 00:44  |
 Steve Northover
Messages: 1636
Registered: July 2009 |
Senior Member |
|
|
The problem was portability. If we invent an API without even understanding
how we might need to implement it on the other platforms, we will fail. We
are looking into advanced graphics for M5.
"John Doe" <rohroh_us@yahoo.com> wrote in message
news:ct61ci$km7$1@www.eclipse.org...
> Swing's Java2D provides some very elaborate rendering capabilities. The
> underlying native Windows OS platform provides for API that allows fairly
> good rendering quality via specified rendering hints, etc. Why is it that
> the SWT GC API architects did not incorporate some of this functionality
> into the SWT API? It would've been a simple JNI mapping into the
> corresponding Win32 API. Was their concern due to portability and
> availability of these features on platforms that do not support it?
> Clearly inavailability of high-quality rendering could have been handled
> as gracefully degraded output. Moreover, because a very large percentage
> of the Eclipse user base runs on a Windows platform, they wouldn't even
> notice.
>
> Having said that, are there any plans in store for the Eclipse SWT team to
> provide a more exhaustive API for rendering? Specifically, we would like
> to see:
>
> 1. Ability to specify rendering hints
> 2. Ability to apply transforms at the GC level
> 3. Add missing API (e.g. fillPolygonGradient, fill/drawCustomShape, etc)
>
> The reason why the Eclipse IDE does so well is because the UI is very
> responsive as it is modelled over a thin JNI layer over the OS API and on
> Windows, the OS UI is clearly very good.
>
> Just a thought. I think there are a lot of other users who would like to
> see these new features added too.
>
|
|
|
| Re: SWT GC - Rendering quality, API, etc [message #449751 is a reply to message #449687] |
Fri, 28 January 2005 15:22 |
Ivan Markov
Messages: 61
Registered: July 2009 |
Member |
|
|
Cairo seems to make a good progress.
Are you planning something similar, i.e. (bindings to) PDF-like API,
or just extending the existing GC class with more X11-GDI-style functions,
like line cap & join?
"Steve Northover" <steve_northover@ca.ibm.com> wrote in message
news:ctc1uo$qhb$1@www.eclipse.org...
> The problem was portability. If we invent an API without even
understanding
> how we might need to implement it on the other platforms, we will fail.
We
> are looking into advanced graphics for M5.
>
> "John Doe" <rohroh_us@yahoo.com> wrote in message
> news:ct61ci$km7$1@www.eclipse.org...
> > Swing's Java2D provides some very elaborate rendering capabilities. The
> > underlying native Windows OS platform provides for API that allows
fairly
> > good rendering quality via specified rendering hints, etc. Why is it
that
> > the SWT GC API architects did not incorporate some of this functionality
> > into the SWT API? It would've been a simple JNI mapping into the
> > corresponding Win32 API. Was their concern due to portability and
> > availability of these features on platforms that do not support it?
> > Clearly inavailability of high-quality rendering could have been handled
> > as gracefully degraded output. Moreover, because a very large percentage
> > of the Eclipse user base runs on a Windows platform, they wouldn't even
> > notice.
> >
> > Having said that, are there any plans in store for the Eclipse SWT team
to
> > provide a more exhaustive API for rendering? Specifically, we would like
> > to see:
> >
> > 1. Ability to specify rendering hints
> > 2. Ability to apply transforms at the GC level
> > 3. Add missing API (e.g. fillPolygonGradient, fill/drawCustomShape, etc)
> >
> > The reason why the Eclipse IDE does so well is because the UI is very
> > responsive as it is modelled over a thin JNI layer over the OS API and
on
> > Windows, the OS UI is clearly very good.
> >
> > Just a thought. I think there are a lot of other users who would like to
> > see these new features added too.
> >
>
>
|
|
|
| Re: SWT GC - Rendering quality, API, etc [message #449753 is a reply to message #449687] |
Fri, 28 January 2005 18:06 |
Jonathan Edwards
Messages: 27
Registered: July 2009 |
Junior Member |
|
|
My vote would be for anti-aliasing. For me, that is the major drawback
compared to Java 2. This is ironic because the ability to do
anti-aliased fonts is a major advantage of SWT.
Jonathan
Steve Northover wrote:
> The problem was portability. If we invent an API without even understanding
> how we might need to implement it on the other platforms, we will fail. We
> are looking into advanced graphics for M5.
>
> "John Doe" <rohroh_us@yahoo.com> wrote in message
> news:ct61ci$km7$1@www.eclipse.org...
>
>>Swing's Java2D provides some very elaborate rendering capabilities. The
>>underlying native Windows OS platform provides for API that allows fairly
>>good rendering quality via specified rendering hints, etc. Why is it that
>>the SWT GC API architects did not incorporate some of this functionality
>>into the SWT API? It would've been a simple JNI mapping into the
>>corresponding Win32 API. Was their concern due to portability and
>>availability of these features on platforms that do not support it?
>>Clearly inavailability of high-quality rendering could have been handled
>>as gracefully degraded output. Moreover, because a very large percentage
>>of the Eclipse user base runs on a Windows platform, they wouldn't even
>>notice.
>>
>>Having said that, are there any plans in store for the Eclipse SWT team to
>>provide a more exhaustive API for rendering? Specifically, we would like
>>to see:
>>
>>1. Ability to specify rendering hints
>>2. Ability to apply transforms at the GC level
>>3. Add missing API (e.g. fillPolygonGradient, fill/drawCustomShape, etc)
>>
>>The reason why the Eclipse IDE does so well is because the UI is very
>>responsive as it is modelled over a thin JNI layer over the OS API and on
>>Windows, the OS UI is clearly very good.
>>
>>Just a thought. I think there are a lot of other users who would like to
>>see these new features added too.
>>
>
>
>
|
|
|
| Re: SWT GC - Rendering quality, API, etc [message #449756 is a reply to message #449753] |
Fri, 28 January 2005 20:37 |
Philippe Marschall
Messages: 121
Registered: July 2009 |
Senior Member |
|
|
You can do antialiased fonts in Swing. They are not native, but they are
antialiased.
http://www.javalobby.org/forums/thread.jspa?forumID=61&t hreadID=14179
Jonathan Edwards wrote:
> My vote would be for anti-aliasing. For me, that is the major drawback
> compared to Java 2. This is ironic because the ability to do
> anti-aliased fonts is a major advantage of SWT.
>
> Jonathan
>
> Steve Northover wrote:
>
>> The problem was portability. If we invent an API without even
>> understanding
>> how we might need to implement it on the other platforms, we will
>> fail. We
>> are looking into advanced graphics for M5.
>>
>> "John Doe" <rohroh_us@yahoo.com> wrote in message
>> news:ct61ci$km7$1@www.eclipse.org...
>>
>>> Swing's Java2D provides some very elaborate rendering capabilities. The
>>> underlying native Windows OS platform provides for API that allows
>>> fairly
>>> good rendering quality via specified rendering hints, etc. Why is it
>>> that
>>> the SWT GC API architects did not incorporate some of this functionality
>>> into the SWT API? It would've been a simple JNI mapping into the
>>> corresponding Win32 API. Was their concern due to portability and
>>> availability of these features on platforms that do not support it?
>>> Clearly inavailability of high-quality rendering could have been handled
>>> as gracefully degraded output. Moreover, because a very large percentage
>>> of the Eclipse user base runs on a Windows platform, they wouldn't even
>>> notice.
>>>
>>> Having said that, are there any plans in store for the Eclipse SWT
>>> team to
>>> provide a more exhaustive API for rendering? Specifically, we would like
>>> to see:
>>>
>>> 1. Ability to specify rendering hints
>>> 2. Ability to apply transforms at the GC level
>>> 3. Add missing API (e.g. fillPolygonGradient, fill/drawCustomShape, etc)
>>>
>>> The reason why the Eclipse IDE does so well is because the UI is very
>>> responsive as it is modelled over a thin JNI layer over the OS API
>>> and on
>>> Windows, the OS UI is clearly very good.
>>>
>>> Just a thought. I think there are a lot of other users who would like to
>>> see these new features added too.
>>>
>>
>>
>>
|
|
|
| Re: SWT GC - Rendering quality, API, etc [message #449924 is a reply to message #449751] |
Mon, 31 January 2005 16:35 |
Steve Northover
Messages: 1636
Registered: July 2009 |
Senior Member |
|
|
Extending the GC class. Stay tuned.
"Ivan Markov" <ivan.markov@wizcom.bg> wrote in message
news:ctdlbd$toj$1@www.eclipse.org...
> Cairo seems to make a good progress.
> Are you planning something similar, i.e. (bindings to) PDF-like API,
> or just extending the existing GC class with more X11-GDI-style functions,
> like line cap & join?
>
>
> "Steve Northover" <steve_northover@ca.ibm.com> wrote in message
> news:ctc1uo$qhb$1@www.eclipse.org...
> > The problem was portability. If we invent an API without even
> understanding
> > how we might need to implement it on the other platforms, we will fail.
> We
> > are looking into advanced graphics for M5.
> >
> > "John Doe" <rohroh_us@yahoo.com> wrote in message
> > news:ct61ci$km7$1@www.eclipse.org...
> > > Swing's Java2D provides some very elaborate rendering capabilities.
The
> > > underlying native Windows OS platform provides for API that allows
> fairly
> > > good rendering quality via specified rendering hints, etc. Why is it
> that
> > > the SWT GC API architects did not incorporate some of this
functionality
> > > into the SWT API? It would've been a simple JNI mapping into the
> > > corresponding Win32 API. Was their concern due to portability and
> > > availability of these features on platforms that do not support it?
> > > Clearly inavailability of high-quality rendering could have been
handled
> > > as gracefully degraded output. Moreover, because a very large
percentage
> > > of the Eclipse user base runs on a Windows platform, they wouldn't
even
> > > notice.
> > >
> > > Having said that, are there any plans in store for the Eclipse SWT
team
> to
> > > provide a more exhaustive API for rendering? Specifically, we would
like
> > > to see:
> > >
> > > 1. Ability to specify rendering hints
> > > 2. Ability to apply transforms at the GC level
> > > 3. Add missing API (e.g. fillPolygonGradient, fill/drawCustomShape,
etc)
> > >
> > > The reason why the Eclipse IDE does so well is because the UI is very
> > > responsive as it is modelled over a thin JNI layer over the OS API and
> on
> > > Windows, the OS UI is clearly very good.
> > >
> > > Just a thought. I think there are a lot of other users who would like
to
> > > see these new features added too.
> > >
> >
> >
>
>
|
|
|
Goto Forum:
Current Time: Thu Apr 25 07:36:50 GMT 2024
Powered by FUDForum. Page generated in 0.04019 seconds |
] 
Search
Help
Register
Login
Home
