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

RE: [Dynapi-Dev] new web release using DynAPI2 - have a look

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

Truly impressed...

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

  -----Oorspronkelijk bericht-----
  Van: dyn...@li...
[mailto:dyn...@li...]Namens NaCHo RaPaLLo
  Verzonden: vrijdag 17 november 2000 14:27
  Aan: dyn...@li...
  Onderwerp: [Dynapi-Dev] new web release using DynAPI2 - have a look


  Hy guys.

  Having started with the old, great DynApi of Dan Steinman, this summer we
realized your new Dynapi was evolving. Since then we begun developing this
project following the new realeases of your DynAPI2, always checking both
distributions - the official at sourceforge and the 'personalized' of
Pascal -

  The result of this is shown to full effect in a new web site that went
on-line yesterday. Check it out: www.zara.com

  With this we would like to thank you for all your efforts, because we
definetly acknowledge this project is also YOURS.

  4 your interest:
      we used 00.10.30 Pascal's version of DynAPI2
      we mixed DHTML & Flash technologies

  lo dicho, gracias a todos
      nacho - na...@do...

  ciao
      filippo - fi...@do...

  ta agin mates
      richard  - ri...@do...

  muchísimas gracias, como siempre
      fran -  jf...@do...

  graciñas
      bea  - be...@do...

  and all the www.doubleyou.com team

Re: [Dynapi-Dev] new web release using DynAPI2 - have a look

[Phil C. <phi...@ya...>]

Yes it does.. that is great.. You are my hero!

pHil


--- Scott Andrew LePera <sc...@sc...> wrote:
> What can I say other than...WOW!  That rules!
> 
> http://www.zara.com/
> 
> 
> > NaCHo RaPaLLo wrote:
> > 
> > Hy guys.
> > 
> > Having started with the old, great DynApi of Dan
> Steinman, this summer
> > we realized your new Dynapi was evolving. Since
> then we begun
> > developing this project following the new
> realeases of your DynAPI2,
> > always checking both distributions - the official
> at sourceforge and
> > the 'personalized' of Pascal -
> > 
> > The result of this is shown to full effect in a
> new web site that
> > went on-line yesterday. Check it out: www.zara.com
> > 
> > With this we would like to thank you for all your
> efforts, because we
> > definetly acknowledge this project is also YOURS.
> > 
> > 4 your interest:
> >     we used 00.10.30 Pascal's version of DynAPI2
> >     we mixed DHTML & Flash technologies
> > 
> > lo dicho, gracias a todos
> >     nacho - na...@do...
> > 
> > ciao
> >     filippo - fi...@do...
> > 
> > ta agin mates
> >     richard  - ri...@do...
> > 
> > muchísimas gracias, como siempre
> >     fran -  jf...@do...
> > 
> > graciñas
> >     bea  - be...@do...
> > 
> > and all the www.doubleyou.com team
> > 
> 
> -- 
> scott andrew lepera
> -----------------------------------
> web stuff:     www.scottandrew.com
> music stuff:   www.walkingbirds.com
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://lists.sourceforge.net/mailman/listinfo/dynapi-dev


__________________________________________________
Do You Yahoo!?
Yahoo! Calendar - Get organized for the holidays!
http://calendar.yahoo.com/

Re: [Dynapi-Dev] new web release using DynAPI2 - have a look

[Scott A. L. <sc...@sc...>]

What can I say other than...WOW!  That rules!

http://www.zara.com/


> NaCHo RaPaLLo wrote:
> 
> Hy guys.
> 
> Having started with the old, great DynApi of Dan Steinman, this summer
> we realized your new Dynapi was evolving. Since then we begun
> developing this project following the new realeases of your DynAPI2,
> always checking both distributions - the official at sourceforge and
> the 'personalized' of Pascal -
> 
> The result of this is shown to full effect in a new web site that
> went on-line yesterday. Check it out: www.zara.com
> 
> With this we would like to thank you for all your efforts, because we
> definetly acknowledge this project is also YOURS.
> 
> 4 your interest:
>     we used 00.10.30 Pascal's version of DynAPI2
>     we mixed DHTML & Flash technologies
> 
> lo dicho, gracias a todos
>     nacho - na...@do...
> 
> ciao
>     filippo - fi...@do...
> 
> ta agin mates
>     richard  - ri...@do...
> 
> muchísimas gracias, como siempre
>     fran -  jf...@do...
> 
> graciñas
>     bea  - be...@do...
> 
> and all the www.doubleyou.com team
> 

-- 
scott andrew lepera
-----------------------------------
web stuff:     www.scottandrew.com
music stuff:   www.walkingbirds.com

[Dynapi-Dev] DynLayer.pad

[Simon D. M. <di...@bi...>]

May I suggest you drop the .pad property from DynLayer

NS4's LAYER element has no native .padding property
so setting a property does nothing

thus a DynLayer's padding is not cross-browser

If padding is needed, we can use the Label widget.

The code using .pad could be removed from api/dynlayer.js
along with the setPadding and getPadding methods in
ext/layer.js

Best, SD

Re: [Dynapi-Dev] A small patch for Dan's label and a question about DynLayer.Event Method

[Dan S. <dy...@fu...>]

