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

Re: [Dynapi-Dev] Netscape 6.0 Layers Not Painting Unless I Hit Refresh + Mac IE 5. 0 (hopeless ?)

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

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: "Michael Ellis" <Mic...@il...>
To: <dyn...@li...>
Sent: Saturday, January 27, 2001 9:09 PM
Subject: [Dynapi-Dev] Netscape 6.0 Layers Not Painting Unless I Hit Refresh
+ Mac IE 5. 0 (hopeless ?)


> I'm having a problem with the new release (and old for that matter) of
> DynAPI. I have a label in a scrollPane nested in a layer. When I load the
> page up in every other browser (except IE 5.0 Mac... what a mess)
everything
> works well. But in NS 6.0 (Mac/PC) only the last layer is visible when
> everything is loaded. On the Mac, if I hit refresh enough, it will
> eventually paint. On the PC hitting refresh never causes it to paint
> properly, however, if I click on the address bar and hit ENTER it paints
> correctly (bizarre).
>
> How do I get Netscape 6.0 to paint up the first time??? I am due to
release
> this in the next couple of weeks, any help would be greatly appreciated!
> (Can be consistently reproduce using
> dynapi.gui.scrollbar.html/dynapi.gui.scrolpane.html supplied with release)
>
> Anyone had any success on IE 5.0 Mac??? If you have please send me any
info
> you can... I know it's less than ideal for DHTML, but I've been told to
find
> a way. I have a couple of Macs set up for testing if anyone needs patches
> tested!
>
> Thanks,
>
> Michael Ellis
> Solution Architect
>
> Interlink Group, Inc.
> Email: mic...@il...
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>

[Dynapi-Dev] Netscape 6.0 Layers Not Painting Unless I Hit Refresh + Mac IE 5. 0 (hopeless ?)

[Michael E. <Mic...@il...>]

I'm having a problem with the new release (and old for that matter) of
DynAPI. I have a label in a scrollPane nested in a layer. When I load the
page up in every other browser (except IE 5.0 Mac... what a mess) everything
works well. But in NS 6.0 (Mac/PC) only the last layer is visible when
everything is loaded. On the Mac, if I hit refresh enough, it will
eventually paint. On the PC hitting refresh never causes it to paint
properly, however, if I click on the address bar and hit ENTER it paints
correctly (bizarre).

How do I get Netscape 6.0 to paint up the first time??? I am due to release
this in the next couple of weeks, any help would be greatly appreciated!
(Can be consistently reproduce using
dynapi.gui.scrollbar.html/dynapi.gui.scrolpane.html supplied with release)

Anyone had any success on IE 5.0 Mac??? If you have please send me any info
you can... I know it's less than ideal for DHTML, but I've been told to find
a way. I have a couple of Macs set up for testing if anyone needs patches
tested!

Thanks,

Michael Ellis
Solution Architect

Interlink Group, Inc.
Email: mic...@il... 

RE: Re[2]: [Dynapi-Dev] DynLayer Bug

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

I think the onresize code stopped working with our new onprecreate system
(not sure if the NS4 bug fix ever worked though).

