The union of all files from all check-ins
in the top-level directory
P(x) is hard to describe. It might be called a "Framework", but that's
a grandiose word for a couple of hundred lines of code. It might be
called a programmable calculator, but it has none of the things one
associates with calculators. It might be called a programming
language, but it's just Python with some extra builtins.
For instructions on writing P(x) programs, invoke P with no
arguments. See the examples directory for some simple examples.
A P(x) program has the full power of Python available to it. Anything
you can do in Python, you can do in a P(x) program. This includes
things that would be considered security risks, so you should treat a
P(x) program of unknown origin the same way you'd treat a Python
program of unknown origin.
On Unix, you can begin a P(x) program with "#!/usr/bin/env P" to make
it an executable. On Windows, they should be invoked as "python <path
to P> <path to applet>". I have no idea what it takes to make them
clickable on OS X or Windows. I'd appreciate being told if you know.
Unpack the tarball, and run "python setup.py install" as root in the
applet directory. This will install applet.py in your Python library,
and P as a script in your path. The directory applet/examples holds
P(x) was stolen from - uh, inspired by - the F(x) application for
Symbian OS. See <URL: http://www.symbianfx.com/ > for more information
Lots. See the F(x) web site for ideas, but handling arrays and
graphical output are just the start of the list. Making F(x) scripts
run on P(x) might be a worthwhile goal, but would probably be a lot of