> I ran into trouble when I tried to bring cancelBrowserEvent() to IE 5. I
> followed the debugger into DynLayer.EventMethod, after I clicked on a Label.
> The e.srcElement is the <FONT>, instead of the <DIV> label layer, and the
> events are ignored for the label. Is there any work-around for IE 5 in this
> case?


My first guess would be event bubbling.  Somehow that event is not bubbling to the DIV element, rather getting stopped as soon as it's fired.  Check in the label code that the event listener for stopping the selection DOES NOT have the "setBubble()" call, rather uses cancelBrowserEvent() - this may/should fix the problem.

Dan

[Dynapi-Dev] Layer image map

[Barre B. <ba...@ho...>]

Hey..

I dug up the code for creating imagemaps outof layers.
Now this addon to dynapi1 is pretty strightforward. ( hmm 
well, not really as I'm using a modified version of 
dynapi1.. but this code should work )
Had to do it in like a couple of hours, so I just hacked it 
quickly. Not my proudest programming effort :) Oh, and it 
only supports rectangular areas.

But the idea is valid, i.e. the whole layer is treated as a 
map and you set areas that correspond to mouseevents(just 
like in an imagemap), which are enabled by tracking the 
mouse coords and comparing them against the areas set. Or 
something to that effect....

-------------------
example of use:
----------------------

window.onload = function(){
  crap = new DynLayer("crapID")			
  crap.setMap(0,0,33,16) // righttop corner, bottom left 
corner
  crap.setMapEvents("www.theurl.com","onmouseClickFunc
()","onmouseOverFunc()","onmouseOutFunc()")
  crap.show_msXY = true // shows coordinates so you can set 
the map		
}

--------------------
the library addons:
----------------------

function setBoxMap(topX,topY,bottomX,bottomY){
	this.show_msXY = false //
	if(typeof this.map_i == "undefined"){
		this.map_overi = this.MSOUT = false
		this.map_i = 0
		
		this.mapTX = new Array()
		this.mapTY = new Array()
		this.mapBX = new Array()
		this.mapBY = new Array()
		this.map_msdown = new Array()
		this.map_msover = new Array()
		this.map_msout = new Array()
		this.map_url = new Array()
		
		if(is.NS) this.elm.captureEvents
(Event.MOUSEMOVE|Event.MOUSEDOWN)
		this.elm.onmousemove = BoxMap_msOver
		this.elm.onmousedown = BoxMap_msDown
		//this.elm.onmouseout = BoxMap_msOut
		this.elm.box = this		
	} else
		 this.map_i++
		 
	
	this.mapTX[this.map_i] = topX
	this.mapTY[this.map_i] = topY
	this.mapBX[this.map_i] = bottomX 
	this.mapBY[this.map_i] = bottomY	
	this.map_msdown[this.map_i] = ""
	this.map_msover[this.map_i] = ""
	this.map_msout[this.map_i] = ""
	this.map_url[this.map_i] = ""
	
}
DynLayer.prototype.setMap = setBoxMap

function setBoxMapEvents(url,msdown,msover,msout){
	this.map_url[this.map_i] = url
	this.map_msdown[this.map_i] = msdown
	this.map_msover[this.map_i] = msover
	this.map_msout[this.map_i] = msout
}
DynLayer.prototype.setMapEvents = setBoxMapEvents

function BoxMap_msDown(e){
	var y = (is.NS)? e.layerY:event.offsetY
	var x = (is.NS)? e.layerX:event.offsetX	
	for(var i=0; i <= this.box.map_i; i++) {
		if( (y >= this.box.mapTY[i]) && (x >= 
this.box.mapTX[i]) && (y <= this.box.mapBY[i]) && (x <= 
this.box.mapBX[i]) ){
			if(this.box.map_msdown[i]) eval
(this.box.map_msdown[i])
			if(this.box.map_url[i]) eval
(this.box.map_url[i])					
					
		}	
	}	
}
function BoxMap_msOver(e){	
	var y = (is.NS)? e.layerY:event.offsetY
	var x = (is.NS)? e.layerX:event.offsetX	
	if(this.box.show_msXY) status = x +" " +y
	for(var i=0; i <= this.box.map_i; i++) {	
		
		if( (y >= this.box.mapTY[i]) && (x >= 
this.box.mapTX[i]) && (y <= this.box.mapBY[i]) && (x <= 
this.box.mapBX[i]) ){
			if(i == this.box.map_overi) return 
false;
			if(this.box.map_msover[i]) eval
(this.box.map_msover[i])				
		
			this.box.map_overi = i
			this.box.MSOUT = false
			break;
		} else this.box.MSOUT = true		
	
	}	
	if(!isNaN(this.box.map_overi) && this.box.MSOUT){
		eval(this.box.map_msout[this.box.map_overi])
	
		this.box.map_overi = null		
		
	}
	return true;
}

[Dynapi-Dev] A small patch for Dan's label and a question about DynLayer.Event Method

[Guangyi Wu <gua...@al...>]

Hi,

I overloaded the setWidth for Label for NN4, because rerending (setText())
is neccessary for browser not supporting DOM. And the rerending should be
before the invokeEvent('resize'), it is hard to call the
DynLayer.setWidth().

Another change is the point size, as I posted last time.

I ran into trouble when I tried to bring cancelBrowserEvent() to IE 5. I
followed the debugger into DynLayer.EventMethod, after I clicked on a Label.
The e.srcElement is the <FONT>, instead of the <DIV> label layer, and the
events are ignored for the label. Is there any work-around for IE 5 in this
case?

br
George


 <<label.js>> 

[Dynapi-Dev] new web release using DynAPI2 - have a look

[NaCHo R. <na...@do...>]

Hy guys.

Having started with the old, great DynApi of Dan Steinman, this summer we
realized your new Dynapi was evolving. Since then we begun developing this
project following the new realeases of your DynAPI2, always checking both
distributions - the official at sourceforge and the 'personalized' of
Pascal -

The result of this is shown to full effect in a new web site that went
on-line yesterday. Check it out: www.zara.com

With this we would like to thank you for all your efforts, because we
definetly acknowledge this project is also YOURS.

4 your interest:
    we used 00.10.30 Pascal's version of DynAPI2
    we mixed DHTML & Flash technologies

lo dicho, gracias a todos
    nacho - na...@do...

ciao
    filippo - fi...@do...

ta agin mates
    richard  - ri...@do...

muchísimas gracias, como siempre
    fran -  jf...@do...

graciñas
    bea  - be...@do...

and all the www.doubleyou.com team

AW: Re[3]: [Dynapi-Dev] Default

[Stephan R. <SR...@la...>]

Alas we don't have a preprocessor, but not use a construct like this (which
u can find in almost every C or C++ source):

