dynapi-dev — List related to the current DynAPI Core development

RE: Re[2]: [Dynapi-Dev] buttons bug??

[Pascal <pb...@oi...>]

> Right-mouse click menu disablement can be cross-browser.

sure about IE4 ?

> Anyway,
>
> I have a question about events/our EventMethod...
> (some of the below has been a reference from Scott Andrew's
> web site -- scottandrew.com -- in the Netscape 6 Events article)
>
> So, I beleive (and I could be wrong, so please correct me if
> I am) the model that we are wanting to use is the IE's target
> to document to window. You might think that events are
> working in NS6 with the current release, but they are not.
> Upon closer examination and testing with very extensive
> examples, the events to not trigger correctly. Well, I have
> fixed the event's in NS6 (the reason everything was happening
> more than once is the fact that there is more than one event
> phase -- 3 actually).

As far as I'm aware someone had already posted a fix for this aswell.. and I
noticed
some code in the event code to try and catch it.

> But the problem is NS4's window to
> document to target. If we want the events to behave in the
> same way cross-browser in very complex examples/widgets that
> uses bubbling, than we need to reverse the way that NS4
> captures events (like IE's), and then use our own event
> bubbling method for the bubble (like in IE).

In my memory, this has always been our target.. and I thought the
Eventlistener was
build to make NS work the same as IE.

I'm actually not sure if the bubbling thing is actually working in the
current releases.

> Part of my reorganization consisted of breaking away mouse
> events form the events.js file, and making it a sperate
> "mouse.js" file.
> This way, you can still have create/delete/resize/etc...
> events get triggered, but not have to worry about the
> weighing down the code/processor with mouse events, if they
> are unecessary. (Plus, I saw this as being consistant with
> some if the file structure now, ie. keyevets.js).

Good idea

> Also, because it they are required by the DynAPI (dynapi.js),
> I have made certain files (document.js, object.js, events.js)
> be automatically included when you set the library path.

Not sure if that's the way to go.. there might eventually be lite versions
(again :)
or some other versions of the document/object/event files. In that case you
would
need to be able to switch.. making people get used to including files will
then be
easier for them.

Also, why so "secretive" about your things.. if you fix something try
posting information
or better post a patch.. this could help speed the DynAPI development. If
you fix things
in your code great! but you can also fix it in the DynAPI code aswell (even
better!)


Pascal Bestebroer (pb...@oi...)
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com

RE: [Dynapi-Dev] Oversight (was: a couple of tools)

[Pascal <pb...@oi...>]

I might upload it to my website to make it available from there, but the
idea is
that it can run on normal client systems.

Hmm, could be an idea, but have to see if that background windows never gets
on top, because
that might be more confusing (having one big empty window,with of course a
very nice wallpaper...uhm background)

Maybe I'll try to change the background or layout of the modules, so that
they are less confusing on top of icons :)


Pascal Bestebroer (pb...@oi...)
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Richard Bennett
> Verzonden: maandag 12 februari 2001 8:36
> Aan: dyn...@li...
> Onderwerp: Re: [Dynapi-Dev] Oversight (was: a couple of tools)
>
>
> yes, this shows a lot of potential. Great job.
> I wonder, are you planning on this being run from a webserver
> or on the
> client machines?
> As you mentioned, the style reflects Borland stuff, (with the floating
> panels) which gives a very confusing effect over a desktop
> full of icons.
> Maybe you can include a "hide desktop" function, opening a
> screensize layer
> in relaxing gray, or even with a nice background image, now
> where could we
> find a few nice backgrounds...
>
> Cheers,
> Richard Bennett
>
> ma...@ri...
> www.richardinfo.com
> (Everything running on, and ported to the 19/12/2000 snapshot
> of DynAPI2)
>
> ----- Original Message -----
> From: "Pascal Bestebroer" <pa...@dy...>
> To: <dyn...@li...>
> Sent: Sunday, February 11, 2001 1:35 PM
> Subject: RE: [Dynapi-Dev] Oversight (was: a couple of tools)
>
>
> > Well, here goes.
> >
> > Just uploaded a pre-beta (read : buggy) version of my current code,
> > you can download it here:
> http://www.dynamic-core.net/oversight-prebeta.zip
> >
> > WARNING:  I only tested so far on IE5 and NS4 (previous
> code also worked
> on
> > IE4), this
> > version if VERY BETA, so please don't start mailing me with
> bug-reports,
> I'm
> > very aware of them
> > and they will eventually get fixed.
> >
> > I AM interested in any opinions, ideas and other notes, so
> please let me
> > know.
> >
> > The zip file contains a Dynacore version aswell, but I tested the
> Oversight
> > code and it works
> > with the latest snapshot (probably not with the release).  Open the
> > Oversight.htm file in the
> > root of the zip, and that should lead you thru it.
> >
> > One big-bug that I will try to fix, is in the DynAPI.. Try
> adding a layer,
> > and then a child-layer.. then
> > reset the html content :-)   I think this is fixable by
> modifying the
> > setHTML in the DynAPI (simply remove all layers, change
> HTML, and re-add
> > them) so I'll try to fix it, and patch it into CVS.
> >
> > The scripter is also working nicely.. so take a look at it :)
> >
> > Pascal Bestebroer
> > pa...@dy...
> > http://www.dynamic-core.net
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> > ____________________________________________________________
> > Get your free domain name and domain-based e-mail from
> > Namezero.com. New!  Namezero Plus domains now available.
> > Find out more at: http://www.namezero.com
> >
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>

Re: [Dynapi-Dev] Idea: expanding the dir-structure

[Richard B. <ma...@ri...>]

I'll be applying this system when I update my site, to avoid further
confusion.

Cheers,
Richard Bennett

ma...@ri...
www.richardinfo.com
(Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2)

----- Original Message -----
From: "Robert Rainwater" <rra...@ya...>
To: "DynAPI Development List" <dyn...@li...>
Sent: Monday, February 12, 2001 4:43 AM
Subject: Re: [Dynapi-Dev] Idea: expanding the dir-structure


>
> There's no need for a contrib directory.  People that write there own
> widgets should create there own packages though.  Thats why the
> addPackage methods are available.  So you would do like this:
>
> lib/
>   dynapi
>      api
>      gui
>      ...
>   robsapi
>      gui
>      util
>   ...
>
>
>
> --
> // Robert Rainwater
>
> On 2/11/2001, 9:11:32 PM EST, robelix wrote about "[Dynapi-Dev] Idea:
expanding the dir-structure":
>
> > Hi!
>
> > Just an Idea to split up the core-dynapi and all the extensions,
> > widgets... everybody is writing:
>
> > we should add a contrib directory to src/lib/dynapi where everybody can
> > add his own dir
>
> > so for example I would add my fixedanim.js extensions to
> > src/lib/dynapi/contrib/robelix/util/fixedanim.js
>
> > Why?
>
> > - the core should not be overloaded
> > - everybody can upload his stuff without conflicting the work of others
> > - future releases could easiely be split into core and contrib packages
>
> > What do you think?
>
>
> > Roland
>
> > P.S.
> > if you want to know what my fixedanim.js will be (not finished so far,
> > I guess in about a week)
> > It's for effects like those on my homepage:
>
> > http://www.robelix.com
>
> > (it's done with dynapi1 - but I'm going to upgrade soon)
>
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
>
> ----------------------
> DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
> DynAPI Homepage: http://dynapi.sourceforge.net/
>
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> ____________________________________________________________
> Get your free domain name and domain-based e-mail from
> Namezero.com. New!  Namezero Plus domains now available.
> Find out more at: http://www.namezero.com
>

