RE: [Dynapi-Dev] Oversight (Code generation)

[Raible, M. <MR...@ED...>]

I have misplaced my mail list information on how to unsubscribe from
this list, can someone help me out?
=20
Thanks,
=20
Matt
=20
-----Original Message-----
From: Michael Pemberton [mailto:mp...@ph...]
Sent: Monday, January 22, 2001 8:38 AM
To: dyn...@li...
Subject: Re: [Dynapi-Dev] Oversight (Code generation)
=20
I was mucking around with this last night.  the attached file is one
method of doing it.=20
Just include the attached file and call layerName.generateCode() this
should return a copy of the initialisation command for the layer.=20
Pascal wrote:=20
Some secondary values are callable, but certain arrays will give
problems=20
(I'm trying to fix that).=20
I'm not sure if I can retrieve variable names (anyone with an idea on
that=20
one?) But I am planning on creating an extra module like Oversight,
which=20
reads the DynAPI tree of objects (dynapi.document and all child layers)
and=20
regenarets correct code for it.. This would be the first step for
wysiwyg=20
editing.. simple attach dragevent listeners to every layer on screen so
that=20
they can be placed, call the code-generator and you have your wysiwyg
editor=20
Also another idea I'm having is including a better object watcher to=20
Oversight.. like the one found in Delph, Visual basic ,etc.. a window=20
showing all properties and values, make them editable and you have easy=20
access to every object, making the Dump Object obsolete.=20
cya,=20
Pascal Bestebroer (pb...@oi...)=20
Software ontwikkelaar=20
Oberon Informatiesystemen b.v.=20
http://www.oibv.com <http://www.oibv.com> =20
> -----Oorspronkelijk bericht-----=20
> Van: dyn...@li...=20
> [ mailto:dyn...@li...
<mailto:dyn...@li...> ]Namens Richard Bennett=20
> Verzonden: maandag 22 januari 2001 0:42=20
> Aan: dyn...@li...=20
> Onderwerp: Re: [Dynapi-Dev] Oversight=20
>=20
>=20
> Hi,=20
> This was another amazing job, both of you, I'll add it to=20
> every example on=20
> my site with the next release,=20
> and have it called from a link instead of my DynAPIDiagnose.=20
> A few points:=20
>     you probably know dumping the secondary values from the hyperlinks

> doesn't work yet.=20
>     Is it possible to get a clickable list of the objects on=20
> the page by the=20
> name they were defined by, like this:=20
>=20
>     Available objects on this page:=20
>     * MyLayer=20
>             *MyChildLayer=20
>=20
>     * SkinWindow1=20
>             *myPushPanel1=20
>                     *myLoadPanel1=20
>     etc.=20
>     oh, and you could add printing, and...=20
>=20
> Cheers,=20
> Richard Bennett=20
>=20
> ma...@ri...=20
> www.richardinfo.com=20
> (Everything running on, and ported to the 19/12/2000 snapshot=20
> of DynAPI2)=20
>=20
>=20
> ----- Original Message -----=20
> From: "Pascal Bestebroer" <pa...@dy...>=20
> To: "Dev" <dyn...@li...>=20
> Sent: Sunday, January 21, 2001 2:58 PM=20
> Subject: [Dynapi-Dev] Oversight=20
>=20
>=20
> > Played "abit" with Martin Str=F6m 's console code, and got=20
> some nice ideas=20
> on=20
> > how to enhance it.=20
> > See the attached result.=20
> >=20
> > Unzip this package into a sub directory of your DynAPI code=20
> (eg. into the=20
> > src/ directory), and add the following two lines to your=20
> code for some=20
> great=20
> > debuggin tools:=20
> >=20
> > DynAPI.include('oversight.js','../src/oversight')=20
> >=20
> > and then in the DynAPI.onLoad, add the first line:=20
> >=20
> > Oversight.run('../src/oversight')=20
> >=20
> > where the '../src/oversight' is the path of your Oversight=20
> root folder.=20
> >=20
> > I haven't done much on errorhandling yet so be carefull,=20
> but currently you=20
> > have the=20
> > following tools:=20
> >=20
> > * Add watch=20
> >   Adds a property to the watcher.. the watcher will then=20
> display the value=20
> > of that property.=20
> >   For example, try adding a watch for myLayer.x  and make the layer=20
> > dragable..=20
> >=20
> > * Delete watch=20
> >   Deletes the property or variable from the watcher list..=20
> no real need=20
> for=20
> > this, every property=20
> >   will have a DEL link in the watcher window, to remove=20
> it.. saves typing=20
> >=20
> > * Dump object=20
> >   Dumps the specified object and it's properties/methods..=20
> also creating=20
> > dynamic hyperlinks for=20
> >   all child objects.=20
> >=20
> > * Show value=20
> >   Displays the value of the specified variable or property=20
> (not watching,=20
> > just printin it once)=20
> >=20
> > * Execute code=20
> >   Will execute any code you type in it.. Basically this=20
> allows you to=20
> create=20
> > DynLayer, move existing=20
> >   DynLayers/widgets, etc,etc,etc.=20
> >=20
> > I want to enhance the Execute code, so that it displays a=20
> memo field so in=20
> > which you can type more lines=20
> > at once.. making it a runtime editor.=20
> >=20
> > I think that when we create more of these types of tools, that the=20
> > DynBuilder as described by Henrik is actually possible as a=20
> Webapplication.=20
> >=20
> > I've only tested this stuff on IE5 and NS4.. and works=20
> under both browsers=20
> > perfectly.=20
> > Let me know of any ideas, comments, flames, rock throwing, etc..=20
> >=20
> > cya,=20
> >=20
> > Pascal Bestebroer=20
> > pa...@dy...=20
> > http://www.dynamic-core.net <http://www.dynamic-core.net> =20
> >=20
>=20
>=20
> _______________________________________________=20
> Dynapi-Dev mailing list=20
> Dyn...@li...=20
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
<http://lists.sourceforge.net/lists/listinfo/dynapi-dev> =20
>=20
_______________________________________________=20
Dynapi-Dev mailing list=20
Dyn...@li...=20
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
<http://lists.sourceforge.net/lists/listinfo/dynapi-dev>=20
--=20
Michael Pemberton=20
mp...@ph...=20
ICQ: 12107010=20
=20