remove the insanely obsolete sodipodi docs and the inkscape-shadow hack as no longer...

diff --git a/doc/API b/doc/API
deleted file mode 100644 (file)
index 129faa6..0000000
--- a/doc/API
+++ /dev/null
@@ -1,61 +0,0 @@
-
-Sodipodi API's
---------------
-
-This file identifies and discusses various Application Programming
-Interfaces (API's) that exist in the codebase.  This is not intended to
-serve as a complete reference but as a high level overview; details
-should be sought from the appropriate code units.
-
-Stable API's
-============
-
-
-Unstable API's
-==============
-Objects and API-s mentioned here, even if implemented,
-may change without notice.
-
-Special item classes
-~~~~~~~~~~~~~~~~~~~~
-SPGroup::SPBinder
-A group with special children
-For example - blender
-1. first
-2. second
-3... intermediate
-
-Sodipodi New Object Tree TM
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Caution: This does not follow necessarily the Real (TM) implementation
-logic.  This should be updated to capture the correct stuff.
-
- SPItem
- Virtual methods:
-    void update (gdouble affine[]);
-    void bbox ();
-    void print (GnomePrintContext * gpc);
-    gchar * description ();
-    void read ();
-    read_attr (const gchar * attr)
-    GnomeCanvasItem * show (GnomeCanvasGroup * canvas_group, gpointer event_handler);
-    hide (GnomeCanvas * canvas)
-    paint (ArtPixBuf * buf, double affine[]);
- Signals:
- Methods:
-    SPRepr * sp_item_repr ()
-    SPItem * sp_item_parent ()
-
- Constructors:
-    sp_item_new (SPRepr * repr);
-
- Destructors:
-    sp_item_destroy (SPItem * item);
-
- Derivatives:
-
-    SPGroup -> SPDocument
-    SPImage
-    SPPath -> SPShape -> SPRect
-                      -> SPEllipse
-                     -> SPChars -> SPText

diff --git a/doc/Makefile.am b/doc/Makefile.am
index 93648cc2ac435795a369a53cc0c6a071eda808b0..fec2189b3f39a933be84b4fffaea36395ddd4df1 100644 (file)
--- a/doc/Makefile.am
+++ b/doc/Makefile.am
@@ -1,11 +1,8 @@
-EXTRA_DIST = API \
-       README.document \
-       WISHLIST \
+EXTRA_DIST = README.document \
        architecture.svg \
        architecture.txt \
        class-hierarchy.dia \
        coordinates.txt \
-       inkscape-shadow.README \
        keys.README \
        keys.xml \
        keys.de.xml \
@@ -14,5 +11,5 @@ EXTRA_DIST = API \
        keys-html.xsl \
        keys.html \
        keys.de.html \
-        keys.fr.html \
+       keys.fr.html \
        refcounting.txt

diff --git a/doc/WISHLIST b/doc/WISHLIST
deleted file mode 100644 (file)
index e083a59..0000000
--- a/doc/WISHLIST
+++ /dev/null
@@ -1,51 +0,0 @@
-
-Inkscape Wishlist
------------------
-This file is for capturing random details about desired development
-work, ideas, etc.  The Inkscape feature request page is probably a
-better location for such things, but this can serve as a convenient
-scratchpad. 
-
-
-Rework xml tree
-===============
-use reprs as lightweight wrappers around gnome-xml,
-keeping syntax as close to DOM as possible
-
-
-Split SPDesktop object into modular inherited objects
-=====================================================
-SPDesktop - base, has drawing group, no contexts
-SPEDesktop - editable desktop - more full-featured
-SPNamedDesktop - Desktop, deriving its layout from NamedView - i.e. guides,
-  grid etc. will be saved per-desktop
-
-desktop_show_borders/hide_borders - show/hide rulers & stuff - usable for
-  Bonobo component
-
-
-
-Javascript for Animation support(?)
-===================================
-> The mozilla javascript engine is under dual MPL/GPL
-> (http://lxr.mozilla.org/seamonkey/source/js/src/) and written in C. 
-> Hopefully there's some nice way to build off that...
-
-The main reason JavaScript would be tricky is that it would be modifying
-the document out from under you via the DOM, so you couldn't have a
-"time slider" or something like you could for the SMIL stuff.
-
-That's a real headache, and the only way I can see it working is if the
-document is cloned and played back in a separate "audition" window, then
-the modified document thrown away at the end.
-
-But then, why implement Javascript in Inkscape?  An audition feature
-that calls out to an external player application would work just as well
-(and indeed, that's exactly how applications like Flash cope with
-scripting).
-
-[ note that implementing scripting for Inkscape itself is a separate
-issue, and probably warrants a language-agnostic scripting interface
-like the GIMP's PDB, only less grotty ]
-
--- Mental
\ No newline at end of file

diff --git a/doc/inkscape-shadow.README b/doc/inkscape-shadow.README
deleted file mode 100644 (file)
index d555fd9..0000000
--- a/doc/inkscape-shadow.README
+++ /dev/null
@@ -1,63 +0,0 @@
-== BLURRED SHADOWS VIA BITMAPS
-
-The "Make a Bitmap Copy" command (Alt+B) exports a bitmap of 
-the selected objects (with all other objects hidden), saves it as a 
-PNG file in the same directory as the document, and imports it 
-back into the document.
-
-Via prefs, you can specify an external filter that will be run on the
-PNG file after it is exported but before it is imported back. I use
-this for grayscaling and blurring the image to create a soft drop
-shadow for any object. So for me, Alt+B creates a shadow for
-selected objects, and you can set it up to work the same for you.
- 
-The script itself is share/extensions/inkscape-shadow.sh, though 
-it's not integrated nto the extensions or plugin system in any way. 
-The script requires Imagemagick 6.x to be installed; you can 
-modify the script as you like, probably adapting it for effects
-other than shadows. The script is Unix-only; you can create
-a similar batch file for Windows if you need it (send it to us
-if you do).
- 
-To enable this, you set in your ~/.inkscape/preferences.xml:
- 
-    <group
-        id="createbitmap"
-        minsize="250"
-        filter="/full/path/to/inkscape-shadow.sh"
-        filter_param1="20" />
-
-Here minsize= gives the minimum size of the generated bitmap in 
-pixels (regardless of the object size); alternatively you can specify 
-resolution= to set the constant resolution (different pixel size
-for different object sizes).
- 
-In filter=, you specify either the full path to the script, or just
-"inkscape-shadow.sh" if the script is in your PATH. The script
-receives the image filename as the first parameter and the
-filter_param1 as the second parameter (more parameters can be 
-added). This particular script interprets that as the blur radius 
-in pixels, but of course that depends on the script you use.
-
-The inkscape-shadow-white.sh script is the same but creates all-white
-blurred shadows ("glows") instead of all-black.
- 
-NOTE: I'm not going to provide a GUI for the blurred shadows feature,
-for these reasons:
- 
- 1. You have to carry around the shadow PNGs along your SVG. It's
- inconvenient, and the PNGs may be much larger than the SVG.
- 
- 2. The shadows are not resolution-independent and are not updated
- automatically. For all this, we need to support the gaussian blur SVG
- filter (a standard SVG feature). But since we don't have any filter
- support yet, hence this hack.
- 
- 3. Both Batik and Adobe have (different) problems with displaying PNGs
- with alpha transparency. (Much like the Internet Exploder - shame on
- them! :) This means that while this is valid SVG, its usefulness is
- pretty much limited to Inkscape only.
- 
-Still, for those who desperately need blurred shadows right now (such
-as myself), this feature works well enough. Try it out, it's fun.
-