Closed Bug 182658 Opened 22 years ago Closed 15 years ago

Create nsImageImpl class; move common code from nsImage* to it

Categories

(Core Graveyard :: Image: Painting, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX
mozilla1.4alpha

People

(Reporter: paper, Assigned: paper)

Details

This is an offshoot of Bug 753.  The difference is that gfxIImageFrame is not
being combined, and nsIImage is not becoming an IDL.  We'll leave those issues
for that bug.

This bug is for creating an nsImage class, inherited from nsIImage.  All the
nsImage* classes will inherit from nsImage.  Common code from nsImage* can be
moved to nsImage, as well as generic "non platform optimized" functionality can
be added.  Of course, nsImage* can overide functions since they are virtual.

Here's that picture again ;)

                           +----------+
                           |nsImageGTK|
                         _ +----------+
                         /|
+--------+    +-------+ /  +----------+
|nsIImage| -> |nsImage| -> |nsImageWin|
+--------+    +-------+ \  +----------+
                        _\|
                           +---------------+
                           |nsImageWhatever|
                           +---------------+
fwiw, I would name the class either nsImageImpl or nsImageCommon
yes, might as well make it consistent with
nsIRenderingContext/nsRenderingContextImpl
Summary: Create nsImage class; move common code from nsImage* to it → Create nsImageImpl class; move common code from nsImage* to it
Let's see if I can make patches and get it in before 1.4a :)
Priority: -- → P1
Target Milestone: --- → mozilla1.4alpha
QA Contact: tpreston → image.gfx
We don't want nsIImage at all.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.