There is documentation with it in our CVS. Using Cons 2.2.0, the last stable version.Īt this point, don't worry about getting fancy with detecting library paths in Cons, just go ahead and specify those absolutely to your distro locations. You can look at the existing CMake or Autotools build scripts for clues what to put in the Cons build files.Ĭons is in CinePaint CVS. We want to use Cons before getting into improving it. We need to create Cons build files for CinePaint. It may be nothing has changed in a decade. There hasn't been much attention to GIMP Perl.
#Cinepaint tumblr code#
We probably want to use recent GIMP source code and may also want to refer to GIMP 1.0.4 from 1999 (when CinePaint was forked from GIMP). It just makes them mad to mention we exist. IMPORTANT! Do not post any plea for assistance from GIMP. TheyĬonsider CinePaint their rival. Embedding Perl is integration of existing code from GIMP, not a coding project. Limited C knowledge should be sufficient. You may want to review that before starting. O'Reilly "Advanced Perl Programming" has a chapter on embedding Perl. It should be feasible to adapt GIMP code to bring Perl into CinePaint.
Perl's been implemented for GIMP, although active support there seems to have ceased. The other is to support Perl as a scripting language in CinePaint.ĬinePaint supports Scheme and Python as scripting languages now. One is to add CinePaint support for Cons, a clever 3-thousand-line Perl script that replaces Make and Autotools. In CVS I have a little Perl batch script I wrote to create thumbnailed web pages from a directory of images, but that uses GraphicsMagick. Image courtesy of photographer Terry Lane These developer notes are for the benefit of those working on adding Perl support to CinePaint.
0 kommentar(er)
