incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ksch...@apache.org
Subject svn commit: r1206299 [19/19] - in /incubator/ooo/ooo-site/trunk/content/gsl: canvas/ canvas/api/ canvas/api/geometry/ canvas/api/index-files/ canvas/api/rendering/ psprint/ vcl/ vcl/plugins/
Date Fri, 25 Nov 2011 20:07:51 GMT
Added: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XVolatileBitmap-xref.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XVolatileBitmap-xref.html?rev=1206299&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XVolatileBitmap-xref.html (added)
+++ incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XVolatileBitmap-xref.html Fri Nov 25 20:06:37 2011
@@ -0,0 +1,65 @@
+<html>
+<head>
+<title>Uses of Interface XVolatileBitmap-xref</title>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<link rel="stylesheet" type="text/css" href="../../../../idl.css">
+</head>
+<body>
+<div id="adc-idlref">
+
+<a name="_top_"> </a>
+<table class="navimain" border="0" cellpadding="3">
+<tr>
+<td class="navimain"><a href="../module-ix.html" class="navimain">Overview</a></td>
+<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+<td class="navimainself">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" class="title-table" style="margin-bottom:6pt;">
+<tr>
+<td class="title">uses of interface XVolatileBitmap</td>
+</tr>
+<tr>
+<td><p><a href="XVolatileBitmap.html"><b>back to interface XVolatileBitmap</b></a><br>
+<br>
+
+Derived Interfaces<br>
+
+Synonym Typedefs<br>
+
+Services which Support this Interface<br>
+
+Singletons which Support this Interface<br>
+
+<a href="#Returns">Uses as Return Type<br>
+
+</a>Uses as Parameter<br>
+
+Uses as Data Type<br>
+
+References in Developers Guide<br>
+
+</p>
+</td>
+</tr>
+</table>
+<hr>
+<a name="Returns"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle">Uses as Return Type</td>
+</tr>
+<tr>
+<td><a href="XGraphicDevice.html">XGraphicDevice</a>::<a href="XGraphicDevice.html#createVolatileAlphaBitmap">createVolatileAlphaBitmap()</a><br>
+<a href="XGraphicDevice.html">XGraphicDevice</a>::<a href="XGraphicDevice.html#createVolatileBitmap">createVolatileBitmap()</a><br>
+</td>
+</tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright &copy; 2003 Sun Microsystems, Inc.</p>
+
+</div> <!-- id="adc-idlref" -->
+</body>
+
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XVolatileBitmap-xref.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XVolatileBitmap.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XVolatileBitmap.html?rev=1206299&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XVolatileBitmap.html (added)
+++ incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XVolatileBitmap.html Fri Nov 25 20:06:37 2011
@@ -0,0 +1,129 @@
+<html>
+<head>
+<title>Interface XVolatileBitmap</title>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<link rel="stylesheet" type="text/css" href="../../../../idl.css">
+</head>
+<body>
+<div id="adc-idlref">
+
+<a name="_top_"> </a>
+<table class="navimain" border="0" cellpadding="3">
+<tr>
+<td class="navimain"><a href="../module-ix.html" class="navimain">Overview</a></td>
+<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+<td class="navimain"><a href="XVolatileBitmap-xref.html" class="navimain">Use</a></td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<table class="navisub" border="0" cellpadding="0">
+<tr>
+<td class="navisub"><a href="#MethodsSummary" class="navisub">Methods' Summary</a></td>
+<td class="navisub"><a href="#MethodsDetails" class="navisub">Methods' Details</a></td>
+<td class="navisub">Attributes' Summary</td>
+<td class="navisub">Attributes' Details</td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" class="title-table" style="margin-bottom:6pt;">
+<tr>
+<td><p class="namechain"><a href="../../../../module-ix.html" class="namechain">::</a> <a href="../../../module-ix.html" class="namechain">com</a> :: <a href="../../module-ix.html" class="namechain">sun</a> :: <a href="../module-ix.html" class="namechain">star</a> :: <a href="module-ix.html" class="namechain">rendering</a> :: </p>
+</td>
+</tr>
+<tr>
+<td class="title"><table class="title-table" width="99%">
+<tr>
+<td width="25%" class="title2">unpublished </td>
+<td width="50%" class="title">interface XVolatileBitmap</td>
+<td width="*"/></tr>
+</table>
+</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Base Interfaces</b></dt>
+<dd><pre style="font-family:monospace;"><strong>XVolatileBitmap</strong>
+&#x2517 <a href="XBitmap.html">XBitmap</a>
+   &#x2517 ::com::sun::star::uno::XInterface
+
+</pre></dd>
+<dd><a name/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="crosstitle">
+<tr>
+<td class="imsum_left"><a href="XBitmap.html">XBitmap</a></td>
+<td class="imsum_right"><dl>
+<dt>(referenced interface's summary:)</dt>
+<dd>This is a generic interface to a bitmap. </dd>
+</dl>
+</td>
+</tr>
+</table>
+</dd>
+</dl>
+</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Description</b></dt>
+<dd>This is a specialized interface to a volatile bitmap (which can 
+become invalid at any point in time). 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+<hr>
+<a name="MethodsSummary"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Methods' Summary</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#isValid">isValid</a></td>
+<td class="imsum_right">Query whether this volatile bitmap still has valid content. 
+
+As the video RAM allocated to this bitmap can be reclaimed at 
+any time, a return value of true here does not imply that the 
+next draw operation with this bitmap will succeed. Instead, 
+the exception VolatileContentDestroyed will be thrown then. 
+&nbsp;</td>
+</tr>
+</table>
+<a name="MethodsDetails"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle">Methods' Details</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="isValid" class="membertitle">isValid</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-method" bgcolor="#ffffff" align="center">
+<tr>
+<td><table class="table-in-method" border="0">
+<tr>
+<td valign="top" colspan="3">boolean</td>
+</tr>
+<tr>
+<td valign="top"><b>isValid</b>();</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Query whether this volatile bitmap still has valid content. 
+
+As the video RAM allocated to this bitmap can be reclaimed at 
+any time, a return value of true here does not imply that the 
+next draw operation with this bitmap will succeed. Instead, 
+the exception VolatileContentDestroyed will be thrown then. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright &copy; 2003 Sun Microsystems, Inc.</p>
+
+</div> <!-- id="adc-idlref" -->
+</body>
+
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XVolatileBitmap.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/module-ix.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/module-ix.html?rev=1206299&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/module-ix.html (added)
+++ incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/module-ix.html Fri Nov 25 20:06:37 2011
@@ -0,0 +1,428 @@
+<html>
+<head>
+<title>Module rendering</title>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<link rel="stylesheet" type="text/css" href="../../../../idl.css">
+</head>
+<body>
+<div id="adc-idlref">
+
+<a name="_top_"> </a>
+<table class="navimain" border="0" cellpadding="3">
+<tr>
+<td class="navimain"><a href="../module-ix.html" class="navimain">Overview</a></td>
+<td class="navimainself">Module</td>
+<td class="navimainnone">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<table class="navisub" border="0" cellpadding="0">
+<tr>
+<td class="navisub">Nested Modules</td>
+<td class="navisub"><a href="#Services" class="navisub">Services</a></td>
+<td class="navisub">Singletons</td>
+<td class="navisub"><a href="#Interfaces" class="navisub">Interfaces</a></td>
+<td class="navisub"><a href="#Structs" class="navisub">Structs</a></td>
+<td class="navisub"><a href="#Exceptions" class="navisub">Exceptions</a></td>
+<td class="navisub"><a href="#Enums" class="navisub">Enums</a></td>
+<td class="navisub"><a href="#Typedefs" class="navisub">Typedefs</a></td>
+<td class="navisub"><a href="#ConstantGroups" class="navisub">Constant Groups</a></td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" class="title-table" style="margin-bottom:6pt;">
+<tr>
+<td><p class="namechain"><a href="../../../../module-ix.html" class="namechain">::</a> <a href="../../../module-ix.html" class="namechain">com</a> :: <a href="../../module-ix.html" class="namechain">sun</a> :: <a href="../module-ix.html" class="namechain">star</a> :: </p>
+</td>
+</tr>
+<tr>
+<td class="title">module rendering</td>
+</tr>
+<tr>
+<td/></tr>
+</table>
+<hr>
+<a name="Services"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Services</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="BitmapCanvas.html">BitmapCanvas</a></td>
+<td class="imsum_right">This service provides the interfaces for a BitmapCanvas 
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="Canvas.html">Canvas</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="CanvasFactory.html">CanvasFactory</a></td>
+<td class="imsum_right">The <a href="CanvasFactory.html">CanvasFactory</a> is used to create the <a href="Canvas.html">Canvas</a> 
+objects, evaluating the user's configuration preferences from 
+
+<code>/org.openoffice.VCL/Settings/Canvas/PreferredServices </code>. 
+
+The latter specifies a string list of service names to use. 
+
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="ParametricPolyPolygon2DFactory.html">ParametricPolyPolygon2DFactory</a></td>
+<td class="imsum_right"/></tr>
+</table>
+<a name="Interfaces"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Interfaces</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XAnimatedSprite.html">XAnimatedSprite</a></td>
+<td class="imsum_right">This interface can be used to control an animated sprite object. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XAnimation.html">XAnimation</a></td>
+<td class="imsum_right">This interface defines an animation sequence. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XBezierPolyPolygon2D.html">XBezierPolyPolygon2D</a></td>
+<td class="imsum_right">This is a specialized interface for a 2D poly-polygon containing 
+straight line and bezier segments. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XBitmap.html">XBitmap</a></td>
+<td class="imsum_right">This is a generic interface to a bitmap. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XBitmapCanvas.html">XBitmapCanvas</a></td>
+<td class="imsum_right">This is a specialization of the canvas interface for bitmapped 
+canvases. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XBitmapPalette.html">XBitmapPalette</a></td>
+<td class="imsum_right">Interface to access the palette of a color-indexed bitmap. 
+
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XBufferController.html">XBufferController</a></td>
+<td class="imsum_right">Interface providing access to double/multi-buffer facilities of 
+screen devices. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XCachedPrimitive.html">XCachedPrimitive</a></td>
+<td class="imsum_right">Interface for cached repaint of already drawn <a href="XCanvas.html">XCanvas</a> 
+primitives. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XCanvas.html">XCanvas</a></td>
+<td class="imsum_right">Central interface for rendering. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XCanvasFont.html">XCanvasFont</a></td>
+<td class="imsum_right">This interface provides access to a specific, XCanvas-dependent 
+font incarnation. This font is not universally usable, but belongs 
+to the XCanvas it was queried from. 
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XColorSpace.html">XColorSpace</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="XCustomSprite.html">XCustomSprite</a></td>
+<td class="imsum_right">Interface to control a custom sprite object on a XSpriteCanvas. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XGraphicDevice.html">XGraphicDevice</a></td>
+<td class="imsum_right">This interface provides access to a graphic device, such as a 
+printer, or a screen device. Every canvas ( </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XHalfFloatBitmap.html">XHalfFloatBitmap</a></td>
+<td class="imsum_right">Specialized interface for bitmaps containing half floats as their 
+color components. Half floats are 16 bit wide, and some high-end 
+GPUs already have them as supported frame buffer format. 
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XIeeeDoubleBitmap.html">XIeeeDoubleBitmap</a></td>
+<td class="imsum_right">This is a specialized interface for bitmaps containing IEEE 
+doubles for their color components. 
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XIeeeFloatBitmap.html">XIeeeFloatBitmap</a></td>
+<td class="imsum_right">Specialized interface for bitmaps containing IEEE floats as their 
+color components. 
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XIntegerBitmap.html">XIntegerBitmap</a></td>
+<td class="imsum_right">This is a specialized interface for bitmaps having integer color 
+channels. 
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XLinePolyPolygon2D.html">XLinePolyPolygon2D</a></td>
+<td class="imsum_right">Specialized interface for a 2D poly-polygon containing only straight line segments. 
+
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XParametricPolyPolygon2D.html">XParametricPolyPolygon2D</a></td>
+<td class="imsum_right">Interface to a dynamic poly-polygon generator, that generates 
+poly-polygons depending on a given parameter value. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XParametricPolyPolygon2DFactory.html">XParametricPolyPolygon2DFactory</a></td>
+<td class="imsum_right">This interface provides factory methods to generate various 
+ready-made XParametricPolyPolygon2Ds 
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XPolyPolygon2D.html">XPolyPolygon2D</a></td>
+<td class="imsum_right">Generic interface for poly-polygons in 2D. 
+
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XSimpleCanvas.html">XSimpleCanvas</a></td>
+<td class="imsum_right">Provides the basic graphical output operations for a canvas. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XSprite.html">XSprite</a></td>
+<td class="imsum_right">Interface to control a sprite object. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XSpriteCanvas.html">XSpriteCanvas</a></td>
+<td class="imsum_right">Specialization of a XBitmapCanvas, where moving, animated objects 
+(called sprites) are supported. 
+
+@attention The screen output of canvas drawing operations is 
+undefined, unless XSpriteCanvas::updateScreen() is called. This is 
+because a sprite canvas might choose to employ double buffering to 
+reduce animation flicker, and cannot know the instant suitable to 
+display the newly rendered canvas content. When using external 
+double-buffering via XBufferController on a sprite canvas, the 
+implementation takes care of this issue, and in this case is able 
+to render correctly even without explicit updateScreen() calls 
+(because there's a defined moment in time where content display 
+can happen, namely the XBufferController::showBuffer()) call. If 
+you don't need sprite functionality, and don't want the 
+updateScreen hassle, simply use the XBitmapCanvas. 
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XTextLayout.html">XTextLayout</a></td>
+<td class="imsum_right">This is the central interface for text layouting. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XVolatileBitmap.html">XVolatileBitmap</a></td>
+<td class="imsum_right">This is a specialized interface to a volatile bitmap (which can 
+become invalid at any point in time). 
+</td>
+</tr>
+</table>
+<a name="Structs"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Structs</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="AnimationAttributes.html">AnimationAttributes</a></td>
+<td class="imsum_right">This structure contains attributes needed to run an animation. 
+
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="Caret.html">Caret</a></td>
+<td class="imsum_right">This structure contains the caret information. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="ColorProfile.html">ColorProfile</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="ColorSpaceType.html">ColorSpaceType</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="FloatingPointBitmapLayout.html">FloatingPointBitmapLayout</a></td>
+<td class="imsum_right">This structure describes the memory layout of a bitmap having 
+floating point color channels. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="FontInfo.html">FontInfo</a></td>
+<td class="imsum_right">This structure provides information about a specific font. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="FontMetrics.html">FontMetrics</a></td>
+<td class="imsum_right">Metrics global to the font, i.e. not specific to single 
+glyphs. The font height is defined as 
+ascent+descent+internalLeading, and therefore not explicitely 
+included here. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="FontRequest.html">FontRequest</a></td>
+<td class="imsum_right">This structure contains all information necessary to describe a 
+font to be queried from XCanvas. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="IntegerBitmapLayout.html">IntegerBitmapLayout</a></td>
+<td class="imsum_right">This structure describes the memory layout of a bitmap having 
+integer color channels. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="Panose.html">Panose</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="RenderState.html">RenderState</a></td>
+<td class="imsum_right">This structure contains information passed to each 
+<a href="XCanvas.html">XCanvas</a> render operation. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="StringContext.html">StringContext</a></td>
+<td class="imsum_right">Collection of string-related arguments used on all canvas text 
+interfaces. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="StrokeAttributes.html">StrokeAttributes</a></td>
+<td class="imsum_right">This structure contains all attributes required for path stroking. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="TextHit.html">TextHit</a></td>
+<td class="imsum_right">This structure contains hit information for <a href="XTextLayout.html">XTextLayout</a> . </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="Texture.html">Texture</a></td>
+<td class="imsum_right">Contains all information needed to define a texture. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="ViewState.html">ViewState</a></td>
+<td class="imsum_right">This structure contains information considered the view state. </td>
+</tr>
+</table>
+<a name="Exceptions"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Exceptions</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="VolatileContentDestroyedException.html">VolatileContentDestroyedException</a></td>
+<td class="imsum_right">This exception indicates an invalid volatile bitmap content. </td>
+</tr>
+</table>
+<a name="Enums"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Enums</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="FillRule.html">FillRule</a></td>
+<td class="imsum_right">Determines which algorithm to use when determining inside and 
+outside of filled poly-polygons. 
+
+</td>
+</tr>
+</table>
+<a name="Typedefs"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Typedefs</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="ColorComponent.html">ColorComponent</a></td>
+<td class="imsum_right">Shorthand for the device-dependent color components, and easier to read </td>
+</tr>
+</table>
+<a name="ConstantGroups"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Constant Groups</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="AnimationRepeat.html">AnimationRepeat</a></td>
+<td class="imsum_right">This are the possible repeat modes for animations. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="CompositeOperation.html">CompositeOperation</a></td>
+<td class="imsum_right">These constants determine how the primitive color is combined with 
+the background. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="EmphasisMark.html">EmphasisMark</a></td>
+<td class="imsum_right">These constants control the automatic rendering of emphasis marks. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="Endianness.html">Endianness</a></td>
+<td class="imsum_right">These constans describe the endiannes of data structures. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="FloatingPointBitmapFormat.html">FloatingPointBitmapFormat</a></td>
+<td class="imsum_right">This structure describes format of a floating point bitmap. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="IntegerBitmapFormat.html">IntegerBitmapFormat</a></td>
+<td class="imsum_right">This structure describes the format of an integer bitmap. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="InterpolationMode.html">InterpolationMode</a></td>
+<td class="imsum_right">These constants specify the interpolation type for animation 
+frames. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="PanoseArmStyle.html">PanoseArmStyle</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="PanoseContrast.html">PanoseContrast</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="PanoseFamilyTypes.html">PanoseFamilyTypes</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="PanoseLetterForm.html">PanoseLetterForm</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="PanoseMidline.html">PanoseMidline</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="PanoseProportion.html">PanoseProportion</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="PanoseSerifStyle.html">PanoseSerifStyle</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="PanoseStrokeVariation.html">PanoseStrokeVariation</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="PanoseWeight.html">PanoseWeight</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="PanoseXHeight.html">PanoseXHeight</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="PathCapType.html">PathCapType</a></td>
+<td class="imsum_right">These constants determine which shape to use for start or end of a 
+stroked path. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="PathJoinType.html">PathJoinType</a></td>
+<td class="imsum_right">Determines which shape to use when joining path segments. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="RenderingIntent.html">RenderingIntent</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="RepaintResult.html">RepaintResult</a></td>
+<td class="imsum_right">These constants specify the result of the 
+<a href="XCachedPrimitive.html">XCachedPrimitive</a> render operation. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="TextDirection.html">TextDirection</a></td>
+<td class="imsum_right">Specifies main text direction in a text portion. </td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="TexturingMode.html">TexturingMode</a></td>
+<td class="imsum_right">Enumeration of possible values to spread a texture across a 
+primitive. 
+
+</td>
+</tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright &copy; 2003 Sun Microsystems, Inc.</p>
+
+</div> <!-- id="adc-idlref" -->
+</body>
+
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/module-ix.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/gsl/psprint/index.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/gsl/psprint/index.html?rev=1206299&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/gsl/psprint/index.html (added)
+++ incubator/ooo/ooo-site/trunk/content/gsl/psprint/index.html Fri Nov 25 20:06:37 2011
@@ -0,0 +1,96 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE></TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Linux)">
+	<META NAME="AUTHOR" CONTENT="Philipp Lohmann">
+	<META NAME="CREATED" CONTENT="20010516;17395100">
+	<META NAME="CHANGEDBY" CONTENT="Philipp Lohmann">
+	<META NAME="CHANGED" CONTENT="20010517;13400000">
+</HEAD>
+<BODY BGCOLOR="#ffffff">
+<H1>PSPrint - a Unix print solution</H1>
+<P STYLE="page-break-after: avoid"><FONT FACE="Times New Roman, serif"><FONT SIZE=4><B>History</B></FONT></FONT></P>
+<P>StarOffice 5.2 (and earlier) relied on a thirdparty solution for
+printing. This solution could of course not be open sourced as it was
+a commercial product. So when StarOffice became OpenOffice there was
+no printing possible at all on the Unix platforms; just a wrapper was
+provided that contained stubs fitting the missing symbols left in
+vcl. A new print solution was desperately needed, so a variety of
+existing print solutions were examined, the most notable of which
+were gnome-print and Xprint. Gnome-print did not really fit into
+OpenOffice.org, since it would require to link against a huge amount
+of other gnome libraries, too, which is unacceptable for
+OpenOffice.org, because we want to run on many desktops. Xprint was
+designed as a standard Unix print solution and has many advantages:
+code for the display would work exactly the same way on the printer.
+A proof of concept version was created by Martin Maher and Oisin
+Boydell with help from Hamburg and the US which made it into
+OpenOffice.org as a temporary solution to have minimal print support
+on Unix. But Xprint in its current state misses many features that
+become increasingly important: fast character metric handling, access
+to glyph substitution tables, easy configurability on a per user
+basis just to name a few. Also one cannot really say that it has
+become the standard solution for printing on Unix yet; in fact only
+recently it was awakened from its long beauty sleep having its major
+bugs fixed so it is now useable.</P>
+<P>This led to the decision that as long as there is no standard
+solution scratching a sufficient number of our itches OpenOffice.org
+should do like everyone else and produce its own PostScript code.
+Hence psprint entered the game.</P>
+<P STYLE="page-break-after: avoid"><FONT FACE="Times New Roman, serif"><FONT SIZE=4><B>Features</B></FONT></FONT></P>
+<UL>
+	<LI><P>international, multilingual print support through abstraction
+	to Unicode (UCS2).</P>
+	<LI><P>support for vertical writing (mostly for CJK printing)</P>
+	<LI><P>support for TrueType fonts and TrueType collections, embedded
+	as Type3 or Type42</P>
+	<LI><P>support for Type1 fonts</P>
+	<LI><P>support for printer resident fonts</P>
+	<LI><P>size optimized output using font subsetting for TrueType
+	fonts/collections</P>
+	<LI><P>configurable font substitution: replaces fonts that require
+	embedding with printer resident fonts on a per glyph basis</P>
+	<LI><P>use of vertical glyphs through GSUB substitution for TrueType
+	fonts</P>
+	<LI><P>image compression using lzw compression and ascii85 encoding</P>
+	<LI><P>easy user configurability through printer adminstration
+	utility (spadmin)</P>
+	<LI><P>support for printer specific features (everything you can put
+	into a PPD (PostScript Printer Description))</P>
+	<LI><P>support for portable PostScript generation through generic
+	PPD</P>
+	<LI><P>automatic recognition of system printer queues</P>
+	<LI><P>support for pdf conversion and fax (external applications
+	like ghostscript/mgetty+sendfax required)</P>
+</UL>
+<P STYLE="page-break-after: avoid"><FONT FACE="Times New Roman, serif"><FONT SIZE=4><B>Overview</B></FONT></FONT></P>
+<P>PSPrint consists of the following major parts:</P>
+<UL>
+	<LI><P>Font management: done by the <CODE>PrintFontManager</CODE>
+	class. This class handles font discovery as well as font information
+	like metrics and font properties.</P>
+	<LI><P>Printer management: done by the <CODE>PrinterInfoManager</CODE>
+	class. This class handles printer discovery and information. It can
+	store and load properties of a printer, most important the default
+	job setup (which contains information like paper size, orientation,
+	etc.). To know about a printers capabilities you need PPD
+	(PostScript Printer Description) files which can be parsed with the
+	<CODE>PPDParser</CODE> class.</P>
+	<LI><P>Graphic operations: done by the <CODE>PrinterGfx</CODE>
+	class. This is really the work horse of PSPrint. It handles all
+	kinds of text output, drawing operations, bitmaps and the like.</P>
+	<LI><P>Font subsetting: provided by <A HREF="mailto://alexander.gelfenbain@Sun.COM">Alexander
+	Gelfenbain</A>. This enables PSPrint to make use of TrueType fonts
+	and collections in a very effective way by sending just the glyphs
+	that are needed down to the printer.</P>
+	<LI><P>Job management: done by the <CODE>PrinterJob</CODE> class.
+	This class ties the PostScript code produced by PrinterGfx together
+	downloading the necessary fonts as well as providing a framework for
+	the raw PostScript code.</P>
+</UL>
+<P><BR><BR>
+</P>
+</BODY>
+</HTML>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/gsl/psprint/index.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/gsl/vcl/index.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/gsl/vcl/index.html?rev=1206299&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/gsl/vcl/index.html (added)
+++ incubator/ooo/ooo-site/trunk/content/gsl/vcl/index.html Fri Nov 25 20:06:37 2011
@@ -0,0 +1,96 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE></TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 7  (Linux)">
+	<META NAME="AUTHOR" CONTENT="Philipp Lohmann">
+	<META NAME="CREATED" CONTENT="20040128;13155300">
+	<META NAME="CHANGEDBY" CONTENT="Philipp Lohmann">
+	<META NAME="CHANGED" CONTENT="20040128;13402900">
+</HEAD>
+<BODY LANG="de-DE" DIR="LTR">
+<H1>Visual Class Library (VCL) Module</H1>
+<P><B>Project Owner:</B> <A HREF="mailto:pl@openoffice.org">Philipp Lohmann</A> 
+</P>
+<P>VCL is the current toolkit of OpenOffice.org. It provides a
+complex control system, abstractions for system dependent API's like
+printing, font discovery, drawing (text and graphics) and the
+application main loop.</P>
+<P><BR><BR>
+</P>
+<TABLE WIDTH=100% BORDER=0 CELLPADDING=4 CELLSPACING=0 BGCOLOR="#ffffff">
+	<COL WIDTH=39*>
+	<COL WIDTH=217*>
+	<TR>
+		<TD COLSPAN=2 WIDTH=100% BGCOLOR="#00315a">
+			<P ALIGN=CENTER><FONT COLOR="#ffffff"><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Subprojects
+			of VCL</B></FONT></FONT></FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TH WIDTH=15% BGCOLOR="#99ccff">
+			<P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Part
+			of VCL </B></FONT></FONT></FONT>
+			</P>
+		</TH>
+		<TH WIDTH=85% BGCOLOR="#99ccff">
+			<P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Function
+			</B></FONT></FONT></FONT>
+			</P>
+		</TH>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=15% BGCOLOR="#f0f0f0">
+			<P><CODE><A HREF="plugins/index.html"><FONT FACE="Courier, monospace">plugins</FONT></A></CODE></P>
+		</TD>
+		<TD WIDTH=85% BGCOLOR="#f0f0f0">
+			<P>Currently available for Unix systems only. Supports a pluggable
+			system dependent part for VCL which enables VCL to be based on
+			different system toolkits like gtk, Qt or the like.</P>
+		</TD>
+	</TR>
+</TABLE>
+<P STYLE="margin-bottom: 0in"><BR>
+</P>
+<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Terminology</FONT></FONT></P>
+<TABLE WIDTH=100% BORDER=1 CELLPADDING=4 CELLSPACING=4>
+	<COL WIDTH=45*>
+	<COL WIDTH=211*>
+	<THEAD>
+		<TR VALIGN=TOP>
+			<TH WIDTH=18%>
+				<P>idiom</P>
+			</TH>
+			<TH WIDTH=82%>
+				<P>translation</P>
+			</TH>
+		</TR>
+	</THEAD>
+	<TBODY>
+		<TR VALIGN=TOP>
+			<TD WIDTH=18%>
+				<P>Control</P>
+			</TD>
+			<TD WIDTH=82%>
+				<P>A user interface element, e.g. a button. On Unix systems these
+				are usually named widgets.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=18%>
+				<P>SolarMutex</P>
+			</TD>
+			<TD WIDTH=82%>
+				<P>The mutex vcl protects itself with. VCL is generally not
+				thread safe, but was made thread aware when threads began to be
+				used within OOo. Code outside VCL must acquire the SolarMutex
+				before calling into VCL or risk  a crash.</P>
+			</TD>
+		</TR>
+	</TBODY>
+</TABLE>
+<P><BR><BR>
+</P>
+</BODY>
+</HTML>

Propchange: incubator/ooo/ooo-site/trunk/content/gsl/vcl/index.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/gsl/vcl/plugins/index.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/gsl/vcl/plugins/index.html?rev=1206299&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/gsl/vcl/plugins/index.html (added)
+++ incubator/ooo/ooo-site/trunk/content/gsl/vcl/plugins/index.html Fri Nov 25 20:06:37 2011
@@ -0,0 +1,157 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE></TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 7  (Linux)">
+	<META NAME="AUTHOR" CONTENT="Philipp Lohmann">
+	<META NAME="CREATED" CONTENT="20040128;13243100">
+	<META NAME="CHANGEDBY" CONTENT="Philipp Lohmann">
+	<META NAME="CHANGED" CONTENT="20040128;15341300">
+	<STYLE>
+	<!--
+		@page { size: 8.27in 11.69in }
+		P.western { font-family: "Helvetica", sans-serif; so-language: en-US }
+	-->
+	</STYLE>
+</HEAD>
+<BODY LANG="de-DE" DIR="LTR">
+<H1 LANG="en-US">Plugins for VCL</H1>
+<P LANG="en-US" CLASS="western"><B>Project Owner:</B> <A HREF="mailto:pl@openoffice.org">Philipp
+Lohmann</A>, last change: 2004/01/28</P>
+<P LANG="en-US" CLASS="western" STYLE="margin-bottom: 0in"><BR>
+</P>
+<P LANG="en-US" CLASS="western">Currently only available for Unix
+platforms: plugins move the whole platform dependent part of
+VCL(Unix) into an own library. At runtime OOo decides what plugin
+would suit the current desktop environment best; e.g. it uses a gtk
+based plugin on GNOME desktops or a generic (plain Xlib based) plugin
+on CDE. The foundation for this the pure abstraction of all Sal
+interfaces (Sal: System Abstraction Layer &ndash; the name is sadly
+coincidental with the sal project; the Sal layer in vcl existed first
+historically).</P>
+<H2 LANG="en-US">Why plugins ?</H2>
+<P LANG="en-US" CLASS="western">For better system integration it is
+necessary to run the system's toolkit inside the OOo process space.
+E.g. to use toolkit themes for drawing controls it is imperative to
+be able to ask the native toolkit to draw OOo's controls. Also
+toolkits know how to access system features like recent document
+lists, file dialogues, etc..</P>
+<H2 LANG="en-US">What are the basics for writing a VCL(Unix) plugin ?</H2>
+<P LANG="en-US" CLASS="western">The starting point for a new VCL
+plugin is SalInstance. This is a factory interface the implementation
+of which produces instances of all other Sal interfaces. At startup
+the independent part of vcl tries to determine the correct plugin
+(desktop autodetection) and then tries to load that library and ask
+it for a SalInstance object. Every other Sal interface implentation
+is produced via the corresponding method of SalInstance (see
+vcl/inc/salinst.hxx for details).</P>
+<H3>SalInstance</H3>
+<P LANG="en-US" CLASS="western">The first step is to create an <CODE><FONT FACE="Courier, monospace">extern
+&quot;C&quot;</FONT></CODE> function named create_SalInstance which
+returns the SalInstance of your plugin. For many plugins it is
+advantageous to inherit their SalInstance from the SalInstance of the
+generic implementation so the new plugin can reuse the generic
+implementation where appropriate; good examples for implementations
+that can be inherited are SalSound, SalBitmap, SalGraphics and
+SalPrinter. Especially SalGraphics should be used from the generic
+implementation as it contains really difficult stuff like drawing
+text with complex text layout (CTL) that would be a real pain to
+implement with little gain since the result should still look like
+the result of the generic SalGraphics. Still, if you want to
+implement every Sal interface on your own there is of course nothing
+to stop you from doing that.</P>
+<P LANG="en-US" CLASS="western">SalInstance is also responsible for
+the application main loop and the SolarMutex (the mutex vcl gets its
+thread awareness from). Since toolkits tend to be nonfunctional
+without their own main loop, this is the first feature you should
+implement. The methods GetYieldMutex, ReleaseYieldMutex and
+AcquireYieldMutex must return a vos::IMutex interface (see
+vos/inc/vos/mutex.hxx) that synchronizes to the mutex of your special
+toolkit. Then Yield must be implemented. Yield is VCL's interface to
+the system main loop; when called it should look for all kinds of
+events (e.g. X events) and dispatch them appropriately. If called
+with parameter bWait set to TRUE it should wait until an event is
+available and then dispatch it. If bWait is FALSE Yield should
+dispatch all events already available and then return immediately.</P>
+<P LANG="en-US" CLASS="western">Please note that this may be far from
+trivial to implement depending on your toolkit since so much depends
+on the main loop. Unless you implement every Sal interface yourself
+it is basically necessary to inherit from the SalDisplay, SalXLib and
+SalData classes of the generic implementation since these lay the
+groundwork for most other generic implementations (X11SalFrame,
+X11SalTimer, etc.). E.g. SalData adds file descriptors to be watched
+for events in the main loop. To make this feasible the corresponding
+methods on the SalXLib, SalData and SalDisplay are virtual so a new
+implementation can overload these and still use the generic
+implementation.</P>
+<H3>SalFrame</H3>
+<P LANG="en-US" CLASS="western">The next step is most likely
+implementing the SalFrame interface. This is necessary for the
+following reasons:</P>
+<UL>
+	<LI><P LANG="en-US" CLASS="western">If you want to use any window
+	inside your toolkit you most likely need a parent that already is a
+	such a toolkit window; e.g. if you want to have native file
+	dialogues you'll want to have a document window as their &ldquo;parent&rdquo;(or
+	rather make the dialogue window make transient for the document
+	window in X speak).</P>
+	<LI><P LANG="en-US" CLASS="western">SalFrame reads the native system
+	settings, so if you want to have OOo's UI using the correct colors
+	and fonts you'll need to implement at least the UpdateSettings
+	method.</P>
+</UL>
+<P LANG="en-US" CLASS="western">When implementing SalFrame you must
+overcome the following problems:</P>
+<UL>
+	<LI><P LANG="en-US" CLASS="western">SalFrame produces a SalGraphics;
+	here you most likely want to inherit from the generic
+	implementation. The X11SalGraphics for a frame needs to be
+	initialized with a native X drawable, so you need to get the Xlib
+	Window from your native top-level widget. You also need the Xlib
+	Window to implement the GetSystemData method.</P>
+	<LI><P LANG="en-US" CLASS="western">SalFrame needs to process
+	internationalized input; there is most likely an abstraction inside
+	your toolkit you'll want to use, so be prepared to send VCL's
+	abstracted input method (IM) events instead of simple key events.</P>
+	<LI><P LANG="en-US" CLASS="western">SalFrame can be constructed as a
+	child window of a native window (this is used e.g. in the SDK's java
+	bean where you plug OOo into another application). You'll need to
+	find an appropriate widget to do that with your toolkit (e.g. like a
+	GtkPlug in gtk).</P>
+	<LI><P LANG="en-US" CLASS="western">You must prevent you frame
+	widget from drawing its own background as this would interfere with
+	VCL's controls which draw themselves directly onto the window
+	without being known to your toolkit.</P>
+</UL>
+<H3>SalObjects</H3>
+<P LANG="en-US" CLASS="western">If you have implemented SalFrame,
+you'll need to implement SalObject, too. SalObject is a child window
+of a SalFrame guaranteed to be a native system window (that is in
+Xtoolkit terms a widget rather than a gadget). This is needed for
+plugins and java applets inside documents. There are only two
+obstacles doing this as SalObject is really rather boring:</P>
+<UL>
+	<LI><P LANG="en-US" CLASS="western">You need to find an appropriate
+	widget (a drawing area will generally do)</P>
+	<LI><P LANG="en-US" CLASS="western">Since the SalObject is embedded
+	into a lot of gadgets (which is what VCL's controls are from a
+	toolkit standpoint), a real widget will overlap them if any geometry
+	is shared. This would e.g. lead to a plugin drawing over OOo's
+	toolbars if you scroll the corresponding document down slowly. To
+	avoid this SalObject windows need to be shaped using the X SHAPE
+	extension.</P>
+</UL>
+<H2>General considerations</H2>
+<P LANG="en-US" CLASS="western">While implementing your own plugin
+you may find it necessary to change something inside the generic
+plugin. Please do so if it suits you, but contact one of the vcl team
+(e.g. The author of this document) to check whether your change does
+not break anything for other implementations.</P>
+<P LANG="en-US" CLASS="western">In general it may be a good idea to
+contact the vcl developers before and during the implementation on
+the <A HREF="mailto:dev@gsl.openoffice.org">dev@gsl.openoffice.org</A>
+mailinglist as all kinds of questions may arise (especially
+considering that VCL is largely undocumented code up today).</P>
+</BODY>
+</HTML>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/gsl/vcl/plugins/index.html
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message