It's browser based.

This is what currently happens:

- You load the oversight.htm page
- this spawns the application window (one small window, containing buttons
to open debugger,wise,property inspector)
- clicking the buttons in the appwindow, opens another window containing one
of the Oversight modules (debugger,wise,etc..)
- Windows can be closed and reopened again..
- Closing the main window (containing your work area) will close all
oversight windows automatically

So in most cases you will have the following windows open:

- main editing window (your normal browser window containing blank page)
- Oversight appbar (small horizontal window.. only 100px high.. and 320px
width (for now))
- Editor (containing editing options to add layers)
- and possibly the property inspector


There will be window switching with alt-tab, but every module's title bar
contains the name of the module.. so with alt-tab it should be possible to
switch to the correct window without much problems.

I will try my best to release something this afternoon.. and post a link.

Pascal Bestebroer
[EMAIL PROTECTED]
http://www.dynamic-core.net

> -----Oorspronkelijk bericht-----
> Van: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]Namens Darin Kadrioski
> Verzonden: zondag 11 februari 2001 5:29
> Aan: '[EMAIL PROTECTED] '
> Onderwerp: RE: [Dynapi-Dev] Oversight (was: a couple of tools)
>
>
>
> Does oversight have an actual executable, or is it all browser based?
>
> If it's browser based, are the window titles constant?
>
> If so, I could write a small tray-icon app in Delphi that could hide
> selected windows based on their captions.
>
> No big deal really, I would just need a list of the window
> captions in their
> exact case.
>
> -----Original Message-----
> From: Bill Lovett
> To: [EMAIL PROTECTED]
> Sent: 2/10/01 7:44 PM
> Subject: RE: [Dynapi-Dev] Oversight (was: a couple of tools)
>
> Instead of managing windows by shading them, what do you think about
> putting
> a "remote control" in the main window of whatever you're debugging? I
> added
> the following crude functions listed below to oversight.js, then called
> addPageController() right after calling Oversight.run(). The result is a
> DynLayer that easily lets you bring a specific window (or all three)
> into
> focus. If pursued further, this approach could lead to a
> best-of-both-worlds
> between Oversight and DynAPI.Diagnose: some stuff happening in external
> windows, some stuff happening inside the main one.
>
> On a related note, does anyone know of a way to filter out Oversight's
> windows from the Windows task switcher? That would be a handy trick,
> saving
> many unnecessary alt-tabs.
>
> -bill
>
> addPageController : function() {
>    OversightController= new DynLayer()
>    OversightController.setSize(100,100)
>    OversightController.moveTo(DynAPI.document.w-OversightController.w,0)
>    OversightController.setBgColor('#cc99ff')
>    DynAPI.document.addChild(OversightController)
>
> OversightController.setHTML(
>    '<a href="#" onClick="Oversight.idewin.focus()">Show IDE</a><br>' +
>    '<a href="#" onClick="Oversight.Oversightwin.focus()">Show
> Console</a><br>' +
>    '<a href="#" onClick="Oversight.watcher.focus()">Show
> Watcher</a><br>' +
>    '<a href="#" onClick="Oversight.arrange()">Arrange All</a>'
>    )
> },
>
> arrange : function() {
>    Oversight.idewin.moveTo(0,0); Oversight.idewin.focus()
>    Oversight.Oversightwin.moveTo(262,0);Oversight.Oversightwin.focus()
>
> Oversight.watcher.moveTo(0,screen.availHeight-230);Oversight.watcher.foc
> us()
> },
>
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Pascal
> Bestebroer
> Sent: Saturday, February 10, 2001 1:19 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [Dynapi-Dev] Oversight (was: a couple of tools)
>
>
> Already struggling with it.. Although not all windows need to be open at
> all
> times, you only have to open the debugger when you need it.
>
> I was trying to work out some way to shade windows (min. size is
> 100x100)
> but can't get it to work correctly yet, and not sure if it works under
> IE4.
>
> I'm now trying to make the windows as easy-placed and small as
> possible..
> but there will be some window moving when your working, for people
> familiar
> with
> Borland development envrionments it won't be such a big thing (there are
> always some windows floating around as well)  but I think for people
> used to
> DreamWeaver this will be not so familiar, and might look a bit difficult
> at
> first)
>
> Today I got the property editor working (simple, with bugs.. but it
> works
> :-)  So I'm pretty sure I can release something this weekend (nothing
> really
> useable
> for projects or anything, but I'm hoping for feed back on it)
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>


_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Reply via email to