Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <13344844.1191423350784.JavaMail.jira@brutus>
Date: Wed, 3 Oct 2007 07:55:50 -0700 (PDT)
From: "Gabriel Gruber (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Subject: [jira] Updated: (COCOON-2137) XSD Schemas for CForms Development
In-Reply-To: <16517710.1191423230958.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/COCOON-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabriel Gruber updated COCOON-2137:
-----------------------------------

    Attachment: clean-xsd-public.zip

> XSD Schemas for CForms Development
> ----------------------------------
>
>                 Key: COCOON-2137
>                 URL: https://issues.apache.org/jira/browse/COCOON-2137
>             Project: Cocoon
>          Issue Type: New Feature
>          Components: Blocks: Forms
>            Reporter: Gabriel Gruber
>            Priority: Minor
>         Attachments: clean-xsd-public.zip
>
>
> A common pitfall in developing cforms applications is the misuse of certain cforms tags.
> A schema for the forms files (definition, binding, template) would greatly help in writing forms code faster and more accurate and minimizing syntax errors in the first place.
> I have started writing such schemas for the binding and definition files and added notations out of the current (2.1.10) cforms documentation.  those schemas are quite completet (well almost).
> I also added starting points for this schemas:
> - i18n transformer
> - jx template generator
> furthermore form template generator (and form instance) would be interesting. the major problem with the template is that we are heavily mixing different xml gramars here and state-of-the-art xml editors (like oxygen) have their problems with providing auto-complete features here.
> the code-completion (assistance) feature for the form-definition and form-binding works quite well. it also has the added benefit, that the important bits of the cocoon forms docs are being displayed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.