Re: [Dynapi-Dev] Idea: expanding the dir-structure

[Robert R. <rra...@ya...>]

There's no need for a contrib directory.  People that write there own
widgets should create there own packages though.  Thats why the
addPackage methods are available.  So you would do like this:

lib/
  dynapi
     api
     gui
     ...
  robsapi
     gui
     util
  ...



-- 
// Robert Rainwater

On 2/11/2001, 9:11:32 PM EST, robelix wrote about "[Dynapi-Dev] Idea: expanding the dir-structure":

> Hi!

> Just an Idea to split up the core-dynapi and all the extensions, 
> widgets... everybody is writing:

> we should add a contrib directory to src/lib/dynapi where everybody can 
> add his own dir

> so for example I would add my fixedanim.js extensions to 
> src/lib/dynapi/contrib/robelix/util/fixedanim.js

> Why?

> - the core should not be overloaded
> - everybody can upload his stuff without conflicting the work of others
> - future releases could easiely be split into core and contrib packages

> What do you think?


> Roland

> P.S.
> if you want to know what my fixedanim.js will be (not finished so far, 
> I guess in about a week)
> It's for effects like those on my homepage:

> http://www.robelix.com

> (it's done with dynapi1 - but I'm going to upgrade soon)

> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev


----------------------
DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
DynAPI Homepage: http://dynapi.sourceforge.net/

Re: [Dynapi-Dev] All this "Rock" discussion...

[Richard B. <ma...@ri...>]

>I'll at least title mark this brief series with...
> "rock" in it...
You didn't.

----- Original Message -----
From: "Raymond Smith" <dst...@or...>
To: <dyn...@li...>
Sent: Monday, February 12, 2001 3:47 AM
Subject: Re: [Dynapi-Dev] All this "Konqueror" discussion...


> The value of  "exposure" Richard.
>
> Plus the "rare" treat of actually being able to produce a smile on the
> logic-etched face of a programmer.
>
> But...
>
> For your benefit (though I think later in life you will pay a greater
price,
> as will your humorless children) I'll at least title mark this brief
series
> with...
>
> "rock" in it...
>
>
>
> ----- Original Message -----
> From: "Richard Bennett" <ma...@ri...>
> To: <dyn...@li...>
> Sent: Sunday, February 11, 2001 3:16 PM
> Subject: Re: [Dynapi-Dev] All this "Konqueror" discussion...
>
>
> > Why doesn't anyone use the chat list for this kind of literary humor
> normal
> > souls don't understand ??
> > dyn...@li...
> >
> > ----- Original Message -----
> > From: "Pascal Bestebroer" <pa...@dy...>
> > To: <dyn...@li...>
> > Sent: Sunday, February 11, 2001 7:12 PM
> > Subject: RE: [Dynapi-Dev] All this "Konqueror" discussion...
> >
> >
> > > hmm.. I'm not sure what you mean with CREW!  please define this.
> > >
> > > Seeing as this should stay a fair war, if you can have a crew to
"throw
> > the
> > > rock"  then I can have a crew to uhm.."defend against the rock".
> > > Please note that we in Holland are some of the best damn dam
builders..
> > and
> > > your "The U.S.S ROCK!!" might be blown back by our wind-mills.. so
don't
> > > think you already came up with the best solution, because I haven't
seen
> > the
> > > U.S.S. ROCK as of yet!
> > >
> > > btw. Love the little yellow hat.. great cover-up! :)
> > >
> > > Pascal Bestebroer
> > > pa...@dy...
> > > http://www.dynamic-core.net
> > >
> > > > -----Oorspronkelijk bericht-----
> > > > Van: dyn...@li...
> > > > [mailto:dyn...@li...]Namens Raymond Smith
> > > > Verzonden: zaterdag 10 februari 2001 22:46
> > > > Aan: dyn...@li...
> > > > Onderwerp: [Dynapi-Dev] All this "Konqueror" discussion...
> > > >
> > > >
> > > > Mr. Pascal, sir...
> > > >
> > > > Much time has been spent, pondering...
> > > >
> > > > the "rock"!
> > > >
> > > > Transglobal warfare within the bounds and guidelines of the
> > > > "Primitive Arms
> > > > Law" required a great deal of thought on my part.
> > > >
> > > > 1)  It needed to be powerful, small rocks suck compared to boulders.
> > > > 2)  It needed to emulate the "throw of a rock".  This all began with
> > rock
> > > > throws to begin with.
> > > > 3)  Stealth in transit was critical.  Something that wouldn't raise
> > alarms
> > > > traveling through European streets and byways.
> > > > 4)  Construction was limited to slightly processed natural
> > > > resources, think
> > > > lumber and of course "rocks".
> > > > 5)  Amphibious capabilities became important later on to allow me to
> > > > maintain "stealth and illusion" to the point of final attack.
> > > > 6)  Finally the "crew", who to partner with in this attack that
> > > > would allow
> > > > me to best "blend" into the likely and probable surrounds where Mr.
> > > > Pascal,.. sir works.
> > > >
> > > > The best way to roll this strategy out is as follows...
> > > >
> > > > First I will present the "primary weapon" in full "stealth mode"
> > > > (reference
> > > > attached photo).
> > > >
> > > > Then over the next few days I will show Mr. Pascal how this
> > > > wonderous device
> > > > "unwraps" itself in stages as it crosses water onto land.
> > > >
> > > > The select "crew" that was assembled to help in this grand
endeavor...
> > > >
> > > >  Then sheads its "modern day trojan horse" disquise as it nears the
> > final
> > > > target...  :O)
> > > >
> > > > Introducing...
> > > >
> > > > The U.S.S ROCK!!
> > > >
> > > >
> > > >
> > >
> > >
> > > _______________________________________________
> > > Dynapi-Dev mailing list
> > > Dyn...@li...
> > > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> > > ____________________________________________________________
> > > Get your free domain name and domain-based e-mail from
> > > Namezero.com. New!  Namezero Plus domains now available.
> > > Find out more at: http://www.namezero.com
> > >
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> >
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> ____________________________________________________________
> Get your free domain name and domain-based e-mail from
> Namezero.com. New!  Namezero Plus domains now available.
> Find out more at: http://www.namezero.com
>

RE: [Dynapi-Dev] a couple of tools

[Darin K. <dka...@ef...>]

yeah, I used to show gdi,user and system values as percentages.  these are
actually win16 items.  in windows 9x, I was able to do some thunking to
continue displaying them, but in nt/2000, the api changed enough to make
this impractical.  what i use now is an api constuct termed MemoryStatus.
the "load" refers to memory load (!?), and the free mem refers to physical
memory that the os has not claimed.  This doesn't nescesarily mean the
memory is being used, just that windows is holding onto it for paging, etc..

if you go to the "details" view, you may get a clearer picture of what is
going on.  I haven't really used ME at all (i got totally off 9x august
1999) so I'm not sure what are normal values for you.  you should start to
get a feel for it after some use.  personally, with win2k, i have mine go
red at 95%, blink at 97 and not beep until 99.  when i hear a beep, i know
the system is hosed.  but usally at that point, my free mem has already
started to rapidly decrease.

happy coding!


