[Gimp-developer] Minkowski morphological operation plug-ins
Just wanted to post that at long last I've submitted my Minkowski erode, dilate, open, and close plug-ins to the GIMP Plug-in Registry. Regards, Cindy Huyser ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] What is the status of the 16-bit GIMP ?
Not true. I'm a software developer at Rhythm and Hues. We're actively maintaining and developing the 16bit GIMP for use in our studio. There is something a little funky with the autoconf/automake setup that we never fully debugged, and the code is a little unstable right now. There are a couple of extra steps because of the weirdness, but it can be built: aclocal; automake -a; autoconf; ./configure --disable-shared --disable-debug --bindir= --datadir= --prefix= --exec-prefix=; ltconfig --disable-shared ltmain.sh; # have to do this separately for some reason gmake all; New features include things like improved UI, frame manager for editing and painting on multiple frames from an animation clip, and save/restore layout. -Jon On 18 Jan 2002, Sven Neumann wrote: > Hi, > > Marcin Skubiszewski <[EMAIL PROTECTED]> writes: > > > Last time I checked, I was unable to autoconf;./configure the version > > in the CVS. > > as fas as I know the Hollywood GIMP branch is unmaintained. Our plan > is to add 16bit depth per color channel and other colorspaces with > GIMP-2.0. Development on this stuff takes place in the GEGL module > while GIMP itself is still on the road to GIMP-1.4. This is explained > more detailed in http://developer.gimp.org/gimp-future. > > > Salut, Sven > ___ > Gimp-developer mailing list > [EMAIL PROTECTED] > http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer > ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: XCF->PSD [was (psd plug-in, adam's plug-ins)]
At 12:40 PM 1/18/2002 +, Adam D. Moss wrote: > > I'd like to help testing anything related to the psd plug-in, because my > > projectleads are breathing down my neck about 'incompatibility' with the > > rest of my designer collegues. I generally use the previous > > state/version of the plug-in that I patch with the 'write psd' patch, as > > I need to send layered files back to people using Photoshop. Let me know > > if/how you'd like me to go about testing the plug-in. Another option is to use ImageMagick. I recently checked in full support for layered writing of PSD files, and extended the XCF support so that you can now go direct from layered XCF->PSD with all layers and layer attributes (mode, opacity, name, etc.) intact!! I hope that GIMP users will find this useful, and please send any bug reports either directly to me (since I'm the XCF and PSD maintainer) or to the ImageMagick lists. Leonard ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
(psd plug-in, adam's plug-ins) Re: [Gimp-developer] [Fwd: Gimp PSD plugin - SEGV when opening files]
(CC:ing gimp-developer) Hi Avi! 'Testing' just involves getting a reasonably sized collection of PSD files with a good mix of 'real world' data and more unusual stuff (various aux channels, layer masks, strange layer modes, strange pixel formats) and seeing in what ways the PSD loader barfs. A 'good' patch is one that allows a greater number of these files to be successfully read without breaking the reading of files which were previously readable. I don't have the (time) resources currently to support any of my plugins in terms of testing/applying patches or looking into error reports. The former should go to gimp-developer and the latter into bugzilla. My name should probably be commented-out from the MAINTAINERS file until my time situation improves (which seems unlikely for a while). Regards, --Adam Avi Bercovich wrote: > "Adam D. Moss" wrote: > > Hi guys and gals, > > > > Could someone with a good collection of .psd files please > > test this against the PSD plugin to make sure it doesn't > > break anything that was not broken before, and if it > > checks out okay commit it to 1.2 and 1.3? I'm afraid I > > don't have the time for GIMPy stuff at the moment to test > > it myself. > > Hi Adam, > > I'd like to help testing anything related to the psd plug-in, because my > projectleads are breathing down my neck about 'incompatibility' with the > rest of my designer collegues. I generally use the previous > state/version of the plug-in that I patch with the 'write psd' patch, as > I need to send layered files back to people using Photoshop. Let me know > if/how you'd like me to go about testing the plug-in. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] What is the status of the 16-bit GIMP ?
Hi, Marcin Skubiszewski <[EMAIL PROTECTED]> writes: > Last time I checked, I was unable to autoconf;./configure the version > in the CVS. as fas as I know the Hollywood GIMP branch is unmaintained. Our plan is to add 16bit depth per color channel and other colorspaces with GIMP-2.0. Development on this stuff takes place in the GEGL module while GIMP itself is still on the road to GIMP-1.4. This is explained more detailed in http://developer.gimp.org/gimp-future. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] [Fwd: Gimp PSD plugin - SEGV when opening files]
Adam D. Moss wrote: > Hi guys and gals, > > Could someone with a good collection of .psd files please > test this against the PSD plugin to make sure it doesn't > break anything that was not broken before, and if it > checks out okay commit it to 1.2 and 1.3? I'm afraid I > don't have the time for GIMPy stuff at the moment to test > it myself. > > Cheers, > --Adam Hi, I just downloaded the whole source tree of gimp-1.2.2, patched the psd plugin and built the tree. Now, when copying the built psd to /usr/lib/gimp/1.2/plug-ins I get an error when starting gimp and PSD files don't get opened at all (unknown file type). I do not want to overwrite my installed gimp with the freshly built. Is it possible just to replace the psd plugin? Maybe someone can send me the build psd plugin for linux with an instruction on how to replace the file. TIA Marco ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] What is the status of the 16-bit GIMP ?
Last time I checked, I was unable to autoconf;./configure the version in the CVS. Thank you in advance. Marcin. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
