summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKristian Lyngstol <kristian@redpill-linpro.com>2010-04-12 15:52:29 +0200
committerKristian Lyngstol <kristian@redpill-linpro.com>2010-04-12 15:52:29 +0200
commitfaf53c2018ae2ddd61e20ebcd74e3871df118da8 (patch)
tree2ea55ff4e2a2ebdfd99f2bbe9bcc78b8f8fffde7
parent2301066b68df10c7ef1758256503c60f8172f6e0 (diff)
downloadDocumentation-faf53c2018ae2ddd61e20ebcd74e3871df118da8.tar.gz
Documentation-faf53c2018ae2ddd61e20ebcd74e3871df118da8.tar.bz2
Necro-committing! Minor fidgeting for rst2pdf
If you can read this, gimme a hug ;) Discovered most of my documents for the last 10 years are mostly parsed by reStructuredText without significant modification, and went wild. If anyone really does read this though: This is what I wanted from the start with this project but never really found the rst-tool in time.
-rw-r--r--CoreStructures15
-rw-r--r--Makefile11
-rw-r--r--PluginDevelopment11
-rw-r--r--README5
4 files changed, 27 insertions, 15 deletions
diff --git a/CoreStructures b/CoreStructures
index 7c859d6..348ee57 100644
--- a/CoreStructures
+++ b/CoreStructures
@@ -1,12 +1,8 @@
+==========================================================
Beryl's core structures - version this-is-not-complete-yet
-=======================
-0. State of this document - Compiz Fusion
-1. Scope of this document
-2. CompDisplay vs CompScreen
-3. CompDisplay
-4. CompScreen
-5. CompWindow
-6. Regions
+==========================================================
+
+.. contents:: Table of Contents
0. State of this document - Compiz Fusion
=========================================
@@ -86,8 +82,10 @@ where an outputDev starts in the screen. region.x1 defines where the X-coordinat
of that specific window starts, and region.x2 describes where it ends. The same
with region.y1/y2 respectively for the Y coordinate.
For a single monitor with 1024x768, the outputdev will look like this:
+
x1: 0
x2: 1023
+
y1: 0
y2: 767
@@ -119,6 +117,7 @@ it will be quite strange on bigscreen-hinted multihead, specially for
asymetric resolutions)
Here's a drawing of an asymetric multihead setup:
+
+--------+-------------+
| | |
| A | |
diff --git a/Makefile b/Makefile
new file mode 100644
index 0000000..27643c3
--- /dev/null
+++ b/Makefile
@@ -0,0 +1,11 @@
+
+OBJECTS=CoreStructures.pdf PluginDevelopment.pdf
+
+pdf: ${OBJECTS}
+
+CoreStructures.pdf: CoreStructures
+ rst2pdf CoreStructures
+PluginDevelopment.pdf: PluginDevelopment
+ rst2pdf PluginDevelopment
+
+.PHONY: pdf
diff --git a/PluginDevelopment b/PluginDevelopment
index fef9246..19a6718 100644
--- a/PluginDevelopment
+++ b/PluginDevelopment
@@ -1,11 +1,8 @@
+====================================
Plugin development for Compiz Fusion
+====================================
-0. About this document
-1. Plugin initialization and finalization
-2. Dealing with options
-3. Hooking into core
-4. Debugging
-5. Pitfalls
+.. contents:: Table of Contents
0. About this document
======================
@@ -56,7 +53,7 @@ can have multiple displays (though the author has no idea why or how), it is
considered good practice to store the screenPracticeIndex in your
PluginDisplay variable.
-initScreen is called for _each screen_ after this. It should do set up
+initScreen is called for *each screen* after this. It should do set up
the PluginScreen structure and wrap anything related to output. You should
probably read up on Multihead to understand how Compiz may or may not have
multiple CompScreen structures on mutlihead setups. The rule of thumb is
diff --git a/README b/README
index 55892ef..3fa1dc6 100644
--- a/README
+++ b/README
@@ -1,2 +1,7 @@
These documents were originally created for Beryl, but as most of them are
somewhat relevant, they are kept. They will be adjusted for Compiz Fusion.
+
+(or not)
+
+At any rate, I did some minor adjustments for the hell of it to make 'em
+build with rst2pdf. Try it out :p