| Index: ppapi/shared_impl/image_data_impl.h
|
| diff --git a/ppapi/shared_impl/image_data_impl.h b/ppapi/shared_impl/image_data_impl.h
|
| deleted file mode 100644
|
| index f931c789fd0f10e5e87bef29896edc75f89a1d9c..0000000000000000000000000000000000000000
|
| --- a/ppapi/shared_impl/image_data_impl.h
|
| +++ /dev/null
|
| @@ -1,31 +0,0 @@
|
| -// Copyright (c) 2011 The Chromium Authors. All rights reserved.
|
| -// Use of this source code is governed by a BSD-style license that can be
|
| -// found in the LICENSE file.
|
| -
|
| -#ifndef PPAPI_SHARED_IMPL_IMAGE_DATA_IMPL_H_
|
| -#define PPAPI_SHARED_IMPL_IMAGE_DATA_IMPL_H_
|
| -
|
| -#include "ppapi/c/pp_bool.h"
|
| -#include "ppapi/c/ppb_image_data.h"
|
| -#include "ppapi/shared_impl/ppapi_shared_export.h"
|
| -
|
| -namespace ppapi {
|
| -
|
| -// Contains the implementation of some simple image data functions that are
|
| -// shared between the proxy and Chrome's implementation. Since these functions
|
| -// are just lists of what we support, it's much easier to just have the same
|
| -// code run in the plugin process than to proxy it.
|
| -//
|
| -// It's possible the implementation will get more complex. In this case, it's
|
| -// probably best to have some kind of "configuration" message that the renderer
|
| -// sends to the plugin process on startup that contains all of these kind of
|
| -// settings.
|
| -class PPAPI_SHARED_EXPORT ImageDataImpl {
|
| - public:
|
| - static PP_ImageDataFormat GetNativeImageDataFormat();
|
| - static bool IsImageDataFormatSupported(PP_ImageDataFormat format);
|
| -};
|
| -
|
| -} // namespace ppapi
|
| -
|
| -#endif // PPAPI_SHARED_IMPL_IMAGE_DATA_IMPL_H_
|
|
|