-----Original Message-----
From: Richard Bennett
To: dyn...@li...
Sent: 2/11/01 3:29 PM
Subject: Re: [Dynapi-Dev] a couple of tools

I checked it out, and it certainly is unobtrusive! I couldn't find it at
first, and was wondering what the pinging was ;o)
It looks to be very handy, I was just wondering, it shows "load 89%" and
"free 5.14 MB" on win ME 128 ram pIII550 with only Outlook open. Do I
have some major trojans eating my resources?? Normally I can easily run
5 or 6 large programs  at the same time, so there should be more than
5mb ram free??
On the windows Resource Meter I get system 47% free, user 49% free, GDI
58% free.
Otherwise a very handy util.
 
Cheers,
Richard Bennett
 
ma...@ri... <mailto:ma...@ri...> 
www.richardinfo.com <http://www.richardinfo.com> 
(Everything running on, and ported to the 19/12/2000 snapshot of
DynAPI2)

----- Original Message ----- 
From: Darin  <mailto:dka...@ef...> Kadrioski 
To: 'dyn...@li...'
<mailto:'dyn...@li...'>  
Sent: Saturday, February 10, 2001 7:04 PM
Subject: RE: [Dynapi-Dev] a couple of tools

Windows users might find my resource monitor useful.
 
It's a small little window that sits in the corner of your screen
displaying the current system load and memory usage in realtime.  It has
an audible alert when you are near locking up.
 
It also includes a screen.magnifier which is helpful when building
widgets and aligning edges to pixel accuracy.
There is also a color matcher.  When engaged, move your mouse over the
screen.  The app will display the hex and RGB values of whatever your
cursor is over.
 
You can find it on my site at http://www.nebiru.com
<http://www.nebiru.com>  
click on downloads.
 
best of all, it's free!  :)

-----Original Message-----
From: Pascal Bestebroer [mailto:pa...@dy...]
Sent: Saturday, February 10, 2001 1:44 AM
To: dyn...@li...
Subject: RE: [Dynapi-Dev] a couple of tools


hmm, I can think of one :)
 
I'm currently working on Oversight, which will be a debugger and editor
in one.. you can still download an early debugger version
from my site : http://www.dynamic-core.net/
<http://www.dynamic-core.net/>   
 
I will hopefully be able to upload the latest code this weekend.. (the
editor part, and an updates debugger)
 

Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net <http://www.dynamic-core.net/>  

-----Oorspronkelijk bericht-----
Van: dyn...@li...
[mailto:dyn...@li...]Namens Monica Keefe
Verzonden: zaterdag 10 februari 2001 2:11
Aan: 'dyn...@li...'
Onderwerp: RE: [Dynapi-Dev] a couple of tools


Does anyone know of any debugging tools to use on the mac? 
Anything other than alert boxes would be very helpful :-)
 
Thanks!

-----Original Message-----
From: Doug Melvin [mailto:do...@cr...]
Sent: Friday, February 09, 2001 2:21 PM
To: dyn...@li...
Subject: [Dynapi-Dev] a couple of tools


I have found the following tools to be indeispensible when working with
(and debuggin) DynAPI
 
(WIN32 - sorry)
 
1) FreeMemPro
http://www.downloads.3bsoftware.com/Downloads/freemem/freemem.html
<http://www.downloads.3bsoftware.com/Downloads/freemem/freemem.html> 
 
    This is a ram 'defragmenter' for Window 32.. the way it works is it
allocates as much ram from windows as it can, which forces windows to
swap unused data from physical ram to swap space.
Then it releases this ram using proper memory management resulting in
more free ram.
It will keep doing this until it gets as close to the specified amount
of free ram as it can.
 
On my Win98 system which has 128 megs of ram, I ask it to free up 128
,egs and it gives me
80 to 100 megs free ram.. Which is damned handy when one has been
re-loading the same DynAPI app over and over again.. 
 
It's not a cure for memory leaks but it make development much easier,
and reduces crashes/reboots.
 
2) Taskinfo http://www.iarsn.com/download.html
<http://www.iarsn.com/download.html> 
    This program is for Window 9X and closly resembles the Task manager
in Windows 2000, with a little extra functionality.
 
You can find out how much ram and CPU time each process is using, what
files the process has open and much more.
 
In fact it was because of my constant observation of running processes
that I discovered last week that I had caught a trojan.. :-)
" what in the hell is this Wininit.exe?!? and hey! I've never seen
DNETC.exe before.. "
 
Just a couple of tools to hopefully make your life easier..
 
Later
Doug
 

---
Outgoing mail is certified Virus Free by AVG Free Edition
http://www.grisoft.com/html/us_index.cfm
<http://www.grisoft.com/html/us_index.cfm> 
Checked by AVG anti-virus system ( http://www.grisoft.com
<http://www.grisoft.com> ).
Version: 6.0.230 / Virus Database: 111 - Release Date: 1/25/01

Re: [Dynapi-Dev] All this "Konqueror" discussion...

[Raymond S. <dst...@or...>]

The value of  "exposure" Richard.

Plus the "rare" treat of actually being able to produce a smile on the
logic-etched face of a programmer.

But...

For your benefit (though I think later in life you will pay a greater price,
as will your humorless children) I'll at least title mark this brief series
with...

"rock" in it...



----- Original Message -----
From: "Richard Bennett" <ma...@ri...>
To: <dyn...@li...>
Sent: Sunday, February 11, 2001 3:16 PM
Subject: Re: [Dynapi-Dev] All this "Konqueror" discussion...


> Why doesn't anyone use the chat list for this kind of literary humor
normal
> souls don't understand ??
> dyn...@li...
>
> ----- Original Message -----
> From: "Pascal Bestebroer" <pa...@dy...>
> To: <dyn...@li...>
> Sent: Sunday, February 11, 2001 7:12 PM
> Subject: RE: [Dynapi-Dev] All this "Konqueror" discussion...
>
>
> > hmm.. I'm not sure what you mean with CREW!  please define this.
> >
> > Seeing as this should stay a fair war, if you can have a crew to "throw
> the
> > rock"  then I can have a crew to uhm.."defend against the rock".
> > Please note that we in Holland are some of the best damn dam builders..
> and
> > your "The U.S.S ROCK!!" might be blown back by our wind-mills.. so don't
> > think you already came up with the best solution, because I haven't seen
> the
> > U.S.S. ROCK as of yet!
> >
> > btw. Love the little yellow hat.. great cover-up! :)
> >
> > Pascal Bestebroer
> > pa...@dy...
> > http://www.dynamic-core.net
> >
> > > -----Oorspronkelijk bericht-----
> > > Van: dyn...@li...
> > > [mailto:dyn...@li...]Namens Raymond Smith
> > > Verzonden: zaterdag 10 februari 2001 22:46
> > > Aan: dyn...@li...
> > > Onderwerp: [Dynapi-Dev] All this "Konqueror" discussion...
> > >
> > >
> > > Mr. Pascal, sir...
> > >
> > > Much time has been spent, pondering...
> > >
> > > the "rock"!
> > >
> > > Transglobal warfare within the bounds and guidelines of the
> > > "Primitive Arms
> > > Law" required a great deal of thought on my part.
> > >
> > > 1)  It needed to be powerful, small rocks suck compared to boulders.
> > > 2)  It needed to emulate the "throw of a rock".  This all began with
> rock
> > > throws to begin with.
> > > 3)  Stealth in transit was critical.  Something that wouldn't raise
> alarms
> > > traveling through European streets and byways.
> > > 4)  Construction was limited to slightly processed natural
> > > resources, think
> > > lumber and of course "rocks".
> > > 5)  Amphibious capabilities became important later on to allow me to
> > > maintain "stealth and illusion" to the point of final attack.
> > > 6)  Finally the "crew", who to partner with in this attack that
> > > would allow
> > > me to best "blend" into the likely and probable surrounds where Mr.
> > > Pascal,.. sir works.
> > >
> > > The best way to roll this strategy out is as follows...
> > >
> > > First I will present the "primary weapon" in full "stealth mode"
> > > (reference
> > > attached photo).
> > >
> > > Then over the next few days I will show Mr. Pascal how this
> > > wonderous device
> > > "unwraps" itself in stages as it crosses water onto land.
> > >
> > > The select "crew" that was assembled to help in this grand endeavor...
> > >
> > >  Then sheads its "modern day trojan horse" disquise as it nears the
> final
> > > target...  :O)
> > >
> > > Introducing...
> > >
> > > The U.S.S ROCK!!
> > >
> > >
> > >
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> > ____________________________________________________________
> > Get your free domain name and domain-based e-mail from
> > Namezero.com. New!  Namezero Plus domains now available.
> > Find out more at: http://www.namezero.com
> >
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>

