--- Doug Melvin <[EMAIL PROTECTED]> wrote: >
>
> 1) DynAPI based IDE: A good idea in itself, but I
> can guarantee that I would not be able to use it on
> my P120 with 24 megs of ram at home.. It's hard
> enough just to view a site like www.zara.com
> (I still haven't seen it at it fullest) and I
> know that a DynAPI IDE would be even more intensive
> that the
> afore mention web site.
>
I feel obliged to answer up on this since I seem to be
the only one holding this as favourite.
Actually I thinking like this: DynBuilder wouldn't
have to be a monster app, because it really should be
reading DynAPI rather than loading, since the common
case you don't add very many layers and/or set many
properties of it and the GUI should be able to keep
very slick to. Other than that I figure that most
Internet users (in target for DynAPI2 development)
will in less than a year have connections with
capacity over 56k and if you're a developer anything
under 64mb in RAM is unusable. Mind you DynBuilder
target developers in more obsoloute extent than DynAPI
itself. If this issue is taken under condersiration
carefully, a DynAPI-based DynBuilder can be really
slick. (the refered to www.zara.com is using mediarich
flash which isn't to be the case of an DynBuilder
tool.
And well, if nothing else gets to you I would like to
point out that a DynBuilder done in DynAPI would prove
how and what can be done with the DynAPI in
webapplication development. It's not just a tool, its
also an exemplification to blender opposition with
with.
> 2) Delphi: While Delphi "will" support Linux, it
> does not yet and counting on future developments for
> a
> current project is a very bad way to go about
> things.
> Not only that, but there are indeed MAC users
> involved in DynAPI as well as Win32 and Linux.
>
I think that if we don't consider users on Mac, we
ignore a large audiance, since webdesigners still
mainly work on Mac (while most the worlds webservers
are Linux with Apache and a few Windows NT with IIS).
> 3) Java: Probably our best bet, as it is indeed open
> platform. Correct me if I am mistaken, but can you
> not use ActiveX object within Java? If so, the
> code parsing/HTML display would NOT be a problem.
> The Enterprise edition if Visual Basic (which we
> use here) come with a license to re-distribute the
> IE
> browser object (I believe it is version 4.0)
> which means that someone (such as myself) could
> create
> an ActiveX browser object for use with Java.
>
Maybe MS have created a java class for running an
ActiveX that integrates it with java seamlessly - I
wouldn't rally know. I would strongly suggest not to
use that approach, since it's to many scripting
translations done for one thread (2 steps or more than
the DynAPI2 approach, 3 more than the Delphi approach
and 2 more than a strict Java approach)
> In conclusion my humble opinion is that we should
> most definitely go with Java for it is
> cross-platform and quite robust in it's own right.
> Java is also well know for extensibility.. i.e.; it
> is very easy to upgrade or replace a single
> component (such as a newer browser object) without
> having to re-write the rest of the program..
>
> Thank You,
> Doug Melvin
> Integrated System Solutions: Design, Development,
> Implementation and Support
> Creative-Workshop.com
>
Well, each approach has its pro and cons - I could
consider them all, but I still think its best to not
stroll away to much from actually use of the DynAPI as
preview output. Actually I think I reside myself as to
be working out models and do graphics (of which i'vw
already done some). I'll be posting a new proposal
soon that won't take part on which approach to go
with, so that anyone who feels up for it can begin
coding or form a project. Maybe we'll go with all 3
approaches if we can't all comfort with one.
Just to make sure, who will contribute efforts to:
* a Java application approach?
* a Delphi approach?
* a DynAPI integrated approach?
I'm actually ready open for all 3 but mostly the last
one since the its the one I could contribute most
coding to.
Also do you think this should be formed under a new
flag - ie a new project on Sourceforge? In that case I
suggest its to be called DynAPI RAD (Rapid Application
Development). How do you all consider that?
Henrik V�glin [[EMAIL PROTECTED]]
__________________________________________________
Do You Yahoo!?
Yahoo! Photos - Share your holiday photos online!
http://photos.yahoo.com/
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/dynapi-help
