This idea is great! I agree with Scott in that it would temendously increase
the popularity of the DynAPI. Right now, DynAPI is such that its application
requires a substantial knowledge of JavaScript and a lot of time invested in
going through the tutorials, source code and examples to see what is
possible and what is not. A GUI tool could reduce this learning curve
significantly. Experienced users would ofcourse edit the source code
produced for advanced tweaking, while novice users would be happy with what
they get.
It is my opinion as an intermediate-level Java Programmer that this project
should be implemented in Java (preferably as an application) for reasons of
ease & portability alone.Ofcourse my opinion is biased ;-). If
application-based I think that the editor portion of the project could be
conveniently taken from jEdit (also in sourceforge) (instead of building an
editor from ground up!) . The browser portion however must be interfaced
with an IE & Mozilla native library. I dont see the point in building a java
browser, when we actually want to see how things turn out in the 2 major
browsers. This might make the project non-portable across platforms, but one
can eliminate this problem by encapsulating this browser-view functionality
in a separate package of its own that is specific to the platform in which
one will use the DynBuilder.
The parser is still the hardest part though. I would be delighted to offer
any help in coding if it turns out to be implemented in Java.
----- Original Message -----
From: "Scott Andrew LePera" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 04, 2001 11:42 PM
Subject: Re: [Dynapi-Help] DynBuilder proposal
> Hmmmm... [wheels turning, smoke coming out of ears]
>
> I think the idea is too darn cool to not try it.
>
> It seems to me that the first working version of such a application
> might not allow for hand-modification of the code at first. The whole
> idea of "predefined structures" appeals to me, if only for the fact that
> it would make things more predictable. Simply drawing upon a cache of
> code templates stored somewhere would be a first step. I'll take
> everyone's word that code-parsing is a nightmare.
>
> And as far as writing a "mini web browser/editor in Java"...aren't there
> existing components that could be embedded or utilized? I really don't
> know, my knowledge of Java is pretty basic right now. But it occurs to
> me that there may already be tools to plunder.
>
> I'd be perfectly happy with an app that allowed me to insert widgets and
> modify their attributes, select a skin, etc. as a first attempt.
> Timelines, custom code and other stuff can come later.
>
> I remember somewhere recently (can't remember who or where) that the
> whole problem with DHTML is it's lack of a slick development
> environment, and that reduces it to the realm of code-wonks like us,
> while Flash takes off (because you really don't need to know how or why
> it works). I'm all for such a project.
>
> --
> scott andrew lepera
> -----------------------------------
> web stuff: www.scottandrew.com
> music stuff: www.walkingbirds.com
>
> _______________________________________________
> Dynapi-Help mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/mailman/listinfo/dynapi-help
>
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/dynapi-help
