How-tos

Handy tricks and short explanations.

Using the config file to get shorter tagged values: Some tagged values' values can get quite lengthy. If you use such a lengthy value a few times, you can store it in your project's config file.
Easy css and javascript registry usage: ArchGenXML has an easy way to register your stylesheets and javascripts with the registry.
Swapping fields around in an ATContentTypes subclass: You're subclassing from ATDocument or ATEvent or so and you want some of your fields to be in a different location (especially in the generated edit form).
Handling i18n translation files with ArchGenXML and i18ndude: How to use i18ndude in combination with ArchGenXML
Subclassing ATContentTypes with ArchGenXML: Subclassing from ATContentTypes is a common task for which you need to know the magic incantations. Once you know them, it is easy, though.
Turn an existing schemata-based product into an ArchGenXML Project: This how-to explains the steps neccessary to convert an existing hand-written schemata based product into an ArchGenXML Project.

Using ArgoUML model with ArchGenXML data types, stereotypes and tagged values: Using ArchGenXML with ArgoUML is much simpler with this base model. It gives you only ArchGenXML data types, stereotypes and tagged values instead of the default Java stereotypes, data types and classes.
Setting up ArgoUML to provide tagged values and stereotypes in a dropdown menu: ArgoUML supports the ability to load a "definition" file with predefined tagged values and stereotypes. This makes it possible to have all the custom tagged values and stereotypes used by a Plone project available in dropdown menus within ArgoUML.
Set up a unit test environment using an UML-editor and ArchGenXML: Testing is vital to integrate your work successfully