[Dynapi-Dev] Idea: expanding the dir-structure

[<ro...@gm...>]

Hi!

Just an Idea to split up the core-dynapi and all the extensions,=20
widgets... everybody is writing:

we should add a contrib directory to src/lib/dynapi where everybody can=20
add his own dir

so for example I would add my fixedanim.js extensions to=20
src/lib/dynapi/contrib/robelix/util/fixedanim.js

Why?

- the core should not be overloaded
- everybody can upload his stuff without conflicting the work of others
- future releases could easiely be split into core and contrib packages

What do you think?


Roland

P.S.
if you want to know what my fixedanim.js will be (not finished so far,=20
I guess in about a week)
It's for effects like those on my homepage:

http://www.robelix.com

(it's done with dynapi1 - but I'm going to upgrade soon)

Re: Re[2]: [Dynapi-Dev] buttons bug??

[labCoat <la...@xe...>]

Richard,

Thank you for the quick response...

But, what did you (and anyone who is reading) think about what I mentioned about needing to reverse the mouse (actually, just mouseover/mouseout seem to be different) events in NS4.

Robert?? Pascal???

> A lot of interesting points touched on there, some examples/code would be
> nice.

Yes, soon... I promise. I am just finishing commenting and documenting before hand.

> feel free to use this ftp to upload anything if you want

I will, but first, I need to get my example site up and running with all of he examples and docs.

Another thing that would be appriciated is that, once it is finished, if anyone that has the time can test the examples on different platforms/browsers.

--proteanman

Re: Re[2]: [Dynapi-Dev] buttons bug??

[Richard B. <ma...@ri...>]

A lot of interesting points touched on there, some examples/code would be
nice.
feel free to use this ftp to upload anything if you want:
ftp.dynapi.f2s.com
username: dynapi
pass: dynapi
port 21
url www.dynapi.f2s.com
PHP & CGI & mySql & SSI enabled

That goes for everybody.
I haven't had time to make an entrance page etc, anyone who wants to can
make one.

Cheers,
Richard Bennett

ma...@ri...
www.richardinfo.com
(Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2)

----- Original Message -----
From: "labCoat" <la...@xe...>
To: <dyn...@li...>
Sent: Monday, February 12, 2001 12:22 AM
Subject: Re: Re[2]: [Dynapi-Dev] buttons bug??


> Robert (and all),
>
> > I believe the right click context menu disabling
> > can be removed.  I don't see why it is needed.
> > Unless it kills the events, it should be
> > removed since it doesn't work cross-browser
> > anyways.
> > --
> > //Robert Rainwater
>
> Right-mouse click menu disablement can be cross-browser.
>
> As you might know, I have been working on fixing most of the existing
(known) bugs with the current release, as well as implementing the
DynaCore's DynObject, reorganizing package structure, and adding some extras
that I have noticed have been "lack-of feature" complaints in the past.
>
> One of the things that I have done is to make the right mouse event
disablment cross-browser (I have tested this on IE4+ & NS4+ on the Windows
OS), and made it optional. You can disable-enable the right menu, on the
fly.
>
>
> Anyway,
>
> I have a question about events/our EventMethod...
> (some of the below has been a reference from Scott Andrew's web site --
scottandrew.com -- in the Netscape 6 Events article)
>
> In Netscape 4, events will travel inward towards the target of the event.
> window --> document --> layer --> childlayer(target)
>
> In Internet Explorer, events travel outward towards the browser window.
> childlayer(target) --> layer --> document --> window
>
> In Netscape 6, events start at the window and travel to the target element
(event capture). But upon reaching the target, the event travels backward
the way it came, until it reaches the browser window again (event bubbling).
>
> window --> document -->layer --> childlayer(target) --> layer -->
document --> window
>
> So, I beleive (and I could be wrong, so please correct me if I am) the
model that we are wanting to use is the IE's target to document to window.
You might think that events are working in NS6 with the current release, but
they are not. Upon closer examination and testing with very extensive
examples, the events to not trigger correctly. Well, I have fixed the
event's in NS6 (the reason everything was happening more than once is the
fact that there is more than one event phase -- 3 actually). But the problem
is NS4's window to document to target. If we want the events to behave in
the same way cross-browser in very complex examples/widgets that uses
bubbling, than we need to reverse the way that NS4 captures events (like
IE's), and then use our own event bubbling method for the bubble (like in
IE).
>
> HERE IS THE QUESTION: ** What are thoughts on this? **
>
> I have been working on a method that will do this, but I am still ironing
out bugs.
>
>
> By the way,
>
> Part of my reorganization consisted of breaking away mouse events form the
events.js file, and making it a sperate "mouse.js" file.
> This way, you can still have create/delete/resize/etc... events get
triggered, but not have to worry about the weighing down the code/processor
with mouse events, if they are unecessary. (Plus, I saw this as being
consistant with some if the file structure now, ie. keyevets.js).
>
> Also, because it they are required by the DynAPI (dynapi.js), I have made
certain files (document.js, object.js, events.js) be automatically included
when you set the library path.
>
> PLEASE, anybody that has any thoughts on this, reply! :-)
>
> --proteanman
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> ____________________________________________________________
> Get your free domain name and domain-based e-mail from
> Namezero.com. New!  Namezero Plus domains now available.
> Find out more at: http://www.namezero.com
>

Re: [Dynapi-Dev] a couple of tools

[Richard B. <ma...@ri...>]

I checked it out, and it certainly is unobtrusive! I couldn't find it at =
first, and was wondering what the pinging was ;o)
It looks to be very handy, I was just wondering, it shows "load 89%" and =
"free 5.14 MB" on win ME 128 ram pIII550 with only Outlook open. Do I =
have some major trojans eating my resources?? Normally I can easily run =
5 or 6 large programs  at the same time, so there should be more than =
5mb ram free??
On the windows Resource Meter I get system 47% free, user 49% free, GDI =
58% free.
Otherwise a very handy util.

Cheers,
Richard Bennett

