A lot of what you all are looking for has already been done by Dan.
Hopefully he can repost his servertask object that he wrote for an
early version of DynAPI 2. It would require it to be updated to the
latest stuff. It allowed you to make server requests from the DynAPI
using a hidden loadpanel. It was written in php, but could easily be
converted to perl and others.
--
// Robert Rainwater
On 1/8/2001, 8:04:26 PM EST, rlb wrote about "[Dynapi-Help] DynAPI RAD (For those
stubborn ones who still want to use DYNAPI to develop)":
> Roland,
> I sure wish I could have described that last week. That's exactly the
> thing I was
> thinking about for a DynBuilder.
> Just use a CGI for the I/O (Output files to the server, Input from a
> server or
> upload) and use DYNAPI for the positioning and content at first, and
> then work
> towards the fancy stuff like animation and timelines. This would also be
> an
> excellent way to divide some skill sets, CGI (DYNAPI extension for
> CGI's??) and
> Client (DYNAPI interface) user interface.
> I too am most comfortable with PERL, and in the end it could be made
> into a PERL
> package for easy distribution. I can't think of a more open
> architecture. Most
> likely it will require more work than traditional programming software
> would
> require.
> bobb
> Roland wrote:
>> I'm quite new to this list, so please excuse if I'm just repeating
>> something.
>>
>> Am Son, 07 Jan 2001 schrieb Eytan Heidingsfeld:
>> > 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!
>>
>> Why to download it?? - I think 90% of all web-developers have a local
>> apache running (and the others should have) - so why not to keep the
>> whole project server-side? If it's no local server you can access the
>> files via ftp, nfs, samba or whatever.
>> Reading this thread I have in mind that the dynapi-RAD would be a
>> collection of cgi-scripts that are - of course - using dynapi-widgets
>> for many things. So the main parts would be written in any language the
>> server can run - my preference is perl - The Browser (and Dynapi) would
>> be the frontend.
>>
>> so long,
>> Roland
>> --
>> Roland "Robelix" Obermayer
>> authorisierter Nichtdenker
>>
>> Mail: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
>> (bitte nicht mehr <[EMAIL PROTECTED]> verwenden!)
>> Homepage: http://www.robelix.com (und stolz d'rauf sei!)
>> Tel: (und nur mehr die!) 0699 / 1154 2243
>>
>> "This `telephone' has too many shortcomings to be seriously
>> considered as a means of communication. The device is
>> inherently of no value to us." - Western Union internal memo, 1876.
>>
>> _______________________________________________
>> Dynapi-Help mailing list
>> [EMAIL PROTECTED]
>> http://lists.sourceforge.net/mailman/listinfo/dynapi-help
> --
> bobb
> http://64.33.167.222/
> _______________________________________________
> 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
