Enhancement Proposals
From OpenLaszlo
An OpenLaszlo feature or API proposal is a design document that describes a new feature, API, or API change for the OpenLaszlo platform. The proposal should provide a concise technical specification of the feature and a rationale for the feature.
We intend this proposal process to be the primary mechanism for proposing new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Laszlo. The proposal author is responsible for updating and augmenting the proposal as needed to see it through the process.
Contents |
Process
To request a significant enhancement or feature, use the Blank Proposal as a template, and create a wiki page that links from the Draft Proposals section of this page. Note that the proposal numbers are hand-generated, please just use the next sequential number. Then, send a proposal to the laszlo-dev@openlaszlo.org mailing list with a pointer to the wiki page.
To request a specific API change or addition, use the API Change Proposal template.
An accepted proposal will have the following properties:
- It should solve a problem that matters to the OpenLaszlo community
- The technical review board agrees this is the right solution
- There is enough information (both reference and expository) to document the feature
- There is enough information to implement the feature
After a period of further discussion, the Laszlo Technical Review Board will consider the proposal, taking into account the feedback of the community, and make a decision.
Draft Proposals
| Number | Title | Author | Status | Target |
|---|---|---|---|---|
| EP 223 | Traits/Mixins | Tucker Withington | Draft | RingDing |
| EP 230 | Attribute Type Coercion | P T Withington | Draft | Legals |
| EP 238 | Browser Event Handling | Max Carlson | Draft | RingDing |
Pending Proposals
| Number | Title | Author | Status | Target |
|---|---|---|---|---|
| EP 225 | Kernel API | Max Carlson | Draft | Legals |
| EP 228 | Simple requires/provides proposal | Max Carlson | Proposed | Legals |
Implemented Proposals
| Number | Title | Owner | Status | Target |
|---|---|---|---|---|
| EP 210 | Browser History | Max Carlson | Implemented | 3.0rc1 |
| EP 201 | Client fonts | Oliver Steele | Implemented | 3.0b1 |
| EP 202 | Canvas resizing | Oliver Steele | Implemented | 3.0b1 |
| EP 203 | JavaScript integration | Max Carlson | Implemented | 3.0b1 |
| EP 204 | Drop swf5 | Oliver Steele | Implemented | 3.0b1 |
| EP 205 | Dynamic Libraries | Oliver Steele | Implemented | 3.0b2 |
| EP 206 | Drawing API | Max Carlson | Implemented | 3.0b2 |
| EP 213 | Inner datasets | Henry Minsky | Implemented | 3.1 |
| EP 214 | Charting components (Requirements, API) | Bloch | Implemented | 3.1 |
| EP 215 | RichInputText | Winters | Implemented | 3.1 |
| EP 217 | Accessibility Support | Max Carlson | Implemented | 3.2 |
| EP 218 | Rich Text Editor | Sarah Allen | Implemented | 3.2 |
| EP 219 | event and handler tags | P Tucker Withington | Implemented | 3.2 |
| EP 216 | Text img tag | Oliver Steele | Implemented | 3.2 |
| EP 231 | Binary Libraries | P T Withington | Implemented | 3.4.2,4.0.3 |
| EP 221 | Video | Sarah Allen | Implemented | 3.4 |
| EP 224 | CSS | Ben Shine, Jim Grandy | Implemented | 3.4 |
| EP 234 | DataProvider API | Henry Minsky | Impelmented | 4.0.5 |
| EP 229 | Explicit Replication | P Tucker Withington | Implemented | 4.0.5 |
| EP 233 | Literal XML Data | Henry Minsky | Implemented | 4.0.5 |
Tabled Proposals
| Number | Title | Owner | Status | |
|---|---|---|---|---|
| EP 207 | Printing | Sarah Allen | Tabled | |
| EP 209 | Target selection | Oliver Steele | Tabled | |
| EP 211 | Constraint tokenization | Oliver Steele | Tabled | |
| EP 212 | Type declarations | Oliver Steele | Tabled | |
| EP 208 | Feature selection | Oliver Steele | Tabled | |
| EP 220 | Import Statement | Oliver Steele | Tabled | |
| EP 231 | Abstract Data API | Jim Grandy | Tabled |
Notes
This list does not include Feature Wishlist items that have not been turned into concrete proposals.