ma...@ri...
www.richardinfo.com
(Everything running on, and ported to the 19/12/2000 snapshot of =
DynAPI2)
  ----- Original Message -----=20
  From: Darin Kadrioski=20
  To: 'dyn...@li...'=20
  Sent: Saturday, February 10, 2001 7:04 PM
  Subject: RE: [Dynapi-Dev] a couple of tools


  Windows users might find my resource monitor useful.

  It's a small little window that sits in the corner of your screen =
displaying the current system load and memory usage in realtime.  It has =
an audible alert when you are near locking up.

  It also includes a screen.magnifier which is helpful when building =
widgets and aligning edges to pixel accuracy.
  There is also a color matcher.  When engaged, move your mouse over the =
screen.  The app will display the hex and RGB values of whatever your =
cursor is over.

  You can find it on my site at http://www.nebiru.com=20
  click on downloads.

  best of all, it's free!  :)
    -----Original Message-----
    From: Pascal Bestebroer [mailto:pa...@dy...]
    Sent: Saturday, February 10, 2001 1:44 AM
    To: dyn...@li...
    Subject: RE: [Dynapi-Dev] a couple of tools


    hmm, I can think of one :)

    I'm currently working on Oversight, which will be a debugger and =
editor in one.. you can still download an early debugger version
    from my site : http://www.dynamic-core.net/ =20

    I will hopefully be able to upload the latest code this weekend.. =
(the editor part, and an updates debugger)

    Pascal Bestebroer
    pa...@dy...
    http://www.dynamic-core.net=20

      -----Oorspronkelijk bericht-----
      Van: dyn...@li... =
[mailto:dyn...@li...]Namens Monica Keefe
      Verzonden: zaterdag 10 februari 2001 2:11
      Aan: 'dyn...@li...'
      Onderwerp: RE: [Dynapi-Dev] a couple of tools


      Does anyone know of any debugging tools to use on the mac?=20
      Anything other than alert boxes would be very helpful :-)

      Thanks!
        -----Original Message-----
        From: Doug Melvin [mailto:do...@cr...]
        Sent: Friday, February 09, 2001 2:21 PM
        To: dyn...@li...
        Subject: [Dynapi-Dev] a couple of tools


        I have found the following tools to be indeispensible when =
working with (and debuggin) DynAPI

        (WIN32 - sorry)

        1) FreeMemPro =
http://www.downloads.3bsoftware.com/Downloads/freemem/freemem.html

            This is a ram 'defragmenter' for Window 32.. the way it =
works is it allocates as much ram from windows as it can, which forces =
windows to swap unused data from physical ram to swap space.
        Then it releases this ram using proper memory management =
resulting in more free ram.
        It will keep doing this until it gets as close to the specified =
amount of free ram as it can.

        On my Win98 system which has 128 megs of ram, I ask it to free =
up 128 ,egs and it gives me
        80 to 100 megs free ram.. Which is damned handy when one has =
been re-loading the same DynAPI app over and over again..=20

        It's not a cure for memory leaks but it make development much =
easier, and reduces crashes/reboots.

        2) Taskinfo http://www.iarsn.com/download.html
            This program is for Window 9X and closly resembles the Task =
manager in Windows 2000, with a little extra functionality.

        You can find out how much ram and CPU time each process is =
using, what files the process has open and much more.

        In fact it was because of my constant observation of running =
processes that I discovered last week that I had caught a trojan.. :-)
        " what in the hell is this Wininit.exe?!? and hey! I've never =
seen DNETC.exe before.. "

        Just a couple of tools to hopefully make your life easier..

        Later
        Doug


        ---
        Outgoing mail is certified Virus Free by AVG Free Edition
        http://www.grisoft.com/html/us_index.cfm
        Checked by AVG anti-virus system (http://www.grisoft.com).
        Version: 6.0.230 / Virus Database: 111 - Release Date: 1/25/01

Re: Re[2]: [Dynapi-Dev] buttons bug??

[labCoat <la...@xe...>]

Robert (and all),

> I believe the right click context menu disabling 
> can be removed.  I don't see why it is needed.
> Unless it kills the events, it should be
> removed since it doesn't work cross-browser 
> anyways.  
> -- 
> //Robert Rainwater

Right-mouse click menu disablement can be cross-browser.

As you might know, I have been working on fixing most of the existing (known) bugs with the current release, as well as implementing the DynaCore's DynObject, reorganizing package structure, and adding some extras that I have noticed have been "lack-of feature" complaints in the past.

One of the things that I have done is to make the right mouse event disablment cross-browser (I have tested this on IE4+ & NS4+ on the Windows OS), and made it optional. You can disable-enable the right menu, on the fly.


Anyway,

I have a question about events/our EventMethod...
(some of the below has been a reference from Scott Andrew's web site -- scottandrew.com -- in the Netscape 6 Events article)

In Netscape 4, events will travel inward towards the target of the event.
window --> document --> layer --> childlayer(target)

In Internet Explorer, events travel outward towards the browser window.
childlayer(target) --> layer --> document --> window

In Netscape 6, events start at the window and travel to the target element (event capture). But upon reaching the target, the event travels backward the way it came, until it reaches the browser window again (event bubbling).

window --> document -->layer --> childlayer(target) --> layer --> document --> window

So, I beleive (and I could be wrong, so please correct me if I am) the model that we are wanting to use is the IE's target to document to window. You might think that events are working in NS6 with the current release, but they are not. Upon closer examination and testing with very extensive examples, the events to not trigger correctly. Well, I have fixed the event's in NS6 (the reason everything was happening more than once is the fact that there is more than one event phase -- 3 actually). But the problem is NS4's window to document to target. If we want the events to behave in the same way cross-browser in very complex examples/widgets that uses bubbling, than we need to reverse the way that NS4 captures events (like IE's), and then use our own event bubbling method for the bubble (like in IE).

HERE IS THE QUESTION: ** What are thoughts on this? **

I have been working on a method that will do this, but I am still ironing out bugs.


By the way, 

Part of my reorganization consisted of breaking away mouse events form the events.js file, and making it a sperate "mouse.js" file.
This way, you can still have create/delete/resize/etc... events get triggered, but not have to worry about the weighing down the code/processor with mouse events, if they are unecessary. (Plus, I saw this as being consistant with some if the file structure now, ie. keyevets.js).

Also, because it they are required by the DynAPI (dynapi.js), I have made certain files (document.js, object.js, events.js) be automatically included when you set the library path.

PLEASE, anybody that has any thoughts on this, reply! :-)

--proteanman

Re: [Dynapi-Dev] All this "Konqueror" discussion...

[Richard B. <ma...@ri...>]

Why doesn't anyone use the chat list for this kind of literary humor normal
souls don't understand ??
dyn...@li...

----- Original Message -----
From: "Pascal Bestebroer" <pa...@dy...>
To: <dyn...@li...>
Sent: Sunday, February 11, 2001 7:12 PM
Subject: RE: [Dynapi-Dev] All this "Konqueror" discussion...


