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

RE: [Dynapi-Dev] Issues, remaining

[<rua...@ee...>]

Yep, I'm on the list and live in Madrid, Spain. I've not contributed =
yet.
I've been trying to figure out exactly how the DynAPI works, but =
there's so
much code and so little comments. Hope I'll be of more help in the =
future.

Ruairi

-----Mensaje original-----
De: Jordi 'IlMaestro' Ministral [mailto:jmi...@or...]
Enviado el: mi=E9rcoles 10 de enero de 2001 12:53
Para: dyn...@li...
Asunto: Re: [Dynapi-Dev] Issues, remaining


Is there any other European guy/girl in this list appart from Pascal =
and me
? I
find it hard to keep a conversation when I'm awaken and then each =
morning I
find
40 mails waiting for me....

Nevermind

Raymond Smith wrote:

> Yoda would look young
>
> I still owe you a set of skins for that skinwidget set you are =
letting
rust.
> I didn't forget.
>
> Later, 4am here...
>
> ----- Original Message -----
> From: "Pascal" <pb...@oi...>
> To: <dyn...@li...>
> Sent: Wednesday, January 10, 2001 3:32 AM
> Subject: RE: [Dynapi-Dev] Issues, remaining
>
> > so.. what's your age then :-)
> >
> > Pascal Bestebroer (pb...@oi...)
> > Software ontwikkelaar
> > Oberon Informatiesystemen b.v.
> > http://www.oibv.com
> >
> > > -----Oorspronkelijk bericht-----
> > > Van: dyn...@li...
> > > [mailto:dyn...@li...]Namens Raymond =
Smith
> > > Verzonden: woensdag 10 januari 2001 12:22
> > > Aan: dyn...@li...
> > > Onderwerp: Re: [Dynapi-Dev] Issues, remaining
> > >
> > >
> > > I contribute to the level of my abilty.  And a master
> > > debugger I am not, but
> > > I have found a 'few' trivial ones.  If I got credit for
> > > bloodshot eyes and
> > > pist off girl friends you might actually get a sense of how
> > > much time I
> > > spend trying to make a contribution.
> > >
> > > I think I tend to frustrate poor Robert as much as make a valid
> > > contribution.
> > >
> > > I never coded a stitch in my life, til 3 months ago.  I am a
> > > mere pup among
> > > men (yet I'm probably older then most of you, don't ask).
> > >
> > >
> > >
> > >
> > > ----- Original Message -----
> > > From: "Pascal" <pb...@oi...>
> > > To: <dyn...@li...>
> > > Sent: Wednesday, January 10, 2001 3:12 AM
> > > Subject: RE: [Dynapi-Dev] Issues, remaining
> > >
> > >
> > > > I agree on the tutors and reference not being uptodate..
> > > the tutorial is
> > > > something I can easily fix (and might do this weekend, if I
> > > find the time)
> > > > but the dev-reference is something almost everyone on this
> > > list can do..
> > > > just take out that which is Dynacore specific (i.e.: not
> > > found in DynAPI)
> > > > and  copy and paste all that is under DynObject to the DynLayer =
and
> > > > DynDocument objects.
> > > >
> > > > I just feel its a sad thing that there are so many people
> > > on this list,
> > > alot
> > > > of which are "complaining" about bugs not being fixed, not much
> > > > documentation being available, and those people fail to =
contribute
> > > anything
> > > > as simple as copy-and-pasting text.
> > > >
> > > > anyway, for a few widget examples look at the widgets with
> > > the dynacore
> > > > release, they use the precreate event (very basic stuff
> > > actually..just
> > > > replace the old oncreate  with onprecreate, and make the
> > > listener not part
> > > > of the prototype but part of the constructor)
> > > >
> > > > Please don't take this mail as an attack or anything (definetly =
not
> > > personal
> > > > to you Raymond), but everyone, please don't be shy to =
contribute
> > > anything..
> > > > it's opensource, and we all had to learn (and are still
> > > learning) this
> > > > "thing" at one point.  Stuff like widget creation is such a
> > > simple task
> > > you
> > > > only need the idea (see any GUI for ideas) and basic knowledge =
of
> > > > DynAPI/javascript (see tutorials).
> > > >
> > > > cya (and have fun :),
> > > >
> > > > Pascal Bestebroer (pb...@oi...)
> > > > Software ontwikkelaar
> > > > Oberon Informatiesystemen b.v.
> > > > http://www.oibv.com
> > > >
> > > > > -----Oorspronkelijk bericht-----
> > > > > Van: dyn...@li...
> > > > > [mailto:dyn...@li...]Namens
> > > Raymond Smith
> > > > > Verzonden: woensdag 10 januari 2001 11:18
> > > > > Aan: dyn...@li...
> > > > > Onderwerp: Re: [Dynapi-Dev] Issues, remaining
> > > > >
> > > > >
> > > > > Currently, there are not alot of good representations of
> > > > > precreate in the
> > > > > widgets.  The ButtonImage doesn't use it and doesn't work
> > > in IE or NS.
> > > > > Others say they will be updated.  The only technical writing
> > > > > on it can be
> > > > > found in your docs and build for Dynacore or one prior post
> > > > > from Dan on
> > > > > 'lots of changes'.  All the docs here date back to November
> > > > > and the last
> > > > > time you updated them.
> > > > >
> > > > > The viewport is a child layer, maybe that explains why the
> > > > > events don't
> > > > > fire.  Yet the images in the widget themselves change.  The
> > > > > event related to
> > > > > the viewport isn't even part of a widget, but defined in
> > > the onLoad()
> > > > > section of the webpage.
> > > > >
> > > > > Eventually enough will leach out (or in) that I will
> > > understand it.
> > > > >
> > > > > Cheers
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > 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
> >
>
> _______________________________________________
> 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] Getting into it

[Jordi 'I. M. <jmi...@or...>]

Please whoever wrote the DynLayer.EventMethod currently in CVS contact me. I'd like
to discuss a couple of things.

Cya


Jordi 'IlMaestro' Ministral wrote:

> Ok, I've eaten and procesed all the new code in the API. I'm starting this new
> thread where I will reply myself and share my progress ( if any ). Good news is
> that my SMI (see my website for details) is finally finished, but I want to make
> sure it works with this precreation code ( which will hopefully decrease the
> time needed to initialize a big menulist ), before I release it.
>
> Ok. Facts
>
> A) The precreation code looks nice.
> B) The current cvs release doesn't have a buttonimage example. Instead, there's
> a button widget and the corresponding example. It doesn't work but that is
> because:
> C) The label widget doesn't work properly in IE, wich brings us to point:
> D) The label widget no longer uses a cover layer and cancelBrowserEvent() does
> not prevent text from being selectable.
> E) I'm not event using IE5.5 but 4.0 and 5.0
> F) Events in child layers in IE5 seem to get lost in the way and never reach the
> API. I still don't know under which circunstances a IE child layer decides that
> I am an evil person and therefore my code must not be executed and if possible a
> lightning should fry me dead.
> G) I've been testing and reloading and reloading and NS didn't crash one single
> time. That is good news.
>
> .
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

Re: [Dynapi-Dev] Getting into it [ prologue ]

