summaryrefslogtreecommitdiff
path: root/graphics/py-piddle
AgeCommit message (Collapse)AuthorFilesLines
2008-06-12Add DESTDIR support.joerg1-1/+3
2006-10-04Update MASTER_SITES and/or HOMEPAGE, from Sergey Svishchev.wiz1-2/+2
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg1-2/+2
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-24Add RMD160 digestsagc1-1/+2
2004-07-22add python as categoryrecht1-2/+2
ok'd a while back at pkgsrcCon by agc and wiz
2004-05-02Convert to buildlink3.snj1-2/+2
2003-09-21Bump rev so folks get proper PLISTjmc1-1/+2
2003-09-21Add missing piddle.pthjmc1-1/+2
2003-09-21Add USE_BUILDLINK2 so this picks up a proper dependjmc1-1/+2
2003-09-14hange extension.mk to also install optimized files for distutils packages.recht1-1/+33
Inspired by FreeBSD "ports". Fix the PLISTs accordingly. Also, while at it, remove now obsolete compileall.py calls in post-install targets and insure that extension.mk is in included before builinlinks of other Python modules. Discussed with/ok'ed by drochner@.
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-06-02Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages.jschauma1-2/+2
Should anybody feel like they could be the maintainer for any of thewe packages, please adjust.
2002-10-30Initial import of py-piddle-1.0.15markd4-0/+189
Plug In Drawing, Does Little Else. A cross-platform drawing library for Python. PIDDLE is a Python module for creating two-dimensional graphics in a manner that is both cross-platform and cross-media; that is, it can support screen graphics (e.g. QuickDraw, Windows, Tk) as well as file output (PostScript, PDF, GIF, etc.). It makes use of the native 2D drawing calls of each backend, for maximum efficiency and quality. It works by defining a base class (piddle.Canvas) with methods for all supported drawing primitives. A particular drawing context is provided in the form of a derived class. PIDDLE applications will be able to automatically select an appropriate backend for the user's environment.