Export command does not work from CGI engine... :-(
Andre
On 1/30/08, Jim Lambert [EMAIL PROTECTED] wrote:
Really, what I wish I could do is to use something like
the print card function of rev -- which is what the
standalone of my bingocard-maker already relies on --
so that a rev cgi
Export command does not work from CGI engine... :-(
Andre
Ah! So true.
Maybe the server could have a second 'full faced' instance of Rev
running. The cgi Rev could hand off the snapshotting to the regular
Rev, which would create the composite image to be sent to the viewer by
cgi Rev.
With the aid of a framebuffer server such as Xfb you can run a full
stack and use snapshots commands but it takes a while to start, maybe
a cgi and a concurrent running daemon on Xfb communicating thru
sockets would do the trick, but I think is overkill for this project.
My sugestions is: go with
I think the bit you found on the PHP forum is a red herring, if the
image doesn't appear in the HTML code *somewhere* then it's not going
to be visible on the screen. It's impossible to totally stop people
accessing an image that's visible in a browser window, you can only
try to make it
Greetings The List,
For a while, I've been relying on a rev-cgi script
that generates an html table representing a 5x5
picture-bingo card. The rev script embeds the
25 images as urls in the html code. A snippet
of the code is below.
However, from a browser people could easily
peek at the code
What is it that you are trying to stop people doing?
Stop them from downloading any one of the individual
images that together make up a bingo-card. That's
the royalty condition of the images according to the
clip-art company that sold them. Of course, people
could still capture the screen,
This is referring to the method of using a database or non-web
directory to hold the actual data to be displayed (in this case html
links to photos) . The database method inserts the URL at page
creation time, as opposed to it sitting there in static html on a
page. Most of the commercial
You can make it as hard and cumbersome and processing intensive as you
like... But at the end of the day, the images are always downloaded to the
client's web browser. Whether they right-click and crop, open their cache,
hit the Print Screen button, or employ a dozen other techniques... those
Really, what I wish I could do is to use something like
the print card function of rev -- which is what the
standalone of my bingocard-maker already relies on --
so that a rev cgi script could, instead of delivering
individual server-side images, combine those images
into one large card-like
