Personal tools

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

NumberTitleAuthorStatusTarget
EP 238Browser Event HandlingMax CarlsonDraftRingDing
EP 256Gen2 ComponentsMax CarlsonDraftMr. Donut
EP 257SWF in DHTMLMaynard DemmonDraftMr. Donut
EP TBACharting API Change ProposalJ CrowleyDraft4.2.2
EP 259HTML5 Multimedia APIHenry MinskyDraft5.0

Pending Proposals

NumberTitleAuthorStatusTarget
EP 225 Kernel APIMax CarlsonDraftLegals
EP 228 Simple requires/provides proposalMax CarlsonProposedLegals

Implemented Proposals

NumberTitleOwnerStatusTarget
EP 210Browser HistoryMax CarlsonImplemented3.0rc1
EP 201Client fontsOliver SteeleImplemented3.0b1
EP 202Canvas resizingOliver SteeleImplemented3.0b1
EP 203JavaScript integrationMax CarlsonImplemented3.0b1
EP 204Drop swf5Oliver SteeleImplemented3.0b1
EP 205Dynamic LibrariesOliver SteeleImplemented3.0b2
EP 206Drawing APIMax CarlsonImplemented3.0b2
EP 213Inner datasetsHenry MinskyImplemented3.1
EP 214Charting components (Requirements, API)BlochImplemented3.1
EP 215 RichInputText Winters Implemented3.1
EP 217Accessibility SupportMax CarlsonImplemented3.2
EP 218Rich Text EditorSarah AllenImplemented3.2
EP 219event and handler tagsP Tucker WithingtonImplemented3.2
EP 216Text img tagOliver SteeleImplemented3.2
EP 231Binary LibrariesP T WithingtonImplemented3.4.2,4.0.3
EP 221VideoSarah AllenImplemented3.4
EP 224 CSS Ben Shine, Jim GrandyImplemented3.4
EP 234 DataProvider API Henry MinskyImpelmented4.0.5
EP 229Explicit ReplicationP Tucker WithingtonImplemented4.0.5
EP 233 Literal XML Data Henry MinskyImplemented4.0.5
EP 258Enhanced Text APIHenry MinskyImplemented4.8
EP 230Attribute Type CoercionP T WithingtonImplemented4.9

Tabled Proposals

NumberTitleOwnerStatus
EP 207PrintingSarah AllenTabled
EP 209Target selectionOliver SteeleTabled
EP 211Constraint tokenizationOliver SteeleTabled
EP 212Type declarationsOliver SteeleTabled
EP 208Feature selectionOliver SteeleTabled
EP 220Import StatementOliver SteeleTabled
EP 231 Abstract Data APIJim GrandyTabled

Notes

This list does not include Feature Wishlist items that have not been turned into concrete proposals.