Product Selector Application Breakdown Categories

From MemberWiki

Jump to: navigation, search

Contents

Introduction

At the May 1, 2007 phone call for the Marketing Working Group, we decided to create a wiki page where the OpenAjax companies could collaborate on the Ajax product selection criteria that we could include in the Product Selector Application that we might post on our Web site in the future. (Early mockup is at [1].)

Collaboration suggestions

People should feel free to reorganize and otherwise modify this wiki page in any manner that they think will be helpful. However, if we keep the organization shown below, here are some ways that individual members might incrementally modify this page:

  1. Look at the breakdown categories and sub-categories. If you see important high-level categories to add, go add them. If you see reasons to modify and remove categories, either modify/remove them or leave a note saying that you think the a particular category should be modified or removed.
  2. Under each bulleted category below, insert a sub-bullet that says whether your toolkit supports the given feature in the form "toolkit-name: answer".

Proposed Breakdown

Supplier characteristics (where "supplier" might be one or more commercial companies or open source projects)

(Note: Chris called this "company-level characteristics". I suggested this might be called "whole product characteristics".)

  • OpenAjax member (yes or no)
    • ToolkitA: ...
    • ToolkitB: ...
  • Commercial (yes or no)
    • ToolkitA: ...
    • ToolkitB: ...
  • Open source (yes or no, and if yes, then details, such as what parts are OS and what license)
    • ToolkitA: ...
    • ToolkitB: ...
  • IDE availability (yes or no, and if yes, then details, such as the supplier sells an IDE or maybe it sort of works with Eclipse)
    • ToolkitA: ...
    • ToolkitB: ...
  • Support availability (yes or no, and if yes, then details, such as the supplier sells professional services or maybe there is a guy in Outer Mongolia who can help you when a particular satellite passes over his herd and his sheep aren't misbehaving)
    • ToolkitA: ...
    • ToolkitB: ...

Architecture characteristics

  • Client-side vs. Server-side (vs. Hybrid?)
    • ToolkitA: ...
    • ToolkitB: ...
  • Single-DOM vs Dual-DOM - this is from our white papers, but maybe there is a better way to express this
    • ToolkitA: ...
    • ToolkitB: ...
    • Dual-DOM Client vs Dual-DOM Server - also from our white papers
    • ToolkitA: ...
    • ToolkitB: ...

Product characteristics

  • OpenAjax Hub support (yes or no, and if yes, which version)
    • ToolkitA: ...
    • ToolkitB: ...
  • All-in-one framework vs special-purpose vs other (OpenLaszlo would be all-in-one framework, scriptaculous would be special-purpose)
    • ToolkitA: ...
    • ToolkitB: ...
  • High-level feature categories
    • Client-server communications features (yes if XHR APIs are provided - think prototype)
      • ToolkitA: ...
      • ToolkitB: ...
    • UI effects (think scriptaculous)
      • ToolkitA: ...
      • ToolkitB: ...
    • UI controls library
      • ToolkitA: ...
      • ToolkitB: ...
    • Declarative markup (yes if features can be defined via HTML or XML. if yes, then provide details)
      • Markup-based controls
        • ToolkitA: ...
        • ToolkitB: ...
      • Markup-based layout
        • ToolkitA: ...
        • ToolkitB: ...
      • Markup-based effects
        • ToolkitA: ...
        • ToolkitB: ...
      • Markup-based data binding
        • ToolkitA: ...
        • ToolkitB: ...
Personal tools