Re: [Dynapi-Dev] Me Again/DynAPI3alpha

[Raymond S. <dst...@or...>]

One thing we need to do is define a "single" header for new ideas.  This
thread is all over the place, and the "subject title" shifts at will.  How
about "DynAPI3alpha"?

I also agree that split-development along the lines of finishing critical
issues with DynAPI2 and expanding browser support as much as "can be done"
should be followed.  Also, how we co-distribute the functional API vs.
BetaAPI should be clearly detailed on the homepage.

But, all that being said.  I think the first objective is to:

1)  STOP!  It's a bit premature to be debating the implementation when we
haven't even detailed the "plan and next-generation API objectives"; Mission
Statement.

then proceed with...

2)  Expose and consolidate all ideas related to what we would like the next
generation of the API to be able to do.  LabCoat, this would be a good time
to unveil your thoughts and learning's.
3)  Discuss and agree upon "how" we would like "do" to be accomplished.  API
structure and implementation.  Maybe a tad UMLish in nature.  So we can
"see" what we would like the API to look like before it's built.
    a) Object/Method Discovery
    b) API assembly/construction diagram (UMLish)
    c) API extensions.  I would assume we are going for a highly extensible
and scalable architecture.
4) Build the base alpha API.
    a) Construct.
    b) Abuse
    c) Iterate
    d) Evolve

First lets agree to agree to think about the next generation API.  Wishes,
wants and desires.  Leave all specifics "out" for now..., just discuss the
objectives of the API in broad brush strokes.

This isn't going to happen overnight, if we think it will and push for
"minor" shifts in the current paradigm will be right here again in a year
"debating grand software architecture".

So, to get the proverbial ball rolling.  I think everyone should detail
their "ideas" in non-specific terms as to what API3 should be capable of
doing.  How it might look from a structure standpoint.  How will it be
extensible?  Lets include the whole world of the web; client/server and
conduits between them.

Almost everything we need to "think" about is already in the API.  But I
would certainly like to see a diagram of what the next generation API would
look like before a single "if,then,else" hits a sheet of paper.

Ray