changeset 387 96aed7d43e4d
parent 363 e72f6cceebca
child 389 99e299fc85ea
--- a/docs/userguide/	Fri Jul 14 12:30:53 2000 +0000
+++ b/docs/userguide/	Fri Jul 14 13:22:21 2000 +0000
@@ -173,3 +173,49 @@
+heading1("""Other Useful $Flowables$""")
+heading2("""$Image(filename, width=None, height=None)$""")
+disc("""Create a flowable which will contain the image defined by the data in file $filename$.
+The default <b>PDF</b> image type <i>jpeg</i> is supported and if the <b>PIL</b> extension to <b>Python</b>
+is installed the other image types can also be handled. If $width$ and or $height$ are specified
+then they determine the dimension of the displayed image in <i>points</i>. If either dimension is
+not specified (or specified as $None$) then the corresponding pixel dimension of the image is assumed
+to be in <i>points</i> and used.
+from reportlab.platypus import Image
+disc("""will display as""")
+Image("../../demos/pythonpoint/lj8100.jpg", width=2*inch, height=2*inch)
+""", after=0.1)
+getStory().append(Image(I, width=2*inch, height=2*inch))
+heading2("""$Spacer(width, height)$""")
+disc("""This does exactly as would be expected; it adds a certain amount of space into the story.
+At present this only works for vertical space.
+disc("""This $Flowable$ represents a page break. It works by effectively consuming all vertical
+space given to it. This is sufficient for a single $frame$ document, but would only be a
+frame break for multiple frames so the $BaseDocTemplate$ mechanism
+detects $pageBreaks$ internally and handles them specially.
+disc("""This $flowable$ attempts to force a $Frame$ break if insufficient vertical space remains 
+in the current $Frame$. It is thus probably wrongly named. And should probably be renamed as
+This compound $Flowable$ takes a list of $Flowables$ and attempts to keep them in the same $Frame$.
+If the total height of the $Flowables$ in the list $flowables$ exceeds the current frame's available
+space then all the space is used and a frame break is forced.