posrel.xml

实现一个网络购物

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE builder PUBLIC "-//MMBase//DTD builder config 1.1//EN" "http://www.mmbase.org/dtd/builder_1_1.dtd">
<builder extends="insrel" maintainer="mmbase.org" name="posrel" version="0">
  <!-- Builder configuration for posrel -->
  <!-- Status of the builder: active or inactive -->
  <status>active</status>
  <!-- Classname of the builder.
This is a optional tag, it names the classfile to use for this builder
Providing an alternate buidler class allows you to add or change support routines. -->
  <classfile>PosRel</classfile>
  <!-- Names defines the different names used in user visible parts
Singular names are used when talking about one object (Url,Person) and plurar when talking about multiple objects (Urls, people).
Names can be provided in various languages. -->
  <names>
    <!-- singular names per language as defined by ISO 639 -->
    <singular xml:lang="nl">Positierelatie</singular>
    <singular xml:lang="fr">Placez La Relation</singular>
    <singular xml:lang="en">Position Relation</singular>
    <!-- plural names per language as defined by ISO 639 -->
    <plural xml:lang="nl">Positie Relaties</plural>
    <plural xml:lang="fr">Placez La Relations</plural>
    <plural xml:lang="en">Position Relations</plural>
  </names>
  <!-- Descriptions are ment to provide some additional clarification to an object.
They are useful for GUI editors to provide helptexts.
Descriptions can be provided in various languages. -->
  <descriptions>
    <description xml:lang="nl">Deze relatie heeft een positie attribuut</description>
    <description xml:lang="fr">Cette relation a un attribut de position</description>
    <description xml:lang="en">This relation has a position attribute</description>
  </descriptions>
  <!-- decsription per language as defined by ISO 639 -->
  <!-- You can define properties to be used by the classfile.
Properties are entered using name/value pairs.
The actual properties available differ by class. -->
  <properties/>
  <!-- defines the different fields in this object
Depending on the database, the order of the fields may be important.
Once defined, it is a good practice to keep the same order.
This counts especially when you convert buidler configurations using builder inheritance. -->
  <fieldlist>
    <!-- field definition for field 8 : pos -->
    <field>
      <!-- field descriptions (help texts) -->
      <descriptions>
        <description xml:lang="nl">Postitie of volgordenummer, te gebruiken voor het sorteren van de relaties</description>
        <description xml:lang="en">Position number, useful for ordering the relations</description>
      </descriptions>
      <!-- gui related -->
      <gui>
        <guiname xml:lang="nl">Positie</guiname>
        <guiname xml:lang="fr">Placent</guiname>
        <guiname xml:lang="en">Position</guiname>
        <guitype>integer</guitype>
      </gui>
      <!-- editor related -->
      <editor>
        <positions>
          <!-- position in the input area of the editor -->
          <input>3</input>
          <!-- position in the list area of the editor -->
          <list>3</list>
          <!-- position in the search area of the editor -->
          <search>3</search>
        </positions>
      </editor>
      <!-- database related -->
      <db>
        <!-- name of the field in the database -->
        <name>pos</name>
        <!-- MMBase datatype and demands on it -->
        <type key="false" notnull="false" state="persistent">INTEGER</type>
      </db>
    </field>
  </fieldlist>
</builder>