> hmm.. I'm not sure what you mean with CREW!  please define this.
>
> Seeing as this should stay a fair war, if you can have a crew to "throw
the
> rock"  then I can have a crew to uhm.."defend against the rock".
> Please note that we in Holland are some of the best damn dam builders..
and
> your "The U.S.S ROCK!!" might be blown back by our wind-mills.. so don't
> think you already came up with the best solution, because I haven't seen
the
> U.S.S. ROCK as of yet!
>
> btw. Love the little yellow hat.. great cover-up! :)
>
> Pascal Bestebroer
> pa...@dy...
> http://www.dynamic-core.net
>
> > -----Oorspronkelijk bericht-----
> > Van: dyn...@li...
> > [mailto:dyn...@li...]Namens Raymond Smith
> > Verzonden: zaterdag 10 februari 2001 22:46
> > Aan: dyn...@li...
> > Onderwerp: [Dynapi-Dev] All this "Konqueror" discussion...
> >
> >
> > Mr. Pascal, sir...
> >
> > Much time has been spent, pondering...
> >
> > the "rock"!
> >
> > Transglobal warfare within the bounds and guidelines of the
> > "Primitive Arms
> > Law" required a great deal of thought on my part.
> >
> > 1)  It needed to be powerful, small rocks suck compared to boulders.
> > 2)  It needed to emulate the "throw of a rock".  This all began with
rock
> > throws to begin with.
> > 3)  Stealth in transit was critical.  Something that wouldn't raise
alarms
> > traveling through European streets and byways.
> > 4)  Construction was limited to slightly processed natural
> > resources, think
> > lumber and of course "rocks".
> > 5)  Amphibious capabilities became important later on to allow me to
> > maintain "stealth and illusion" to the point of final attack.
> > 6)  Finally the "crew", who to partner with in this attack that
> > would allow
> > me to best "blend" into the likely and probable surrounds where Mr.
> > Pascal,.. sir works.
> >
> > The best way to roll this strategy out is as follows...
> >
> > First I will present the "primary weapon" in full "stealth mode"
> > (reference
> > attached photo).
> >
> > Then over the next few days I will show Mr. Pascal how this
> > wonderous device
> > "unwraps" itself in stages as it crosses water onto land.
> >
> > The select "crew" that was assembled to help in this grand endeavor...
> >
> >  Then sheads its "modern day trojan horse" disquise as it nears the
final
> > target...  :O)
> >
> > Introducing...
> >
> > The U.S.S ROCK!!
> >
> >
> >
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> ____________________________________________________________
> Get your free domain name and domain-based e-mail from
> Namezero.com. New!  Namezero Plus domains now available.
> Find out more at: http://www.namezero.com
>

Re: [Dynapi-Dev] Oversight (was: a couple of tools)

[Richard B. <ma...@ri...>]

yes, this shows a lot of potential. Great job.
I wonder, are you planning on this being run from a webserver or on the
client machines?
As you mentioned, the style reflects Borland stuff, (with the floating
panels) which gives a very confusing effect over a desktop full of icons.
Maybe you can include a "hide desktop" function, opening a screensize layer
in relaxing gray, or even with a nice background image, now where could we
find a few nice backgrounds...

Cheers,
Richard Bennett

ma...@ri...
www.richardinfo.com
(Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2)

----- Original Message -----
From: "Pascal Bestebroer" <pa...@dy...>
To: <dyn...@li...>
Sent: Sunday, February 11, 2001 1:35 PM
Subject: RE: [Dynapi-Dev] Oversight (was: a couple of tools)


> Well, here goes.
>
> Just uploaded a pre-beta (read : buggy) version of my current code,
> you can download it here:
http://www.dynamic-core.net/oversight-prebeta.zip
>
> WARNING:  I only tested so far on IE5 and NS4 (previous code also worked
on
> IE4), this
> version if VERY BETA, so please don't start mailing me with bug-reports,
I'm
> very aware of them
> and they will eventually get fixed.
>
> I AM interested in any opinions, ideas and other notes, so please let me
> know.
>
> The zip file contains a Dynacore version aswell, but I tested the
Oversight
> code and it works
> with the latest snapshot (probably not with the release).  Open the
> Oversight.htm file in the
> root of the zip, and that should lead you thru it.
>
> One big-bug that I will try to fix, is in the DynAPI.. Try adding a layer,
> and then a child-layer.. then
> reset the html content :-)   I think this is fixable by modifying the
> setHTML in the DynAPI (simply remove all layers, change HTML, and re-add
> them) so I'll try to fix it, and patch it into CVS.
>
> The scripter is also working nicely.. so take a look at it :)
>
> Pascal Bestebroer
> pa...@dy...
> http://www.dynamic-core.net
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> ____________________________________________________________
> Get your free domain name and domain-based e-mail from
> Namezero.com. New!  Namezero Plus domains now available.
> Find out more at: http://www.namezero.com
>

Re: [Dynapi-Dev] DynAPI resizeHandler

[Michael P. <mp...@ph...>]

it is better to do it using resize handlers.  this way, you can use a single
handler to deal with the resize event on frames other than the one that
contains the main api code.

Darin Kadrioski wrote:

>
> have I been wrong in just doing it like this?
>
> DynAPI.onResize=function(){WebBrowser1.moveToImage('browserImage')}
>
> what would be the consequences?
>
> -----Original Message-----
> From: Michael Pemberton
> To: dyn...@li...
> Sent: 2/11/01 2:20 PM
> Subject: Re: [Dynapi-Dev] DynAPI resizeHandler
>
> I think that your changes should be added to the API by one of the
> admins.  I'm
> surprised no one has mentioned of it earlier. : )
>
> David Holbrook wrote:
>
> > I have been trying to make a Layer that would resize as the browser
> window
> > resizes...  I tried something like this without much luck:
> >
> > DynAPI.onLoad = function() {
> >
> >    var pad = 10;
> >
> >  myLayer = new DynLayer();
> >
> >
> myLayer.setSize(DynAPI.document.getWidth()-(pad*2),DynAPI.document.getHe
> ight
> > ()-(pad*2));
> >  myLayer.setBgColor('#c0c0c0');
> >  myLayer.moveTo(pad,pad);
> >
> >  rszLstn=new EventListener(myLayer);
> >   rszLstn.onresize=function(e) {
> >          target = e.getTarget();
> >
> >
> target.setSize(target.parent.getWidth()-(pad*2),target.parent.getHeight(
> )-(p
> > ad*2));
> >       }
> >  DynAPI.document.addEventListener(rszLstn);
> >
> >  DynAPI.document.addChild(myLayer);
> >
> > }
> >
> > It didn't seem that there was a resize event in the document...  I
> took a
> > look at the resizeHandler and also the loadHandler and noticed the
> load
> > handler was invoking a beforeload, load, and afterload event.  I
> borrowed
> > the event code from the loadHandler and add this line to the
> resizeHandler:
> >
> > if (DynAPI.document.invokeEvent)
> DynAPI.document.invokeEvent('resize');
> >
> > ..and my code worked like I expected it to.
> >
> > I have two questions.
> > 1)  What would be the "normal" way of doing this without modifying the
> > DynAPI.
> > 2)  Should the resize event be added to the resize handler for
> convenience
> > and consistency.
> >
> > Thanks
> > Dave Holbrook
> > dav...@ho...
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

--
Michael Pemberton
mp...@ph...
ICQ: 12107010

RE: [Dynapi-Dev] DynAPI resizeHandler

[Darin K. <dka...@ef...>]

 
have I been wrong in just doing it like this?

DynAPI.onResize=function(){WebBrowser1.moveToImage('browserImage')}

what would be the consequences?

-----Original Message-----
From: Michael Pemberton
To: dyn...@li...
Sent: 2/11/01 2:20 PM
Subject: Re: [Dynapi-Dev] DynAPI resizeHandler

I think that your changes should be added to the API by one of the
admins.  I'm
surprised no one has mentioned of it earlier. : )