#ifndef __DIRECTRY_H
#include "directry.h"
#endif

public vars should be ok in JS.

Stephan

>
>
>
> Of course you'd need to keep a running list of all the files that had
> already been loaded are not loaded again.  Otherwise, you could
> be making a
> lot of useless trips to the server :)
>
>
>
> You could have a DynAPI.require method that will add required files.
> Then when the first file is included, it will include all of the
> required files.  I've done something similar to this before and it
> worked quite easily.  Also, this allows you to set the required files
> in the widgets.  That way if someone wanted to use the button widget,
> the only file that have to include is the button.js file and all of
> the others would automatically be included.
>
>
> > I think the DynAPi is already very modular, you don't need to use events
> or
> > dragging objects.
> > The only problem we're having is that you need to include
> dyndocument and
> > dynlayer, because dynlayers can only be added to dyndocuments.. but the
> rest
> > isn't that bad is it?
> >
> > Brandon, care to share your ideas ?
> >

Re[5]: [Dynapi-Dev] Default

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

Yep, there's already a patch at sourceforge that does this with the
include method, but unless we would actually use requires in the
widgets, we don't really need it.


\\Robert
-- 
rra...@ya...

Re: Re[3]: [Dynapi-Dev] Default

[Brandon M. <tr...@us...>]

Although that's a novel idea, it would require a "standard" in writing
widgets, which we all know, has created a long standing problem in that:
 - one side says development should be free-form. No rules to develop the
app.
 - the other says that there should be standards so that widgets work
together with little to no changes in code.

Well... I say just leave things the way they are. don't bother creating a
require, as it would require that all scripts that are included within the
'include' method notify the API that it has completed loading. Only IE5+ can
truely detect successful completion of an external script.

I say keep the list of "include" statements at the top for every required
file. It allows a user viewing an application for the first time to know
exactly everything that is needed to run the app. This shouldn't be C++
include within include within include.... simple one-pass include should
suffice.

----- Original Message -----
From: "Robert Rainwater" <rra...@ya...>
To: "Pascal Bestebroer" <dyn...@li...>
Sent: Thursday, November 16, 2000 3:01 PM
Subject: Re[3]: [Dynapi-Dev] Default


>
> You could have a DynAPI.require method that will add required files.
> Then when the first file is included, it will include all of the
> required files.  I've done something similar to this before and it
> worked quite easily.  Also, this allows you to set the required files
> in the widgets.  That way if someone wanted to use the button widget,
> the only file that have to include is the button.js file and all of
> the others would automatically be included.
>
>
> \\Robert
> --
> rra...@ya...
>
> > I think the DynAPi is already very modular, you don't need to use events
or
> > dragging objects.
> > The only problem we're having is that you need to include dyndocument
and
> > dynlayer, because dynlayers can only be added to dyndocuments.. but the
rest
> > isn't that bad is it?
> >
> > Brandon, care to share your ideas ?
> >
> >
> >
> > Pascal Bestebroer
> > pb...@oi...
> > http://www.oibv.com
> >
> >
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

RE: Re[3]: [Dynapi-Dev] Default

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

Of course you'd need to keep a running list of all the files that had
already been loaded are not loaded again.  Otherwise, you could be making a
lot of useless trips to the server :)

-----Original Message-----
From: Robert Rainwater [mailto:rra...@ya...]
Sent: Thursday, November 16, 2000 12:01 PM
To: Pascal Bestebroer
Subject: Re[3]: [Dynapi-Dev] Default



You could have a DynAPI.require method that will add required files.
Then when the first file is included, it will include all of the
required files.  I've done something similar to this before and it
worked quite easily.  Also, this allows you to set the required files
in the widgets.  That way if someone wanted to use the button widget,
the only file that have to include is the button.js file and all of
the others would automatically be included.


