[Chameleon-dev] [Bug 92] New: [Chameleon] - preparation for 1.1 beta

[bugzilla-daemon@www.maptools.org]

http://www.maptools.org/bugzilla/show_bug.cgi?id=92

           Summary: [Chameleon] - preparation for 1.1 beta
           Product: Chameleon
           Version: 1.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P1
         Component: Core
        AssignedTo: chameleon-dev@lists.maptools.org
        ReportedBy: spencer@dmsolutions.ca


All, I would like to start chameleon onto a release cycle with the intention of
getting version 1.1 released by Christmas or early in the new year.  We have a
lot of interest in chameleon right now and I think delaying a release will only
hurt us in the long run.  That being said, the purpose of this bug is to track
the tasks required to get a Beta release of Chameleon 1.1.

My intention with a Beta release is to:

1. freeze changes to the core of chameleon.
2. identify widget groups and their status (beta, alpha, development) with
respect to chameleon 1.1
3. thorough review and QA on the chameleon core and base widget groups (those
that are considered part of the chameleon package)

With this in mind, I need feedback from the chameleon developers on outstanding
features that need to be implemented.  AFAIK, the list is:

* Sacha to implement support for handling widgets in multiple forms
* Paul to implement complete buttonizer/button support in widget.php, including
non-javascript mode for buttons
* Darren/Sacha/Paul to redo widget documentation architecture (already in bug 74)

Once these (at least the first two) items are complete (and any others that get
added), I would like to do a code review of the chameleon core components,
including:

* chameleon.php (522 lines)
* UIManager.php (427 lines)
* WidgetManager.php (183 lines)
* TemplateParser.php (248 lines)
* Widget.php (925 lines)

As part of this, I would also like to review the current contents of the
configuration files for chameleon and validate all the items there.

This represents a fair amount of code, and could take quite a while to
thoroughly review.  I think this is an important step, though.

Once this is done, I think we can move to a beta status and then begin to use
bugzilla extensively to report and track remaining issues for a full release.

Comments are welcome.  Also, who should be on the code review and when should we
do it?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.