Tor Lillqvist wrote:
<http://api.openoffice.org/docs/DevelopersGuide/Extensions/Extensions.xhtml#1_7_Dependencies>:

Hmm, so could I have an example of how to specify a dependency on a feature 
present only in some FooBar version of OOo?

Btw, do I read the referred-to section of the specification correctly, that 
"OpenOffice.org-minimal-version" is both an element and and an optional attribute of 
each child element of <description>?

Would the below example be the correct way to specify a requirement for a specific build of OOo 
that recognizes and implements certain version-specific dependencies? Let's ssume this 
"Foo" version of OOo contains code so that it knows that it implements the foo:HavePatch 
dependency for some foo:PatchName attribute values, and the foo:Platform dependency with its 
attributes. Would a non-Foo build of OOo then correctly reject this extension with some message 
like "This extension requires the following features not present in this version: 'The 
xyzzy.diff patch present in the Foo build of OOo', 'Windows XP'" ?

<description xmlns="http://openoffice.org/extensions/description/2006";
        xmlns:dep="http://openoffice.org/extensions/description/2006";
        xmlns:foo="http://foo.whatever.org/whatever/foo/12345";
        xmlns:xlink="http://www.w3.org/1999/xlink";>
        <version value="1.0.6-1" />
        <dependencies>
                <OpenOffice.org-minimal-version value="2.1" dep:name="OpenOffice.org 
2.1"/>
                <foo:HavePatch foo:PatchName="xyzzy.diff" dep:name="The xyzzy.diff 
patch present in the Foo build of OOo"/>
                <foo:Platform foo:PlatformArchitecture="x86" foo:OS="Windows" 
foo:MinOSVer="XP" dep:name="Windows XP"/>
        </dependencies>
</description>

well, independent of the flexibility of the dependency feature i would say that such a dependency <foo:HavePatch> would be a misuse of the whole feature. So your intention is obvious and stupid.

Juergen

(Do I understand the specification correctly, it is possible to specify 
platform requirements only for UNO native components (shared libraries), not 
for extensions in general that do not contain UNO components? Or *should* all 
extensions contain even just a minimal dummy UNO component shared library?)

Cheers,
--tml



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to