Greg Daniel 9ed1a2cd71 Add ability for an SkDevice to handle the drawing of an SkDrawable. ... If supported, an Sk*Device can take charge of handling of an SkDrawable. The specific use case right now will be to use this to execute Vulkan specific SkDrawable's that need to know information about our Vulkan state and objects at the time the SkDrawable is executed. If a device does not support the SkDrawable we fall back to the cavans version like we did previously. BUG=skia: Change-Id: I821fa600a80ff645412f296be36990ef390ae0a9 Reviewed-on: https://skia-review.googlesource.com/c/7740 Commit-Queue: Greg Daniel <egdaniel@google.com> Reviewed-by: Brian Salomon <bsalomon@google.com>		2018-10-19 15:21:54 +00:00
..
GrVkBackendContext.h	Update vulkan features (again) to support extension features.	2018-08-08 13:48:38 +00:00
GrVkDefines.h	Reland "Reland "Always include public/include headers for vulkan and just guard src files with SK_VULKAN.""	2018-10-03 18:44:59 +00:00
GrVkExtensions.h	Start adding support for some base extensions which others build on.	2018-08-06 14:26:15 +00:00
GrVkMemoryAllocator.h	Always keep buffers in vulkan persistently mapped.	2018-06-01 18:01:26 +00:00
GrVkTypes.h	Add ability for an SkDevice to handle the drawing of an SkDrawable.	2018-10-19 15:21:54 +00:00