\\Robert
-- 
rra...@ya...

> I think the DynAPi is already very modular, you don't need to use events
or
> dragging objects.
> The only problem we're having is that you need to include dyndocument and
> dynlayer, because dynlayers can only be added to dyndocuments.. but the
rest
> isn't that bad is it?
> 
> Brandon, care to share your ideas ?
> 
> 
> 
> Pascal Bestebroer
> pb...@oi...
> http://www.oibv.com
> 
>


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

Re[3]: [Dynapi-Dev] Default

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

You could have a DynAPI.require method that will add required files.
Then when the first file is included, it will include all of the
required files.  I've done something similar to this before and it
worked quite easily.  Also, this allows you to set the required files
in the widgets.  That way if someone wanted to use the button widget,
the only file that have to include is the button.js file and all of
the others would automatically be included.


\\Robert
-- 
rra...@ya...

> I think the DynAPi is already very modular, you don't need to use events or
> dragging objects.
> The only problem we're having is that you need to include dyndocument and
> dynlayer, because dynlayers can only be added to dyndocuments.. but the rest
> isn't that bad is it?
> 
> Brandon, care to share your ideas ?
> 
> 
> 
> Pascal Bestebroer
> pb...@oi...
> http://www.oibv.com
> 
>

Re: RE: RE: [Dynapi-Dev] Default

[Barre B. <ba...@ho...>]

Ok.. will do.
Yeah, that widget test thingy seems pretty good to work 
with... I will try it.

Thx, Bart

> I think the easiest way would be that you simply mail 
your patches to this
> mailing list, or use the patch area at sourceforge.. We 
can then see if the
> patch isn't breaking any windows/linux code and then use 
it in the DynAPI.
> 
> 
> You could use the test code I mailed to this list a few 
days ago and see how
> far things run on the Mac.. still some "deeper" code 
isn't included in the
> test so they would need other testing, but using the 
different widgets
> usually seem to be a good way of testing things aswell.
> 
> 
> Pascal Bestebroer
> pb...@oi...
> http://www.oibv.com
> 
> 
> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens 
Barre Bizon
> Verzonden: donderdag 16 november 2000 14:40
> Aan: dyn...@li...
> Onderwerp: Re: RE: [Dynapi-Dev] Default
> 
> 
> Yeah.. I see what you mean :)
> 
> Sure, as I say I have a mac at work and I am in the 
process
> of converting to dynapi2.
> Although I am not too fond of the mac and especially all
> the f***** problems/bugs that browsers on that platform
> have, I am quite cabable of debugging stuff on it; as it 
is
> part of my job :)
> So I'm totally up for hacking the mac to pieces. 
Literally.
> Heh
> I will however try stuff on a PC first and foremost.
> 
> Anyway, how do you want me to go about it, sending reports
> or files or whatever?
> 
> /Bart
> 
> >
> > Answer:
> > Yes it is an integral part, but as you already mentioned
> > there is modularity, and also the fact that you might 
want
> > to use your own browser detection or another browser
> detection
> > in the future (just an idea :)
> >
> >
> > It's great that you have a Mac, and hopefully you'r
> capable
> > of debugging javascript because I tried to do it a 
couple
> of
> > times with people who own a Mac, they would tell me the
> errors
> > and I'd try to fix them one by one... and that doesn't
> work, so
> > we really need someone who can hack it on a Mac.
> >
> >
> >
> > Pascal Bestebroer
> > pb...@oi...
> > http://www.oibv.com
> >
> >
> > -----Oorspronkelijk bericht-----
> > Van: dyn...@li...
> > [mailto:dyn...@li...]Namens
> Barre Bizon
> > Verzonden: maandag 13 november 2000 13:47
> > Aan: dyn...@li...
> > Onderwerp: [Dynapi-Dev] Default
> >
> >
> >
> > Question:
> > Shouldn't browser.js be included by default when you
> create
> > dynlayers?
> > I mean it is an integral part of the DynAPI and cannot 
be
> > left out...
> > And as far as keeping modularity.. ok.. but it really
> seems
> > reduntant to always include browser.js as practically
> > nothing will work without it...
> >
> > Maybe I'm missing something, though, as I'm just 
starting
> > to check DynAPI2 out. :)
> >
> > Oh and by the way,I have access to a mac (I have it as a
> > testcomputer at my work desk) so I could help with the
> > development for mac.
> > I have worked extensivly with a modified version of the
> > first dynapi before, including the creation of a text
> > dropdown menu with extensive platform support.
> > I even made a simplified scroll that works with mac.
> >
> > checkout
> > http://www.saabusa.com/home/US/en/95_intro.xml
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
> >
> 
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

RE: Re: [Dynapi-Dev] Default

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

I think the DynAPi is already very modular, you don't need to use events or
dragging objects.
The only problem we're having is that you need to include dyndocument and
dynlayer, because dynlayers can only be added to dyndocuments.. but the rest
isn't that bad is it?

Brandon, care to share your ideas ?



Pascal Bestebroer
pb...@oi...
http://www.oibv.com