David Holbrook wrote:

> I have been trying to make a Layer that would resize as the browser
window
> resizes...  I tried something like this without much luck:
>
> DynAPI.onLoad = function() {
>
>    var pad = 10;
>
>  myLayer = new DynLayer();
>
>
myLayer.setSize(DynAPI.document.getWidth()-(pad*2),DynAPI.document.getHe
ight
> ()-(pad*2));
>  myLayer.setBgColor('#c0c0c0');
>  myLayer.moveTo(pad,pad);
>
>  rszLstn=new EventListener(myLayer);
>   rszLstn.onresize=function(e) {
>          target = e.getTarget();
>
>
target.setSize(target.parent.getWidth()-(pad*2),target.parent.getHeight(
)-(p
> ad*2));
>       }
>  DynAPI.document.addEventListener(rszLstn);
>
>  DynAPI.document.addChild(myLayer);
>
> }
>
> It didn't seem that there was a resize event in the document...  I
took a
> look at the resizeHandler and also the loadHandler and noticed the
load
> handler was invoking a beforeload, load, and afterload event.  I
borrowed
> the event code from the loadHandler and add this line to the
resizeHandler:
>
> if (DynAPI.document.invokeEvent)
DynAPI.document.invokeEvent('resize');
>
> ..and my code worked like I expected it to.
>
> I have two questions.
> 1)  What would be the "normal" way of doing this without modifying the
> DynAPI.
> 2)  Should the resize event be added to the resize handler for
convenience
> and consistency.
>
> Thanks
> Dave Holbrook
> dav...@ho...
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev



_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Re: [Dynapi-Dev] DynAPI resizeHandler

[Michael P. <mp...@ph...>]

I think that your changes should be added to the API by one of the admins.  I'm
surprised no one has mentioned of it earlier. : )

David Holbrook wrote:

> I have been trying to make a Layer that would resize as the browser window
> resizes...  I tried something like this without much luck:
>
> DynAPI.onLoad = function() {
>
>    var pad = 10;
>
>  myLayer = new DynLayer();
>
> myLayer.setSize(DynAPI.document.getWidth()-(pad*2),DynAPI.document.getHeight
> ()-(pad*2));
>  myLayer.setBgColor('#c0c0c0');
>  myLayer.moveTo(pad,pad);
>
>  rszLstn=new EventListener(myLayer);
>   rszLstn.onresize=function(e) {
>          target = e.getTarget();
>
> target.setSize(target.parent.getWidth()-(pad*2),target.parent.getHeight()-(p
> ad*2));
>       }
>  DynAPI.document.addEventListener(rszLstn);
>
>  DynAPI.document.addChild(myLayer);
>
> }
>
> It didn't seem that there was a resize event in the document...  I took a
> look at the resizeHandler and also the loadHandler and noticed the load
> handler was invoking a beforeload, load, and afterload event.  I borrowed
> the event code from the loadHandler and add this line to the resizeHandler:
>
> if (DynAPI.document.invokeEvent) DynAPI.document.invokeEvent('resize');
>
> ..and my code worked like I expected it to.
>
> I have two questions.
> 1)  What would be the "normal" way of doing this without modifying the
> DynAPI.
> 2)  Should the resize event be added to the resize handler for convenience
> and consistency.
>
> Thanks
> Dave Holbrook
> dav...@ho...
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Re[2]: [Dynapi-Dev] buttons bug??

[Robert R. <rra...@ya...>]

I believe the right click context menu disabling can be removed.  I
don't see why it is needed.  Unless it kills the events, it should be
removed since it doesn't work cross-browser anyways.  I though this
was removed a few weeks back but it must not have.

-- 
// Robert Rainwater

On 2/11/2001, 11:02:33 AM EST, Glen wrote about "[Dynapi-Dev] buttons bug??":

> I can answer some of this. "Dynapi.gui.loadpanel-file1" and "dynapi.gui.loadpanel-file2", are part of the dynapi.gui.loadpanel.  They are the files that get loaded.  ;-)

> The right click context menu is disabled so the right click can be captured for other events.  Right click on the square in examples/dynapi.api.mouseevents.htm :-) 
> http://sandymermaid.com/examples/dynapi.api.mouseevents.htm
> It can be changed in the events js in the api folder.

> The buttons stay on if you release outside the button area, because the event is fired onmouseup.  You can add an onmouseup eventListener to the document, if you want, to get the affect you want.

> Please read the faq at
> http://sourceforge.net/docman/display_doc.php?docid=656&group_id=5757

> Glen
>   ----- Original Message ----- 
>   From: Roberto Peña 
>   To: dyn...@li... 
>   Sent: Sunday, February 11, 2001 12:52 PM
>   Subject: [Dynapi-Dev] buttons bug??


>   hey you've done a great work!!

>   maybe I just have not read enough but I think you haven't noticed that buttons may get stuck if you click on them, hold and release outside the button; if you do this the button gets stuck and
> follows the mousepointer when you move it (on scrollbars) or stays pressed (on regular buttons).
>   as I told you I haven't read all your manual, I found it yesterday; so I don't know if its really a bug on your code, I think you did this because of the mousepointer events, you can not see the
> pop up menu when you rightclick on some pages from the examples.
>   and you've got 2 files in your examples which are nothing: "dynapi.gui.loadpanel-file1" and "dynapi.gui.loadpanel-file2"

>   I've just downloded your:
>   Version 2001.01.25

>   I'd like you to write back, just send a "keep on reading!!" if I'm wrong or "ok" if I'm right



----------------------
DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
DynAPI Homepage: http://dynapi.sourceforge.net/

[Dynapi-Dev] DynAPI resizeHandler

[David H. <dav...@ho...>]

I have been trying to make a Layer that would resize as the browser window
resizes...  I tried something like this without much luck:

DynAPI.onLoad = function() {

   var pad = 10;

 myLayer = new DynLayer();

myLayer.setSize(DynAPI.document.getWidth()-(pad*2),DynAPI.document.getHeight
()-(pad*2));
 myLayer.setBgColor('#c0c0c0');
 myLayer.moveTo(pad,pad);

 rszLstn=new EventListener(myLayer);
  rszLstn.onresize=function(e) {
         target = e.getTarget();

target.setSize(target.parent.getWidth()-(pad*2),target.parent.getHeight()-(p
ad*2));
      }
 DynAPI.document.addEventListener(rszLstn);

 DynAPI.document.addChild(myLayer);

}

It didn't seem that there was a resize event in the document...  I took a
look at the resizeHandler and also the loadHandler and noticed the load
handler was invoking a beforeload, load, and afterload event.  I borrowed
the event code from the loadHandler and add this line to the resizeHandler:

if (DynAPI.document.invokeEvent) DynAPI.document.invokeEvent('resize');

...and my code worked like I expected it to.

I have two questions.
1)  What would be the "normal" way of doing this without modifying the
DynAPI.
2)  Should the resize event be added to the resize handler for convenience
and consistency.

Thanks
Dave Holbrook
dav...@ho...

Re: [Dynapi-Dev] buttons bug??

[Glen D. <gle...@gt...>]

I can answer some of this. "Dynapi.gui.loadpanel-file1" and =
"dynapi.gui.loadpanel-file2", are part of the dynapi.gui.loadpanel.  =
They are the files that get loaded.  ;-)

