More on design thoughts.
I've been thinking about this some (I know, dangerous territory).

I'm not a javascript expert (or even close), so sorry if this is supposed to be blatantly obvious to me (I'm really more of an idea man), but . . .

What would it take to extend the core objects and maybe a couple of the more popular widgets to also have a 'Object settings/values' parameter for each. Something that could be called and passed back for inclusion in a CGI POST (new DYN core Object [DynFormBuild]???). This would also, I believe, help with debugging efforts of sorts, at least for me. I could test just by sending the settings to a CGI as a Form POST

Would this kind of modification introduce too much in the way of overhead into the Core objects?

bobb

Henrik Våglin wrote:

IMHO, a DynBuilder tool should be like you say to have
it save server-side and as I'm trying to keep it true
to the OOM (object oriented model) concept, several
packages - server-side and others - should be able to
be applied for the saving feature (as well with any
other feature of the DynBuilder tool).

But I see it come off as two different projects
really, DynAPI RAD - which I leave for others to build
and construct in a fit programming enviroment - and
the DynBuilder class I have begun scripting and
constructing in DynAPI - and that will be able to
include different flavors of (Server)Tasks for saving
and such features. The latter is to be a somewhat
simplier, but still a quite monumentous task (I figure
a semi-duplicate of the dynapi itself must be
constructed), that will take me a few weeks yet to
even make presentable. I hope everybody awaiting it is
patiant, cause it seems I'll be working alone on this
one...

Henrik Våglin [ [EMAIL PROTECTED] ] (the stubborn one)

 --- Roland <[EMAIL PROTECTED]> skrev: > 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

=====
// Henrik Vaglin

**************************************************
Visit my comics artpage at
http://photos.yahoo.com/bc/hvaglin?d&.flabel=fld5&.src=bc
**************************************************

__________________________________________________
Do You Yahoo!?
Yahoo! Photos - Share your holiday photos online!
http://photos.yahoo.com/

_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/dynapi-help

--

bobb

http://64.33.167.222/
 

Reply via email to