Text for XAP report below - due 2/14 I believe. Once agreed to, I believe it
needs to be posted to web site.
-------- text -----
Since the last report in November 2006, the focus of project has not changed.
Items to resolve have not changed either:
• Bring the codebase to a level that contributors can make contributions
without significant pain;
- Status: Added documentation to the Wiki supporting both XAP users and XAP
developers. A deeper level of documentation still needed.
• Create a XAP incubating release with proper packaging and quality
- Status: Release process for 0.3 is currently ongoing; release is currently
being voted on.
• Engage a higher level of community activity and contribution
- Status: See Community section below.
Licensing
• Added appropriate headers to all files. Added correct NOTICE and LICENSE
files.
- Removed non compliant files and binaries from the release; still need to
be removed from the source code repository.
• [EMAIL PROTECTED] tags flagged as to be removed.
Community
• Various discussions on the XAP dev list on a range of technical and
licensing/packaging issues;
• XAP presented as part of session on “Declarative Java and Ajax” at Northern
Virginia Java User Group in January;
• Various third party expressed interest in learning more about XAP;
• Upcoming events where XAP will be featured:
- EclipseCon (March 5-8) through Nexaweb and Eclipse ecosystem;
- AjaxWorld (March 19-21) speaking slot entitled “Visual AJAX - Combining
Open Source Projects to Achieve Ease-of-Development”
- JavaOne (May 8-11)
- Apache Con Europe (May 2-4) speaking slot entitled “XAP: Declarative Ajax
Development”.
- Others being considered
• An average of 35 web visitors/day to the web site.
Development
• Significant development progress since last report.
• Achieved milestone 4 with all high level XAL syntax supported and data
binding.
• Next development steps:
- Fully support XAL syntax – effort ongoing.
- Improve functionality for specific components: tables, trees, windows, etc.
- Research the inclusion of other Ajax toolkits to expand user interface
richness.
- Performance optimization.
Documentation
• A Wiki page for XAP has been created and is used for much of the user
documentation. This makes documentation contribution easier.
Ben Bloch