[Jordi 'I. M. <jmi...@or...>]

DynLayer.EventMethod:

....
 if (is.ie) {
  var e=dyndoc.elm.event;
  e.cancelBubble=true;
  if (e.type=="click" && DynAPI.wasDragging) {
   // e.cancelBubble=true;  this is already done two lines before
   DynAPI.wasDragging=false;
   return true;
  }
  if (e.type!="mouseout" && e.type!="mouseover") e.cancelBubble=true;
  if (e.type=="mouseout" && this.contains(e.toElement)) return true;
  if (e.type=="mouseover" && this.contains(e.fromElement)) return true;
 }
.....

too many 'e.cancelBubble= true'. Either some are redundant or some of them should
not be there. Moving on....


Jordi 'IlMaestro' Ministral wrote:

> Ok, I've eaten and procesed all the new code in the API. I'm starting this new
> thread where I will reply myself and share my progress ( if any ). Good news is
> that my SMI (see my website for details) is finally finished, but I want to make
> sure it works with this precreation code ( which will hopefully decrease the
> time needed to initialize a big menulist ), before I release it.
>
> Ok. Facts
>
> A) The precreation code looks nice.
> B) The current cvs release doesn't have a buttonimage example. Instead, there's
> a button widget and the corresponding example. It doesn't work but that is
> because:
> C) The label widget doesn't work properly in IE, wich brings us to point:
> D) The label widget no longer uses a cover layer and cancelBrowserEvent() does
> not prevent text from being selectable.
> E) I'm not event using IE5.5 but 4.0 and 5.0
> F) Events in child layers in IE5 seem to get lost in the way and never reach the
> API. I still don't know under which circunstances a IE child layer decides that
> I am an evil person and therefore my code must not be executed and if possible a
> lightning should fry me dead.
> G) I've been testing and reloading and reloading and NS didn't crash one single
> time. That is good news.
>
> .
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

RE: [Dynapi-Dev] Getting into it [ prologue ]

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

sorry to interrupt you here :)

> F) Events in child layers in IE5 seem to get lost in the way
> and never reach the
> API. I still don't know under which circunstances a IE child
> layer decides that
> I am an evil person and therefore my code must not be
> executed and if possible a
> lightning should fry me dead.

Hmm, I've tested with a small parent-child-child-child thingie, and the
events triggered correctly (under IE5.0) maybe the code likes me more..
strange :-)



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

Re: [Dynapi-Dev] Issues, remaining

[Jordi 'I. M. <jmi...@or...>]

Is there any other European guy/girl in this list appart from Pascal and me ? I
find it hard to keep a conversation when I'm awaken and then each morning I find
40 mails waiting for me....

Nevermind

Raymond Smith wrote:

> Yoda would look young
>
> I still owe you a set of skins for that skinwidget set you are letting rust.
> I didn't forget.
>
> Later, 4am here...
>
> ----- Original Message -----
> From: "Pascal" <pb...@oi...>
> To: <dyn...@li...>
> Sent: Wednesday, January 10, 2001 3:32 AM
> Subject: RE: [Dynapi-Dev] Issues, remaining
>
> > so.. what's your age then :-)
> >
> > Pascal Bestebroer (pb...@oi...)
> > Software ontwikkelaar
> > Oberon Informatiesystemen b.v.
> > http://www.oibv.com
> >
> > > -----Oorspronkelijk bericht-----
> > > Van: dyn...@li...
> > > [mailto:dyn...@li...]Namens Raymond Smith
> > > Verzonden: woensdag 10 januari 2001 12:22
> > > Aan: dyn...@li...
> > > Onderwerp: Re: [Dynapi-Dev] Issues, remaining
> > >
> > >
> > > I contribute to the level of my abilty.  And a master
> > > debugger I am not, but
> > > I have found a 'few' trivial ones.  If I got credit for
> > > bloodshot eyes and
> > > pist off girl friends you might actually get a sense of how
> > > much time I
> > > spend trying to make a contribution.
> > >
> > > I think I tend to frustrate poor Robert as much as make a valid
> > > contribution.
> > >
> > > I never coded a stitch in my life, til 3 months ago.  I am a
> > > mere pup among
> > > men (yet I'm probably older then most of you, don't ask).
> > >
> > >
> > >
> > >
> > > ----- Original Message -----
> > > From: "Pascal" <pb...@oi...>
> > > To: <dyn...@li...>
> > > Sent: Wednesday, January 10, 2001 3:12 AM
> > > Subject: RE: [Dynapi-Dev] Issues, remaining
> > >
> > >
> > > > I agree on the tutors and reference not being uptodate..
> > > the tutorial is
> > > > something I can easily fix (and might do this weekend, if I
> > > find the time)
> > > > but the dev-reference is something almost everyone on this
> > > list can do..
> > > > just take out that which is Dynacore specific (i.e.: not
> > > found in DynAPI)
> > > > and  copy and paste all that is under DynObject to the DynLayer and
> > > > DynDocument objects.
> > > >
> > > > I just feel its a sad thing that there are so many people
> > > on this list,
> > > alot
> > > > of which are "complaining" about bugs not being fixed, not much
> > > > documentation being available, and those people fail to contribute
> > > anything
> > > > as simple as copy-and-pasting text.
> > > >
> > > > anyway, for a few widget examples look at the widgets with
> > > the dynacore
> > > > release, they use the precreate event (very basic stuff
> > > actually..just
> > > > replace the old oncreate  with onprecreate, and make the
> > > listener not part
> > > > of the prototype but part of the constructor)
> > > >
> > > > Please don't take this mail as an attack or anything (definetly not
> > > personal
> > > > to you Raymond), but everyone, please don't be shy to contribute
> > > anything..
> > > > it's opensource, and we all had to learn (and are still
> > > learning) this
> > > > "thing" at one point.  Stuff like widget creation is such a
> > > simple task
> > > you
> > > > only need the idea (see any GUI for ideas) and basic knowledge of
> > > > DynAPI/javascript (see tutorials).
> > > >
> > > > cya (and have fun :),
> > > >
> > > > Pascal Bestebroer (pb...@oi...)
> > > > Software ontwikkelaar
> > > > Oberon Informatiesystemen b.v.
> > > > http://www.oibv.com
> > > >
> > > > > -----Oorspronkelijk bericht-----
> > > > > Van: dyn...@li...
> > > > > [mailto:dyn...@li...]Namens
> > > Raymond Smith
> > > > > Verzonden: woensdag 10 januari 2001 11:18
> > > > > Aan: dyn...@li...
> > > > > Onderwerp: Re: [Dynapi-Dev] Issues, remaining
> > > > >
> > > > >
> > > > > Currently, there are not alot of good representations of
> > > > > precreate in the
> > > > > widgets.  The ButtonImage doesn't use it and doesn't work
> > > in IE or NS.
> > > > > Others say they will be updated.  The only technical writing
> > > > > on it can be
> > > > > found in your docs and build for Dynacore or one prior post
> > > > > from Dan on
> > > > > 'lots of changes'.  All the docs here date back to November
> > > > > and the last
> > > > > time you updated them.
> > > > >
> > > > > The viewport is a child layer, maybe that explains why the
> > > > > events don't
> > > > > fire.  Yet the images in the widget themselves change.  The
> > > > > event related to
> > > > > the viewport isn't even part of a widget, but defined in
> > > the onLoad()
> > > > > section of the webpage.
> > > > >
> > > > > Eventually enough will leach out (or in) that I will
> > > understand it.
> > > > >
> > > > > Cheers
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > 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
> >
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

[Dynapi-Dev] Getting into it [ prologue ]

[Jordi 'I. M. <jmi...@or...>]

Ok, I've eaten and procesed all the new code in the API. I'm starting this new
thread where I will reply myself and share my progress ( if any ). Good news is
that my SMI (see my website for details) is finally finished, but I want to make
sure it works with this precreation code ( which will hopefully decrease the
time needed to initialize a big menulist ), before I release it.

Ok. Facts

A) The precreation code looks nice.
B) The current cvs release doesn't have a buttonimage example. Instead, there's
a button widget and the corresponding example. It doesn't work but that is
because:
C) The label widget doesn't work properly in IE, wich brings us to point:
D) The label widget no longer uses a cover layer and cancelBrowserEvent() does
not prevent text from being selectable.
E) I'm not event using IE5.5 but 4.0 and 5.0
F) Events in child layers in IE5 seem to get lost in the way and never reach the
API. I still don't know under which circunstances a IE child layer decides that
I am an evil person and therefore my code must not be executed and if possible a
lightning should fry me dead.
G) I've been testing and reloading and reloading and NS didn't crash one single
time. That is good news.

