----- Original Message -----
From: "Eytan Heidingsfeld" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, January 07, 2001 5:15 PM
Subject: [Dynapi-Help] DynAPI RAD (For those stubborn ones who still want to use
DYNAPI to develop)
> I have a few idea for how YOU could get over the I/O problem.
> a. Use a small downloadable java applet that is signed and only saves a file
> if you approve.
> b. Use a tiny server side script. You send it the code and it returns it
> with a .djs extension (or something of the sort) and then the browser
> automatically offers to download!
>
Mmmh, I had something of option B in mind. But rather than downloading from server,
save directly to server via the servers installed serverside scripting languague,
utilising its function for saving to a text-file (with extension html of course).
Fact is I was so sure this was the way to apply it, since DynAPI itself is to be
placed on a server, that I hadn't really considered the case of anybody using it
locally or at least saving locally. But I was also tempted by the thought of a IDE
for local use. Java of course could do as both I figure even though not optimal in
performance on every system, while Delphi is the more proper choice for a localbound
app.
I think we're really been discussing 3 different aproaches for 3 different cases (and
this sums it up as I figure):
1) DynAPI IDE in DynAPI for adding to an site on a server-side scripting enhanced
server for use by visitors and user of the site (my initial thought and aim)
2) An flexibel development tool to work in any OS enviroment that supports JAVA that
works wheter on a site or if downloaded and run locally
3) An development made in Delphi for use locally only (unless someone has a really
radical idea as to employ it as a server installed Application Service Provider
Application (not to be confused with ASP scripting server)
4) An component for download, which adds this feature toi the browser when using this
feature on a site that supports it on a page that is enablesd for it.
Each and all of them has desirable features, and I personally think it would be
limiting if we narrowed it down. Let anyone that wants form and/or build at their own
pick. I'm a sell-out cause I'll join any project where I could be contributing to,
just to have any kind of tool, but if i'm to work it alone (ie nobody wants to
collaborate with me) I'm chosing the DynAPI with ASP as serverside approach - and I
will stick with it even if it takes a very long time to reach. I have several ideas
(and some preliminary work) already that I'd be more than happy to share to any
project of the sort.
> 8an
> (C I can co-operate 2)
>
Yeah, well, thanks a lot for sorting things out a bit. I'd just wish it be a bit more
focused collaboration - a project (on any approach really) . If nothing else I'll be
looking forward to see what you - and anybody else - have going... :)
BTW I have some coding to do - I figure it will take me a couple of weeks even to get
together a presentation (by myself) - but I'll at least be notifying when done (as to
not pollute the list more with it). And as I have plead all along - anybody is
welecome to team up.
Henrik Våglin [ [EMAIL PROTECTED] ]
_________________________________________________________
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