I guess we're back at the NS4 resize-bug again :-)


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

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Robert Rainwater
> Verzonden: zaterdag 27 januari 2001 0:23
> Aan: DynAPI Development List
> Onderwerp: Re[2]: [Dynapi-Dev] DynLayer Bug
>
>
>
> I don't recall any fix being made for this bug.  As far as I can tell,
> nothing has changed with the code that would have fixed this.
>
> --
> // Robert Rainwater
>
> On 1/26/2001, 6:18:22 PM EST, Abel wrote about "[Dynapi-Dev]
> DynLayer Bug":
>
> > that bug was fixed already doesn't it?
>
> > i remembered the following post:
>
> > -----Original Message-----
> > From: dyn...@li...
> > [mailto:dyn...@li...]On Behalf Of
> > no...@so...
> > Sent: Martes, 09 de Enero de 2001 01:40 p.m.
> > To: no...@so...; no...@so...;
> > dyn...@so...
> > Subject: [Dynapi-Dev] [Bug #128201] Duplicating layers in case of NS4
> > when resizing the browser
>
>
> > Bug #128201, was updated on 2001-Jan-09 11:39
> > Here is a current snapshot of the bug.
>
> > Project: DynAPI 2
> > Category: None
> > Status: Open
> > Resolution: None
> > Bug Group: None
> > Priority: 5
> > Submitted by: nobody
> > Assigned to : nobody
> > Summary: Duplicating layers in case of NS4 when resizing the browser
>
> > Details: We should avoid calling invokeEvent('create') in
> > DynLayer.createElement when
> > it is called from DynDocument.recreateAll. (The latter  is
> called after the
> > NS 4.x browser window is resized.)
> > The 'create' event duplicates all the layers which are created in custom
> > widgets' onCreate event handlers
> > when we resize the NS 4.x browser.
>
> > For detailed info, follow this link:
> > http://sourceforge.net/bugs/?func=detailbug&bug_id=128201&group_id=5757
>
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>
>
>
> > -----Original Message-----
> > From: dyn...@li...
> > [mailto:dyn...@li...]On Behalf Of Nathan
> > Winder
> > Sent: Viernes, 26 de Enero de 2001 05:05 p.m.
> > To: dyn...@li...
> > Subject: [Dynapi-Dev] DynLayer Bug
>
>
> > I was working with DynLayers and I discovered a bug in Netscape 4
>
> > When the Browser Window is resized it invokes "oncreate" and
> results in a
> > program defined error saying that certain elements, ei.
> DynLayers, which I
> > created in the oncreate function are already created, and are
> children of
> > the parent DynLayer. This error does not however occur in ie.
>
> > I have not had a chance to look at DynLayer source yet, but
> when I figure
> > out the problem I will send the solution. However I might not be bale to
> > figure it out, so I will figure out what is causeing the error
> and send you
> > that.
>
> > _________________________________________________________________
> > Get your FREE download of MSN Explorer at http://explorer.msn.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 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] DynLayer Bug

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

I don't recall any fix being made for this bug.  As far as I can tell,
nothing has changed with the code that would have fixed this.

-- 
// Robert Rainwater

On 1/26/2001, 6:18:22 PM EST, Abel wrote about "[Dynapi-Dev] DynLayer Bug":

> that bug was fixed already doesn't it?

> i remembered the following post:

> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]On Behalf Of
> no...@so...
> Sent: Martes, 09 de Enero de 2001 01:40 p.m.
> To: no...@so...; no...@so...;
> dyn...@so...
> Subject: [Dynapi-Dev] [Bug #128201] Duplicating layers in case of NS4
> when resizing the browser


> Bug #128201, was updated on 2001-Jan-09 11:39
> Here is a current snapshot of the bug.

> Project: DynAPI 2
> Category: None
> Status: Open
> Resolution: None
> Bug Group: None
> Priority: 5
> Submitted by: nobody
> Assigned to : nobody
> Summary: Duplicating layers in case of NS4 when resizing the browser

> Details: We should avoid calling invokeEvent('create') in
> DynLayer.createElement when
> it is called from DynDocument.recreateAll. (The latter  is called after the
> NS 4.x browser window is resized.)
> The 'create' event duplicates all the layers which are created in custom
> widgets' onCreate event handlers
> when we resize the NS 4.x browser.

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

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



> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]On Behalf Of Nathan
> Winder
> Sent: Viernes, 26 de Enero de 2001 05:05 p.m.
> To: dyn...@li...
> Subject: [Dynapi-Dev] DynLayer Bug


> I was working with DynLayers and I discovered a bug in Netscape 4

> When the Browser Window is resized it invokes "oncreate" and results in a
> program defined error saying that certain elements, ei. DynLayers, which I
> created in the oncreate function are already created, and are children of
> the parent DynLayer. This error does not however occur in ie.

> I have not had a chance to look at DynLayer source yet, but when I figure
> out the problem I will send the solution. However I might not be bale to
> figure it out, so I will figure out what is causeing the error and send you
> that.

> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.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 Snapshots: http://dynapi.sourceforge.net/snapshot/
DynAPI Homepage: http://dynapi.sourceforge.net/

RE: [Dynapi-Dev] DynLayer Bug

[<abe...@al...>]

that bug was fixed already doesn't it?