.

Re: [Dynapi-Dev] Issues, remaining

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

Yoda would look young

I still owe you a set of skins for that skinwidget set you are letting rust.
I didn't forget.

Later, 4am here...


----- Original Message -----
From: "Pascal" <pb...@oi...>
To: <dyn...@li...>
Sent: Wednesday, January 10, 2001 3:32 AM
Subject: RE: [Dynapi-Dev] Issues, remaining


> so.. what's your age then :-)
>
> Pascal Bestebroer (pb...@oi...)
> Software ontwikkelaar
> Oberon Informatiesystemen b.v.
> http://www.oibv.com
>
> > -----Oorspronkelijk bericht-----
> > Van: dyn...@li...
> > [mailto:dyn...@li...]Namens Raymond Smith
> > Verzonden: woensdag 10 januari 2001 12:22
> > Aan: dyn...@li...
> > Onderwerp: Re: [Dynapi-Dev] Issues, remaining
> >
> >
> > I contribute to the level of my abilty.  And a master
> > debugger I am not, but
> > I have found a 'few' trivial ones.  If I got credit for
> > bloodshot eyes and
> > pist off girl friends you might actually get a sense of how
> > much time I
> > spend trying to make a contribution.
> >
> > I think I tend to frustrate poor Robert as much as make a valid
> > contribution.
> >
> > I never coded a stitch in my life, til 3 months ago.  I am a
> > mere pup among
> > men (yet I'm probably older then most of you, don't ask).
> >
> >
> >
> >
> > ----- Original Message -----
> > From: "Pascal" <pb...@oi...>
> > To: <dyn...@li...>
> > Sent: Wednesday, January 10, 2001 3:12 AM
> > Subject: RE: [Dynapi-Dev] Issues, remaining
> >
> >
> > > I agree on the tutors and reference not being uptodate..
> > the tutorial is
> > > something I can easily fix (and might do this weekend, if I
> > find the time)
> > > but the dev-reference is something almost everyone on this
> > list can do..
> > > just take out that which is Dynacore specific (i.e.: not
> > found in DynAPI)
> > > and  copy and paste all that is under DynObject to the DynLayer and
> > > DynDocument objects.
> > >
> > > I just feel its a sad thing that there are so many people
> > on this list,
> > alot
> > > of which are "complaining" about bugs not being fixed, not much
> > > documentation being available, and those people fail to contribute
> > anything
> > > as simple as copy-and-pasting text.
> > >
> > > anyway, for a few widget examples look at the widgets with
> > the dynacore
> > > release, they use the precreate event (very basic stuff
> > actually..just
> > > replace the old oncreate  with onprecreate, and make the
> > listener not part
> > > of the prototype but part of the constructor)
> > >
> > > Please don't take this mail as an attack or anything (definetly not
> > personal
> > > to you Raymond), but everyone, please don't be shy to contribute
> > anything..
> > > it's opensource, and we all had to learn (and are still
> > learning) this
> > > "thing" at one point.  Stuff like widget creation is such a
> > simple task
> > you
> > > only need the idea (see any GUI for ideas) and basic knowledge of
> > > DynAPI/javascript (see tutorials).
> > >
> > > cya (and have fun :),
> > >
> > > Pascal Bestebroer (pb...@oi...)
> > > Software ontwikkelaar
> > > Oberon Informatiesystemen b.v.
> > > http://www.oibv.com
> > >
> > > > -----Oorspronkelijk bericht-----
> > > > Van: dyn...@li...
> > > > [mailto:dyn...@li...]Namens
> > Raymond Smith
> > > > Verzonden: woensdag 10 januari 2001 11:18
> > > > Aan: dyn...@li...
> > > > Onderwerp: Re: [Dynapi-Dev] Issues, remaining
> > > >
> > > >
> > > > Currently, there are not alot of good representations of
> > > > precreate in the
> > > > widgets.  The ButtonImage doesn't use it and doesn't work
> > in IE or NS.
> > > > Others say they will be updated.  The only technical writing
> > > > on it can be
> > > > found in your docs and build for Dynacore or one prior post
> > > > from Dan on
> > > > 'lots of changes'.  All the docs here date back to November
> > > > and the last
> > > > time you updated them.
> > > >
> > > > The viewport is a child layer, maybe that explains why the
> > > > events don't
> > > > fire.  Yet the images in the widget themselves change.  The
> > > > event related to
> > > > the viewport isn't even part of a widget, but defined in
> > the onLoad()
> > > > section of the webpage.
> > > >
> > > > Eventually enough will leach out (or in) that I will
> > understand it.
> > > >
> > > > Cheers
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > 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: [Dynapi-Dev] Issues, remaining

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

so.. what's your age then :-)

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

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Raymond Smith
> Verzonden: woensdag 10 januari 2001 12:22
> Aan: dyn...@li...
> Onderwerp: Re: [Dynapi-Dev] Issues, remaining
> 
> 
> I contribute to the level of my abilty.  And a master 
> debugger I am not, but
> I have found a 'few' trivial ones.  If I got credit for 
> bloodshot eyes and
> pist off girl friends you might actually get a sense of how 
> much time I
> spend trying to make a contribution.
> 
> I think I tend to frustrate poor Robert as much as make a valid
> contribution.
> 
> I never coded a stitch in my life, til 3 months ago.  I am a 
> mere pup among
> men (yet I'm probably older then most of you, don't ask).
> 
> 
> 
> 
> ----- Original Message -----
> From: "Pascal" <pb...@oi...>
> To: <dyn...@li...>
> Sent: Wednesday, January 10, 2001 3:12 AM
> Subject: RE: [Dynapi-Dev] Issues, remaining
> 
> 
> > I agree on the tutors and reference not being uptodate.. 
> the tutorial is
> > something I can easily fix (and might do this weekend, if I 
> find the time)
> > but the dev-reference is something almost everyone on this 
> list can do..
> > just take out that which is Dynacore specific (i.e.: not 
> found in DynAPI)
> > and  copy and paste all that is under DynObject to the DynLayer and
> > DynDocument objects.
> >
> > I just feel its a sad thing that there are so many people 
> on this list,
> alot
> > of which are "complaining" about bugs not being fixed, not much
> > documentation being available, and those people fail to contribute
> anything
> > as simple as copy-and-pasting text.
> >
> > anyway, for a few widget examples look at the widgets with 
> the dynacore
> > release, they use the precreate event (very basic stuff 
> actually..just
> > replace the old oncreate  with onprecreate, and make the 
> listener not part
> > of the prototype but part of the constructor)
> >
> > Please don't take this mail as an attack or anything (definetly not
> personal
> > to you Raymond), but everyone, please don't be shy to contribute
> anything..
> > it's opensource, and we all had to learn (and are still 
> learning) this
> > "thing" at one point.  Stuff like widget creation is such a 
> simple task
> you
> > only need the idea (see any GUI for ideas) and basic knowledge of
> > DynAPI/javascript (see tutorials).
> >
> > cya (and have fun :),
> >
> > Pascal Bestebroer (pb...@oi...)
> > Software ontwikkelaar
> > Oberon Informatiesystemen b.v.
> > http://www.oibv.com
> >
> > > -----Oorspronkelijk bericht-----
> > > Van: dyn...@li...
> > > [mailto:dyn...@li...]Namens 
> Raymond Smith
> > > Verzonden: woensdag 10 januari 2001 11:18
> > > Aan: dyn...@li...
> > > Onderwerp: Re: [Dynapi-Dev] Issues, remaining
> > >
> > >
> > > Currently, there are not alot of good representations of
> > > precreate in the
> > > widgets.  The ButtonImage doesn't use it and doesn't work 
> in IE or NS.
> > > Others say they will be updated.  The only technical writing
> > > on it can be
> > > found in your docs and build for Dynacore or one prior post
> > > from Dan on
> > > 'lots of changes'.  All the docs here date back to November
> > > and the last
> > > time you updated them.
> > >
> > > The viewport is a child layer, maybe that explains why the
> > > events don't
> > > fire.  Yet the images in the widget themselves change.  The
> > > event related to
> > > the viewport isn't even part of a widget, but defined in 
> the onLoad()
> > > section of the webpage.
> > >
> > > Eventually enough will leach out (or in) that I will 
> understand it.
> > >
> > > Cheers
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > 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] Issues, remaining

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

