> Michael,
>
> If you look at the Compatability Matrix
> http://mocha.ctlt.wsu.edu/DynAPIMatrix/matrix20010407.htm, we introduced new
> problems with viewport, pushpanel, scrollpane and scrollpanel. I'm not sure
> if you've resolved them or not. Maybe you could review it and post an
> update.
nks,
Also, I think we should update the Matrix more frequently
Ray
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Michael
Buerge
Sent: Monday, April 30, 2001 3:50 AM
To: [EMAIL PROTECTED]
Subject: Re: [Dynapi-Dev] New File Structure
> I think the
> I think the above are the issues we should really be focussing on here.
> Particularly the fact that the API doesn't work on a Mac anymore. That's a
> big let down for the Mac community, and would turn a lot of developers
away
> from using the API. Documentation in my mind is also a biggie.
>
>
> Additionally, I think the base API should focus on "staying lean and mean"
> and solving some fundamental problems. That being:
>
> 1) Memory Issues (API and Widget) - This needs a focused effort as it is
> probably the greatest handicap this API has right now.
> 2) Documentation and Instruct
I fully agree with the splitting of the project, I see no problem with having
the extensions built separately, I do however believe that the API should be
built with extensions in mind.
In my current structure, the type of language matches the file extension and
directory. this would mean that w
Ok, time for the "rockman" to put a little input here. I've put a
"disgusting" amount of time in server-side strategies. Before I get to that
I agree with the overall strategy to expand the scope and depth of the API.
That said I think the best path is one similar to that deployed by
PHPGroupWa