i remembered the following post:

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of
no...@so...
Sent: Martes, 09 de Enero de 2001 01:40 p.m.
To: no...@so...; no...@so...;
dyn...@so...
Subject: [Dynapi-Dev] [Bug #128201] Duplicating layers in case of NS4
when resizing the browser


Bug #128201, was updated on 2001-Jan-09 11:39
Here is a current snapshot of the bug.

Project: DynAPI 2
Category: None
Status: Open
Resolution: None
Bug Group: None
Priority: 5
Submitted by: nobody
Assigned to : nobody
Summary: Duplicating layers in case of NS4 when resizing the browser

Details: We should avoid calling invokeEvent('create') in
DynLayer.createElement when
it is called from DynDocument.recreateAll. (The latter  is called after the
NS 4.x browser window is resized.)
The 'create' event duplicates all the layers which are created in custom
widgets' onCreate event handlers
when we resize the NS 4.x browser.

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

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



-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Nathan
Winder
Sent: Viernes, 26 de Enero de 2001 05:05 p.m.
To: dyn...@li...
Subject: [Dynapi-Dev] DynLayer Bug


I was working with DynLayers and I discovered a bug in Netscape 4

When the Browser Window is resized it invokes "oncreate" and results in a
program defined error saying that certain elements, ei. DynLayers, which I
created in the oncreate function are already created, and are children of
the parent DynLayer. This error does not however occur in ie.

I have not had a chance to look at DynLayer source yet, but when I figure
out the problem I will send the solution. However I might not be bale to
figure it out, so I will figure out what is causeing the error and send you
that.

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com


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

[Dynapi-Dev] DynLayer Bug

[Nathan W. <win...@ho...>]

I was working with DynLayers and I discovered a bug in Netscape 4

When the Browser Window is resized it invokes "oncreate" and results in a 
program defined error saying that certain elements, ei. DynLayers, which I 
created in the oncreate function are already created, and are children of 
the parent DynLayer. This error does not however occur in ie.

I have not had a chance to look at DynLayer source yet, but when I figure 
out the problem I will send the solution. However I might not be bale to 
figure it out, so I will figure out what is causeing the error and send you 
that.

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

Re[2]: [Dynapi-Dev] getDocument

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

Yes, I like the way you collected the common properties of both and
combined them.  It makes the dynlayer and dyndocument much more
friendlier to work with.

Also, I think that the Netscape 6 problems need to be the highest
priority right now.  I know there have been fixes to the events.  But
one of the major problems is with the getContentW/H since NS 6 is a
peice of crap, and doesn't initialize these offsetW/Height until it
wants to.

-- 
// Robert Rainwater

On 1/26/2001, 2:49:53 AM EST, Pascal wrote about "[Dynapi-Dev] getDocument":

> Now that the release is finished, I think we should change the object model
> of the dynapi abit.
> I want to make the same changes as done in dynacore, making a dynobject off
> which the dyndocument and dynlayer are based. This makes things slightly
> smaller and also easier to maintain (all  parent-child stuff is controlled
> in the DynObject and updating that will make the DynLayer and DynDocument
> work the same with one single change)

> Also dyndocuments should be added to the dynapi, this makes a better
> object-tree available.. the DynAPI object will then contain child objects
> (dyndocuments)  and this also means that all layers created can be freeed
> from the unLoad event of the DynAPI (simply walk thru all children of the
> DynAPI object, and call deleteAllChildren())

> I also think the getdocument() is not needed anymore (seeing as I have
> removed it from dynacore, and everything works)

> the findLayers() extension should be a method of the DynDocument, not the
> DynAPI object.. this looks more logicall:

> DynAPI.document.findLayers()


> The eventMethod should be possible to combine into one for DynLayer and
> DynDocument, so that it can be attached to the DynObject (I've done this
> already, but I think some small bugs for document-events are still
> happening).


> any ideas, comments,rocks?

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

>> -----Oorspronkelijk bericht-----
>> Van: dyn...@li...
>> [mailto:dyn...@li...]Namens Robert Rainwater
>> Verzonden: vrijdag 26 januari 2001 2:46
>> Aan: DynAPI Development List
>> Onderwerp: [Dynapi-Dev] getDocument
>>
>>
>>
>> I was wondering if it would be better to move DynAPI.getDocument() to
>> DynDocument.getDocument().  It seems more logical that getDocument
>> belongs to DynDocument.  Of course DynAPI.getDocument could be kept
>> for a while too.
>>
>> --
>> // Robert Rainwater
>> ----------------------
>> 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
>>


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


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

Re: [Dynapi-Dev] Using cab files instead of gz, for IE.

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

It seems like someone looked into this a while back and didn't find a
solution.  The problem is there is very little documentation on any of
this, including .jar and .gz compressed js files.

Even without the special compressed files, you can still use the
jspacked .js files which are much smaller than the originals. For me,
this is a much better solution, then doing a bunch of different
includes for different package types.

But we do need to fix the semicolon problems before we can use any
solution.

-- 
// Robert Rainwater

On 1/26/2001, 10:32:42 AM EST, Nuno wrote about "[Dynapi-Dev] Using cab files instead of gz, for IE.":

> Hi guys,

> I was wondering if it was possible to devise a way
> of using CAB files instead of GZ files for the compressed
> dynapi, on explorer. If it can be done, we wouldn't need to 
> configure the server, and consequently be able to construct
> a client-side user-friendly way of using the compressed dynapi
> in IE 

> Do you know something about this?


> best,
> NunoF



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


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

[Dynapi-Dev] Weirdness: More setHTML and NS nested layers

[Jeff <je...@we...>]

Ok, here's some weirdness for you:

Earlier, I posted a way to get the setHTML to work when writing inline styles
into nested layers in Netscape by removing the layer from the parent, writing
the style into it, then adding the layer back to the parent. Everything worked
fine.

It just so happens that I had been passing values to a function that wrote the
style into the layer, something like:

(pseudo-code)

function writeIt(text,fontSize, fontFamily,color) {

eval(layeName+".setHTML='<SPAN STYLE=\"font-size: " + fontSize + "px;
fontFamily: " + fontFamily + "; color:" + color +";\">" + text + "</span>");

}

Don't ask me why, I just happened to be doing it that way for the test. So, as I
said it worked fine. Then I decide to just pass the function a string
representing the entire style to be applied, something like this:

writeIt("text goes here","font-size: 13px;fontFamily: courier;color: white;");

function writeIt(text,style) {

eval(layeName+".setHTML='<SPAN STYLE=\" ' + style + ' \">" + text + "</span>");

}

Now, here's the weird part:

This second version works fine too... except for one thing: the font-size
doesn't get applied in Netscape (4.7 and 4.76 under Win98). The color and the
fontFamily do get applied however....  and the whole thing works in IE 5.0 and
5.5 (Win98). But that's just too strange... it can't be a CSS syntax thing,
since the cobbled together style string in the first example works fine. So
what's the deal?

-- Jeff Greenberg

RE: [Dynapi-Dev] LoadPanel alternative.

[Jay C. <jch...@ou...>]

Aaaugh! Why? Is this documented by MS or NS?

thanks,

-J

> -----Original Message-----
> From: Matthew Alan Shirey [mailto:ms...@go...]
> Sent: Friday, January 26, 2001 9:34 AM
> To: dyn...@li...
> Subject: RE: [Dynapi-Dev] LoadPanel alternative.
> 
> 
> There's also the minor problem that JavaScript cannot talk to 
> an Applet on
> the Mac...
> 
> M.
> 
> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]On Behalf Of francesco
> AGATI
> Sent: Friday, January 26, 2001 12:46 AM
> To: dyn...@li...
> Subject: Re: [Dynapi-Dev] LoadPanel alternative.
> 
> 
> Hi,
> 
> i have make something of similar with an applet like the 
> Remote Scripting of
> Microsoft
> and i have tested that this don't work with IE5 on 
> Machintosh, is like if
> the virtual machine
> don't see the class urlconnection
> 
> 
> ----- Original Message -----
> From: "Michael Pemberton" <mp...@ph...>
> To: <dyn...@li...>
> Sent: Friday, January 26, 2001 5:11 AM
> Subject: [Dynapi-Dev] LoadPanel alternative.
> 
> 
> > I've created a method of using Java to download the URL contents.
> >
> > It appears to work in bot NS4.7+ and IE5+.  I haven't got 
> access to an
> > IE4 installation to test it.
> >
> > Is there a developer out there who would be able to test it 
> in IE4 for
> > me?
> > Is there a developer out there who knows how I could parse 
> the contents
> > to extract the different sections of the page (<title> / <body> /
> > <script> sections).  The code used in the IO.js parseHTML 
> method works
> > only if the openning and closing tags are on the same line. 
>  This is ok
> > for the <title> but is not  great for the <body> and <script> tags.
> >
> > Thanks.
> > --
> > Michael Pemberton
> > mp...@ph...
> > ICQ: 12107010
> >
> >
> 
> 
> _______________________________________________
> 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] Works For Me

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