I contribute to the level of my abilty.  And a master debugger I am not, but
I have found a 'few' trivial ones.  If I got credit for bloodshot eyes and
pist off girl friends you might actually get a sense of how much time I
spend trying to make a contribution.

I think I tend to frustrate poor Robert as much as make a valid
contribution.

I never coded a stitch in my life, til 3 months ago.  I am a mere pup among
men (yet I'm probably older then most of you, don't ask).




----- Original Message -----
From: "Pascal" <pb...@oi...>
To: <dyn...@li...>
Sent: Wednesday, January 10, 2001 3:12 AM
Subject: RE: [Dynapi-Dev] Issues, remaining


> I agree on the tutors and reference not being uptodate.. the tutorial is
> something I can easily fix (and might do this weekend, if I find the time)
> but the dev-reference is something almost everyone on this list can do..
> just take out that which is Dynacore specific (i.e.: not found in DynAPI)
> and  copy and paste all that is under DynObject to the DynLayer and
> DynDocument objects.
>
> I just feel its a sad thing that there are so many people on this list,
alot
> of which are "complaining" about bugs not being fixed, not much
> documentation being available, and those people fail to contribute
anything
> as simple as copy-and-pasting text.
>
> anyway, for a few widget examples look at the widgets with the dynacore
> release, they use the precreate event (very basic stuff actually..just
> replace the old oncreate  with onprecreate, and make the listener not part
> of the prototype but part of the constructor)
>
> Please don't take this mail as an attack or anything (definetly not
personal
> to you Raymond), but everyone, please don't be shy to contribute
anything..
> it's opensource, and we all had to learn (and are still learning) this
> "thing" at one point.  Stuff like widget creation is such a simple task
you
> only need the idea (see any GUI for ideas) and basic knowledge of
> DynAPI/javascript (see tutorials).
>
> cya (and have fun :),
>
> Pascal Bestebroer (pb...@oi...)
> Software ontwikkelaar
> Oberon Informatiesystemen b.v.
> http://www.oibv.com
>
> > -----Oorspronkelijk bericht-----
> > Van: dyn...@li...
> > [mailto:dyn...@li...]Namens Raymond Smith
> > Verzonden: woensdag 10 januari 2001 11:18
> > Aan: dyn...@li...
> > Onderwerp: Re: [Dynapi-Dev] Issues, remaining
> >
> >
> > Currently, there are not alot of good representations of
> > precreate in the
> > widgets.  The ButtonImage doesn't use it and doesn't work in IE or NS.
> > Others say they will be updated.  The only technical writing
> > on it can be
> > found in your docs and build for Dynacore or one prior post
> > from Dan on
> > 'lots of changes'.  All the docs here date back to November
> > and the last
> > time you updated them.
> >
> > The viewport is a child layer, maybe that explains why the
> > events don't
> > fire.  Yet the images in the widget themselves change.  The
> > event related to
> > the viewport isn't even part of a widget, but defined in the onLoad()
> > section of the webpage.
> >
> > Eventually enough will leach out (or in) that I will understand it.
> >
> > Cheers
> >
> >
> >
> >
> >
> > _______________________________________________
> > 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] [Bug #128155] Overriding setHTML method in sub class of DynLayer problem

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

haven't been following it to closely, but I think this is what you need:


function MyWidget(name,x,y,w,h,color) {
	... <snip> ...
	this.DynLayer = DynLayer
	this.DynLayer(null,x,y,w,h,color);

	this.canvas = new
DynLayer(null,10,10,this.getWidth()-20,this.getHeight()-20,'#c0c0c0');
	this.addChild(this.canvas);
 	return this;
};
MyWidget.prototype=new DynLayer();
MyWidget.prototype.MyWidgetsetHTML=DynLayer.prototype.setHTML
MyWidget.prototype.setHTML=function(html,noevt) {
	if (!this.created) this.MyWidgetsetHTML(html,noevt)
	else this.canvas.setHTML(html,noevt);
};
MyWidget.prototype.MyWidgetgetHTML=DynLayer.prototype.getHTML
MyWidget.prototype.getHTML=function(html,noevt) {
	if (!this.created) return this.MyWidgetgetHTML()
	else return this.canvas.getHTML();
};


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

RE: [Dynapi-Dev] Issues, remaining

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

I agree on the tutors and reference not being uptodate.. the tutorial is
something I can easily fix (and might do this weekend, if I find the time)
but the dev-reference is something almost everyone on this list can do..
just take out that which is Dynacore specific (i.e.: not found in DynAPI)
and  copy and paste all that is under DynObject to the DynLayer and
DynDocument objects.

I just feel its a sad thing that there are so many people on this list, alot
of which are "complaining" about bugs not being fixed, not much
documentation being available, and those people fail to contribute anything
as simple as copy-and-pasting text.

anyway, for a few widget examples look at the widgets with the dynacore
release, they use the precreate event (very basic stuff actually..just
replace the old oncreate  with onprecreate, and make the listener not part
of the prototype but part of the constructor)

Please don't take this mail as an attack or anything (definetly not personal
to you Raymond), but everyone, please don't be shy to contribute anything..
it's opensource, and we all had to learn (and are still learning) this
"thing" at one point.  Stuff like widget creation is such a simple task you
only need the idea (see any GUI for ideas) and basic knowledge of
DynAPI/javascript (see tutorials).

cya (and have fun :),

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

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Raymond Smith
> Verzonden: woensdag 10 januari 2001 11:18
> Aan: dyn...@li...
> Onderwerp: Re: [Dynapi-Dev] Issues, remaining
>
>
> Currently, there are not alot of good representations of
> precreate in the
> widgets.  The ButtonImage doesn't use it and doesn't work in IE or NS.
> Others say they will be updated.  The only technical writing
> on it can be
> found in your docs and build for Dynacore or one prior post
> from Dan on
> 'lots of changes'.  All the docs here date back to November
> and the last
> time you updated them.
>
> The viewport is a child layer, maybe that explains why the
> events don't
> fire.  Yet the images in the widget themselves change.  The
> event related to
> the viewport isn't even part of a widget, but defined in the onLoad()
> section of the webpage.
>
> Eventually enough will leach out (or in) that I will understand it.
>
> Cheers
>
>
>
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>

