From: Michael P. <mp...@ph...> - 2001-01-22 15:42:01
|
<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> I was mucking around with this last night. the attached file is one method of doing it. <br>Just include the attached file and call <i>layerName</i>.generateCode() this should return a copy of the initialisation command for the layer. <p>Pascal wrote: <blockquote TYPE=CITE>Some secondary values are callable, but certain arrays will give problems <br>(I'm trying to fix that). <p>I'm not sure if I can retrieve variable names (anyone with an idea on that <br>one?) But I am planning on creating an extra module like Oversight, which <br>reads the DynAPI tree of objects (dynapi.document and all child layers) and <br>regenarets correct code for it.. This would be the first step for wysiwyg <br>editing.. simple attach dragevent listeners to every layer on screen so that <br>they can be placed, call the code-generator and you have your wysiwyg editor <p>Also another idea I'm having is including a better object watcher to <br>Oversight.. like the one found in Delph, Visual basic ,etc.. a window <br>showing all properties and values, make them editable and you have easy <br>access to every object, making the Dump Object obsolete. <p>cya, <p>Pascal Bestebroer (pb...@oi...) <br>Software ontwikkelaar <br>Oberon Informatiesystemen b.v. <br><a href="http://www.oibv.com">http://www.oibv.com</a> <p>> -----Oorspronkelijk bericht----- <br>> Van: dyn...@li... <br>> [<a href="mailto:dyn...@li...">mailto:dyn...@li...</a>]Namens Richard Bennett <br>> Verzonden: maandag 22 januari 2001 0:42 <br>> Aan: dyn...@li... <br>> Onderwerp: Re: [Dynapi-Dev] Oversight <br>> <br>> <br>> Hi, <br>> This was another amazing job, both of you, I'll add it to <br>> every example on <br>> my site with the next release, <br>> and have it called from a link instead of my DynAPIDiagnose. <br>> A few points: <br>> you probably know dumping the secondary values from the hyperlinks <br>> doesn't work yet. <br>> Is it possible to get a clickable list of the objects on <br>> the page by the <br>> name they were defined by, like this: <br>> <br>> Available objects on this page: <br>> * MyLayer <br>> *MyChildLayer <br>> <br>> * SkinWindow1 <br>> *myPushPanel1 <br>> *myLoadPanel1 <br>> etc. <br>> oh, and you could add printing, and... <br>> <br>> Cheers, <br>> Richard Bennett <br>> <br>> ma...@ri... <br>> www.richardinfo.com <br>> (Everything running on, and ported to the 19/12/2000 snapshot <br>> of DynAPI2) <br>> <br>> <br>> ----- Original Message ----- <br>> From: "Pascal Bestebroer" <pa...@dy...> <br>> To: "Dev" <dyn...@li...> <br>> Sent: Sunday, January 21, 2001 2:58 PM <br>> Subject: [Dynapi-Dev] Oversight <br>> <br>> <br>> > Played "abit" with Martin Ström 's console code, and got <br>> some nice ideas <br>> on <br>> > how to enhance it. <br>> > See the attached result. <br>> > <br>> > Unzip this package into a sub directory of your DynAPI code <br>> (eg. into the <br>> > src/ directory), and add the following two lines to your <br>> code for some <br>> great <br>> > debuggin tools: <br>> > <br>> > DynAPI.include('oversight.js','../src/oversight') <br>> > <br>> > and then in the DynAPI.onLoad, add the first line: <br>> > <br>> > Oversight.run('../src/oversight') <br>> > <br>> > where the '../src/oversight' is the path of your Oversight <br>> root folder. <br>> > <br>> > I haven't done much on errorhandling yet so be carefull, <br>> but currently you <br>> > have the <br>> > following tools: <br>> > <br>> > * Add watch <br>> > Adds a property to the watcher.. the watcher will then <br>> display the value <br>> > of that property. <br>> > For example, try adding a watch for myLayer.x and make the layer <br>> > dragable.. <br>> > <br>> > * Delete watch <br>> > Deletes the property or variable from the watcher list.. <br>> no real need <br>> for <br>> > this, every property <br>> > will have a DEL link in the watcher window, to remove <br>> it.. saves typing <br>> > <br>> > * Dump object <br>> > Dumps the specified object and it's properties/methods.. <br>> also creating <br>> > dynamic hyperlinks for <br>> > all child objects. <br>> > <br>> > * Show value <br>> > Displays the value of the specified variable or property <br>> (not watching, <br>> > just printin it once) <br>> > <br>> > * Execute code <br>> > Will execute any code you type in it.. Basically this <br>> allows you to <br>> create <br>> > DynLayer, move existing <br>> > DynLayers/widgets, etc,etc,etc. <br>> > <br>> > I want to enhance the Execute code, so that it displays a <br>> memo field so in <br>> > which you can type more lines <br>> > at once.. making it a runtime editor. <br>> > <br>> > I think that when we create more of these types of tools, that the <br>> > DynBuilder as described by Henrik is actually possible as a <br>> Webapplication. <br>> > <br>> > I've only tested this stuff on IE5 and NS4.. and works <br>> under both browsers <br>> > perfectly. <br>> > Let me know of any ideas, comments, flames, rock throwing, etc.. <br>> > <br>> > cya, <br>> > <br>> > Pascal Bestebroer <br>> > pa...@dy... <br>> > <a href="http://www.dynamic-core.net">http://www.dynamic-core.net</a> <br>> > <br>> <br>> <br>> _______________________________________________ <br>> Dynapi-Dev mailing list <br>> Dyn...@li... <br>> <a href="http://lists.sourceforge.net/lists/listinfo/dynapi-dev">http://lists.sourceforge.net/lists/listinfo/dynapi-dev</a> <br>> <p>_______________________________________________ <br>Dynapi-Dev mailing list <br>Dyn...@li... <br><a href="http://lists.sourceforge.net/lists/listinfo/dynapi-dev">http://lists.sourceforge.net/lists/listinfo/dynapi-dev</a></blockquote> <p>-- <br>Michael Pemberton <br>mp...@ph... <br>ICQ: 12107010 <br> </html> |