<<< ----- Original Message -----
From: "Eytan Heidingsfeld" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, December 31, 2000 7:18 AM
Subject: RE: [Dynapi-Help] Dreamweaver plug-in specific (or maybe a webapp?)
I told you all that I already started (although I didn't do much) in
creating such a standalone. I was doing it in Delphi and I figured out how
to make delphi interact with the webbrowser object (where the DynAPI
document will be displayed) if anyone wants to help pls let me know.
8an >>>
Sorry for not read the thread more carefully, I'm not trying to step on any toes
though.
Anyway, I'm not that advanced with Delphi, but if you take a look at the post I will
make in a day or two (a UI model proposal), maybe you can figure wheter or not you
would like me to contribute in some other area of the DW extension development (I have
for example some iniating DW command extension halfway done). just let me know what
you figure...
<<< ---- Original Message -----
From: "rlb" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, December 31, 2000 8:27 AM
Subject: Re: [Dynapi-Help] DynBuilder - Was "WEB App"
Henrik (and others),
I'm most likely going to stir up something here, sorry if I'm to naive
in my thinking. >>>
Hey, I thought we were brainstorming here - any idea is to be considered, no?
<<< Henrik V�glin wrote:
> Instead I have had the idea that maybe a webapp that
> is a webeditor fit for DynAPI development is in place.
> It's actually what I was planning to do anyway[...]
I believe that I started this thread, and mentioned something similar to
using the web as the building interface to DYNAPI. I think that using
the same tack in building DYNAPI itself, CORE, Widgets, Util, etc. would
work well in the development of a basic Web based DYNAPI enabled page
builder, if only to build the basics and then leaving the detailed
design elements to the individual author(s), at least in the beginning. >>>
I'm going about it as a widgetpack or sublibrary in my thinking... (ie
src='js/lib/DynBuilder/*.*')
<<< Another option might be to build a DYNAPI debugger of sorts that is web
enabled, a sort of "DYNAPI enabled Web Page" deconstructor if you will.
This sounds on the surface like it would be an excellent resource for
learning the API and could incorporate the tutorials that are already in
existence. Even something as simple as the INFO option presented from a
right click in Netscape, only DYNAPI enhanced would I believe go a long
ways towards promotion of DYNAPI. >>>
A debugger sounds like it requires a lot of insight into the DynAPI which a Web IDE
wouldn't - it's one thing to handle using the code but another to understand it at
it's core. Here it really seems only one of the main developers (ie admins) could do
the job, but what do I know, maybe you do ( and that honestly wasn't meant to be
sarcastic )
<<< > (especially with the heavy development changes
> of the DynAPI itself), so we better be a few (approx
> at least 6-8 people) with varied experience before we
> even start planning it.
I believe that an experienced DYNAPI developer would need to be coaxed
into participation to launch such an effort like this for it to become
useful and keep up with the development of the API itself. It may even
be too early to start this type of development until a good stable build
is in the can for a known set of CORE files and basic Widgets. >>>
well, I do think there would be good if a really experienced developer would cooperate
at least during the planning phase, but actually I think there are a lot in DynAPI
that could be used to build the IDE interface.
<<< I myself am still getting a handle on DYNAPI, and see this (Web Enabled
Dynamic Page Builder [DynBuilder??]) as just another application that
could be built using DYNAPI. >>>
I was kind of heading the same way in thinking. I'm not sure wheter it could go as a
widget (after all it might fit within a layer)
<<< My original goal with the suggestion for a Web enabled Dynamic page
builder was to get folks thinking about the idea. >>>
you certainly got me thinking (see the attachments)
<<< I also had
reservations about building a similar interface tied to any one
proprietary application (DreamWeaver, etc) as others contributing to
this thread have voiced. With a Web interface, there is an excellent
opportunity to position the DYNAPI as a standard for dynamic development
and promotion, and at the same time, retaining control and direction of
future capabilities, especially alongside development of the API itself. >>>
I don't have that kind of reservations - especially not against Dreamweaver which I'm
quite fond of - but I do think DynBuilder sounds more tempting as I like the idea of
making the tool if created accessible to anyone and because it can be a part of a
DynAPi distro.
I'll be releasing a DynBuilder model proposal in a day or 2.
I don't expect anything, but it would be so kind if you would care to consider it,
because I will have spent an hour or a few on it. Your then most welecome to have own
contributions or suggestions to it, since I'll be releasing it under the same GNU
liscence as the DynAPI ;)
(In case I forget later: Don't mind that I might have named it DynAPI_RAD on a couple
of places - I just needed a working name, so I snapped a short one from one of the
recent posts on the thread)
Sorry if I'm being pushy, it's just that when I have a go at a project I enjoy the
idea of, I want to get the most out of the creativity that keeps flowing and possible
get things moving. I don't intend to monopolize anything by that, but others better
keep up with me or slow me down if they want to take part - I'm very open minded when
it comes different ideas or suggestions others make and will consider and discuss all
carefully when notified.
Henrik V�glin
_________________________________________________________
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