The right click context menu is disabled so the right click can be =
captured for other events.  Right click on the square in =
examples/dynapi.api.mouseevents.htm :-)=20
http://sandymermaid.com/examples/dynapi.api.mouseevents.htm
It can be changed in the events js in the api folder.

The buttons stay on if you release outside the button area, because the =
event is fired onmouseup.  You can add an onmouseup eventListener to the =
document, if you want, to get the affect you want.

Please read the faq at
http://sourceforge.net/docman/display_doc.php?docid=3D656&group_id=3D5757=


Glen
  ----- Original Message -----=20
  From: Roberto Pe=F1a=20
  To: dyn...@li...=20
  Sent: Sunday, February 11, 2001 12:52 PM
  Subject: [Dynapi-Dev] buttons bug??


  hey you've done a great work!!

  maybe I just have not read enough but I think you haven't noticed that =
buttons may get stuck if you click on them, hold and release outside the =
button; if you do this the button gets stuck and follows the =
mousepointer when you move it (on scrollbars) or stays pressed (on =
regular buttons).
  as I told you I haven't read all your manual, I found it yesterday; so =
I don't know if its really a bug on your code, I think you did this =
because of the mousepointer events, you can not see the pop up menu when =
you rightclick on some pages from the examples.
  and you've got 2 files in your examples which are nothing: =
"dynapi.gui.loadpanel-file1" and "dynapi.gui.loadpanel-file2"

  I've just downloded your:
  Version 2001.01.25

  I'd like you to write back, just send a "keep on reading!!" if I'm =
wrong or "ok" if I'm right

RE: [Dynapi-Dev] All this "Konqueror" discussion...

[Pascal B. <pa...@dy...>]

hmm.. I'm not sure what you mean with CREW!  please define this.

Seeing as this should stay a fair war, if you can have a crew to "throw the
rock"  then I can have a crew to uhm.."defend against the rock".
Please note that we in Holland are some of the best damn dam builders.. and
your "The U.S.S ROCK!!" might be blown back by our wind-mills.. so don't
think you already came up with the best solution, because I haven't seen the
U.S.S. ROCK as of yet!

btw. Love the little yellow hat.. great cover-up! :)

Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Raymond Smith
> Verzonden: zaterdag 10 februari 2001 22:46
> Aan: dyn...@li...
> Onderwerp: [Dynapi-Dev] All this "Konqueror" discussion...
>
>
> Mr. Pascal, sir...
>
> Much time has been spent, pondering...
>
> the "rock"!
>
> Transglobal warfare within the bounds and guidelines of the
> "Primitive Arms
> Law" required a great deal of thought on my part.
>
> 1)  It needed to be powerful, small rocks suck compared to boulders.
> 2)  It needed to emulate the "throw of a rock".  This all began with rock
> throws to begin with.
> 3)  Stealth in transit was critical.  Something that wouldn't raise alarms
> traveling through European streets and byways.
> 4)  Construction was limited to slightly processed natural
> resources, think
> lumber and of course "rocks".
> 5)  Amphibious capabilities became important later on to allow me to
> maintain "stealth and illusion" to the point of final attack.
> 6)  Finally the "crew", who to partner with in this attack that
> would allow
> me to best "blend" into the likely and probable surrounds where Mr.
> Pascal,.. sir works.
>
> The best way to roll this strategy out is as follows...
>
> First I will present the "primary weapon" in full "stealth mode"
> (reference
> attached photo).
>
> Then over the next few days I will show Mr. Pascal how this
> wonderous device
> "unwraps" itself in stages as it crosses water onto land.
>
> The select "crew" that was assembled to help in this grand endeavor...
>
>  Then sheads its "modern day trojan horse" disquise as it nears the final
> target...  :O)
>
> Introducing...
>
> The U.S.S ROCK!!
>
>
>

RE: [Dynapi-Dev] buttons bug??

[Pascal B. <pa...@dy...>]

make sure to read the f.a.q.

Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net

  -----Oorspronkelijk bericht-----
  Van: dyn...@li...
[mailto:dyn...@li...]Namens Roberto Peña
  Verzonden: zondag 11 februari 2001 18:52
  Aan: dyn...@li...
  Onderwerp: [Dynapi-Dev] buttons bug??


  hey you've done a great work!!

  maybe I just have not read enough but I think you haven't noticed that
buttons may get stuck if you click on them, hold and release outside the
button; if you do this the button gets stuck and follows the mousepointer
when you move it (on scrollbars) or stays pressed (on regular buttons).
  as I told you I haven't read all your manual, I found it yesterday; so I
don't know if its really a bug on your code, I think you did this because of
the mousepointer events, you can not see the pop up menu when you rightclick
on some pages from the examples.
  and you've got 2 files in your examples which are nothing:
"dynapi.gui.loadpanel-file1" and "dynapi.gui.loadpanel-file2"

  I've just downloded your:
  Version 2001.01.25

  I'd like you to write back, just send a "keep on reading!!" if I'm wrong
or "ok" if I'm right

[Dynapi-Dev] buttons bug??

[<Rob...@te...>]

hey you've done a great work!!

maybe I just have not read enough but I think you haven't noticed that =
buttons may get stuck if you click on them, hold and release outside the =
button; if you do this the button gets stuck and follows the =
mousepointer when you move it (on scrollbars) or stays pressed (on =
regular buttons).
as I told you I haven't read all your manual, I found it yesterday; so I =
don't know if its really a bug on your code, I think you did this =
because of the mousepointer events, you can not see the pop up menu when =
you rightclick on some pages from the examples.
and you've got 2 files in your examples which are nothing: =
"dynapi.gui.loadpanel-file1" and "dynapi.gui.loadpanel-file2"

I've just downloded your:
Version 2001.01.25

I'd like you to write back, just send a "keep on reading!!" if I'm wrong =
or "ok" if I'm right

RE: [Dynapi-Dev] Oversight (was: a couple of tools)

[Pascal B. <pa...@dy...>]

Well, here goes.

Just uploaded a pre-beta (read : buggy) version of my current code,
you can download it here:  http://www.dynamic-core.net/oversight-prebeta.zip

WARNING:  I only tested so far on IE5 and NS4 (previous code also worked on
IE4), this
version if VERY BETA, so please don't start mailing me with bug-reports, I'm
very aware of them
and they will eventually get fixed.

I AM interested in any opinions, ideas and other notes, so please let me
know.

The zip file contains a Dynacore version aswell, but I tested the Oversight
code and it works
with the latest snapshot (probably not with the release).  Open the
Oversight.htm file in the
root of the zip, and that should lead you thru it.

One big-bug that I will try to fix, is in the DynAPI.. Try adding a layer,
and then a child-layer.. then
reset the html content :-)   I think this is fixable by modifying the
setHTML in the DynAPI (simply remove all layers, change HTML, and re-add
them) so I'll try to fix it, and patch it into CVS.

The scripter is also working nicely.. so take a look at it :)

Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net

RE: [Dynapi-Dev] Oversight (was: a couple of tools)

[Pascal B. <pa...@dy...>]

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
pa...@dy...
http://www.dynamic-core.net

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Darin Kadrioski
> Verzonden: zondag 11 februari 2001 5:29
> Aan: 'dyn...@li... '
> 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: dyn...@li...
> 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: dyn...@li...
> [mailto:dyn...@li...]On Behalf Of Pascal
> Bestebroer
> Sent: Saturday, February 10, 2001 1:19 PM
> To: dyn...@li...
> 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
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>