and to keep this project fun we like to use the "works for me" fix as often
as possible ;-)

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

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Doug Melvin
> Verzonden: vrijdag 26 januari 2001 21:39
> Aan: dyn...@li...
> Onderwerp: Re: [Dynapi-Dev] Works For Me
>
>
> Lucky you..
> My boss has been known to make us work for days on end just to find some
> little
> bug he SWEARS he saw but can't describe, explain or reproduce..
>
> Ugg..
> ----- Original Message -----
> From: "Matthew Alan Shirey" <ms...@go...>
> To: <dyn...@li...>
> Sent: Friday, January 26, 2001 9:36 AM
> Subject: RE: [Dynapi-Dev] Works For Me
>
>
> > In most development situations there is a "Work for Me" category for
> closing
> > a bug.  This does not delete the bug but leaves it open to someone to
> > challenge the finding with more information.  In my department
> we use this
> > cagegory rarely but it does come up from time to time.
> >
> > M.
> >
> > -----Original Message-----
> > From: dyn...@li...
> > [mailto:dyn...@li...]On Behalf Of Eytan
> > Heidingsfeld
> > Sent: Friday, January 26, 2001 2:11 AM
> > To: Dynapi-Dev
> > Subject: [Dynapi-Dev] Works For Me
> >
> >
> > I don't believe this. You can't close bugs on a works for me
> clause. When
> > creating an API it has to be stable on all systems. Not only on Robert
> > Rainwater system. Specially as a developer. When I client will come and
> > complain that your site tends to crash certain machines what
> are you going
> > to do? Tell him "Works For Me"
> >
> > 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 mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>

