Which version? Here's code for an old version (v5.0?) http://www.telegraphics.com.au/svn/abrformat/trunk/ ... View more

This would be the wrong forum. In fact you've probably got the wrong company -- try Quark support. ... View more

Portable plugins aren't difficult; Adobe's API is crossplatform. As for .NET, the Mac has no runtime for it. Plan to use C/C++, or do what Microsoft hopes, and write for Windows only. ... View more

Don't hold your breath - we'll have to wait out the decline of the monopoly first. But in the meantime try out Inkscape. Illustrator and Photoshop will run under WINE or CrossOver Linux. ... View more

Re: Xcode, Sample project for CS2 plugin is provided here. Xcode cannot build plugins for earlier versions of Illustrator (MPW and CodeWarrior can). ... View more

My GPL Illustrator plugins can be found here - one Tool and several Filters which create/manipulate paths. ... View more

Apologies for the confusion, that's a "custom" PiPL.r created some time ago before I saw the PS7 SDK, Adobe called it something different. You'll have to refer to the official SDK for the precise name but in other respects it's identical of course. I've never used the third parameter, but my v6 documentation describes it as follows: Pstring fEntryName Pascal string used to lookup the address of the function to call within the fragment. In order for the Code Fragment Manager to find an entrypoint by name, that name must be an exported symbol of the code fragment. If NULL, the default entrypoint will be used. fEntryName allows a single code fragment to contain more than one plug-in. One day I mean to regularise my sources to match their official published selectors for Carbon CFM and Mach-O... The disparity is an artefact of the SDK's Iron Curtain period. ... View more

Ivan, it should be clear from my MPW makefiles (via link above). Also you should be able to find this documented in the SDK, and/or in PiPL.r. ... View more

The normal way of dealing with this in a filter is to define the FilterCaseInfo in the PiPL, for each of: filterCaseFlatImageNoSelection filterCaseFlatImageWithSelection filterCaseFloatingSelection filterCaseEditableTransparencyNoSelection filterCaseEditableTransparencyWithSelection filterCaseProtectedTransparencyNoSelection filterCaseProtectedTransparencyWithSelection This defines how input data is matted, or whether you wish to use the transparency data directly (see PIFilter.h and PiPL.r). ... View more

The same approach used to package Carbon/Classic in one file can be used to ship multiple Carbon plugins. Just link separately and set the appropriate executable offset and length in each respective PiPL. (This can be automated by MPW, of course.) If you don't wish to link separately and instead want multiple entry points, I have not done that. Perhaps someone from Adobe can confirm whether that works. ... View more

Easy - all my plugin projects do this - examine the MPW makefiles. ... View more

There's also Hugin, I'm currently trying out. But why is this thread in the SDK forum?? ... View more

MNR -> Mark Neimann-Ross, also see http://blogs.adobe.com/notesfrommnr/ ... View more

It doesn't look inside IRBs, but you might find my PSD parser useful as reference. It extracts all raster data. ... View more

You noticed you can use the planeMap[] array to permute the channels. It's not so obvious that Photoshop should offer generalised bit depth/colour space/palette processing. It can be argued that's the role of the plugin itself: to mediate between Photoshop's native image data (which it does offer conveniently) and whatever arbitrary image format the user requires. At least, that's what most of my plugins do. Sure, there are a few obvious conversions, but you have to stop somewhere... Sooner or later you'll be implementing stuff on the Photoshop side that should be in a plugin. I don't have a big problem with the line drawn in the current API. ... View more

As you guess, it is stored in the PSD, but only with the Maximise Compatibility switch. Without that switch, a dummy image is stored which has the text "This layered Photoshop file was not saved with a composite image.", in English, German, Japanese and French. My program psdparse extracts each layer in an 8-bit file as a PNG, and the merged image for both 8- and 16-bit files. That link is to a Subversion repository containing source code. ... View more

Despite the fact that SupportedModes has a bit for it, I don't believe Filter plugins are/were ever allowed in Bitmap mode. ... View more

I haven't seen the CS2 SDK, but typically Photoshop decides when to disable/enable plugins based on the PiPL (property list). Have you set any relevant flag in the PiPL? ... View more

What development environment are you using? On Windows, building plugins with VS6 and VS2005, I recently found that crashes could be caused by using malloc() to allocate data that is supposed to persist between plugin calls (such as the pb->parameters block). Changing to the pb->handleProcs calls fixed this issue. Using malloc()/free() within a single plugin entry does not appear to be a problem. ... View more

Yesterday I added an NMAKE makefile to my most recent plugin, Scramble. This means you can easily build it with the VS6 tools (or any Visual Studio CLI toolkit). Starting from that code, you can modify it to make an Export plugin. ... View more

After testing Visual Studio Express, I can report mixed results: The IDE has been crippled so that it cannot build DLL projects. The command line compiler and linker supplied with VS Express work just fine to build plugins, with a suitable makefile. I have written such a makefile ( nmake.mak) as part of my latest release, Scramble. (The same makefile works with VS6 and should work with the free VS CLI Toolkit.) ... View more

For Windows, you can use any Visual Studio (including the free versions), or Borland (free), Watcom (free), MinGW (free), CodeWarrior and others. My earlier post has some links. The Adobe sample code is only tested against a recent Visual Studio (and CodeWarrior?), so that is usually the easiest system to get started with. For Mac, CodeWarrior, MPW (free), and Xcode (free, but builds for CS2 only). Disclaimer: I don't know which of these support symbolic debugging (I don't use it). ... View more

Visual Studio Express should work. Contact me for more specific information. Some Visual Studio 6 projects, and much portable plugin source code, is available from my site. In fact nearly all of the free Windows development systems will work, including Borland CBuilder, OpenWatcom, and probably Digital Mars and lcc-win32. I use MinGW (a complete GNU-based Win32 development system) frequently to build Illustrator and Photoshop plugins. ... View more

> It's my understanding that psd format is essentially Tiff with some custom/extended tags. No, there is no similarity. Also, TIFF is better documented and more extensible. ... View more

Sample code for many different types of plugins can be found on my site - (to check out the sources you need a Subversion client installed, such as TortoiseSVN). Contact me if you want an Export sample tailored to VS6. ... View more

It will install and run fine, but you may need to tweak page file settings: http://groups.google.ca/group/alt.graphics.photoshop/msg/10f4f3bd133c0ae1?hl=en& ... View more

"We can't tell you until you've paid." ... View more

All this, and more, would be possible if Adobe did not insist on absolute secrecy in order to discourage plugin development. A modern software company would offer something better than this creaky, obsolete forum software, too: It's 2006, why not a TWiki? ... View more

Yes. ... View more

PSDs (layers and all) can definitely be used directly in InDesign - it was always one of ID's selling points. ... View more