-----Oorspronkelijk bericht-----
Van: dyn...@li...
[mailto:dyn...@li...]Namens Barre Bizon
Verzonden: donderdag 16 november 2000 14:43
Aan: dyn...@li...
Onderwerp: Re: Re: [Dynapi-Dev] Default


Hmm... this is very interesting.. yes you are right
offcourse..
And I have noticed this problem in other libraries that I
have built.
What is being done about modularity.. I would be very
intrested to take a deeper look at it.

/Bart

> The DynAPI as it stands is only partially modular.
> This is aparent by the fact that when one bug is fixed,
it causes a problem
> in either the widgets, or somewhere else in the core.
>
> Take heart though. There's hope for this problem in the
future!
>
> ----- Original Message -----
> From: "Pascal Bestebroer" <pb...@oi...>
> To: <dyn...@li...>
> Sent: Tuesday, November 14, 2000 6:20 AM
> Subject: RE: [Dynapi-Dev] Default
>
>
> >
> > Answer:
> > Yes it is an integral part, but as you already mentioned
> > there is modularity, and also the fact that you might
want
> > to use your own browser detection or another browser
detection
> > in the future (just an idea :)
> >
> >
> > It's great that you have a Mac, and hopefully you'r
capable
> > of debugging javascript because I tried to do it a
couple of
> > times with people who own a Mac, they would tell me the
errors
> > and I'd try to fix them one by one... and that doesn't
work, so
> > we really need someone who can hack it on a Mac.
> >
> >
> >
> > Pascal Bestebroer
> > pb...@oi...
> > http://www.oibv.com
> >
> >
> > -----Oorspronkelijk bericht-----
> > Van: dyn...@li...
> > [mailto:dyn...@li...]Namens
Barre Bizon
> > Verzonden: maandag 13 november 2000 13:47
> > Aan: dyn...@li...
> > Onderwerp: [Dynapi-Dev] Default
> >
> >
> >
> > Question:
> > Shouldn't browser.js be included by default when you
create
> > dynlayers?
> > I mean it is an integral part of the DynAPI and cannot
be
> > left out...
> > And as far as keeping modularity.. ok.. but it really
seems
> > reduntant to always include browser.js as practically
> > nothing will work without it...
> >
> > Maybe I'm missing something, though, as I'm just
starting
> > to check DynAPI2 out. :)
> >
> > Oh and by the way,I have access to a mac (I have it as a
> > testcomputer at my work desk) so I could help with the
> > development for mac.
> > I have worked extensivly with a modified version of the
> > first dynapi before, including the creation of a text
> > dropdown menu with extensive platform support.
> > I even made a simplified scroll that works with mac.
> >
> > checkout
> > http://www.saabusa.com/home/US/en/95_intro.xml
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev


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

RE: RE: [Dynapi-Dev] Default

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

I think the easiest way would be that you simply mail your patches to this
mailing list, or use the patch area at sourceforge.. We can then see if the
patch isn't breaking any windows/linux code and then use it in the DynAPI.


You could use the test code I mailed to this list a few days ago and see how
far things run on the Mac.. still some "deeper" code isn't included in the
test so they would need other testing, but using the different widgets
usually seem to be a good way of testing things aswell.


Pascal Bestebroer
pb...@oi...
http://www.oibv.com


-----Oorspronkelijk bericht-----
Van: dyn...@li...
[mailto:dyn...@li...]Namens Barre Bizon
Verzonden: donderdag 16 november 2000 14:40
Aan: dyn...@li...
Onderwerp: Re: RE: [Dynapi-Dev] Default


Yeah.. I see what you mean :)

Sure, as I say I have a mac at work and I am in the process
of converting to dynapi2.
Although I am not too fond of the mac and especially all
the f***** problems/bugs that browsers on that platform
have, I am quite cabable of debugging stuff on it; as it is
part of my job :)
So I'm totally up for hacking the mac to pieces. Literally.
Heh
I will however try stuff on a PC first and foremost.

Anyway, how do you want me to go about it, sending reports
or files or whatever?

/Bart

>
> Answer:
> Yes it is an integral part, but as you already mentioned
> there is modularity, and also the fact that you might want
> to use your own browser detection or another browser
detection
> in the future (just an idea :)
>
>
> It's great that you have a Mac, and hopefully you'r
capable
> of debugging javascript because I tried to do it a couple
of
> times with people who own a Mac, they would tell me the
errors
> and I'd try to fix them one by one... and that doesn't
work, so
> we really need someone who can hack it on a Mac.
>
>
>
> Pascal Bestebroer
> pb...@oi...
> http://www.oibv.com
>
>
> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens
Barre Bizon
> Verzonden: maandag 13 november 2000 13:47
> Aan: dyn...@li...
> Onderwerp: [Dynapi-Dev] Default
>
>
>
> Question:
> Shouldn't browser.js be included by default when you
create
> dynlayers?
> I mean it is an integral part of the DynAPI and cannot be
> left out...
> And as far as keeping modularity.. ok.. but it really
seems
> reduntant to always include browser.js as practically
> nothing will work without it...
>
> Maybe I'm missing something, though, as I'm just starting
> to check DynAPI2 out. :)
>
> Oh and by the way,I have access to a mac (I have it as a
> testcomputer at my work desk) so I could help with the
> development for mac.
> I have worked extensivly with a modified version of the
> first dynapi before, including the creation of a text
> dropdown menu with extensive platform support.
> I even made a simplified scroll that works with mac.
>
> checkout
> http://www.saabusa.com/home/US/en/95_intro.xml
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>


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

