Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Z
zodb
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Joshua
zodb
Commits
95f49ed6
Commit
95f49ed6
authored
Jul 10, 2003
by
Fred Drake
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Remove commented-out documentation related to component extensions.
parent
9533ddd4
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
22 deletions
+0
-22
doc/ZConfig/zconfig.tex
doc/ZConfig/zconfig.tex
+0
-22
No files found.
doc/ZConfig/zconfig.tex
View file @
95f49ed6
...
...
@@ -630,22 +630,12 @@ include additional types in application-provided abstract types.
Components are identified using a dotted
-
name, similar to a Python
module name. For example, one component may be
\code
{
zodb.storage
}
.
%A schema component \dfn{extension} is allowed to define new abstract
%and section types, extend types provided by the component it extends,
%and include new section types in abstract types provided by the
%component. The expected usage is that extensions will provide one or
%more concrete types that implement abstract types defined by the
%component.
Schema components are stored alongside application code since they
directly reference datatype code. Schema components are provided by
Python packages; packages which contain a file named
\file
{
component.xml
}
can be ``imported''. The
\file
{
component.xml
}
file defines the types provided by that component; it must have a
\element
{
component
}
element as the document element.
%Extensions to a component are stored in immediate subdirectories; a
%file \file{extension.xml} provides the extension types. Extensions
%must have an \element{extension} element as the document element.
The following element is used as the document element for schema
components. Note that schema components do not allow keys and
...
...
@@ -664,18 +654,6 @@ provide type definitions.
\end
{
attributedesc
}
\end
{
elementdesc
}
%\begin{elementdesc}{extension}{description?, (abstracttype | sectiontype)*}
% The top-level element for schema component extensions.
% \begin{attributedesc}{prefix}{\datatype{dotted-name}}
% Prefix to be pre-pended in front of partial dotted-names that
% start with a period. The value of this attribute is used in all
% contexts within the \element{extension} element if it hasn't been
% overridden by an inner element with a \attribute{prefix}
% attribute.
% \end{attributedesc}
%\end{elementdesc}
\section
{
Standard
\module
{
ZConfig
}
Datatypes
\label
{
standard
-
datatypes
}}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment