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

Re: RE: [Dynapi-Dev] Next Generation part II

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

Hey...
I think most of you seem to be missing the point somewhat. 
Let me explain:

There are certain reasons why languages such as Java and 
other OO languages have evolved. Such as stability, 
reusabilty/modularity, ease of use, security etc. Object 
Orientation exists because people wanted have a way to do 
easier abstraction of problems, and representing them in a 
more human-like fashion.
Now what DynLayer tries to do is simulate parts of this 
whilst providing funcionality for robust, consistant and 
simple dHtml creation.

But how can you create a complex API such as DynAPI without 
having some fundamentals already in place? Such as a fast, 
stable, easy and safe way of creating a class 
hierarchy/implementing basic OOP functionality.
I mean, how long has this "current" release been in a 
debugging phase ??! Do you not think that this could have 
been avoided, atleast in part, by having a more stable 
coding ground to develop with?

True, Javascript's prototype based OO provide some 
functionality for creating "classes". But this approach is 
inherantly slow, memory consuming and error prone, since 
some of the most fundamental OOP functionality is not 
supported (such as encapsulation).
Why go halfway, sort of do OOP, but not really, because 
it's too hard ? It's not! In the long run it's much 
simpler. Which is the exact point of DynAPI in the first 
place. There is a longer learning curve before you can use 
it, but when you do, your efforts are greatly simplified 
and accellerated.

What you would want, is somekind of Object providing the 
remaining OOP functionality that Javascript does not 
inherantly support, so that you don't have to recreate the 
wheel everytime you develop somekind of JS application or 
extension to it.
Pascals DynObject and Eytans SuperObject, are examples of 
what I'm talking about.
DynObject provides better modularity for DynAPI, and a 
SuperObject would provide the tools with which to better 
build a more modular DynAPI (there are infact a couple of 
more people that have developed a SuperObject/SuperClass).

Yes, you could argue that this would only lead to more 
bugs, and that you should rely on JavaScript's built-in way 
of handling OOP, and that this should be a API for 
designers, not for programmers and what have you...
But this is simply not true. 

1. DynAPI is a programming tool/interface for creating 
dHtml.
Now programming is the key word here. No matter what, you 
still have to PROGRAM. If you would want to create a 
simpler interface for creating dHtml (a WYSIWYG for 
instance), there still has to be somone who creates this 
interface, and I guarantee you, it won't be a designer! ;)

2. Having a SuperClass that provides basic OOP 
functionality, would provide the PROGRAMMER with the tools 
nessessary to create DynAPI with a lot more ease 
(again,this is the goal of OOP). 
For example, say that you would want to split up DynAPI per 
browser basis and make this seamless for the end 
programmer. If you would not have fundamental OOP 
functionality in place, this would be HARD!  

True, the SuperClass would have to be flawless and 
completely without bugs for this premise to work. 
But this is not impossible. I know, because I'm in the 
finishing stages of creating a comprehensive SuperClass 
myself (I might even create an opensource forum for it ;D )
SuperClass is, and should be, inherantly separate from 
DynAPI, and you should be able to create whatever class 
hierarchy you would want, including DynAPI. 

So in closing, I hope that the coin will finally drop, and 
what I've said to sing in ( i.e not just be flamed) ;)

Alea Jacta Est, 
Bart

Re: [Dynapi-Dev] Last Post by mistake

[Dann <da...@to...>]

Don't worry 8an,

'shoot-and-forget' military hardware is totally out of fashion, these
days they can reprogram that missile in mid-air, to change the target
for a splash-down in the sea or anywhere at random inside the M$ campus.
Of course, people need to want to do that :) LOL !

CU,
 Dann

Re: Re[2]: [Dynapi-Dev] [Bug #130357] small typo in list.js

[Doug M. <do...@cr...>]

I've just had that conversation with a co-worker.
Can anyone tell me why this is not proper?
The best my co-worker could come up with was 'it doesn't feel right'
....


> Either way, we shouldn't be using if (this.selected=b).  That's not
> very proper.
>
> --
> // Robert Rainwater
>
> On 1/30/2001, 8:47:21 AM EST, Raides wrote about "[Dynapi-Dev] [Bug
#130357] small typo in list.js":
>
> > Michael Pemberton wrote:
> >>
> >> please put the "typo" back.  What is does is set the value of
this.selected to
> >> b and then evaluates the returned value (the new value of
this.selected).  It
> >> is needed to change the selected state of the item.
> >>
>
> >> > if (this.selected=b) {
> >> >
> >> > should be
> >> >
> >> > if (this.selected==b) {
> >> >
> >> > right?
>
> >         I will answer both for NS6's sake:
>
> >         This is indeed a bug in NS6 and prevents normal execution of the
rest of the
> > code. It should read:
>
> > this.selected=b
> > if(this.selected){
> > ...
> > }else{
> > ...
> > }
>
> >         I have done this kind of changes all around my local dynapi
distribution and
> > those pesky errors that NS6 throwed at me and their side effect of code
not
> > executing in that function anymore disappeared. Other special
perso-NS6-ality of
> > this browser is that if you want to dynamically resize an image, you
have to do
> > it TWICE, using a setTimeout to delay appropiately (30 millisecs are
enough) the
> > effect. The code I use to test NS6 comes with this mail. It is spanish
code and
> > HTML, poorly documented but that can be executed in IE4.0 and above with
no
> > changes at all and some errors due to their different underlying model.
>
> >         Raides J.
>
>
> ----------------------
> DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
> DynAPI Homepage: http://dynapi.sourceforge.net/
>
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Re[2]: [Dynapi-Dev] [Bug #130357] small typo in list.js

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

Either way, we shouldn't be using if (this.selected=b).  That's not
very proper.

-- 
// Robert Rainwater

On 1/30/2001, 8:47:21 AM EST, Raides wrote about "[Dynapi-Dev] [Bug #130357] small typo in list.js":

> Michael Pemberton wrote:
>> 
>> please put the "typo" back.  What is does is set the value of this.selected to
>> b and then evaluates the returned value (the new value of this.selected).  It
>> is needed to change the selected state of the item.
>> 

>> > if (this.selected=b) {
>> >
>> > should be
>> >
>> > if (this.selected==b) {
>> >
>> > right?

>         I will answer both for NS6's sake:

>         This is indeed a bug in NS6 and prevents normal execution of the rest of the
> code. It should read:

> this.selected=b
> if(this.selected){
> ...
> }else{
> ...
> }

>         I have done this kind of changes all around my local dynapi distribution and
> those pesky errors that NS6 throwed at me and their side effect of code not
> executing in that function anymore disappeared. Other special perso-NS6-ality of
> this browser is that if you want to dynamically resize an image, you have to do
> it TWICE, using a setTimeout to delay appropiately (30 millisecs are enough) the
> effect. The code I use to test NS6 comes with this mail. It is spanish code and
> HTML, poorly documented but that can be executed in IE4.0 and above with no
> changes at all and some errors due to their different underlying model.

>         Raides J.


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

RE: [Dynapi-Dev] Next Generation

[Cameron H. <ca...@bi...>]

i'm well aware of that doug.

i don't think my earlier statement really required close examination (i.e.
it was meant to be a joke)...

> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]On Behalf Of Doug Melvin
> Sent: 30 January 2001 18:23
> To: dyn...@li...
> Subject: Re: [Dynapi-Dev] Next Generation
>
>
> that's not 'in the world'
> All stats on that site are from visiter to that site, and
> represent ONLY visiters to that site.
> Not the world.
>
> ----- Original Message -----
> From: "Cameron Hart" <ca...@bi...>
> To: <dyn...@li...>
> Sent: Tuesday, January 30, 2001 1:59 AM
> Subject: RE: [Dynapi-Dev] Next Generation
>
>
> > It is quite frightening to know that 5 people in the world are
> using MSIE
> > 1.x ;-)
> >
> > I mean, has anyone even seen IE 1???
> >
> > > -----Original Message-----
> > > From: dyn...@li...
> > > [mailto:dyn...@li...]On Behalf Of Raymond
> > > Smith
> > > Sent: 30 January 2001 05:50
> > > To: dyn...@li...
> > > Subject: Re: [Dynapi-Dev] Next Generation
> > >
> > >
> > > Carefull if your using the "sample stats" from there.  They
> date back to
> > > 1999 and reflect an older reality.  Most recent browser stats I have
> found
> > > are at www.thecounter.com.  From October 2000.
> > >
> > > ----- Original Message -----
> > > From: "Michael Ellis" <Mic...@il...>
> > > To: <dyn...@li...>
> > > Sent: Monday, January 29, 2001 2:53 PM
> > > Subject: RE: [Dynapi-Dev] Next Generation
> > >
> > >
> > > > Amen brother!
> > > >
> > > > No argument here... Although we can be educated to, we cannot expect
> nor
> > > > demand which platform/browser our end-users choose. If our
> > > software is to
> > > be
> > > > taken seriously, and serve a broad community we must be reasonable
> about
> > > > which platforms/browsers we support. If you think I'm full of it,
> check
> > > the
> > > > browser/platform statistics at www.statmarket.com (don't rely on
> > > statistics
> > > > gathered by developer forums, they attract developers like
> us and are
> > > > typically not representative of our products end-users).
> > > >
> > > > Mike Ellis
> > > >
> > > > -----Original Message-----
> > > > From: .:: OCB ::. [mailto:oc...@ho...]
> > > > Sent: Monday, January 29, 2001 10:15
> > > > To: dyn...@li...
> > > > Subject: Re: [Dynapi-Dev] Next Generation
> > > >
> > > >
> > > > Next generation ???
> > > >
> > > > Would it not be a good idea to get the DynApi2 working in
> all browsers
> > > > (basic methods, moveTo, event handlers etc; not wigits, IMO
> they take
> a
> > > > backseat to basic functionality) before even discussing another
> > > generation
> > > > of the API.
> > > >
> > > > I haven't contributed anything in months (which is beyond
> my control)
> so
> > > > feel quite apprehensive about posting this but again, IMO, it
> > > makes common
> > > > sense to get the basic's of this project crossbrowser (NN6 included)
> and
> > > bug
> > > >
> > > > free before launching into another generation of the API.
> > > >
> > > > Flame away !!!!
> > > >
> > > >
> > > > >From: "Jared Nuzzolillo" <ja...@aa...>
> > > > >Reply-To: dyn...@li...
> > > > >To: <dyn...@li...>
> > > > >Subject: [Dynapi-Dev] Next Generation
> > > > >Date: Mon, 29 Jan 2001 11:46:41 -0500
> > > > >
> > > > >I have a feeling that certain people are wanting to implement
> > > class-like
> > > > >inheritance because it is more familiar/comfortable to them.
> > > > >
> > > > >I strongly agree with Pascal. Prototype-based inheritance works
> > > > >beautifully,
> > > > >and is native to javascript, so why would we want to enforce a
> > > different
> > > > >type of inheritance to use the API? Most dynapi users will at least
> be
> > > > >familiar with javascript, and may be expecting Prototype-like
> behavior.
> > > > >
> > > > >It's kind of like creating a number class instead of using built in
> > > number
> > > > >objects and primitive types. It's pointeless.
> > > > >
> > > > >As far as the class/prototype argument as to what Netscape
> says, the
> > > first
> > > > >line of this article:
> > > > >
> > > >
> > > >http://developer.netscape.com/docs/manuals/communicator/jsobj/con
> > tents.htm
> > > >
> > > >reads as follows:
> > > >
> > > >"JavaScript is an object-oriented language based on
> prototypes, rather
> > > >than,
> > > >as is common, being class-based."
> > > >
> > > >-jaredn
> > > >
> > > >
> > > >
> > > >
> > > >_______________________________________________
> > > >Dynapi-Dev mailing list
> > > >Dyn...@li...
> > > >http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> > >
> > >
> _________________________________________________________________________
> > > Get Your Private, Free E-mail from MSN Hotmail at
> http://www.hotmail.com.
> > >
> > >
> > >
> > > _______________________________________________
> > > Dynapi-Dev mailing list
> > > Dyn...@li...
> > > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> > >
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Re: [Dynapi-Dev] ns6 w/h and browser advocacy

[Dann <da...@to...>]

Hi,

Has anybody ever done some testing or wondered about the safety nature of
concurrent execution of code in JS ? It struck me that this timeout gimmick has
been discovered over and over again, to apparantly fix a recurring issue. It was
already pointed out by Cameron, that if you could fix this kind of behaviour by
using a Timeout, you probably stumbled on a browser bug... usually, in my years
of fooling around with JS, a Timeout could even prevent a browser from crashing
entirely.

What exactly happens if you would hook load event handlers to to two images, who
would fire simultaneously and call the same function, to change some common
global variables ?

CU,
 Dann

[Dynapi-Dev] Last Post by mistake

[Eytan H. <ey...@tr...>]

I tried to post that yesterday and it just sent now most of it is
irrelevant.
8an

RE: [Dynapi-Dev] Next Generation part II

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

Why not use a simple image tag for a simple image? why use a complete
dynlayer?

An object that can delete itself effectively is indeed something that we
need, but my main concern on that topic is the fact of where this bug
exists? The DynAPI or the browsers?  Anyway, if a problem of the DynAPI it
should also be possible to fix in the current code and is no need for a full
change on the dynapi.

The current dynlayer might be possible to make smaller, but that means no
controll over dynlayers at all (no setsize, moveto, etc) so you could just
as easy use normal html tags for that (it's not dynamic anyway).

So, what extra functionality (which is not possible with the current model)
could we achieve by changing to a new structure ?

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

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Doug Melvin
> Verzonden: dinsdag 30 januari 2001 19:21
> Aan: dyn...@li...
> Onderwerp: Re: [Dynapi-Dev] Next Generation part II
>
>
> I vote for a 'modified' 'object model.
> My main concern is for an object that can delete itself effectively.
> Also, the base Layer Object should be just that,
> BASIC. A small and simple as possible.
> An icon in the top left corner of you web page.
> Which does nothing more than just sit at the top left corner
> of your webpage
> uses a very small fraction of the functionality currently
> built into the
> DynLayer object.
>
> ----- Original Message -----
> From: "Eytan Heidingsfeld" <ey...@tr...>
> To: <dyn...@li...>
> Sent: Tuesday, January 30, 2001 12:31 AM
> Subject: [Dynapi-Dev] Next Generation part II
>
>
> > Ok, so now we have all discussed and recommended and
> finished throwing
> > stones. After we all got in-depth about OO and prototypes
> and classes
> where
> > are we going. My recommendation of how to act is as such:
> > * Create a DynLayer(mayber change it's name) that is
> totally seprate and
> > stand alone. It includes only methods to affect the layer
> and events that
> > are triggered from the outside(mouse and keyboard events).
> > * Create the basic objects: Application, Object, Component
> > Application:
> > Manages the DynLayers focus and events
> > Object:
> > Basic object with create and destroy
> > Component:
> > Basic object with dynlayer.
> >
> > I'd be glad to change the model if anyone has new and
> improved ideas.
> >
> > Now except for the actual model I want to know if we have
> enough ppl who
> > want a next generation to continue.
> >
> > 8an
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>

[Dynapi-Dev] Why, What Where and when

[Eytan H. <ey...@tr...>]

This is about the whole redesign issue.

Why
---
One of the reasons for the lack of stability in DynAPI is the way it is put
together. I respect that professor very much and I understand he likes the
model but this exact model is why it crashes and why it develops like it
does.
What
----
What do I mean. I want to rewrite the actual core meaning changing
everything. Making a DynLayer class that is totally independent. Then
creating a whole OO environment (it doesn't matter at this stage if we use
prototypes or classes for OO but the current API misuses OO completely).
Where
-----
I know that you guys want this to be the perfect "Dreamweaver" use solution.
For that this thing has to be modeled in a logical simple way.  It also has
to be a whole lot more stable then it is today
When
----
As they say "Never been a better time then right now!" As I previously
stated the development of support for other browsers can be integrated in
the rewrite.

I can see that most ppl disagree with me and like things the way they are, I
hope I can change your mind but I guess its up to the majority.

8an

Re: [Dynapi-Dev] [Bug #130357] small typo in list.js

[Doug M. <do...@cr...>]

Well I'll be...
I shoulda known 'perfectly valid coding technique' and
NS6 don't belong in the same sentance.


> Michael Pemberton wrote:
> >
> > please put the "typo" back.  What is does is set the value of
this.selected to
> > b and then evaluates the returned value (the new value of
this.selected).  It
> > is needed to change the selected state of the item.
> >
>
> > > if (this.selected=b) {
> > >
> > > should be
> > >
> > > if (this.selected==b) {
> > >
> > > right?
>
> I will answer both for NS6's sake:
>
> This is indeed a bug in NS6 and prevents normal execution of the rest of
the
> code. It should read:
>
> this.selected=b
> if(this.selected){
> ...
> }else{
> ...
> }
>
> I have done this kind of changes all around my local dynapi distribution
and
> those pesky errors that NS6 throwed at me and their side effect of code
not
> executing in that function anymore disappeared. Other special
perso-NS6-ality of
> this browser is that if you want to dynamically resize an image, you have
to do
> it TWICE, using a setTimeout to delay appropiately (30 millisecs are
enough) the
> effect. The code I use to test NS6 comes with this mail. It is spanish
code and
> HTML, poorly documented but that can be executed in IE4.0 and above with
no
> changes at all and some errors due to their different underlying model.
>
> Raides J.

Re: [Dynapi-Dev] [Bug #130357] small typo in list.js

[Doug M. <do...@cr...>]

That just plain silly.
It's perfectly valid coding technique.

  perhaps it would be safer to assign the value first and then test the =
condition...
    -----Original Message-----
    From: dyn...@li... =
[mailto:dyn...@li...]On Behalf Of Michael =
Pemberton
    Sent: 30 January 2001 13:28
    To: dyn...@li...
    Subject: Re: [Dynapi-Dev] [Bug #130357] small typo in list.js


    please put the "typo" back.  What is does is set the value of =
this.selected to b and then evaluates the returned value (the new value =
of this.selected).  It is needed to change the selected state of the =
item.=20
    no...@so... wrote:=20

      Bug #130357, was updated on 2001-Jan-28 14:27=20
      Here is a current snapshot of the bug.=20
      Project: DynAPI 2=20
      Category: Core - Widgets=20
      Status: Closed=20
      Resolution: Fixed=20
      Bug Group: None=20
      Priority: 5=20
      Submitted by: marstr=20
      Assigned to : rainwater=20
      Summary: small typo in list.js=20

      Details: there's a small typo (i think) in list.js line 76=20

      if (this.selected=3Db) {=20

      should be=20

      if (this.selected=3D=3Db) {=20

      right?=20

      Follow-Ups:=20

      Date: 2001-Jan-28 17:50=20
      By: rainwater=20

      Comment:=20
      Doh!  Its been updated in CVS.  Closing this bug.=20
      -------------------------------------------------------=20

      For detailed info, follow this link:=20
      =
http://sourceforge.net/bugs/?func=3Ddetailbug&bug_id=3D130357&group_id=3D=
5757=20

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

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

RE: [Dynapi-Dev] Loosing mail

[Jack_Speranza <jsp...@gr...>]

Yes to both... rocks and e-mail, that is (though because I tend to keep my
head low in this forum, most of the rocks I receive come from a different
direction ;-).  Being on the east coast, perhaps the rocks Raymond is
throwing from out west are falling here instead of on the Continent?

-----Original Message-----
From: Pascal [mailto:pb...@oi...]
Sent: Tuesday, January 30, 2001 2:46 AM
To: dyn...@li...
Subject: [Dynapi-Dev] Loosing mail


Uhm, is it just me or am I missing emails now and then?

I sometimes read replies on email I haven't seen on the list.

One example, the mail from Michael Ellis into reply on OCB.. I never
received the OCB mail!? I had the same thing yesterday also a reply on
something I never saw on the list?

Has my email been hit by rocks or something? Anyone else has this problem?
(not the rock problem, but email problem)

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


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

Re: [Dynapi-Dev] Next Generation

[Doug M. <do...@cr...>]

that's not 'in the world'
All stats on that site are from visiter to that site, and
represent ONLY visiters to that site.
Not the world.

----- Original Message -----
From: "Cameron Hart" <ca...@bi...>
To: <dyn...@li...>
Sent: Tuesday, January 30, 2001 1:59 AM
Subject: RE: [Dynapi-Dev] Next Generation


> It is quite frightening to know that 5 people in the world are using MSIE
> 1.x ;-)
>
> I mean, has anyone even seen IE 1???
>
> > -----Original Message-----
> > From: dyn...@li...
> > [mailto:dyn...@li...]On Behalf Of Raymond
> > Smith
> > Sent: 30 January 2001 05:50
> > To: dyn...@li...
> > Subject: Re: [Dynapi-Dev] Next Generation
> >
> >
> > Carefull if your using the "sample stats" from there.  They date back to
> > 1999 and reflect an older reality.  Most recent browser stats I have
found
> > are at www.thecounter.com.  From October 2000.
> >
> > ----- Original Message -----
> > From: "Michael Ellis" <Mic...@il...>
> > To: <dyn...@li...>
> > Sent: Monday, January 29, 2001 2:53 PM
> > Subject: RE: [Dynapi-Dev] Next Generation
> >
> >
> > > Amen brother!
> > >
> > > No argument here... Although we can be educated to, we cannot expect
nor
> > > demand which platform/browser our end-users choose. If our
> > software is to
> > be
> > > taken seriously, and serve a broad community we must be reasonable
about
> > > which platforms/browsers we support. If you think I'm full of it,
check
> > the
> > > browser/platform statistics at www.statmarket.com (don't rely on
> > statistics
> > > gathered by developer forums, they attract developers like us and are
> > > typically not representative of our products end-users).
> > >
> > > Mike Ellis
> > >
> > > -----Original Message-----
> > > From: .:: OCB ::. [mailto:oc...@ho...]
> > > Sent: Monday, January 29, 2001 10:15
> > > To: dyn...@li...
> > > Subject: Re: [Dynapi-Dev] Next Generation
> > >
> > >
> > > Next generation ???
> > >
> > > Would it not be a good idea to get the DynApi2 working in all browsers
> > > (basic methods, moveTo, event handlers etc; not wigits, IMO they take
a
> > > backseat to basic functionality) before even discussing another
> > generation
> > > of the API.
> > >
> > > I haven't contributed anything in months (which is beyond my control)
so
> > > feel quite apprehensive about posting this but again, IMO, it
> > makes common
> > > sense to get the basic's of this project crossbrowser (NN6 included)
and
> > bug
> > >
> > > free before launching into another generation of the API.
> > >
> > > Flame away !!!!
> > >
> > >
> > > >From: "Jared Nuzzolillo" <ja...@aa...>
> > > >Reply-To: dyn...@li...
> > > >To: <dyn...@li...>
> > > >Subject: [Dynapi-Dev] Next Generation
> > > >Date: Mon, 29 Jan 2001 11:46:41 -0500
> > > >
> > > >I have a feeling that certain people are wanting to implement
> > class-like
> > > >inheritance because it is more familiar/comfortable to them.
> > > >
> > > >I strongly agree with Pascal. Prototype-based inheritance works
> > > >beautifully,
> > > >and is native to javascript, so why would we want to enforce a
> > different
> > > >type of inheritance to use the API? Most dynapi users will at least
be
> > > >familiar with javascript, and may be expecting Prototype-like
behavior.
> > > >
> > > >It's kind of like creating a number class instead of using built in
> > number
> > > >objects and primitive types. It's pointeless.
> > > >
> > > >As far as the class/prototype argument as to what Netscape says, the
> > first
> > > >line of this article:
> > > >
> > >
> > >http://developer.netscape.com/docs/manuals/communicator/jsobj/con
> tents.htm
> > >
> > >reads as follows:
> > >
> > >"JavaScript is an object-oriented language based on prototypes, rather
> > >than,
> > >as is common, being class-based."
> > >
> > >-jaredn
> > >
> > >
> > >
> > >
> > >_______________________________________________
> > >Dynapi-Dev mailing list
> > >Dyn...@li...
> > >http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> >
> >
_________________________________________________________________________
> > Get Your Private, Free E-mail from MSN Hotmail at
http://www.hotmail.com.
> >
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> >
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Re: [Dynapi-Dev] Next Generation part II

[Doug M. <do...@cr...>]

I vote for a 'modified' 'object model.
My main concern is for an object that can delete itself effectively.
Also, the base Layer Object should be just that,
BASIC. A small and simple as possible.
An icon in the top left corner of you web page.
Which does nothing more than just sit at the top left corner of your webpage
uses a very small fraction of the functionality currently built into the
DynLayer object.

----- Original Message -----
From: "Eytan Heidingsfeld" <ey...@tr...>
To: <dyn...@li...>
Sent: Tuesday, January 30, 2001 12:31 AM
Subject: [Dynapi-Dev] Next Generation part II


> Ok, so now we have all discussed and recommended and finished throwing
> stones. After we all got in-depth about OO and prototypes and classes
where
> are we going. My recommendation of how to act is as such:
> * Create a DynLayer(mayber change it's name) that is totally seprate and
> stand alone. It includes only methods to affect the layer and events that
> are triggered from the outside(mouse and keyboard events).
> * Create the basic objects: Application, Object, Component
> Application:
> Manages the DynLayers focus and events
> Object:
> Basic object with create and destroy
> Component:
> Basic object with dynlayer.
>
> I'd be glad to change the model if anyone has new and improved ideas.
>
> Now except for the actual model I want to know if we have enough ppl who
> want a next generation to continue.
>
> 8an
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Re: [Dynapi-Dev] ns6 w/h and browser advocacy

[Joachim L. <lu...@ho...>]

Time for me to bud in... I did quite a lot of testing for this bug some 
time ago.

Mozilla.org had issued the bug at that time as #56810 :
         http://bugzilla.mozilla.org/show_bug.cgi?id=56810

I never got the work-around to, well, work :-(

But I got the right result by calling the function as the result of a timeout:
         setTimeout("alert("+o+".elm.offsetWidth)", 0);
In other words: timeout in 0 ms - just after the layout engine has done its 
deed

Now I checked bugzilla again, and there is another one:
         http://bugzilla.mozilla.org/show_bug.cgi?id=65548

Guess it never got fixed...

The problem as I see it is this: Because the bug is in Netscape 6 (I 
assume, the installer crashes for me, but I use Mozilla 0.6 which is 
supposed to be from the same codebase) the fix must work for the release 
version.

I was hoping there was a way to programmatically get the result, such as
         this.elm.ownerDocument.defaultView.getComputedStyle(this.elm,null).getPropertyValue("width");
but whatever I tried I couldn't get it to work.

The only reliable way was the setTimeout() trick. I think the easiest for 
you to make it work in DynAPI is to skip the precreation code for that 
browser, at least when the width and height aren't known.

(The code here is from memory - it seems to be right though.)

/Lunna


At 2001-01-30 11:24, you wrote:
>Hi,
>
>I remember a post from Robert saying he'd got offsetWidth and offsetHeight
>working in NS6 using a setTimeout. Was this specific to one of the widgets
>Robert, or did it fix W/H for everything in NS6?
>
>If you need a setTimeout for the thing to work properly, it sounds like a
>bug in the browser. The great thing about Mozilla is if you post a bug,
>they'll fix it for you ;-) It can take a while, it depends on how important
>the developers feel that peice of functionality is. But I think it would be
>worth writing a test case and a bug report for the W/H bug. I can submit one
>if someone (Robert I guess) tells me how to reproduce the bug, that is how
>it works versus how you think it should work.
>
>Something else which might be if interest to DOM enthusiasts, I was
>wondering why offsetHeight and offsetWidth and similar measurements aren't
>in any of the DOM's. I posted a query about this to ww...@w3..., and the
>response was it's been put on the back burner as there hasn't been that much
>interest in this functionality. Apparently it will probably end up in DOM3.
>I thought it would have been pretty core functionality...

RE: [Dynapi-Dev] [Bug #130357] small typo in list.js

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

i think it would, the reason i found this "bug"
was because ns6 thrown an error on that line..


/m

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Cameron Hart
Sent: den 30 januari 2001 14:42
To: dyn...@li...
Subject: RE: [Dynapi-Dev] [Bug #130357] small typo in list.js


perhaps it would be safer to assign the value first and then test the
condition...
-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Michael
Pemberton
Sent: 30 January 2001 13:28
To: dyn...@li...
Subject: Re: [Dynapi-Dev] [Bug #130357] small typo in list.js


please put the "typo" back.  What is does is set the value of this.selected
to b and then evaluates the returned value (the new value of this.selected).
It is needed to change the selected state of the item.
no...@so... wrote:
Bug #130357, was updated on 2001-Jan-28 14:27
Here is a current snapshot of the bug.
Project: DynAPI 2
Category: Core - Widgets
Status: Closed
Resolution: Fixed
Bug Group: None
Priority: 5
Submitted by: marstr
Assigned to : rainwater
Summary: small typo in list.js
Details: there's a small typo (i think) in list.js line 76
if (this.selected=b)

should be
if (this.selected==b)

right?
Follow-Ups:
Date: 2001-Jan-28 17:50
By: rainwater
Comment:
Doh!  Its been updated in CVS.  Closing this bug.
-------------------------------------------------------
For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=130357&group_id=5757
_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
--
Michael Pemberton
mp...@ph...
ICQ: 12107010

Re: [Dynapi-Dev] [Bug #130357] small typo in list.js

[Raides J. <ra...@te...>]

Michael Pemberton wrote:
> 
> please put the "typo" back.  What is does is set the value of this.selected to
> b and then evaluates the returned value (the new value of this.selected).  It
> is needed to change the selected state of the item.
> 

> > if (this.selected=b) {
> >
> > should be
> >
> > if (this.selected==b) {
> >
> > right?

	I will answer both for NS6's sake:

	This is indeed a bug in NS6 and prevents normal execution of the rest of the
code. It should read:

this.selected=b
if(this.selected){
...
}else{
...
}

	I have done this kind of changes all around my local dynapi distribution and
those pesky errors that NS6 throwed at me and their side effect of code not
executing in that function anymore disappeared. Other special perso-NS6-ality of
this browser is that if you want to dynamically resize an image, you have to do
it TWICE, using a setTimeout to delay appropiately (30 millisecs are enough) the
effect. The code I use to test NS6 comes with this mail. It is spanish code and
HTML, poorly documented but that can be executed in IE4.0 and above with no
changes at all and some errors due to their different underlying model.

	Raides J.

RE: [Dynapi-Dev] [Bug #130357] small typo in list.js

[Cameron H. <ca...@bi...>]

perhaps it would be safer to assign the value first and then test the
condition...
  -----Original Message-----
  From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Michael
Pemberton
  Sent: 30 January 2001 13:28
  To: dyn...@li...
  Subject: Re: [Dynapi-Dev] [Bug #130357] small typo in list.js


  please put the "typo" back.  What is does is set the value of
this.selected to b and then evaluates the returned value (the new value of
this.selected).  It is needed to change the selected state of the item.
  no...@so... wrote:

    Bug #130357, was updated on 2001-Jan-28 14:27
    Here is a current snapshot of the bug.
    Project: DynAPI 2
    Category: Core - Widgets
    Status: Closed
    Resolution: Fixed
    Bug Group: None
    Priority: 5
    Submitted by: marstr
    Assigned to : rainwater
    Summary: small typo in list.js

    Details: there's a small typo (i think) in list.js line 76

    if (this.selected=b)


    should be

    if (this.selected==b)


    right?

    Follow-Ups:

    Date: 2001-Jan-28 17:50
    By: rainwater

    Comment:
    Doh!  Its been updated in CVS.  Closing this bug.
    -------------------------------------------------------

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

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

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

Re: [Dynapi-Dev] [Bug #130357] small typo in list.js

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

please put the "typo" back.  What is does is set the value of this.selected
to b and then evaluates the returned value (the new value of
this.selected).  It is needed to change the selected state of the item.

no...@so... wrote:

> Bug #130357, was updated on 2001-Jan-28 14:27
> Here is a current snapshot of the bug.
>
> Project: DynAPI 2
> Category: Core - Widgets
> Status: Closed
> Resolution: Fixed
> Bug Group: None
> Priority: 5
> Submitted by: marstr
> Assigned to : rainwater
> Summary: small typo in list.js
>
> Details: there's a small typo (i think) in list.js line 76
>
> if (this.selected=b) {
>
> should be
>
> if (this.selected==b) {
>
> right?
>
> Follow-Ups:
>
> Date: 2001-Jan-28 17:50
> By: rainwater
>
> Comment:
> Doh!  Its been updated in CVS.  Closing this bug.
> -------------------------------------------------------
>
> For detailed info, follow this link:
> http://sourceforge.net/bugs/?func=detailbug&bug_id=130357&group_id=5757
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

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

Re: [Dynapi-Dev] Next Generation

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

from memory, two words: NO TABLES

Cameron Hart wrote:

> It is quite frightening to know that 5 people in the world are using MSIE
> 1.x ;-)
>
> I mean, has anyone even seen IE 1???
>
> > -----Original Message-----
> > From: dyn...@li...
> > [mailto:dyn...@li...]On Behalf Of Raymond
> > Smith
> > Sent: 30 January 2001 05:50
> > To: dyn...@li...
> > Subject: Re: [Dynapi-Dev] Next Generation
> >
> >
> > Carefull if your using the "sample stats" from there.  They date back to
> > 1999 and reflect an older reality.  Most recent browser stats I have found
> > are at www.thecounter.com.  From October 2000.
> >
> > ----- Original Message -----
> > From: "Michael Ellis" <Mic...@il...>
> > To: <dyn...@li...>
> > Sent: Monday, January 29, 2001 2:53 PM
> > Subject: RE: [Dynapi-Dev] Next Generation
> >
> >
> > > Amen brother!
> > >
> > > No argument here... Although we can be educated to, we cannot expect nor
> > > demand which platform/browser our end-users choose. If our
> > software is to
> > be
> > > taken seriously, and serve a broad community we must be reasonable about
> > > which platforms/browsers we support. If you think I'm full of it, check
> > the
> > > browser/platform statistics at www.statmarket.com (don't rely on
> > statistics
> > > gathered by developer forums, they attract developers like us and are
> > > typically not representative of our products end-users).
> > >
> > > Mike Ellis
> > >
> > > -----Original Message-----
> > > From: .:: OCB ::. [mailto:oc...@ho...]
> > > Sent: Monday, January 29, 2001 10:15
> > > To: dyn...@li...
> > > Subject: Re: [Dynapi-Dev] Next Generation
> > >
> > >
> > > Next generation ???
> > >
> > > Would it not be a good idea to get the DynApi2 working in all browsers
> > > (basic methods, moveTo, event handlers etc; not wigits, IMO they take a
> > > backseat to basic functionality) before even discussing another
> > generation
> > > of the API.
> > >
> > > I haven't contributed anything in months (which is beyond my control) so
> > > feel quite apprehensive about posting this but again, IMO, it
> > makes common
> > > sense to get the basic's of this project crossbrowser (NN6 included) and
> > bug
> > >
> > > free before launching into another generation of the API.
> > >
> > > Flame away !!!!
> > >
> > >
> > > >From: "Jared Nuzzolillo" <ja...@aa...>
> > > >Reply-To: dyn...@li...
> > > >To: <dyn...@li...>
> > > >Subject: [Dynapi-Dev] Next Generation
> > > >Date: Mon, 29 Jan 2001 11:46:41 -0500
> > > >
> > > >I have a feeling that certain people are wanting to implement
> > class-like
> > > >inheritance because it is more familiar/comfortable to them.
> > > >
> > > >I strongly agree with Pascal. Prototype-based inheritance works
> > > >beautifully,
> > > >and is native to javascript, so why would we want to enforce a
> > different
> > > >type of inheritance to use the API? Most dynapi users will at least be
> > > >familiar with javascript, and may be expecting Prototype-like behavior.
> > > >
> > > >It's kind of like creating a number class instead of using built in
> > number
> > > >objects and primitive types. It's pointeless.
> > > >
> > > >As far as the class/prototype argument as to what Netscape says, the
> > first
> > > >line of this article:
> > > >
> > >
> > >http://developer.netscape.com/docs/manuals/communicator/jsobj/con
> tents.htm
> > >
> > >reads as follows:
> > >
> > >"JavaScript is an object-oriented language based on prototypes, rather
> > >than,
> > >as is common, being class-based."
> > >
> > >-jaredn
> > >
> > >
> > >
> > >
> > >_______________________________________________
> > >Dynapi-Dev mailing list
> > >Dyn...@li...
> > >http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> >
> > _________________________________________________________________________
> > Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
> >
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> >
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

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

RE: [Dynapi-Dev] Next Generation

[<hv...@ya...>]

 --- Cameron Hart <ca...@bi...> skrev: >
It is quite frightening to know that 5 people in the
> world are using MSIE
> 1.x ;-)
> 
> I mean, has anyone even seen IE 1???
> 

Yep - and it wasn't a pretty sight. It was based on
Mosaic and meant for use with Microsofts big project
MSN online which was to be the dominating computer
network. We all know how that turned out, don't we...
;)

Henrik Våglin [ hv...@ya... ] 

=====
// Henrik Vaglin

**************************************************
Visit my comics artpage at 
http://photos.yahoo.com/bc/hvaglin?d&.flabel=fld5&.src=bc
**************************************************

__________________________________________________
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

[Dynapi-Dev] What does this line do

[Eytan H. <ey...@tr...>]

This is from DynLayer.js
parentElement=(dlyr.parent.isCanvas)?dlyr.parent.elm:dlyr.parent.doc.body;
what does it do?
8an

RE: [Dynapi-Dev] Loosing mail

[Cameron H. <ca...@bi...>]

i think you've got programming-language-name-envy Ray. it's never too late
to change yours. how about modula-2, it's kind of like pascal ;-)

> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]On Behalf Of Raymond
> Smith
> Sent: 30 January 2001 11:23
> To: dyn...@li...
> Subject: Re: [Dynapi-Dev] Loosing mail
>
>
> I'm think you missed this one.
>
> I tried "allot" of things on good ole Mac IE5.  Anything "rich in DHTML
> blood" tends to knock the knees out from under it.  Most bugs breed like a
> festering desease from its inability to deliver correct Width and
> Height in
> content that it set based on determining this at load time (scrollpane,
> pushpanel,etc).
>
> I've pretty much abandoned trying support this obviously satanic
> browser.  I
> tell my clients to use NS on Mac and watch the horizon for IE6 and "hope".
> Or sniff the arrival of the vile thing and deliver a Jacob
> Nielson "type" of
> experience.
>
> At one point I even took Pascal "my mother tatooed binary digits
> on my ass"
> Bestebroer's noteworthy advise and pelleted my newly acquired
> Macintosh with
> large "rocks".  While this did cause some "significant" events to
> transpire
> I won't truely know the result til I get the machine back from the repair
> shop.
>
> Hope this helped.
>
> Ray
>
> ----- Original Message -----
> From: "Pascal" <pb...@oi...>
> To: <dyn...@li...>
> Sent: Tuesday, January 30, 2001 3:18 AM
> Subject: RE: [Dynapi-Dev] Loosing mail
>
>
> > I don't think email really cares about timezones :p
> >
> > there might be a problem with the list server I guess (to many
> persons on
> > the list ? :-)
> >
> >
> > Pascal Bestebroer (pb...@oi...)
> > Software ontwikkelaar
> > Oberon Informatiesystemen b.v.
> > http://www.oibv.com
> >
> > > -----Oorspronkelijk bericht-----
> > > Van: dyn...@li...
> > > [mailto:dyn...@li...]Namens Richard Bennett
> > > Verzonden: dinsdag 30 januari 2001 11:55
> > > Aan: dyn...@li...
> > > Onderwerp: Re: [Dynapi-Dev] Loosing mail
> > >
> > >
> > > Hi,
> > > Yes, I have the same problem, I thought it had something to do with
> > > timezones; the people who are six hours ahead of the others
> > > are responding
> > > to messages the others still have to write. (it's great for meeting
> > > deadlines).
> > >
> > > Cheers,
> > > Richard Bennett
> > >
> > > ma...@ri...
> > > www.richardinfo.com
> > > (Everything running on, and ported to the 19/12/2000 snapshot
> > > of DynAPI2)
> > >
> > > ----- Original Message -----
> > > From: "Pascal" <pb...@oi...>
> > > To: <dyn...@li...>
> > > Sent: Tuesday, January 30, 2001 8:46 AM
> > > Subject: [Dynapi-Dev] Loosing mail
> > >
> > >
> > > > Uhm, is it just me or am I missing emails now and then?
> > > >
> > > > I sometimes read replies on email I haven't seen on the list.
> > > >
> > > > One example, the mail from Michael Ellis into reply on OCB.. I never
> > > > received the OCB mail!? I had the same thing yesterday also
> > > a reply on
> > > > something I never saw on the list?
> > > >
> > > > Has my email been hit by rocks or something? Anyone else
> > > has this problem?
> > > > (not the rock problem, but email problem)
> > > >
> > > > Pascal Bestebroer (pb...@oi...)
> > > > Software ontwikkelaar
> > > > Oberon Informatiesystemen b.v.
> > > > http://www.oibv.com
> > > >
> > > >
> > > > _______________________________________________
> > > > Dynapi-Dev mailing list
> > > > Dyn...@li...
> > > > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> > > > ____________________________________________________________
> > > > Get your free domain name and domain-based e-mail from
> > > > Namezero.com. New!  Namezero Plus domains now available.
> > > > Find out more at: http://www.namezero.com
> > > >
> > >
> > >
> > > _______________________________________________
> > > Dynapi-Dev mailing list
> > > Dyn...@li...
> > > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> > >
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> >
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

RE: [Dynapi-Dev] Loosing mail

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

Nah, got that one.. just ignored it :)

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 30 januari 2001 12:23
> Aan: dyn...@li...
> Onderwerp: Re: [Dynapi-Dev] Loosing mail
> 
> 
> I'm think you missed this one.
> 
> I tried "allot" of things on good ole Mac IE5.  Anything 
> "rich in DHTML
> blood" tends to knock the knees out from under it.  Most bugs 
> breed like a
> festering desease from its inability to deliver correct Width 
> and Height in
> content that it set based on determining this at load time 
> (scrollpane,
> pushpanel,etc).
> 
> I've pretty much abandoned trying support this obviously 
> satanic browser.  I
> tell my clients to use NS on Mac and watch the horizon for 
> IE6 and "hope".
> Or sniff the arrival of the vile thing and deliver a Jacob 
> Nielson "type" of
> experience.
> 
> At one point I even took Pascal "my mother tatooed binary 
> digits on my ass"
> Bestebroer's noteworthy advise and pelleted my newly acquired 
> Macintosh with
> large "rocks".  While this did cause some "significant" 
> events to transpire
> I won't truely know the result til I get the machine back 
> from the repair
> shop.
> 
> Hope this helped.
> 
> Ray
> 
> ----- Original Message -----
> From: "Pascal" <pb...@oi...>
> To: <dyn...@li...>
> Sent: Tuesday, January 30, 2001 3:18 AM
> Subject: RE: [Dynapi-Dev] Loosing mail
> 
> 
> > I don't think email really cares about timezones :p
> >
> > there might be a problem with the list server I guess (to 
> many persons on
> > the list ? :-)
> >
> >
> > Pascal Bestebroer (pb...@oi...)
> > Software ontwikkelaar
> > Oberon Informatiesystemen b.v.
> > http://www.oibv.com
> >
> > > -----Oorspronkelijk bericht-----
> > > Van: dyn...@li...
> > > [mailto:dyn...@li...]Namens 
> Richard Bennett
> > > Verzonden: dinsdag 30 januari 2001 11:55
> > > Aan: dyn...@li...
> > > Onderwerp: Re: [Dynapi-Dev] Loosing mail
> > >
> > >
> > > Hi,
> > > Yes, I have the same problem, I thought it had something 
> to do with
> > > timezones; the people who are six hours ahead of the others
> > > are responding
> > > to messages the others still have to write. (it's great 
> for meeting
> > > deadlines).
> > >
> > > Cheers,
> > > Richard Bennett
> > >
> > > ma...@ri...
> > > www.richardinfo.com
> > > (Everything running on, and ported to the 19/12/2000 snapshot
> > > of DynAPI2)
> > >
> > > ----- Original Message -----
> > > From: "Pascal" <pb...@oi...>
> > > To: <dyn...@li...>
> > > Sent: Tuesday, January 30, 2001 8:46 AM
> > > Subject: [Dynapi-Dev] Loosing mail
> > >
> > >
> > > > Uhm, is it just me or am I missing emails now and then?
> > > >
> > > > I sometimes read replies on email I haven't seen on the list.
> > > >
> > > > One example, the mail from Michael Ellis into reply on 
> OCB.. I never
> > > > received the OCB mail!? I had the same thing yesterday also
> > > a reply on
> > > > something I never saw on the list?
> > > >
> > > > Has my email been hit by rocks or something? Anyone else
> > > has this problem?
> > > > (not the rock problem, but email problem)
> > > >
> > > > Pascal Bestebroer (pb...@oi...)
> > > > Software ontwikkelaar
> > > > Oberon Informatiesystemen b.v.
> > > > http://www.oibv.com
> > > >
> > > >
> > > > _______________________________________________
> > > > Dynapi-Dev mailing list
> > > > Dyn...@li...
> > > > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> > > > ____________________________________________________________
> > > > Get your free domain name and domain-based e-mail from
> > > > Namezero.com. New!  Namezero Plus domains now available.
> > > > Find out more at: http://www.namezero.com
> > > >
> > >
> > >
> > > _______________________________________________
> > > Dynapi-Dev mailing list
> > > Dyn...@li...
> > > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> > >
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> >
> 
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> 

Re: [Dynapi-Dev] Loosing mail

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

I'm think you missed this one.

I tried "allot" of things on good ole Mac IE5.  Anything "rich in DHTML
blood" tends to knock the knees out from under it.  Most bugs breed like a
festering desease from its inability to deliver correct Width and Height in
content that it set based on determining this at load time (scrollpane,
pushpanel,etc).

I've pretty much abandoned trying support this obviously satanic browser.  I
tell my clients to use NS on Mac and watch the horizon for IE6 and "hope".
Or sniff the arrival of the vile thing and deliver a Jacob Nielson "type" of
experience.

At one point I even took Pascal "my mother tatooed binary digits on my ass"
Bestebroer's noteworthy advise and pelleted my newly acquired Macintosh with
large "rocks".  While this did cause some "significant" events to transpire
I won't truely know the result til I get the machine back from the repair
shop.

Hope this helped.

Ray

----- Original Message -----
From: "Pascal" <pb...@oi...>
To: <dyn...@li...>
Sent: Tuesday, January 30, 2001 3:18 AM
Subject: RE: [Dynapi-Dev] Loosing mail


> I don't think email really cares about timezones :p
>
> there might be a problem with the list server I guess (to many persons on
> the list ? :-)
>
>
> Pascal Bestebroer (pb...@oi...)
> Software ontwikkelaar
> Oberon Informatiesystemen b.v.
> http://www.oibv.com
>
> > -----Oorspronkelijk bericht-----
> > Van: dyn...@li...
> > [mailto:dyn...@li...]Namens Richard Bennett
> > Verzonden: dinsdag 30 januari 2001 11:55
> > Aan: dyn...@li...
> > Onderwerp: Re: [Dynapi-Dev] Loosing mail
> >
> >
> > Hi,
> > Yes, I have the same problem, I thought it had something to do with
> > timezones; the people who are six hours ahead of the others
> > are responding
> > to messages the others still have to write. (it's great for meeting
> > deadlines).
> >
> > Cheers,
> > Richard Bennett
> >
> > ma...@ri...
> > www.richardinfo.com
> > (Everything running on, and ported to the 19/12/2000 snapshot
> > of DynAPI2)
> >
> > ----- Original Message -----
> > From: "Pascal" <pb...@oi...>
> > To: <dyn...@li...>
> > Sent: Tuesday, January 30, 2001 8:46 AM
> > Subject: [Dynapi-Dev] Loosing mail
> >
> >
> > > Uhm, is it just me or am I missing emails now and then?
> > >
> > > I sometimes read replies on email I haven't seen on the list.
> > >
> > > One example, the mail from Michael Ellis into reply on OCB.. I never
> > > received the OCB mail!? I had the same thing yesterday also
> > a reply on
> > > something I never saw on the list?
> > >
> > > Has my email been hit by rocks or something? Anyone else
> > has this problem?
> > > (not the rock problem, but email problem)
> > >
> > > Pascal Bestebroer (pb...@oi...)
> > > Software ontwikkelaar
> > > Oberon Informatiesystemen b.v.
> > > http://www.oibv.com
> > >
> > >
> > > _______________________________________________
> > > Dynapi-Dev mailing list
> > > Dyn...@li...
> > > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> > > ____________________________________________________________
> > > Get your free domain name and domain-based e-mail from
> > > Namezero.com. New!  Namezero Plus domains now available.
> > > Find out more at: http://www.namezero.com
> > >
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> >
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>