Re: [Dynapi-Dev] Layers and Image maps

[Brandon M. <tr...@us...>]

Would you be willing to share this library with the DynAPI group?

----- Original Message ----- 
From: "Barre Bizon" <ba...@ho...>
To: <dyn...@li...>
Sent: Thursday, November 16, 2000 8:46 AM
Subject: Re: [Dynapi-Dev] Layers and Image maps


> I have run across this problem before.
> I did not find a solution to having imagemaps in layers for 
> Netscape.
> My solution was making a Javascript imagemap, i.e. I 
> constructed a library that took care of the problem.
> 
> 
> /Bart
> 
> > Is there a way to reset the point of origin of a layer?  
> Right now
> > I'm having problems with an image map that is contained 
> withing a layer.
> > In IE, the image map works perfectly but in Netscape, the 
> image map
> > is not taking in consideration the current x,y position.
> > 
> > Anyone got a solution?  Please don't say I have to branch 
> my code
> > and make one map for IE and one for Netscape that will be 
> map for IE
> > offset by N & M.
> > 
> >   Eric
> > 
> ____________________________________________________________
> _____________
> > Get Your Private, Free E-mail from MSN Hotmail at 
> http://www.hotmail.com.
> > 
> > Share information about yourself, create your own public 
> profile at 
> > http://profiles.msn.com.
> > 
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
> 
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

Re: [Dynapi-Dev] Layers and Image maps

[Barre B. <ba...@ho...>]

I have run across this problem before.
I did not find a solution to having imagemaps in layers for 
Netscape.
My solution was making a Javascript imagemap, i.e. I 
constructed a library that took care of the problem.


/Bart

> Is there a way to reset the point of origin of a layer?  
Right now
> I'm having problems with an image map that is contained 
withing a layer.
> In IE, the image map works perfectly but in Netscape, the 
image map
> is not taking in consideration the current x,y position.
> 
> Anyone got a solution?  Please don't say I have to branch 
my code
> and make one map for IE and one for Netscape that will be 
map for IE
> offset by N & M.
> 
>   Eric
> 
____________________________________________________________
_____________
> Get Your Private, Free E-mail from MSN Hotmail at 
http://www.hotmail.com.
> 
> Share information about yourself, create your own public 
profile at 
> http://profiles.msn.com.
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

Re: Re: [Dynapi-Dev] Default

[Barre B. <ba...@ho...>]

Hmm... this is very interesting.. yes you are right 
offcourse.. 
And I have noticed this problem in other libraries that I 
have built.
What is being done about modularity.. I would be very 
intrested to take a deeper look at it.

/Bart

> The DynAPI as it stands is only partially modular.
> This is aparent by the fact that when one bug is fixed, 
it causes a problem
> in either the widgets, or somewhere else in the core.
> 
> Take heart though. There's hope for this problem in the 
future!
> 
> ----- Original Message -----
> From: "Pascal Bestebroer" <pb...@oi...>
> To: <dyn...@li...>
> Sent: Tuesday, November 14, 2000 6:20 AM
> Subject: RE: [Dynapi-Dev] Default
> 
> 
> >
> > Answer:
> > Yes it is an integral part, but as you already mentioned
> > there is modularity, and also the fact that you might 
want
> > to use your own browser detection or another browser 
detection
> > in the future (just an idea :)
> >
> >
> > It's great that you have a Mac, and hopefully you'r 
capable
> > of debugging javascript because I tried to do it a 
couple of
> > times with people who own a Mac, they would tell me the 
errors
> > and I'd try to fix them one by one... and that doesn't 
work, so
> > we really need someone who can hack it on a Mac.
> >
> >
> >
> > Pascal Bestebroer
> > pb...@oi...
> > http://www.oibv.com
> >
> >
> > -----Oorspronkelijk bericht-----
> > Van: dyn...@li...
> > [mailto:dyn...@li...]Namens 
Barre Bizon
> > Verzonden: maandag 13 november 2000 13:47
> > Aan: dyn...@li...
> > Onderwerp: [Dynapi-Dev] Default
> >
> >
> >
> > Question:
> > Shouldn't browser.js be included by default when you 
create
> > dynlayers?
> > I mean it is an integral part of the DynAPI and cannot 
be
> > left out...
> > And as far as keeping modularity.. ok.. but it really 
seems
> > reduntant to always include browser.js as practically
> > nothing will work without it...
> >
> > Maybe I'm missing something, though, as I'm just 
starting
> > to check DynAPI2 out. :)
> >
> > Oh and by the way,I have access to a mac (I have it as a
> > testcomputer at my work desk) so I could help with the
> > development for mac.
> > I have worked extensivly with a modified version of the
> > first dynapi before, including the creation of a text
> > dropdown menu with extensive platform support.
> > I even made a simplified scroll that works with mac.
> >
> > checkout
> > http://www.saabusa.com/home/US/en/95_intro.xml
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

Re: RE: [Dynapi-Dev] Default

