Rev 332 | Rev 385 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
Rev 332 | Rev 384 | ||
---|---|---|---|
Line 1... | Line 1... | ||
1 | 1 | ||
2 | Please download the Adobe Photoshop SDK here: |
2 | How to download the latest version of the SDK: |
3 | https://www.adobe.com/devnet/photoshop/sdk.html |
- | |
4 | Note: The download of SDK 2017 at the end of the EULA page |
- | |
5 | won't work on some browsers due to security settings: |
- | |
6 | "adobe.com" uses HTTPS, while the download target "macromedia.com" uses HTTP. |
- | |
7 | Therefore, the download does not work. |
- | |
8 | Direct download of SDK 2017 here: |
- | |
9 | http://download.macromedia.com/pub/developer/photoshop/sdk/adobe_photoshop_sdk_cc_2017_win.zip |
- | |
10 | 3 | ||
- | 4 | 1. Go to https://www.adobe.com/devnet/photoshop/sdk.html |
|
11 | 5 | ||
- | 6 | 2. At the section "C++ SDK", click "Download the SDK" |
|
12 | 7 | ||
13 | Important: |
- | |
14 | Please carefully read the SDK EULA before processing! |
- | |
15 | The SDK contents are NOT part of this plugin source code, |
8 | 3. You need to create a Adobe developer account now, |
16 | and they are not subject to the plugin's license! |
9 | or log in if you already have an account. |
17 | The SDK contents may not be distributed together with the plugin |
- | |
18 | or the plugin source code, and must stay on the computer of the developer. |
- | |
19 | 10 | ||
20 | If you do not agree to the EULA of the latest SDK, |
- | |
21 | you could try to obtain an older version of the SDK which |
11 | 4. Scroll down to "Photoshop" (NOT "Adobe Photoshop API (Trial)") |
22 | might have different license terms. This plugin should be |
- | |
23 | compatible with older versions of the SDK too. |
12 | and then click "View downloads". |
24 | 13 | ||
- | 14 | 5. Download "Photoshop Plug-In and Connection SDK" for Windows. |
|
25 | 15 | ||
26 | Once you have obtained the SDK, extract the SDK contents in this directory: |
16 | 6. Once you have obtained the SDK, extract the SDK contents in the "photoshop_sdk" directory: |
27 | - connectionsdk/ |
17 | - connectionsdk/ |
28 | - images/ |
18 | - images/ |
29 | - pluginsdk/ |
19 | - pluginsdk/ |
30 | - license.html |
20 | - license.html |
31 | - ReadMe.html |
21 | - ReadMe.html |
32 | 22 | ||
33 | These folders are excluded in SVN and GIT to avoid that they |
23 | These folders are excluded in SVN and GIT to avoid that they |
34 | are accidentally uploaded somewhere. |
24 | are accidentally uploaded somewhere. |
35 | 25 | ||
36 | - | ||
37 | Actually, you only need the following files: |
26 | Note: Actually, you only need the following files: |
38 | - pluginsdk/photoshopapi/photoshop/*.h |
27 | - pluginsdk/photoshopapi/photoshop/*.h |
39 | - pluginsdk/photoshopapi/pica_sp/*.h |
28 | - pluginsdk/photoshopapi/pica_sp/*.h |
40 | - pluginsdk/photoshopapi/resources/*.r |
29 | - pluginsdk/photoshopapi/resources/*.r |
41 | 30 | ||
42 | 31 | ||
- | 32 | Important: |
|
- | 33 | Please carefully read the SDK EULA before processing! |
|
- | 34 | The SDK contents are NOT part of this plugin source code, |
|
- | 35 | and they are not subject to the plugin's license! |
|
- | 36 | The SDK contents may not be distributed together with the plugin |
|
- | 37 | or the plugin source code, and must stay on the computer of the developer. |
|
- | 38 | ||
- | 39 | If you do not agree to the EULA of the latest SDK, |
|
- | 40 | you could try to obtain an older version of the SDK which |
|
- | 41 | might have different license terms. For example, the SDK was |
|
- | 42 | also distributed with Photoshop 6.0 and earlier. |
|
- | 43 | ||
- | 44 | ||
- | 45 | Compatibility: |
|
- | 46 | The source code has been built with SDK 6.0, CS2, CS3 beta, CC 2017, and 2022 |
|
- | 47 | but older versions should work, too. |
|
- | 48 | (If building with SDK v4, edit 68k.r, carbon.r, classic.r, and PiMI_68k.r |
|
- | 49 | to remove references to "PIResDefines.h", "PiPL.r" and "PiMI.r" and replace |
|
- | 50 | with a single #include "PIGeneral.r"; also remove "fmtCanWriteTransparency" |
|
- | 51 | from PiPL_common.r.) |
|
- | 52 | ||
- | 53 | ||
43 | Additional notes: |
54 | Additional notes: |
44 | - Adobe's stand in regards to using SDK to write OpenSource plugins: |
55 | - Adobe's stand in regards to using SDK to write OpenSource plugins: |
45 | https://web.archive.org/web/20070203075622/http://blogs.adobe.com/notesfrommnr/2006/04/using_adobe_sdk.html |
56 | https://web.archive.org/web/20070203075622/http://blogs.adobe.com/notesfrommnr/2006/04/using_adobe_sdk.html |
46 | So it should be fine if the SDK contents are not included in the plugin's source code and not part of the license. |
57 | So it should be fine if the SDK contents are not included in the plugin's source code and not part of the license. |
47 | - The GPL license has some problems with this: |
58 | - The GPL license has some problems with this: |