From 698569f8428ca088f764d704034a1330517b98c0 Mon Sep 17 00:00:00 2001 From: tpearson Date: Sun, 26 Jun 2011 00:41:16 +0000 Subject: Finish rebranding of Krita as Chalk git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/applications/koffice@1238363 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- chalk/doc/sdk | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 chalk/doc/sdk (limited to 'chalk/doc/sdk') diff --git a/chalk/doc/sdk b/chalk/doc/sdk new file mode 100644 index 00000000..b811d80a --- /dev/null +++ b/chalk/doc/sdk @@ -0,0 +1,10 @@ +Chalk SDK + +The Chalk SDK is in development. Basically, plugins and extensions should +not include anything from chalk/core, but only the headers from chalk/sdk. + +Problem: creating new paint devices, layers and images. You cannot, obviously, +instantiate an interface, and we should not, equally obvious, code against +implementations. The solution is a factory class that is made available to +the plugin when it is created -- i.e, the tqparent class of a plugin should +implement the various factory interfaces for paint devices, images and layers. -- cgit v1.2.1