Bug 125200
| Summary: | Rename DragImage to PlatformImage | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Brian Burg <burg> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | darin, simon.fraser, thorton |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 124325 | ||
Brian Burg
DragImage.h and the functions in it are used in lots of places besides dragging code. It should be renamed to something like RenderedImage while retaining platform typedefs. Then, dragging-related callsites can pass parameters to enable drag-specific rendering.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Brian Burg
I would like feedback on this before I go do 500 renamings. What should we do about functions that are only used for dragging (in particular, link and image previews, and the various scaling/dissolving ops)? Should they be named createRenderedImageForLink? In that case, it's implicit that they are doing some extra rendering to make it look pretty for dragging. Maybe the drag-specific things can stay in DragImage.h and non-drag things (and the typedef) can go into RenderedImage.h
Simon Fraser (smfr)
DragImageRef could be PlatformImageRef. It doesn't really have anything to do with renderers.
Brian Burg
(In reply to comment #2)
> DragImageRef could be PlatformImageRef. It doesn't really have anything to do with renderers.
That makes sense. So it would be similar to PlatformLayer, then.