RE: [Dynapi-Dev] [Bug #128263] PathAnimation.stopAnimation() bug (& patch)

[<ma...@ab...>]

wouldn't it be better to add a noevt-parameter to stopAnimation():

PathAnimation.prototype.stopAnimation = function (noevt) {
	if (this.pathPlaying && this.pathPlaying.resets && !this.cancelThread &&
this.dlyr!=null) this.dlyr.moveTo(this.pathPlaying[0],this.pathPlaying[1]);
	this.stop();
	delete this.pathPlaying;  // only deletes unstored path
	this.playing = false;
	if (this.dlyr != null && noevt!=false) this.dlyr.invokeEvent("pathstop");
};

and maybe use stopAnimationNow() just to do a stopAnimation(false) -call

PathAnimation.prototype.stopAnimationNow=function() {
	this.stopAnimation(false);
}


/mrtin


> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]On Behalf Of Raymond
> Smith
> Sent: den 10 januari 2001 11:36
> To: dyn...@li...
> Subject: Re: [Dynapi-Dev] [Bug #128263] PathAnimation.stopAnimation()
> bug (& patch)
>
>
> I'm for including  the 'PathAnimation.prototype.stopAnimationNow ' method
> Richard discussed.  If your doing chained animations that lead to other
> events it's a must have.  Or the whole thing repeats again.
>
>
> ----- Original Message -----
> From: "Richard :o" <ma...@ri...>
> To: <dyn...@li...>
> Sent: Tuesday, January 09, 2001 2:32 AM
> Subject: Re: [Dynapi-Dev] [Bug #128263]
> PathAnimation.stopAnimation() bug (&
> patch)
>
>
> > Hi,
> > I'm glad to see pathanim tackled at last.What you're sayng is
> correct, and
> > is what I did in my modified pathanim (see:
> > http://www.resass.f2s.com/?menu=examples&node=1  or
> > http://www.richardinfo.f2s.com/?menu=examples&node=1
> > under "dynapi.util.pathanim.chained.html" when the servers up again)
> >
> > But I also had to add the method stopAnimation now() , which is
> identical,
> > but without
> > invoke-ing pathstop, so the animation could be manually halted without
> > starting the next one from the onpathstop listener:
> >
> > PathAnimation.prototype.stopAnimationNow = function () {
> >  if (this.pathPlaying && this.pathPlaying.resets &&
> !this.cancelThread &&
> > this.dlyr!=null)
> this.dlyr.moveTo(this.pathPlaying[0],this.pathPlaying[1]);
> >  this.stop();
> >  delete this.pathPlaying;  // only deletes unstored path
> >  this.playing = false;
> > };
> >  And I don't understand why slideBy() has been scrapped just because you
> can
> > do that manually aswell; you can do most of the
> > API manually, but it's easier if you can just call a method.
> And we still
> > use moveBy(), so slideBy() keeps consistency, and saves
> changing existing
> > webcode when you upgrade you're API.
> >
> > DynLayer.prototype.slideBy = function(x,y,inc,ms) {
> >  if (x==null) x = 0;
> >  if (y==null) y = 0;
> >  this.slideTo(this.x+x,this.y+y,inc,ms);
> > };
> >
> > Cheers,
> > Richard  :o
> >
> > ma...@ri...
> > www.richardinfo.com
> > (Everything running on, and ported to the 19/12/2000 snapshot
> of DynAPI2)
> >
> > ----- Original Message -----
> > From: <no...@so...>
> > To: <ma...@ab...>; <no...@so...>;
> > <dyn...@so...>
> > Sent: Wednesday, January 10, 2001 9:30 AM
> > Subject: [Dynapi-Dev] [Bug #128263] PathAnimation.stopAnimation() bug (&
> > patch)
> >
> >
> > > Bug #128263, was updated on 2001-Jan-10 00:30
> > > Here is a current snapshot of the bug.
> > >
> > > Project: DynAPI 2
> > > Category: API Extentions
> > > Status: Open
> > > Resolution: None
> > > Bug Group: None
> > > Priority: 5
> > > Submitted by: marstr
> > > Assigned to : nobody
> > > Summary: PathAnimation.stopAnimation() bug (& patch)
> > >
> > > Details: dynapi/util/pathanim.js
> > >
> > > a bug in PathAnimation.stopAnimation() causes the onpathstop-event to
> fire
> > > before some values were set
> > > (this.playing=false)
> > > before you couldn't slide a DynLayer directly in a
> > > onpathstop eventListener (while this.playing still
> > > was true)
> > >
> > > i've moved the line
> > > if (this.dlyr != null) this.dlyr.invokeEvent("pathstop");
> > >
> > > last in the method which solved the problem
> > >
> > > PathAnimation.prototype.stopAnimation = function () {
> > > if (this.pathPlaying && this.pathPlaying.resets &&
> !this.cancelThread &&
> > > this.dlyr!=null)
> > > this.dlyr.moveTo(this.pathPlaying[0],this.pathPlaying[1]);
> > > this.stop();
> > > delete this.pathPlaying;  // only deletes unstored path
> > > this.playing = false;
> > > if (this.dlyr != null) this.dlyr.invokeEvent("pathstop");
> > > };
> > >
> > > For detailed info, follow this link:
> > >
http://sourceforge.net/bugs/?func=detailbug&bug_id=128263&group_id=5757
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/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/mailman/listinfo/dynapi-dev
>


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

Re: [Dynapi-Dev] [Bug #128263] PathAnimation.stopAnimation() bug (& patch)

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

I'm for including  the 'PathAnimation.prototype.stopAnimationNow ' method
Richard discussed.  If your doing chained animations that lead to other
events it's a must have.  Or the whole thing repeats again.


----- Original Message -----
From: "Richard :o" <ma...@ri...>
To: <dyn...@li...>
Sent: Tuesday, January 09, 2001 2:32 AM
Subject: Re: [Dynapi-Dev] [Bug #128263] PathAnimation.stopAnimation() bug (&
patch)


> Hi,
> I'm glad to see pathanim tackled at last.What you're sayng is correct, and
> is what I did in my modified pathanim (see:
> http://www.resass.f2s.com/?menu=examples&node=1  or
> http://www.richardinfo.f2s.com/?menu=examples&node=1
> under "dynapi.util.pathanim.chained.html" when the servers up again)
>
> But I also had to add the method stopAnimation now() , which is identical,
> but without
> invoke-ing pathstop, so the animation could be manually halted without
> starting the next one from the onpathstop listener:
>
> PathAnimation.prototype.stopAnimationNow = function () {
>  if (this.pathPlaying && this.pathPlaying.resets && !this.cancelThread &&
> this.dlyr!=null)
this.dlyr.moveTo(this.pathPlaying[0],this.pathPlaying[1]);
>  this.stop();
>  delete this.pathPlaying;  // only deletes unstored path
>  this.playing = false;
> };
>  And I don't understand why slideBy() has been scrapped just because you
can
> do that manually aswell; you can do most of the
> API manually, but it's easier if you can just call a method. And we still
> use moveBy(), so slideBy() keeps consistency, and saves changing existing
> webcode when you upgrade you're API.
>
> DynLayer.prototype.slideBy = function(x,y,inc,ms) {
>  if (x==null) x = 0;
>  if (y==null) y = 0;
>  this.slideTo(this.x+x,this.y+y,inc,ms);
> };
>
> Cheers,
> Richard  :o
>
> ma...@ri...
> www.richardinfo.com
> (Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2)
>
> ----- Original Message -----
> From: <no...@so...>
> To: <ma...@ab...>; <no...@so...>;
> <dyn...@so...>
> Sent: Wednesday, January 10, 2001 9:30 AM
> Subject: [Dynapi-Dev] [Bug #128263] PathAnimation.stopAnimation() bug (&
> patch)
>
>
> > Bug #128263, was updated on 2001-Jan-10 00:30
> > Here is a current snapshot of the bug.
> >
> > Project: DynAPI 2
> > Category: API Extentions
> > Status: Open
> > Resolution: None
> > Bug Group: None
> > Priority: 5
> > Submitted by: marstr
> > Assigned to : nobody
> > Summary: PathAnimation.stopAnimation() bug (& patch)
> >
> > Details: dynapi/util/pathanim.js
> >
> > a bug in PathAnimation.stopAnimation() causes the onpathstop-event to
fire
> > before some values were set
> > (this.playing=false)
> > before you couldn't slide a DynLayer directly in a
> > onpathstop eventListener (while this.playing still
> > was true)
> >
> > i've moved the line
> > if (this.dlyr != null) this.dlyr.invokeEvent("pathstop");
> >
> > last in the method which solved the problem
> >
> > PathAnimation.prototype.stopAnimation = function () {
> > if (this.pathPlaying && this.pathPlaying.resets && !this.cancelThread &&
> > this.dlyr!=null)
> > this.dlyr.moveTo(this.pathPlaying[0],this.pathPlaying[1]);
> > this.stop();
> > delete this.pathPlaying;  // only deletes unstored path
> > this.playing = false;
> > if (this.dlyr != null) this.dlyr.invokeEvent("pathstop");
> > };
> >
> > For detailed info, follow this link:
> > http://sourceforge.net/bugs/?func=detailbug&bug_id=128263&group_id=5757
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/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/mailman/listinfo/dynapi-dev
>

Re: [Dynapi-Dev] [Bug #128263] PathAnimation.stopAnimation() bug (& patch)

[Richard :o <ma...@ri...>]

Hi,
I'm glad to see pathanim tackled at last.What you're sayng is correct, and
is what I did in my modified pathanim (see:
http://www.resass.f2s.com/?menu=examples&node=1  or
http://www.richardinfo.f2s.com/?menu=examples&node=1
under "dynapi.util.pathanim.chained.html" when the servers up again)

But I also had to add the method stopAnimation now() , which is identical,
but without
invoke-ing pathstop, so the animation could be manually halted without
starting the next one from the onpathstop listener:

PathAnimation.prototype.stopAnimationNow = function () {
 if (this.pathPlaying && this.pathPlaying.resets && !this.cancelThread &&
this.dlyr!=null) this.dlyr.moveTo(this.pathPlaying[0],this.pathPlaying[1]);
 this.stop();
 delete this.pathPlaying;  // only deletes unstored path
 this.playing = false;
};
 And I don't understand why slideBy() has been scrapped just because you can
do that manually aswell; you can do most of the
API manually, but it's easier if you can just call a method. And we still
use moveBy(), so slideBy() keeps consistency, and saves changing existing
webcode when you upgrade you're API.

DynLayer.prototype.slideBy = function(x,y,inc,ms) {
 if (x==null) x = 0;
 if (y==null) y = 0;
 this.slideTo(this.x+x,this.y+y,inc,ms);
};

Cheers,
Richard  :o

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

----- Original Message -----
From: <no...@so...>
To: <ma...@ab...>; <no...@so...>;
<dyn...@so...>
Sent: Wednesday, January 10, 2001 9:30 AM
Subject: [Dynapi-Dev] [Bug #128263] PathAnimation.stopAnimation() bug (&
patch)


> Bug #128263, was updated on 2001-Jan-10 00:30
> Here is a current snapshot of the bug.
>
> Project: DynAPI 2
> Category: API Extentions
> Status: Open
> Resolution: None
> Bug Group: None
> Priority: 5
> Submitted by: marstr
> Assigned to : nobody
> Summary: PathAnimation.stopAnimation() bug (& patch)
>
> Details: dynapi/util/pathanim.js
>
> a bug in PathAnimation.stopAnimation() causes the onpathstop-event to fire
> before some values were set
> (this.playing=false)
> before you couldn't slide a DynLayer directly in a
> onpathstop eventListener (while this.playing still
> was true)
>
> i've moved the line
> if (this.dlyr != null) this.dlyr.invokeEvent("pathstop");
>
> last in the method which solved the problem
>
> PathAnimation.prototype.stopAnimation = function () {
> if (this.pathPlaying && this.pathPlaying.resets && !this.cancelThread &&
> this.dlyr!=null)
> this.dlyr.moveTo(this.pathPlaying[0],this.pathPlaying[1]);
> this.stop();
> delete this.pathPlaying;  // only deletes unstored path
> this.playing = false;
> if (this.dlyr != null) this.dlyr.invokeEvent("pathstop");
> };
>
> For detailed info, follow this link:
> http://sourceforge.net/bugs/?func=detailbug&bug_id=128263&group_id=5757
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/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] [Bug #128263] PathAnimation.stopAnimation() bug (& patch)

[<no...@so...>]

Bug #128263, was updated on 2001-Jan-10 00:30
Here is a current snapshot of the bug.

Project: DynAPI 2
Category: API Extentions
Status: Open
Resolution: None
Bug Group: None
Priority: 5
Submitted by: marstr
Assigned to : nobody
Summary: PathAnimation.stopAnimation() bug (& patch)

Details: dynapi/util/pathanim.js

a bug in PathAnimation.stopAnimation() causes the onpathstop-event to fire
before some values were set
(this.playing=false)
before you couldn't slide a DynLayer directly in a
onpathstop eventListener (while this.playing still
was true)

i've moved the line 
if (this.dlyr != null) this.dlyr.invokeEvent("pathstop");

last in the method which solved the problem

PathAnimation.prototype.stopAnimation = function () {
	if (this.pathPlaying && this.pathPlaying.resets && !this.cancelThread &&
this.dlyr!=null)
this.dlyr.moveTo(this.pathPlaying[0],this.pathPlaying[1]);
	this.stop();
	delete this.pathPlaying;  // only deletes unstored path
	this.playing = false;
	if (this.dlyr != null) this.dlyr.invokeEvent("pathstop");
};

Follow-Ups:

Date: 2001-Jan-10 02:27
By: nobody

Comment:
Hi,
I'm glad to see pathanim tackled at last.What you're sayng is correct, and
is what I did in my modified pathanim (see:
http://www.resass.f2s.com/?menu=examples&node=1  or
http://www.richardinfo.f2s.com/?menu=examples&node=1 
under "dynapi.util.pathanim.chained.html" when the servers up again)

But I also had to add the method stopAnimation now() , which is identical,
but without
invoke-ing pathstop, so the animation could be manually halted without
starting the next one from the onpathstop listener:

PathAnimation.prototype.stopAnimationNow = function () {  
 if (this.pathPlaying && this.pathPlaying.resets && !this.cancelThread &&
this.dlyr!=null)
this.dlyr.moveTo(this.pathPlaying[0],this.pathPlaying[1]);
 this.stop();
 delete this.pathPlaying;  // only deletes unstored path
 this.playing = false;
};
 And I don't understand why slideBy() has been scrapped just because you
can do that manually aswell; you can do most of the 
API manually, but it's easier if you can just call a method. And we still
use moveBy(), so slideBy() keeps consistency, and saves changing existing
webcode when you upgrade you're API.

DynLayer.prototype.slideBy = function(x,y,inc,ms) { 
 if (x==null) x = 0;
 if (y==null) y = 0;
 this.slideTo(this.x+x,this.y+y,inc,ms);
};

Cheers,
Richard  :o

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

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=128263&group_id=5757

Re: [Dynapi-Dev] [Bug #128155] Overriding setHTML method in sub class of DynLayer problem

[<cam...@ya...>]

Hi,

I sent a reply to this yesterday, but it bounced
because I attached the Javascipt file. This time I've
pasted it in...

>Can you give an example of your custom method. 
>If you place a check
>for "this.created==true", it should stop it from
>executing during the initial
>creation stage.

I'm defining setHTML as a prototype in my widget
definition. I'm not sure how I can do a
this.created==true test on a prototype definition.

I thought perhaps I shouldn't be overriding setHTML,
but I was looking at IllMaestro's widget's yesterday,
and his window widget also overrides setHTML. I'd be
interested to hear if anyone has tried these widgets
with the latest API.

Anyway, here's some example code so you can see the
problem:

mywidget.js
-----------------------
function MyWidget(name,x,y,w,h,color) {
	x = x || 0;
	y = y || 0;
	w = w || 300;
	h = h || 200;
	color = color || '#ffffff';

	this.DynLayer = DynLayer
	this.DynLayer(null,x,y,w,h,color);

	this.canvas = new
DynLayer(null,10,10,this.getWidth()-20,this.getHeight()-20,'#c0c0c0');
	this.addChild(this.canvas);
	return this;
};
MyWidget.prototype=new DynLayer();
MyWidget.prototype.setHTML=function(html,noevt) {
	this.canvas.setHTML(html,noevt);
};
MyWidget.prototype.getHTML=function(html,noevt) {
	return this.canvas.getHTML();
};
------------------

mywidget.html
------------------
<html>
<head>
<script language="Javascript"
src="../src/dynapi.js"></script>
<script language="Javascript">
DynAPI.setLibraryPath('../src/lib/');
DynAPI.include('dynapi.api.*');
</script>
<script language="Javascript"
src="mywidget.js"></script>
<script language="Javascript">

DynAPI.onLoad = function() {
	myLayer = new MyWidget()
	myLayer.setBgColor('#000000')
	myLayer.moveTo(100,100)
	myLayer.setHTML('this is the canvas')
	DynAPI.document.addChild(myLayer)
}

</script>
</head>
<body bgcolor="#ffffff">
</body>
</html>
---------------

__________________________________________________
Do You Yahoo!?
Yahoo! Photos - Share your holiday photos online!
http://photos.yahoo.com/

Re: [Dynapi-Dev] Issues, remaining

[Jordi 'I. M. <jmi...@or...>]

Oops, I meant UNTIL this morning

Jordi 'IlMaestro' Ministral wrote:

> I have not been able to use CVS since this morning.

Re: [Dynapi-Dev] Issues, remaining

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

Currently, there are not alot of good representations of precreate in the
widgets.  The ButtonImage doesn't use it and doesn't work in IE or NS.
Others say they will be updated.  The only technical writing on it can be
found in your docs and build for Dynacore or one prior post from Dan on
'lots of changes'.  All the docs here date back to November and the last
time you updated them.

The viewport is a child layer, maybe that explains why the events don't
fire.  Yet the images in the widget themselves change.  The event related to
the viewport isn't even part of a widget, but defined in the onLoad()
section of the webpage.

Eventually enough will leach out (or in) that I will understand it.

Cheers

Re: [Dynapi-Dev] Issues, remaining

[Jordi 'I. M. <jmi...@or...>]

I have not been able to use CVS since this morning. SSH was giving a warning
about some hacker doing a man-in-the-middle attack. This morning I spoke to
my admin and found out that he had changed the network's configuration so
now there's a Linux machine rounting all traffic. ( The man in-the-middle ).
sigh....

Ok, on to the point. As usual when I wait too much before updating my API's
version when I do I don't recognize the code. ( Even mine ). One good thing
about being a web developer is that I can spend the whole day debugging the
API and still I'm doing my job :)

I'm trying to fix the label and button widgets in the hope that this will
lead to fix many other bugs. Now, tracking down one of these pestering
event-not-happening bugs I've reached this place inside event.js

 if (is.ns4 && is.platform=="other" && type=="mouseup")
this.invokeEvent("click",e);

I'm reasonabily sure that this -is.platform- condition should not be there.
Coded that way, click events only fire when you're running a Linux/Unix
Netscape, don't they ? By removing the condition, the button widget worked
fine in NS( did you notice that clicking the text in the button was causing
the button to animate but the resizing did not happen ? ). IE, as Pascal
already stated, has another problem.

I don't want to directly update CVS with this change because I have a
terrible feeling that this code was placed there because some platform issue
and I may have broken something else. Would the person that coded that
condition please tell me if it is a mistake or not ?

Another issue. Same function, several lines before:

if (is.ns4 && is.platform=="other") {
  if (type=="mousedown") {
   if (this.dbltimer!=null) type="dblclick";
   else this.dbltimer=setTimeout(this+'.dbltimer=null',300);
  }
 }

Again it seems that Win NS won't fire any doubleclick events. Since this
code has been there since Dan's first DynAPI2 release and whenever I remove
it, it reappears again, my best guesses are:

- 1: The condition should be platform!='other'. I know that win NS handles
doubleclick events correctly ( I've tryed removing the condition and did
well ). Then maybe some Linux/Unix doesn't but the condition is miswritten.

- 2: There's something that I have missed and dblclick events under Windows
are handled in another way.

- 3: I'm dumb

I'll continue to investigate ( I will dedicate the rest of the day to debug
this release )  In the meantime it would be useful if you all posted all the
bugs you can think of so I don't forget something.


----


I like OOP as much as anyone and I do recognize the benefits of modularity,
classes, inheritance, etc, etc. However, we must keep in mind that sometimes
the ground we're steping is not solid enought to build a skyscraper on top
of it. I understand that programming Delphy and such is easier, and I do
understant that JAVA's object model is cool and scalable and you can reuse
code but, how many years did it took until technology was mature enought to
support things as abstract and platform-independant as JAVA ( I lived the
old ASM days, one mistake-one reboot, registers, pointers.... ) ? Concepts
such as code size still count. You may have a fast connection but still a
website 10k smaller is a better website.

Lots more will be said.

[Dynapi-Dev] [Bug #128263] PathAnimation.stopAnimation() bug (& patch)

[<no...@so...>]

Bug #128263, was updated on 2001-Jan-10 00:30
Here is a current snapshot of the bug.

Project: DynAPI 2
Category: API Extentions
Status: Open
Resolution: None
Bug Group: None
Priority: 5
Submitted by: marstr
Assigned to : nobody
Summary: PathAnimation.stopAnimation() bug (& patch)

Details: dynapi/util/pathanim.js

a bug in PathAnimation.stopAnimation() causes the onpathstop-event to fire
before some values were set
(this.playing=false)
before you couldn't slide a DynLayer directly in a
onpathstop eventListener (while this.playing still
was true)

i've moved the line 
if (this.dlyr != null) this.dlyr.invokeEvent("pathstop");

last in the method which solved the problem

PathAnimation.prototype.stopAnimation = function () {
	if (this.pathPlaying && this.pathPlaying.resets && !this.cancelThread &&
this.dlyr!=null)
this.dlyr.moveTo(this.pathPlaying[0],this.pathPlaying[1]);
	this.stop();
	delete this.pathPlaying;  // only deletes unstored path
	this.playing = false;
	if (this.dlyr != null) this.dlyr.invokeEvent("pathstop");
};

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=128263&group_id=5757

RE: [Dynapi-Dev] New OOJS

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

Uhm, not sure where your heading here.. but the DynAPI is an API, yes.. that
has nothing to do with class or object based languages.

The DynAPI is just sitting in the middle of your own code and the browsers
DOM. That's all an API should do. Why (how) are we using it as a language?

I don't see what you want to create with your OOJS, you'r actually creating
another "layer"? So eventually we'll have something like your OOJS,
interfacing to DynAPI code, which is interfacting thru Javascript with the
DOM..

If you want to see how the DynAPI could be turned into more OOP like
behaviour take a look at Dynacore.. that's basically the object model your
referring to. With DynObject being the base (containing the
add/remove/delete functionality) and DynLayer and DynDocument inheriting
from that.

What your describing with your TComponent (to much Delphi here :) is
basically any widget we created upto now, but in the way that Javascript
works: (chain)prototyping.  This means we're again at the widget-model
problem here (as I've also read a post about the superclass again) and I'm
getting a bit tiered of having to explain everytime that prototyping is the
way Javascript works, and that all the inheriting is working perfectly
without adding extra code (or using more memory, because prototyping does
not COPY the methods, but simply referes to them.. like a Delphi
pointer/handle)

How would your TComponent look.. like this:

function TComponent() {
	this.canvas=new DynLayer
	this.canvas()

	return this
}

and widgets:

function TButton() {
	this.component=new TComponent
	this.component()

	return this
}

Which is basically adding an extra level TComponent, which might contain
some general code for all widgets, but since I can think of alot of widgets
that are not using "general" GUI ideas the TComponent would add
functionality that the widget wouldn't use.


So please show me some of your ideas in code, and tell me what the
advantages are (not the differences, but the advantages).

cya (back to work :)

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

> Eytan Heidingsfeld wrote:
>
> > Like I have mentioned many times before I don't like how
> DynAPI is used. It
> > is an API not a language, but I'm getting ahead of myself.
> Let's start at
> > the beginning. In the beginning there is JS. Problem number
> one is that JS
> > is class oriented  and not object oriented therefore the
> "weird" inheriting.
> > That problem was later solved by my Inherit method. Problem
> Number two is
> > that although it is a program language that is class
> oriented it doesn't
> > give you the necesary building blocks to use it correctly.
> Because of this
> > reason I decided to write the OOJS (Object Oriented Java
> Script). Before I
> > explain my ideas for how when and where (which you are free and are
> > encouraged to criticize) I will warn you that unlike JS
> which is a scrambled
> > mix of Java, C and some other languages this OOJS is Delphi
> like in syntax.
> > The reason for this is that when I started I was doing this
> for a certain
> > project which I would be working on with Delphi
> programmers. Now for the
> > OOJS.
> >
> > First of all you have the most base object TObject. All
> objects inherit from
> > it! It includes a small amount of properties and methods
> including a create
> > and a destroy (and there events). Then you have TComponent.
> TComponent is
> > the base class used for visual objects. How does it work.
> It uses the DynAPI
> > as I think it is supposed to be used, as an API. That means
> that I have a
> > DynLayer as a private variable. Then I have methods as such
> DrawComponent,
> > Draw and events such as onPaint or onRefresh. Then if you
> want to create
> > your visual component all you have to do is inherit from
> TComponent and call
> > the correct methods. As you may have noticed the event structure is
> > different too. It is like in Delphi (big surprise) you
> define a type which
> > is basically a definition of a procedure then you implement
> it and set a
> > property of your object with this procedure and when the
> object wants to
> > invoke it calls its property for the event.
> >
> > This is just the beginning and I know it is very jumbled.
> By tomorrow I will
> > send out the basic code I have till now and anyone who is
> interested in
> > helping please email me.
> >
> > Work needed to be done:
> > A. Finish fixing up base types
> > B. Rewrite DynDocument to a new type called TApplication
> (no biggie since
> > DynDocument is 80 lines)
> > C. Start converting objects from the library to the new
> OOJS model (easy
> > enough once model is done)
> >
> > Any Takers,
> >
> > Thanx,
> > 8an
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>

RE: [Dynapi-Dev] [Bug #128146] netscape addChild() bug

[<ma...@ab...>]

yes it solved the problem.
can you update CVS? currently i 
havent got cvs to work except anonymous-read-access.

update in dynlayer.js line #75 and #272 (in my version that is..)

/martin

> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]On Behalf Of Robert
> Rainwater
> Sent: den 9 januari 2001 17:31
> To: DynAPI Development List
> Subject: Re: [Dynapi-Dev] [Bug #128146] netscape addChild() bug
> 
> 
> 
> A possible fix is to use:
> 
> if (dlyr.clip)
> 
> That should fix the problem I think.
> 
> -- 
> // Robert Rainwater
> 
> On 1/9/2001, 3:50:22 AM EST, noreply wrote about "[Dynapi-Dev] 
> [Bug #128146] netscape addChild() bug":
> 
> > Bug #128146, was updated on 2001-Jan-09 00:50
> > Here is a current snapshot of the bug.
> 
> > Project: DynAPI 2
> > Category: Core API
> > Status: Open
> > Resolution: None
> > Bug Group: None
> > Priority: 5
> > Submitted by: nobody
> > Assigned to : nobody
> > Summary: netscape addChild() bug
> 
> > Details: this basic code: 
> 
> > DynAPI.onLoad=function() {
> >   lay = new DynLayer(null,0,0,280,12,'red');
> >   DynAPI.document.addChild(lay);
> > };
> 
> > doesn't work under netscape 4.76.
> > ("clip is not defined. ")
> 
> > this is because the clip-check on line 75 (im using
> > the latest files from cvs):
> 
> > if (dlyr.clip!=null) {
> 
> > isn't correct, dlyr.clip is undefined when i check the value.
> 
> > line 272 has the same problems, dlyr.clip is undefined
> > but it only checks for null
> 
> > maybe a possible fix would be:
> 
> > if (dlyr.clip!=null && typeof dlyr.clip!='undefined') {
> 
> 
> 
> 
> > For detailed info, follow this link:
> > http://sourceforge.net/bugs/?func=detailbug&bug_id=128146&group_id=5757
> 
> > _______________________________________________
> > 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] Issues, remaining

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

1) events work correctly, only event code not working is mouse events on
child layers in IE5.5..  Please make sure that your widget is using the
correct way (i.e. precreation events.. see other widgets for more info)

2) no clue.. haven't looked at it

3) not a label issue, but a child-event issue only happening in IE5.5

4) no clue.

cya,

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

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Raymond Smith
> Verzonden: dinsdag 9 januari 2001 23:28
> Aan: dyn...@li...
> Onderwerp: [Dynapi-Dev] Issues, remaining
>
>
> These are remaining issues, that I know of.
>
> 1) Event problems.  None of my widgets 'on mouseover' work
> right now in IE
> or NS since precreation was introduced.  If you test
> ButtonImage you can see
> what I mean.  Also, this widget is throwing an error at line
> 49 (I believe)
> in NS.  Line 49 is related to setImage with a boolean for
> checkbox vs not a
> check box.
>
> This might be related to removal of get.component methods.
> Worked in IE til
> I updated them to the new methods.  But I am not sure what
> replaced this, so
> I have to go back and read up on alot of code I am unfamiliar with.
>
> 2) Scrollpane currently doesn't render knobs and bars in
> IE5.5 on Inw ME.
> Works fine in NS.
>
> 3) Select text Label issues (ie) in child elements.  Pascal
> mentioned he was
> working on this last night.
>
> 4) Hard to explain this one but it might provide clues as to
> where to look.
> I had a viewport widget with an oversized image element
> (content).  I used a
> series of moveTo's to window a portion of the element in a
> viewport.  All
> worked wonderous til recent updates, now moveTo does nothing.
>  I fixed this
> by dumping the viewport and using a clipped dynlayer with
> moveTo's.  Might
> be related to auto-size detection, just a guess.
>
> Later
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>

Re: [Dynapi-Dev] W3C DOCTYPE interferes with DynAPI

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

FWIW, the DOCTYPE declaration forces NS6 to run in either normal,
'quirks', or 'strict' mode.  Never mind what that means.

For best results, either use 'strict' or no DOCTYPE at all.  It won't
validate, but who cares?

scottandrew

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

RE: [Dynapi-Dev] W3C DOCTYPE interferes with DynAPI

[William L. <wil...@ve...>]

Same thing happens on IE5 Mac, but you get vague error messages (ie. error
on line 600, but your document only has 400 lines). No doctype, and
everything works fine.

-bill

> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]On Behalf Of Dann
> Sent: Monday, January 08, 2001 2:36 PM
> To: dyn...@li...
> Subject: [Dynapi-Dev] W3C DOCTYPE interferes with DynAPI
>
>
> Hi,
>
> I've just spent a boring two hours debugging DynAPI code on NS6, only to
> discover that nothing was wrong with the code. Instead, NS6's
> interpretation of the DOCTYPE at the beginning of the HTML file :
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
> "http://www.w3.org/TR/html4/loose.dtd">
>
> caused DynAPI to stop functioning without errors.
>
> If I remove it, it works as with all the other browsers. The file can be
> perfectly validated as a HTML 4.01 document, for which the DOCTYPE tag
> is imperative.
>
> Does NE1 have any idea why this happens on NS6 ?
>
> CU,
>  Dann
>