Re: [Dynapi-Dev] Works For Me

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

Lucky you..
My boss has been known to make us work for days on end just to find some
little
bug he SWEARS he saw but can't describe, explain or reproduce..

Ugg..
----- Original Message -----
From: "Matthew Alan Shirey" <ms...@go...>
To: <dyn...@li...>
Sent: Friday, January 26, 2001 9:36 AM
Subject: RE: [Dynapi-Dev] Works For Me


> In most development situations there is a "Work for Me" category for
closing
> a bug.  This does not delete the bug but leaves it open to someone to
> challenge the finding with more information.  In my department we use this
> cagegory rarely but it does come up from time to time.
>
> M.
>
> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]On Behalf Of Eytan
> Heidingsfeld
> Sent: Friday, January 26, 2001 2:11 AM
> To: Dynapi-Dev
> Subject: [Dynapi-Dev] Works For Me
>
>
> I don't believe this. You can't close bugs on a works for me clause. When
> creating an API it has to be stable on all systems. Not only on Robert
> Rainwater system. Specially as a developer. When I client will come and
> complain that your site tends to crash certain machines what are you going
> to do? Tell him "Works For Me"
>
> 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
>

RE: [Dynapi-Dev] Works For Me

[Matthew A. S. <ms...@go...>]

In most development situations there is a "Work for Me" category for closing
a bug.  This does not delete the bug but leaves it open to someone to
challenge the finding with more information.  In my department we use this
cagegory rarely but it does come up from time to time.

M.

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Eytan
Heidingsfeld
Sent: Friday, January 26, 2001 2:11 AM
To: Dynapi-Dev
Subject: [Dynapi-Dev] Works For Me


I don't believe this. You can't close bugs on a works for me clause. When
creating an API it has to be stable on all systems. Not only on Robert
Rainwater system. Specially as a developer. When I client will come and
complain that your site tends to crash certain machines what are you going
to do? Tell him "Works For Me"

8an


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

RE: [Dynapi-Dev] LoadPanel alternative.

[Matthew A. S. <ms...@go...>]

There's also the minor problem that JavaScript cannot talk to an Applet on
the Mac...

M.

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of francesco
AGATI
Sent: Friday, January 26, 2001 12:46 AM
To: dyn...@li...
Subject: Re: [Dynapi-Dev] LoadPanel alternative.


Hi,

i have make something of similar with an applet like the Remote Scripting of
Microsoft
and i have tested that this don't work with IE5 on Machintosh, is like if
the virtual machine
don't see the class urlconnection


----- Original Message -----
From: "Michael Pemberton" <mp...@ph...>
To: <dyn...@li...>
Sent: Friday, January 26, 2001 5:11 AM
Subject: [Dynapi-Dev] LoadPanel alternative.


> I've created a method of using Java to download the URL contents.
>
> It appears to work in bot NS4.7+ and IE5+.  I haven't got access to an
> IE4 installation to test it.
>
> Is there a developer out there who would be able to test it in IE4 for
> me?
> Is there a developer out there who knows how I could parse the contents
> to extract the different sections of the page (<title> / <body> /
> <script> sections).  The code used in the IO.js parseHTML method works
> only if the openning and closing tags are on the same line.  This is ok
> for the <title> but is not  great for the <body> and <script> tags.
>
> Thanks.
> --
> Michael Pemberton
> mp...@ph...
> ICQ: 12107010
>
>


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

[Dynapi-Dev] (no subject)

[francesco A. <fa...@we...>]

hi

i have see two problems with netscape

if the dragevents of a layer is enable the click and doubleclick events =
of the layer do not responds with
Netscape but responds with explorer

Francesco

[Dynapi-Dev] [Patch #103442] NS6 updates to dynlayer.js for use with my events.js patch

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

Patch #103442 has been updated. 

Project: dynapi
Category: None
Status: Open
Submitted by: camhart
Assigned to : nobody
Summary: NS6 updates to dynlayer.js for use with my events.js patch

-------------------------------------------------------
For more info, visit:

http://sourceforge.net/patch/?func=detailpatch&patch_id=103442&group_id=5757

RE: [Dynapi-Dev] getDocument

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

> 	Just two comments (my rocks supply is starving):

Probably because of the transportation problems with rocks..you ordered
yours from California aswell?

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

[Dynapi-Dev] [Patch #103359] NS6 event fixes

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

Patch #103359 has been updated. 

Project: dynapi
Category: DynAPI-Event
Status: Open
Submitted by: camhart
Assigned to : nobody
Summary: NS6 event fixes

Follow-Ups:

Date: 2001-Jan-26 08:09
By: camhart

Comment:
NS6 was grabbing mouseclicks on form elements in my previous patch. This is
now fixed.

-------------------------------------------------------

Date: 2001-Jan-22 19:55
By: nobody

Comment:
Tested and working
Richard Bennett
-------------------------------------------------------

-------------------------------------------------------
For more info, visit:

http://sourceforge.net/patch/?func=detailpatch&patch_id=103359&group_id=5757

[Dynapi-Dev] Using cab files instead of gz, for IE.

[Nuno F. <nun...@wi...>]

Hi guys,

I was wondering if it was possible to devise a way
of using CAB files instead of GZ files for the compressed
dynapi, on explorer. If it can be done, we wouldn't need to 
configure the server, and consequently be able to construct
a client-side user-friendly way of using the compressed dynapi
in IE 

Do you know something about this?


best,
NunoF

Re: [Dynapi-Dev] cross frame layer access

[Martin W. <mwe...@pl...>]

Hi Fridiric,

If you care, see on dynapi-help for my 2 Pfennig

Martin
,
On Fre, 26 Jan 2001 you wrote:
>Hello,
>
>According to the DynAPI2 tutorial part 6, I created 2 frames. From the f=
ile
>loaded in the first frame I created a layer in it and a layer in the oth=
er
>frame. Now I want to access from the second frame the layer of the first
>frame.

[Dynapi-Dev] cross frame layer access

[<f....@wa...>]

Hello,

According to the DynAPI2 tutorial part 6, I created 2 frames. From the file
loaded in the first frame I created a layer in it and a layer in the other
frame. Now I want to access from the second frame the layer of the first
frame.

I don't know how to get it.
here is the code.

1) in the first document:
------------------------
<Script language="Javascript" src="../dynapi/src/dynapi.js"></script>
<Script language="Javascript">

DynAPI.setLibraryPath('../dynapi/src/lib/')
DynAPI.include('dynapi.api.*')
DynAPI.include('dynapi.gui.label')
</script>

<script>
DynAPI.onLoad=function() {

 sectiontitle=new Label('sectiontitle')
 sectiontitle.moveTo(200,5)
 sectiontitle.setWidth(300)
 sectiontitle.setFontSize('25px; font-weight: bold;');
 sectiontitle.setText('Titre de section')
 DynAPI.document.addChild(sectiontitle)  // This is the layer I want to
access afterwards from the other frame

 menu=new DynDocument(parent.menu)
 testlayer=new DynLayer('menu1',5,10,100,100,'yellow')
 menu.addChild(testlayer)
}
</script>

2) in the document of the other frame
--------------------------------------
<Script language="Javascript" src="../dynapi/src/dynapi.js"></script>
<Script language="Javascript">

