Personal tools

Status 2005-12-02

From OpenLaszlo

Platform Team Activity Report, week ending 12-02-05

Contents

Upcoming Dates

  • 12/7: inline <img> initial support to be checked in

Project Status

Quill

  • This minor release will contain mainly documentation improvements, with only a few critical code changes.
  • One code change already checked in, the other still under investigation
  • Many case sensitivity issues resolved in docs and examples
  • Copyediting of docs to continue this week

Ginger

  • Rich Text Editor code was checked into lps-dev Incubator and is at beta
  • MSAA accessibility code was check into lps-dev and is at beta
  • Inline <img> code will be checked in next week
  • JavaScript compiler port is still underway; expect code to be checked in next week
  • Components improvements underway, focused initially on unit tests and bug fixes

StarAnise

  • Planning is underway, development has not yet begun

Development

  • Components
    • Unit tests were checked in for LzNode, basecomponent, baseslider, baselist, and basetabs
    • Bug fixes were checked in for baseslider and basetabs, and minor code cleanups were added for baselist and basetabs
  • Rich Text Editor
    • Code for the rich text editor was checked into the Incubator.
  • MSAA Accessibility
    • First code was checked in, with preliminary support for Win IE only
  • Inline <img> tag
    • Work began on this new feature
  • JavaScript compiler port from Jython to Java
    • Work continues on this task. The difficult coding is almost done, then the bulk of the remaining work will be relatively easy

QA

  • Copied a number of older open bugs from Bugzilla to JIRA

Documentation

  • Added a number of new documentation tasks to JIRA.
  • (jsundman) wrote draft of rich input text chapter
  • (jsundman) created reference page for LzTextFormat. Because this class was created with the <class> tag but is intended for script use and not as a tag, the reference page is somewhat awkward.
    • There are two possible fixes for this, which I'll investigate next week:
    1. change the implementation of LzTextFormat -- by putting it in a .as file the problem solves itself; or
    2. I can create by hand a new XML file & hard-wire this into the reference page. Kludgey, but it would work.
  • (jsundman) In trying to come up with a reference page in the right format for <LzTextFormat>, I caused to surface several interesting questions about:
    • doctools -- in particular, how they do and do not handle .js and <script> files
    • "dual APIs"
    • the architecture of platform-neutral text formatting API
  • (jsundman) posted same on laszlo-dev

Community

  • A new version of the openlaszlo.org site is close to completion (those curious can look at http://staging.openlaszlo.org). We expect the new site to go live next week.

Planning

  • New version of the Platform_Roadmap published.
  • Lots of work on Multiple Runtimes planning. Still much more to be done to refine and sequence task lists, but the basic outline of work for the necessary infrastructure changes is complete.