[Barre B. <ba...@ho...>]

Yeah.. I see what you mean :)

Sure, as I say I have a mac at work and I am in the process 
of converting to dynapi2.
Although I am not too fond of the mac and especially all 
the f***** problems/bugs that browsers on that platform 
have, I am quite cabable of debugging stuff on it; as it is 
part of my job :)
So I'm totally up for hacking the mac to pieces. Literally. 
Heh
I will however try stuff on a PC first and foremost.

Anyway, how do you want me to go about it, sending reports 
or files or whatever?

/Bart

> 
> Answer:
> Yes it is an integral part, but as you already mentioned
> there is modularity, and also the fact that you might want
> to use your own browser detection or another browser 
detection
> in the future (just an idea :)
> 
> 
> It's great that you have a Mac, and hopefully you'r 
capable
> of debugging javascript because I tried to do it a couple 
of
> times with people who own a Mac, they would tell me the 
errors
> and I'd try to fix them one by one... and that doesn't 
work, so
> we really need someone who can hack it on a Mac.
> 
> 
> 
> Pascal Bestebroer
> pb...@oi...
> http://www.oibv.com
> 
> 
> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens 
Barre Bizon
> Verzonden: maandag 13 november 2000 13:47
> Aan: dyn...@li...
> Onderwerp: [Dynapi-Dev] Default
> 
> 
> 
> Question: 
> Shouldn't browser.js be included by default when you 
create 
> dynlayers? 
> I mean it is an integral part of the DynAPI and cannot be 
> left out...
> And as far as keeping modularity.. ok.. but it really 
seems 
> reduntant to always include browser.js as practically 
> nothing will work without it...
> 
> Maybe I'm missing something, though, as I'm just starting 
> to check DynAPI2 out. :)
> 
> Oh and by the way,I have access to a mac (I have it as a 
> testcomputer at my work desk) so I could help with the 
> development for mac. 
> I have worked extensivly with a modified version of the 
> first dynapi before, including the creation of a text 
> dropdown menu with extensive platform support.
> I even made a simplified scroll that works with mac.
> 
> checkout 
> http://www.saabusa.com/home/US/en/95_intro.xml
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
> 

RE: [Dynapi-Dev] My set of widgets can now be used

[Guangyi Wu <gua...@al...>]

Hi,

I am relative new to DynAPI 2 and learning it with code now. Please bear
with me if I make trival mistakes.

I just tested the Dan's widgets in NN 4.5 and IE 5.0 on Windows NT 4. It
seems the label does not work properly at following points:

1. "non-selectable" does not work for both NN and IE;

2. "resize" works well for IE and the text does not adjust itself for NN.

3. When the font size and family is undefined, it looks strange in NN. It
might be better for testing if the value is set like following
	var pointSize = this.font.size? ' point-size='+this.font.size : ''
	var fontFamily = this.font.family? ' family='+this.font.family : ''
	var styled = '<font'+pointSize+fontFamily+'>'+this.text+'</font>'
instead of that in Label.prototype.setText()
	var styled = '<font point-size='+this.font.size+'
family="'+this.font.family+'">'+this.text+'</b>'

I'll have a deeper look into the code.

br
George

