----- Original Message -----
From: "Scott Andrew LePera" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 04, 2001 7:12 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.
>
I figured this was the toughest part, but is it really that impossible a task?
> 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.
>
In my experience it's not a great idea to try and mount together different apps to
build a new one (especially with a language like Java) unless you have access to
modify code as needed. I still propose that DynAPI itself provides the most scalable
and flexible base to build from and is to a good enough rate standardisized to work
seamlessly integrated. Don't you guys belive in what you've created or your ability to
extend it as neeeded? I remeber that DynAPI amazed me the first time after seen a lot
of crap DHTML. Are there nobody but me that believes there's still can be done magic
with this excellent tool?
> 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.
>
Me too. It begins with the dynlayer anyhow for most people - for some it might be all
they'll ever need from DynAPI2. Timelines and stuff would be desirable (at least for
my own developments), but you gotta keep it simple to ever get it finished - so
keeping a short list of features to begin with should probably be smart idea. Actually
I'm thinking that once a basic DynBuilder constructur is ready and working with basic
features there's no limit to the number of extensions can be created (except to
consider the amount of actual RAM it will consume).
> 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.
>
This is true only until a DynBuilder is ready for distribution no? (boldness and
bigheadness in one package)
> --
> scott andrew lepera
> -----------------------------------
> web stuff: www.scottandrew.com
> music stuff: www.walkingbirds.com
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/dynapi-help
