public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug AWT/20630] New: Image APIs should use BufferedImage exclusively
@ 2005-03-24 22:13 fitzsim at redhat dot com
2005-09-10 1:15 ` [Bug awt/20630] GTK 2.8 peer Image and Graphics API reorganization fitzsim at redhat dot com
0 siblings, 1 reply; 5+ messages in thread
From: fitzsim at redhat dot com @ 2005-03-24 22:13 UTC (permalink / raw)
To: gcc-bugs
The Java 1.1 imaging APIs were designed to be asynchronous, for loading images
over slow networks. The design is very complicated and hard to implement. In
1.2 BufferedImages seem to have replaced Images. So, for example,
Component.createImage() is declared to return an Image, but actually returns a
BufferedImage. This makes the APIs synchronous -- which should make them much
simpler to implement.
We should do the same in our AWT implementation. This will involve the following:
- removing all uses of ImageObserver, except when reporting errors in image
loading, and when reporting a new frame in animated gifs
- replacing GtkImage with BufferedImage
- merging GtkImagePainter into GdkGraphics2D
- making the switch to using GdkGraphics2D exclusively
--
Summary: Image APIs should use BufferedImage exclusively
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: AWT
AssignedTo: fitzsim at redhat dot com
ReportedBy: fitzsim at redhat dot com
CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20630
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug awt/20630] GTK 2.8 peer Image and Graphics API reorganization
2005-03-24 22:13 [Bug AWT/20630] New: Image APIs should use BufferedImage exclusively fitzsim at redhat dot com
@ 2005-09-10 1:15 ` fitzsim at redhat dot com
0 siblings, 0 replies; 5+ messages in thread
From: fitzsim at redhat dot com @ 2005-09-10 1:15 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From fitzsim at redhat dot com 2005-09-10 01:15 -------
I'm changing the summary to be more general. Now that GTK 2.8 and Cairo 1.0 are
out we can make the transition to using Graphics2D exclusively in the GTK peers.
This will allow us to re-organize the Image APIs to handle VolatileImages,
BufferedImages and normal Images, remove GdkGraphics, remove GdkPixbufDecoder
and split GdkGraphics2D into Image- and Component-specific graphics-contexts.
--
What |Removed |Added
----------------------------------------------------------------------------
Summary|Image APIs should use |GTK 2.8 peer Image and
|BufferedImage exclusively |Graphics API reorganization
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20630
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2008-02-17 22:12 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-20630-8711@http.gcc.gnu.org/bugzilla/>
2005-11-21 21:11 ` [Bug awt/20630] GTK 2.8 peer Image and Graphics API reorganization mark at gcc dot gnu dot org
2006-05-17 0:56 ` sven at physto dot se
2008-02-17 19:43 ` gnu_andrew at member dot fsf dot org
2008-02-17 22:12 ` gnu_andrew at member dot fsf dot org
2005-03-24 22:13 [Bug AWT/20630] New: Image APIs should use BufferedImage exclusively fitzsim at redhat dot com
2005-09-10 1:15 ` [Bug awt/20630] GTK 2.8 peer Image and Graphics API reorganization fitzsim at redhat dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).