> -----Original Message-----
> From: Dan Steinman [mailto:dy...@fu...]
> Sent: Tuesday, November 14, 2000 7:22 AM
> To: dyn...@li...
> Subject: [Dynapi-Dev] My set of widgets can now be used
> 
> 
> I've released 3 small patches to SourceForge with the 
> necessary changes for my set of widgets to work properly 
> (based on the latest 11-07 release).
> 
> 1. New order of method calls in DynLayer.create() - this is 
> needed for my widgets to draw correctly, the setSize() was 
> called too soon etc.
> 
> 2. I've added another method onto MouseEvent:
> 
> e.cancelBrowserEvent()
> 
> This is not the same as setBubble().  For Netscape the event 
> handler needs to return a boolean value.  Previously what we 
> were doing was returning the "bubble" value, but there is a 
> case where you need to enable bubbling, but still return 
> "false" to Netscape (this is to stop text selection during 
> drags etc).  In Label I removed the "cover layer" idea and 
> simply replaced with with an event listener that cancels the 
> browser event, the result is the same.  DragEvents has been 
> updated to accomidate this change.
> 
> I've repackaged dynapi-2000.11.07 with my widgets and it can 
> be downloaded from:
> 
> http://fury161.dyndns.org/dynapi-2000.11.07-danwidgets.zip
> 
> This includes all the dynapi files with my new files in 
> place.  Mine are:
> 
> /dynapi/js/images/*  (scrollpane and arrow images)
> /dynapi/js/lib/dynapi/gui/* (new/updated widgets)
> /dynapi/examples/dynapi.gui.* (examples of each widget)
> 
> Widgets:
> Label - updated with new listeners and new methods for 
> "packing" which must be done manually now
> Button - a small button widget with metal styling (used for 
> arrow buttons in PushPanel, but has support for text using Label)
> Sprite - this is merely a DynLayer with slide methods already 
> attached, not sure if this is what anyone else had in mind 
> but I think it would be valuable to hava separate widget 
> specifically for use during animation.  It could be the 
> object that you attach other methods for a timeline or 
> something like that.
> ButtonImage - quick port of the old buttonimage, in 
> ScrollPane this will probably be replaced with just Button
> ViewPort - the equivalent of what used to be ScrollWindow
> ScrollBar - the scrollbar objects used in Scrollpane
> ScrollPane - the new "Scroll" widget, functionally complete, 
> but not tested on Windows/IE
> PushPanel - a rewritten DynAPI1 pushpanel that extends off of ViewPort
> 
> Notes:
> Actually both ScrollPane and PushPanel extend ViewPort, so 
> they have the same set of methods.  This shows how you can do 
> inheritance (DynLayer->ViewPort->Scrollpane) in DynAPI2 
> without using any SuperClass type of tricks.  No need for 
> "super" methods because you rely solely on event listeners.
> 
> LoadPanel can be used along with ScrollPane quite easily.  
> All you do is:
> 
> scrollpane.setContent(loadpanel)
> 
> Tada!  Now you can load files into loadpanel (loadpanel will 
> resize), and scrollpane will scroll loadpanel (or any other 
> widget you put inside it).
> 
> Please test them out on Windows/Mac and post any patches needed.
> 
> Again note: you either need my patches to 11-07 or use the 
> api files included in my zip file mentioned above in order 
> for my widgets to work properly.
> 
> Over and out,
> Dan
> 

[Dynapi-Dev] Events being triggered in the wrong places.

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

I have just started working with Dan's latest creation.  I have done a 
fair bit of work with both versions 1 and 2 and have started building my 
own widgets to help me.

The most recent is a Cell object that extends the DynLayer object.  This 
happens with no problems.
I then have a Button object that extens the Cell object.  Again, it 
creates with no problems.  The problems becomes apparent when I start 
using events to capture mouse clicks.

I have a test page that has three buttons on it, TestButton1, 
TestButton2, TestButton3.  All are Buttons as explained before.  They 
each just have a sample alert message when they are clicked.

When any of these are pressed, it triggers all of the Buttons' click 
events, regardless of which is clicked.  In IE5.5 and NS4.75, it cycles 
once.  In NS6, it cycles twice.

If anyone has any ideas on what is causing the broblem, please help me 
out.  Thanks.

[Dynapi-Dev] Layers and Image maps

[Eric G. <egr...@ho...>]

Is there a way to reset the point of origin of a layer?  Right now
I'm having problems with an image map that is contained withing a layer.
In IE, the image map works perfectly but in Netscape, the image map
is not taking in consideration the current x,y position.

Anyone got a solution?  Please don't say I have to branch my code
and make one map for IE and one for Netscape that will be map for IE
offset by N & M.

  Eric
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at 
http://profiles.msn.com.

RE: [Dynapi-Dev] Looking for some help

[Samuel, M. M <Sam...@ed...>]

Thanks for all the suggestions on this curly one - After hours of frustration -
and utilising W3C's Amaya browser, we figured out that the server had HTML
compression turned on.

A word of warning - browsers DON'T like HTML compression! :)

I wasn't in the best of moods with the sysadmin yesterday!

Mike

-----Original Message-----
From: Brandon Myers [mailto:bnd...@ho...]
Sent: Wednesday, 15 November 2000 2:44 AM
To: dyn...@li...
Subject: Re: [Dynapi-Dev] Looking for some help



>
> > I've got a most unusual problem going on - and I'm looking to you guys
> > for advice.
> >
> > The webapp I've written using DynAPI II is successfully running on 6 of
> > 7 servers in a web farm. The files are identical on all the servers, and
> > the servers are identical in setup etc.
> >
> > The only problem is that on this one box - the loadpanel.js doesn't seem
> > to be functioning correctly.
> >
> > I don't know if you guys have witnessed this before - and if it's not
> > remotely connecting to DynAPI - I can understand - it's just i've been
> > thrashing through this problem for the last 4+ hours - and I'm at my
> > wits end....
>
> Its most probaly a security problem.  Are you trying to load a page
> that is own another server.  I believe loadpanel only works for local
> pages.  Also, are you linking the scripts to other servers?  Just some
> ideas.  Whats the error message that you get?
>

I'm not totally sure where the problem is occuring, but given Robert's angle
he is right. There is a security issue in IE and Netscape that will cause
problems when using loadpanel to load content from a server other than the
server that loaded the base document.
So the question is, are you trying to load a page outside of the original
server from the URL which includes the loadpanel.js file?

You also said that you where using a web farm. If you where to use a the
SAME server name to access all of these servers then the problem probably is
not within loadpanel.

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

[Dynapi-Dev] NS 6

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

well, it was kind of a quiet release, but better or for worse, ns6 was
rushed to release.

http://www.netscape.com

if you believe the following article, seeing a NS6 this early means it is
*seriously* non-compliant

http://www.oreilly.com/news/flanagan_1100.html

The guy who wrote it (a writer for o'reilly) got flamed up the wassoo, so
there is also a rebuttal here:

http://www.oreilly.com/news/flanagan2_1100.html

Guess it's time to put it to the test :)


--------------------------------------------------
Darin Kadrioski
Applications/Internet Developer

> Electronic Freight Exchange, Corp.
dka...@ef...
(916) 933-0724 x315