DynAPI.setLibraryPath('../dynapi/src/lib/')
DynAPI.include('dynapi.api.*')
DynAPI.include('dynapi.gui.label')
</script>

</HEAD>
<BODY>

<A HREF="#" onclick="top = DynAPI.getDocument(parent.top); titlesection =
top.children[titlesection]; titlesection.setText('new title');">new
title</A>



Could someone ligth me on the issue and tell me how to access from a frame a
layer created in another frame? Actually, is there a simple way implemented
in DynAPI2 to do so?

Many thanks.

Fred Leuba

Re: [Dynapi-Dev] getDocument

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

Pascal wrote:
> 
> Now that the release is finished, I think we should change the object model
> of the dynapi abit.

(... snip ...)

> The eventMethod should be possible to combine into one for DynLayer and
> DynDocument, so that it can be attached to the DynObject (I've done this
> already, but I think some small bugs for document-events are still
> happening).
>
> any ideas, comments,rocks?

	Just two comments (my rocks supply is starving):

	The main difference between document-events and the rest of events is that the
document doesn't have any "onmouseover"-"onmouseout" events and that other
elements have no "onload" or "onunload" events in the browser DOM. Other small
differences can be spotted by carefully reading the documentation of each
browser.
	A graphical representation of each browser's DOM (from JavaScript developer
point of view) will be a good idea for someone to prepare (myself, when my
workload is lower) so each developer can have a God's view over the objects at
his/her disposal before developping anything and also a good place to look
before complaining about this or that bug. These DOM views could be shown in a
web page/PDF doc/whatever-the-format so people can use them as basis for every
other thing.

	I hope this lights new roads ahead in DynAPI development...

	Raides J.

RE: [Dynapi-Dev] Works For Me

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

If your talking about the mouse x and y problem, I also posted a reply to
that bug stating that it worked on my machine as well (and on about 3 other
systems here at work).

Seeing that Robert is doing ALOT of work on getting patches and bug fixes
organised I think he has all the right to close bugs if he can't reproduce
it (or none of use can) to clean up the full bug list.

If the bug ever surfaces on someone elses system then it can always be
reopened or resubmitted... but for now this seems to work for us.

Please remember this is an opensource project (although not everyone has
full controll over the deletion/creation/modification in CVS for -should be-
obvious reasons) everyone IS capable of getting the full code and fixing
bugs them selves..

the way Robert is handling everything works for me.

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

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Eytan
> Heidingsfeld
> Verzonden: vrijdag 26 januari 2001 11:11
> Aan: Dynapi-Dev
> Onderwerp: [Dynapi-Dev] Works For Me
>
>
> I don't believe this. You can't close bugs on a works for me
> clause. When
> creating an API it has to be stable on all systems. Not only on Robert
> Rainwater system. Specially as a developer. When I client
> will come and
> complain that your site tends to crash certain machines what
> are you going
> to do? Tell him "Works For Me"
>
> 8an
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>

[Dynapi-Dev] Works For Me

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

I don't believe this. You can't close bugs on a works for me clause. When
creating an API it has to be stable on all systems. Not only on Robert
Rainwater system. Specially as a developer. When I client will come and
complain that your site tends to crash certain machines what are you going
to do? Tell him "Works For Me"

8an

[Dynapi-Dev] drag events

[francesco A. <fa...@we...>]

 i have make a modify
 to the drag events for disabling the drag of a layer
 
 i have add the property boolean canDrag at the layer
 at the DragBoundary
 
 When the layer is dragged this is moved only if this
 is set to true
 
 the default is true
 
 i have try this ono ie 5.5 win and ns4.08 win