Menu
▾
▴
dynapi-dev — List related to the current DynAPI Core development
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(75) |
Nov
(252) |
Dec
(418) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(659) |
Feb
(1039) |
Mar
(870) |
Apr
(235) |
May
(329) |
Jun
(251) |
Jul
(123) |
Aug
(119) |
Sep
(67) |
Oct
(194) |
Nov
(535) |
Dec
(133) |
| 2002 |
Jan
(122) |
Feb
(24) |
Mar
(29) |
Apr
(28) |
May
(16) |
Jun
(20) |
Jul
(11) |
Aug
(12) |
Sep
(13) |
Oct
(14) |
Nov
(23) |
Dec
(19) |
| 2003 |
Jan
(28) |
Feb
(170) |
Mar
(288) |
Apr
(211) |
May
(126) |
Jun
(166) |
Jul
(131) |
Aug
(102) |
Sep
(211) |
Oct
(301) |
Nov
(22) |
Dec
(6) |
| 2004 |
Jan
(14) |
Feb
(16) |
Mar
(7) |
Apr
|
May
(8) |
Jun
(25) |
Jul
(21) |
Aug
(2) |
Sep
(7) |
Oct
|
Nov
(2) |
Dec
(1) |
| 2005 |
Jan
(4) |
Feb
(2) |
Mar
(14) |
Apr
(24) |
May
(3) |
Jun
(7) |
Jul
(30) |
Aug
(5) |
Sep
(1) |
Oct
(3) |
Nov
|
Dec
(1) |
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
|
From: Brandon M. <bnd...@ho...> - 2000-11-14 15:42:28
|
> > > I've got a most unusual problem going on - and I'm looking to you guys > > for advice. > > > > The webapp I've written using DynAPI II is successfully running on 6 of > > 7 servers in a web farm. The files are identical on all the servers, and > > the servers are identical in setup etc. > > > > The only problem is that on this one box - the loadpanel.js doesn't seem > > to be functioning correctly. > > > > I don't know if you guys have witnessed this before - and if it's not > > remotely connecting to DynAPI - I can understand - it's just i've been > > thrashing through this problem for the last 4+ hours - and I'm at my > > wits end.... > > Its most probaly a security problem. Are you trying to load a page > that is own another server. I believe loadpanel only works for local > pages. Also, are you linking the scripts to other servers? Just some > ideas. Whats the error message that you get? > I'm not totally sure where the problem is occuring, but given Robert's angle he is right. There is a security issue in IE and Netscape that will cause problems when using loadpanel to load content from a server other than the server that loaded the base document. So the question is, are you trying to load a page outside of the original server from the URL which includes the loadpanel.js file? You also said that you where using a web farm. If you where to use a the SAME server name to access all of these servers then the problem probably is not within loadpanel. |
|
From: Brandon M. <bnd...@ho...> - 2000-11-14 15:35:46
|
The DynAPI as it stands is only partially modular. This is aparent by the fact that when one bug is fixed, it causes a problem in either the widgets, or somewhere else in the core. Take heart though. There's hope for this problem in the future! ----- Original Message ----- From: "Pascal Bestebroer" <pb...@oi...> To: <dyn...@li...> Sent: Tuesday, November 14, 2000 6:20 AM Subject: RE: [Dynapi-Dev] Default > > Answer: > Yes it is an integral part, but as you already mentioned > there is modularity, and also the fact that you might want > to use your own browser detection or another browser detection > in the future (just an idea :) > > > It's great that you have a Mac, and hopefully you'r capable > of debugging javascript because I tried to do it a couple of > times with people who own a Mac, they would tell me the errors > and I'd try to fix them one by one... and that doesn't work, so > we really need someone who can hack it on a Mac. > > > > Pascal Bestebroer > pb...@oi... > http://www.oibv.com > > > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Barre Bizon > Verzonden: maandag 13 november 2000 13:47 > Aan: dyn...@li... > Onderwerp: [Dynapi-Dev] Default > > > > Question: > Shouldn't browser.js be included by default when you create > dynlayers? > I mean it is an integral part of the DynAPI and cannot be > left out... > And as far as keeping modularity.. ok.. but it really seems > reduntant to always include browser.js as practically > nothing will work without it... > > Maybe I'm missing something, though, as I'm just starting > to check DynAPI2 out. :) > > Oh and by the way,I have access to a mac (I have it as a > testcomputer at my work desk) so I could help with the > development for mac. > I have worked extensivly with a modified version of the > first dynapi before, including the creation of a text > dropdown menu with extensive platform support. > I even made a simplified scroll that works with mac. > > checkout > http://www.saabusa.com/home/US/en/95_intro.xml > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Robert R. <rra...@ya...> - 2000-11-14 14:52:04
|
> I've got a most unusual problem going on - and I'm looking to you guys > for advice. > > The webapp I've written using DynAPI II is successfully running on 6 of > 7 servers in a web farm. The files are identical on all the servers, and > the servers are identical in setup etc. > > The only problem is that on this one box - the loadpanel.js doesn't seem > to be functioning correctly. > > I don't know if you guys have witnessed this before - and if it's not > remotely connecting to DynAPI - I can understand - it's just i've been > thrashing through this problem for the last 4+ hours - and I'm at my > wits end.... Its most probaly a security problem. Are you trying to load a page that is own another server. I believe loadpanel only works for local pages. Also, are you linking the scripts to other servers? Just some ideas. Whats the error message that you get? \\Robert -- rra...@ya... |
|
From: Pascal B. <pb...@oi...> - 2000-11-14 11:20:15
|
Answer: Yes it is an integral part, but as you already mentioned there is modularity, and also the fact that you might want to use your own browser detection or another browser detection in the future (just an idea :) It's great that you have a Mac, and hopefully you'r capable of debugging javascript because I tried to do it a couple of times with people who own a Mac, they would tell me the errors and I'd try to fix them one by one... and that doesn't work, so we really need someone who can hack it on a Mac. Pascal Bestebroer pb...@oi... http://www.oibv.com -----Oorspronkelijk bericht----- Van: dyn...@li... [mailto:dyn...@li...]Namens Barre Bizon Verzonden: maandag 13 november 2000 13:47 Aan: dyn...@li... Onderwerp: [Dynapi-Dev] Default Question: Shouldn't browser.js be included by default when you create dynlayers? I mean it is an integral part of the DynAPI and cannot be left out... And as far as keeping modularity.. ok.. but it really seems reduntant to always include browser.js as practically nothing will work without it... Maybe I'm missing something, though, as I'm just starting to check DynAPI2 out. :) Oh and by the way,I have access to a mac (I have it as a testcomputer at my work desk) so I could help with the development for mac. I have worked extensivly with a modified version of the first dynapi before, including the creation of a text dropdown menu with extensive platform support. I even made a simplified scroll that works with mac. checkout http://www.saabusa.com/home/US/en/95_intro.xml _______________________________________________ Dynapi-Dev mailing list Dyn...@li... http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Samuel, M. M <Sam...@ed...> - 2000-11-14 05:04:02
|
I've got a most unusual problem going on - and I'm looking to you guys for advice. The webapp I've written using DynAPI II is successfully running on 6 of 7 servers in a web farm. The files are identical on all the servers, and the servers are identical in setup etc. The only problem is that on this one box - the loadpanel.js doesn't seem to be functioning correctly. I don't know if you guys have witnessed this before - and if it's not remotely connecting to DynAPI - I can understand - it's just i've been thrashing through this problem for the last 4+ hours - and I'm at my wits end.... Thanks Mike |
|
From: Dan S. <dy...@fu...> - 2000-11-14 01:04:55
|
I've released 3 small patches to SourceForge with the necessary changes for my set of widgets to work properly (based on the latest 11-07 release). 1. New order of method calls in DynLayer.create() - this is needed for my widgets to draw correctly, the setSize() was called too soon etc. 2. I've added another method onto MouseEvent: e.cancelBrowserEvent() This is not the same as setBubble(). For Netscape the event handler needs to return a boolean value. Previously what we were doing was returning the "bubble" value, but there is a case where you need to enable bubbling, but still return "false" to Netscape (this is to stop text selection during drags etc). In Label I removed the "cover layer" idea and simply replaced with with an event listener that cancels the browser event, the result is the same. DragEvents has been updated to accomidate this change. I've repackaged dynapi-2000.11.07 with my widgets and it can be downloaded from: http://fury161.dyndns.org/dynapi-2000.11.07-danwidgets.zip This includes all the dynapi files with my new files in place. Mine are: /dynapi/js/images/* (scrollpane and arrow images) /dynapi/js/lib/dynapi/gui/* (new/updated widgets) /dynapi/examples/dynapi.gui.* (examples of each widget) Widgets: Label - updated with new listeners and new methods for "packing" which must be done manually now Button - a small button widget with metal styling (used for arrow buttons in PushPanel, but has support for text using Label) Sprite - this is merely a DynLayer with slide methods already attached, not sure if this is what anyone else had in mind but I think it would be valuable to hava separate widget specifically for use during animation. It could be the object that you attach other methods for a timeline or something like that. ButtonImage - quick port of the old buttonimage, in ScrollPane this will probably be replaced with just Button ViewPort - the equivalent of what used to be ScrollWindow ScrollBar - the scrollbar objects used in Scrollpane ScrollPane - the new "Scroll" widget, functionally complete, but not tested on Windows/IE PushPanel - a rewritten DynAPI1 pushpanel that extends off of ViewPort Notes: Actually both ScrollPane and PushPanel extend ViewPort, so they have the same set of methods. This shows how you can do inheritance (DynLayer->ViewPort->Scrollpane) in DynAPI2 without using any SuperClass type of tricks. No need for "super" methods because you rely solely on event listeners. LoadPanel can be used along with ScrollPane quite easily. All you do is: scrollpane.setContent(loadpanel) Tada! Now you can load files into loadpanel (loadpanel will resize), and scrollpane will scroll loadpanel (or any other widget you put inside it). Please test them out on Windows/Mac and post any patches needed. Again note: you either need my patches to 11-07 or use the api files included in my zip file mentioned above in order for my widgets to work properly. Over and out, Dan |
|
From: Scott A. L. <sc...@sc...> - 2000-11-14 00:05:02
|
Brandon is correct...using setHTML on a DynLayer will destroy any child DynLayers within it. You will probably have to make a special layer for containing the HTML within Layer1 so it does not destroy Layer2. Brandon Myers wrote: > > Well Eric, given the order of events that you set, if you where to setHTML > in a layer that contains child layers, you loose all of the child layers. > > ----- Original Message ----- > From: "Eric Gravel" <egr...@ho...> > To: <dyn...@li...> > Sent: Monday, November 13, 2000 6:29 PM > Subject: [Dynapi-Dev] Having problems with 3 level layers > > > I'm having some real bizarre problems and hope you guys can help me out > > in pin pointing them. > > > > Basically, I have an object that has Layer1. The object has 1 child > > Layer2 who in turn has 3 child (Layer3, Layer4, Layer5). > > > > I'd like to know how you guys would create and setup the layers? Right > > now what I do is create my layers (new DynLayer) in my object's > > constructor function and then in the Layer1 oncreate I call functions > > to change the Layer2's dimension and HTML contain and after that the > > Layer2's child dimension and HMTML. Unfortunately, setting Layer2 > > childs doesn't work and I don't know why. > > > > Thanks, > > > > Eric > > _________________________________________________________________________ > > Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. > > > > Share information about yourself, create your own public profile at > > http://profiles.msn.com. > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev -- scott andrew lepera ----------------------------------- web stuff: www.scottandrew.com music stuff: www.walkingbirds.com |
|
From: Brandon M. <bnd...@ho...> - 2000-11-13 23:50:26
|
Well Eric, given the order of events that you set, if you where to setHTML in a layer that contains child layers, you loose all of the child layers. ----- Original Message ----- From: "Eric Gravel" <egr...@ho...> To: <dyn...@li...> Sent: Monday, November 13, 2000 6:29 PM Subject: [Dynapi-Dev] Having problems with 3 level layers > I'm having some real bizarre problems and hope you guys can help me out > in pin pointing them. > > Basically, I have an object that has Layer1. The object has 1 child > Layer2 who in turn has 3 child (Layer3, Layer4, Layer5). > > I'd like to know how you guys would create and setup the layers? Right > now what I do is create my layers (new DynLayer) in my object's > constructor function and then in the Layer1 oncreate I call functions > to change the Layer2's dimension and HTML contain and after that the > Layer2's child dimension and HMTML. Unfortunately, setting Layer2 > childs doesn't work and I don't know why. > > Thanks, > > Eric > _________________________________________________________________________ > Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. > > Share information about yourself, create your own public profile at > http://profiles.msn.com. > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Eric G. <egr...@ho...> - 2000-11-13 23:29:07
|
I'm having some real bizarre problems and hope you guys can help me out in pin pointing them. Basically, I have an object that has Layer1. The object has 1 child Layer2 who in turn has 3 child (Layer3, Layer4, Layer5). I'd like to know how you guys would create and setup the layers? Right now what I do is create my layers (new DynLayer) in my object's constructor function and then in the Layer1 oncreate I call functions to change the Layer2's dimension and HTML contain and after that the Layer2's child dimension and HMTML. Unfortunately, setting Layer2 childs doesn't work and I don't know why. Thanks, Eric _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. |
|
From: Barre B. <ba...@ho...> - 2000-11-13 14:45:10
|
Nope. It has to do with the setClip function.
One line was removed from it causing it to access
properties not yet set.. it seems
At any rate, it works if you change
var c=this.css.clip
to
if (!this.created) return
var c=this.css.clip
in setClip
Line 356 i believe.
//Bart
> Under NS 4.08, the following error occurs using the 2000-
11-12b release:
>
> dynlayer.js - line 356
> c has no properties
>
> I've rolled dynlayer.js back to the 2000-11-09b release
and everything's fine. I
> think it has to do with the getClip function...
>
> Mike
>
|
|
From: Barre B. <ba...@ho...> - 2000-11-13 12:07:08
|
Question: Shouldn't browser.js be included by default when you create dynlayers? I mean it is an integral part of the DynAPI and cannot be left out... And as far as keeping modularity.. ok.. but it really seems reduntant to always include browser.js as practically nothing will work without it... Maybe I'm missing something, though, as I'm just starting to check DynAPI2 out. :) Oh and by the way,I have access to a mac (I have it as a testcomputer at my work desk) so I could help with the development for mac. I have worked extensivly with a modified version of the first dynapi before, including the creation of a text dropdown menu with extensive platform support. I even made a simplified scroll that works with mac. checkout http://www.saabusa.com/home/US/en/95_intro.xml |
|
From: Samuel, M. M <Sam...@ed...> - 2000-11-13 05:45:38
|
Under NS 4.08, the following error occurs using the 2000-11-12b release: dynlayer.js - line 356 c has no properties I've rolled dynlayer.js back to the 2000-11-09b release and everything's fine. I think it has to do with the getClip function... Mike |
|
From: Samuel, M. M <Sam...@ed...> - 2000-11-13 05:28:17
|
Sorry for yet another post. With the loadpanel.js - I've noticed that the loadpanel sets the HTML of the layer to the <iframe> or <iLayer> when created. This however conflicts with my need to setHTML of the layer prior to actually setURL. Since there's actually a check for the <iframe> tag to make sure it's been created - is there actually a need to setHTML to the <iframe> oncreate? What's the best method for this? What I'm trying to achieve is for the loadpanel to behave the same as the loadhtml.js file did - leave any html in the layer in place while the new content is loading Mike |
|
From: Samuel, M. M <Sam...@ed...> - 2000-11-13 03:46:10
|
Afternoon all!
I've been trying to work my way through the Loadpanel.js file... I'm trying to
see if I can help out with some of the issues and maybe even throw in some code
myself. Be warned however - that I do not understand all about the API as yet,
so bear with me please!
I'm using the 11-09 release of the loadpanel.js file - which I noticed had just
the one change (taking the eval statement off a line).
I cannot get the example to work under NS 4.04 - but I'm guessing that's not
such a bad thing now... It works under NS 4.08. However - I've noticed that when
clicking the file links under IE5.5 the actual layer doesn't change size. Under
NS4.08 - the layer resizes it's height to accomodate the extra content. Should
this be the case?
It relates to the line in the code:
this.autoH=true
this.autoW=false
this.isILayer=false
this.isIFrame=true
When I set autoH to false - it behaves exactly as IE5.5 does. Is there actually
a way to set this from the html page rather than having it specified in the JS
file?
Further down is this code segment:
LoadPanel.prototype.insertInlineElements = function() {
if (is.ns4 && this.isILayer) {
this.setHTML('<ilayer></ilayer>')
}
else {
if (is.ie5) this.setHTML('<DIV ID="'+this.id+'loadElement"
STYLE="behavior:url(#default#download)" style="display: none;"></DIV>');
if (is.ie4) {
if (this.useBuffer) {
this.setHTML('<IFRAME
ID="'+this.id+'loadElement" STYLE="visibility: hidden; display: none;"
onLoad="LoadQueue.loadHandler()"></IFRAME>');
}
else {
// size iframe to the layer
}
}
}
}
Specifically - the this.useBuffer statement... where does it get the useBuffer
property from? Is that a property of the iframe?
Okay - I'm writing this as I'm playing - so forgive my jumping around... :)
I've managed to get the loadpanel.js working under IE 4.01 now. It relates to
the if (this.useBuffer) statement. Without knowing what it's derived from, I
can't determine it's value. However, IE4.01 kept on bombing out any time there
was an attempt to get any attributes (or set any) for the IFrame... It relates
to the this.useBuffer not being true.
Full code from LoadPanel.prototype.insertInlineElements
** Notice missing code under the if (is.ie4) function
LoadPanel.prototype.insertInlineElements = function() {
if (is.ns4 && this.isILayer) {
this.setHTML('<ilayer></ilayer>')
}
else {
if (is.ie5) this.setHTML('<DIV ID="'+this.id+'loadElement"
STYLE="behavior:url(#default#download)" style="display: none;"></DIV>');
if (is.ie4) {
this.setHTML('<IFRAME
ID="'+this.id+'loadElement" STYLE="visibility: hidden; display: none;"
onLoad="LoadQueue.loadHandler()"></IFRAME>');
}
}
}
Full code from LoadQueue.prototype.loadNext
LoadQueue.prototype.loadNext = function() {
if (!this.busy && this.queue[this.index]) {
this.busy = true
var lpanel = this.currentLoadPanel = this.queue[this.index][1]
var url = this.currentURL = this.queue[this.index][0]
if (is.ns4) {
DynAPI.document.releaseMouseEvents()
var lyr=lpanel.elm
while(lyr.parentLayer!=window) lyr=lyr.parentLayer
lyr.onload=LoadQueue.loadHandler
lpanel.loadElement.onload=LoadQueue.loadHandler
lpanel.loadElement.src=url
}
else if (is.ie5) {
lpanel.loadElement.startDownload(url,LoadQueue.loadHandler)
}
else if (is.ie4) {
// HAS NOT BEEN TESTED
if (lpanel.elm.innerHTML.indexOf("<IFRAME") == -1) {
lpanel.insertInlineElements()
}
lpanel.timerID=setInterval("if
(document.frames['"+lpanel.id+"loadElement'].document.readyState=='interactive')
{clearInterval("+lpanel.toString()+".timerID);LoadQueue.loadHandler(document.fra
mes['"+lpanel.id+"loadElement'].document.body.innerHTML)}",250)
document.frames[lpanel.id+"loadElement"].document.location=url
}
this.index++
}
}
Hope this helps further development
Mike
|
|
From: Robert R. <rra...@ya...> - 2000-11-13 03:01:43
|
These issues should be resolved in the latest beta ( http://dynapi.sourceforge.net/beta/dynapi-11.12-beta.zip ). Hopefully everyone can test the beta so we can release it sometime soon. The only other major additions to it will be Dan's widgets. > Well, I'm currently porting some of the changes of the DynAPI into my > Dynacore dis. > and I'm walking into a few things, so here's a list of questions/remarks: > > 1) The elm={}, css={} and doc={} lines have been removed from the DynLayer > constructor.. > Why? There's now more lines added to the other methods that check for the > .created=true property > this is slower and requires more lines of code, so a bigger file size.. ?! > For webapps speed might > not be an issue, but for multi-media (dhtml sites, games, etc) this IS a big > issue. > > 2) setPageX() and setPageY() have been changed to call setX(), setY().. why? > This is obviously > slower (setX and setY call moveTo) AND more importantly not the same! the > original setPageX/Y sets > the pageX property, NOT the left property.. not sure how browsers handle > the differences, but it doesn't > sound right. > > 3) in the deleteChildElements there's no check to see if the child is > actually created, I think it should be > checked (again for reasons of speed, but also because it might use more > memory then required, setting > properties to false or empty while there not even created yet. > > 4) setBgImage() there was a bug-fix for NS in case the path was NULL, I > think because netscape won't repaint > the layer with an empty image, so you had to reset the bgcolor to make sure > it was showing correctly.. I think > that was the reason why it was there.. > > 5) Not sure about the current getClip() does it work correctly on an inline > div that > hasn't had a setSize() call? I think it should always read the real > css.clip values > > that's it for now :) > > I'll be trying to create a new benchmark test this weekend doing better > tests > of all functionality (previous benchmarks didn't include all, this one > should cover > more of the DynAPI) > > cya, > > Pascal Bestebroer > pa...@dy... > http://www.dynamic-core.net > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev \\Robert -- rra...@ya... |
|
From: Joachim L. <lu...@ho...> - 2000-11-10 20:58:17
|
Yes I did, but I never really understood its merits. It made me want to extend JavaScript to have more class-like classes instead of prototype-based, however. The XObject file I sent will do that. If the classes are built that way the objects have getClass(), isInstanceOf() and callSuper() methods, for instance. [callSuper() is actually called callMethod() as it doesn't require the called method to be in a superclass at that level.) There's also a clone() method (to make a clone of course :-), but I haven't tested it fully. It seems to work just fine in the places I have used it though. At 2000-11-10 18:03 , you wrote: >Have you had the opportunity to check out the SuperClass Object that was in >the API about 2 or 3 months back? > >I have since expanded on this to work in both IE and NS. It has been >extensivly tested and is virtually bug-free. (No bugs found for over a >month) > >I use it with a version of the API that I have been working on for over 3 >months. It is now an integrated part of the system, allowing creation of >very advanced web applications with simple code extending other objects. > >----- Original Message ----- >From: "Joachim Lundgren" <lu...@ho...> >To: <dyn...@li...> >Sent: Friday, November 10, 2000 9:51 AM >Subject: [Dynapi-Dev] XObject, a superclass > >> I have noticed y'all might wanna use a superclass-type I've been working >on. >> >> In the zip there is a stripped-down version I use (quite successfully) and >> some sort of documentation (which isn't finished - so an examination of >the >> source might reveal how it's supposed to work). >> >> If you need more thorough example than what's in the doc and source please >> let me know. >> >> /Lunna >> >_______________________________________________ >Dynapi-Dev mailing list >Dyn...@li... >http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Pascal B. <pa...@dy...> - 2000-11-10 20:39:33
|
Well, I'm currently porting some of the changes of the DynAPI into my
Dynacore dis.
and I'm walking into a few things, so here's a list of questions/remarks:
1) The elm={}, css={} and doc={} lines have been removed from the DynLayer
constructor..
Why? There's now more lines added to the other methods that check for the
.created=true property
this is slower and requires more lines of code, so a bigger file size.. ?!
For webapps speed might
not be an issue, but for multi-media (dhtml sites, games, etc) this IS a big
issue.
2) setPageX() and setPageY() have been changed to call setX(), setY().. why?
This is obviously
slower (setX and setY call moveTo) AND more importantly not the same! the
original setPageX/Y sets
the pageX property, NOT the left property.. not sure how browsers handle
the differences, but it doesn't
sound right.
3) in the deleteChildElements there's no check to see if the child is
actually created, I think it should be
checked (again for reasons of speed, but also because it might use more
memory then required, setting
properties to false or empty while there not even created yet.
4) setBgImage() there was a bug-fix for NS in case the path was NULL, I
think because netscape won't repaint
the layer with an empty image, so you had to reset the bgcolor to make sure
it was showing correctly.. I think
that was the reason why it was there..
5) Not sure about the current getClip() does it work correctly on an inline
div that
hasn't had a setSize() call? I think it should always read the real
css.clip values
that's it for now :)
I'll be trying to create a new benchmark test this weekend doing better
tests
of all functionality (previous benchmarks didn't include all, this one
should cover
more of the DynAPI)
cya,
Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net
|
|
From: Brandon M. <bnd...@ho...> - 2000-11-10 19:08:24
|
Have you had the opportunity to check out the SuperClass Object that was in the API about 2 or 3 months back? I have since expanded on this to work in both IE and NS. It has been extensivly tested and is virtually bug-free. (No bugs found for over a month) I use it with a version of the API that I have been working on for over 3 months. It is now an integrated part of the system, allowing creation of very advanced web applications with simple code extending other objects. ----- Original Message ----- From: "Joachim Lundgren" <lu...@ho...> To: <dyn...@li...> Sent: Friday, November 10, 2000 9:51 AM Subject: [Dynapi-Dev] XObject, a superclass > I have noticed y'all might wanna use a superclass-type I've been working on. > > In the zip there is a stripped-down version I use (quite successfully) and > some sort of documentation (which isn't finished - so an examination of the > source might reveal how it's supposed to work). > > If you need more thorough example than what's in the doc and source please > let me know. > > /Lunna > ---------------------------------------------------------------------------- ---- > |
|
From: Joachim L. <lu...@ho...> - 2000-11-10 14:51:40
|
I have noticed y'all might wanna use a superclass-type I've been working on. In the zip there is a stripped-down version I use (quite successfully) and some sort of documentation (which isn't finished - so an examination of the source might reveal how it's supposed to work). If you need more thorough example than what's in the doc and source please let me know. /Lunna |
|
From: Robert R. <rra...@ya...> - 2000-11-10 06:27:21
|
> In trying to get caught up with the latest versions I have a few questions.
> I'm a little unclear with the file structure and where things are supposed
> to be. The latest dynapi releases have no widgets - are the ones
> from 20001024-full.zip supposed to work with the latest or is the effort
> right now trying to get them to work and be re-integrated?
Yes, most of the widgets were removed recently. The idea is to have a
standard set of widgets (label, etc). Then, other people can offer
thre own packages separately. Its impossible to maintain people's
widgets in the main dynapi distribution. Since you've updated the
Label, viewport, etc, then they should be included in the next
release.
> I've made the necessary changes to my Label, ViewPort, ScrollBar,
> and ScrollWindow in order for them to work with the 11.06 release.
> Only 1 further change is needed/requested in dynlayer and that's
> to make SetSize the last command before issuing a create event:
>
> this.setVisible(this.visible)
> this.setSize(this.w,this.h)
> this.createChildElements()
> this.invokeEvent('create')
I'll make that change.
> Also, where are standard images (that are linked with widgets) going
> to be located? I think the images that are needed in widgets should be
> located along with the js files because they are essentially part of
> the api if widgets require them. Would the following structure be ok?:
>
> /dynapi/lib/
> /dynapi/lib/dynapi.js
> /dynapi/lib/api/
> /dynapi/lib/ext/
> /dynapi/lib/gui/
> /dynapi/lib/images/
> /dynapi/examples/
>
> That way we can require that you set the library path
> to "/dynapi/lib/", and no image directories have to sepecified
> when using dynwindow, or any others - they'll by default pick
> up the library path and use it +/images/widgetdir/. I realize
> there's an auto-include function now, but it should be easy to
> reconfigure it for such a directory structure.
The structure has changed a bit in the last release. Its now a true
file structure as in java. If you say include('dynapi.gui.xxx'), then
it loads xxx.js from <library-path>/dynapi/gui/ located in the library
path. This allows you to have separate packages than the dynapi
package (ex. widet-sets can be there own separate packages that will
be located in the library path, but in a separate directory than
dynapi). So, it now looks like:
js/
lib/
dynapi/
api/
dynlayer.js,etc...
gui/
...
anotherpackage/
gui/
etc.
So, the dynapi package should be separate than other peoples add-ons.
So, for the widgets that are to be included in the dynapi package,
they can have a images directory under the dynapi directory
<library-path>/dynapi/images/xxx.
> Next I think there should only be one set of widgets, none of these
> ibs, obc directories. Have one "gui" directory put em all in there,
> or at least the ones that should be part of the standard dynapi
> package. Other people can easily release their own "widget packs",
> but I think really they should be distributed and maintained
> separately if they are divergent from the structure/look/syntax of
> the "standard dynapi".
This issue should be solved with the new directory structure.
Previously when you said include('dynapi.gui.x'), it looked for gui
under the lib directory. Now it uses the packagename.
I posted the latest beta release at
http://dynapi.sourceforge.net/beta/dynapi-11.10-beta.zip. It removed
the .all and .unassigned arrays and renamed .allID and .unassignedID
to them. So to reference layers (or inline layers) by id you say:
DynAPI.document.all['layer1']. It also fixes the double-click problem
in inline layers in Netscape. It includes to loadPanel, but apparently
is does not work in IE 4, so this needs to be fixed. If you have your
widgets ready, then we can make a new release soon that will include
all of these changes.
\\Robert
--
rra...@ya...
|
|
From: Dan S. <dy...@fu...> - 2000-11-10 05:53:24
|
In trying to get caught up with the latest versions I have a few questions. I'm a little unclear with the file structure and where things are supposed to be. The latest dynapi releases have no widgets - are the ones from 20001024-full.zip supposed to work with the latest or is the effort right now trying to get them to work and be re-integrated?
I've made the necessary changes to my Label, ViewPort, ScrollBar, and ScrollWindow in order for them to work with the 11.06 release. Only 1 further change is needed/requested in dynlayer and that's to make SetSize the last command before issuing a create event:
this.setVisible(this.visible)
this.setSize(this.w,this.h)
this.createChildElements()
this.invokeEvent('create')
The reason is, the first resize event was being called before any html was written to the layer therefore it was impossible to get the content size. I could have used the create event but it's unneeded if this change is made (it saves you from making identicle resize and create event listeners in some cases which is nice).
Also, where are standard images (that are linked with widgets) going to be located? I think the images that are needed in widgets should be located along with the js files because they are essentially part of the api if widgets require them. Would the following structure be ok?:
/dynapi/lib/
/dynapi/lib/dynapi.js
/dynapi/lib/api/
/dynapi/lib/ext/
/dynapi/lib/gui/
/dynapi/lib/images/
/dynapi/examples/
That way we can require that you set the library path to "/dynapi/lib/", and no image directories have to sepecified when using dynwindow, or any others - they'll by default pick up the library path and use it +/images/widgetdir/. I realize there's an auto-include function now, but it should be easy to reconfigure it for such a directory structure.
Next I think there should only be one set of widgets, none of these ibs, obc directories. Have one "gui" directory put em all in there, or at least the ones that should be part of the standard dynapi package. Other people can easily release their own "widget packs", but I think really they should be distributed and maintained separately if they are divergent from the structure/look/syntax of the "standard dynapi".
For such a widget pack or extention, it'll be located in some directory off of /lib/ such as /lib/myextensions/. If images for that extention are needed, you can create your own /lib/myextensions/images/ directory and specify that to be the default location to pickup them up in the JS code. And when using the auto-include you'd do include('dynapi.myextensions.Widget') and not interfere with the base dynapi at all.
Other than that everything's working fine, I just need to finish off the updated Label this weekend and I'll post my stuff up this weekend. (I did not touch my LoadPanel, I assume it's working fine).
Dan
|
|
From: Robert R. <rra...@ya...> - 2000-11-10 02:06:19
|
This fix in events.js (invokeEvent) should fix the problem with
doubleclick not being called in Netscape:
DynLayer.prototype.invokeEvent=function(type,e) {
...
if (is.ns4 && is.platform=="other") { // <-- the problem is here
...
change that line to:
if (is.ns4) {
Now the doubleclick should work correctly. (I hope!)
\\Robert
--
rra...@ya...
|
|
From: Robert R. <rra...@ya...> - 2000-11-09 23:17:47
|
I've updated the beta at sourceforge. http://dynapi.sourceforge.net/beta/dynapi-11.09-beta.zip The major change is that the .all and .unassigned have been removed. The .allID and .unassignedID have been renamed to .all and .unassigned. Also, the deleteChild and deleteAllChildren should now be consistent with each other. \\Robert -- rra...@ya... |
|
From: Brandon M. <bnd...@ho...> - 2000-11-09 22:26:11
|
RE: [Dynapi-Dev] issues with 11-07 releaseno.
It's more like netscape changed the way they parse, and how they support =
DHTML between versions 4.04 and 4.06 of their browser.
Most of the scripts I had written prior to working with DynAPI, had been =
used with NS4.04, but due to script engine difference, I had to move up =
the minimums.
----- Original Message -----=20
From: Samuel, Michael M=20
To: 'dyn...@li...'=20
Sent: Thursday, November 09, 2000 3:55 PM
Subject: RE: [Dynapi-Dev] issues with 11-07 release
The problem with upgrading to a new version is that in the corporate =
environment I'm working in, they have set the minimums at IE4.01 and =
NS4.04. I can't alter that... Once NS6 becomes official -I'll be trying =
to lobby for that as the new minimum... but until then - I have to work =
with NS 4.04
=20
Does adding the line return false harm the application?
=20
Mike
-----Original Message-----
From: Pascal Bestebroer [mailto:pa...@dy...]
Sent: Friday, 10 November 2000 5:13 AM
To: dyn...@li...
Subject: RE: [Dynapi-Dev] issues with 11-07 release
It's not a bad thing.. the change that is, netscape 4.04 IS a bad =
thing, there are a few other
methods in the DynAPI that will popup the "not always return" =
message.. you should really try and upgrade to a newer version of =
Netscape
=20
Pascal Bestebroer
pa...@dy...=20
http://www.dynamic-core.net=20
=20
=20
-----Oorspronkelijk bericht-----
Van: dyn...@li... =
[mailto:dyn...@li...]Namens Samuel, Michael M
Verzonden: donderdag 9 november 2000 1:41
Aan: 'dyn...@li...'
Onderwerp: RE: [Dynapi-Dev] issues with 11-07 release
Okay - I think I may have fixed the following issue. Can someone =
tell me if the change I've made is a bad thing?=20
Nutscrape 4.04 was whinging that a particular function in =
events.js didn't always return a value:=20
DynLayer.prototype.captureMouseEvents=3Dfunction() {=20
if (!this.eventListeners) this.eventListeners=3D[]=20
this.hasEventListeners=3Dtrue=20
if (!this.created) return false=20
var elm=3Dthis.elm=20
if (is.ns4) elm.captureEvents(Event.MOUSEDOWN | =
Event.MOUSEUP | Event.CLICK | Event.DBLCLICK)=20
=
elm.onmousedown=3Delm.onmouseup=3Delm.onmouseover=3Delm.onmouseout=3Delm.=
onclick=3Delm.ondblclick=3DDynLayer.prototype.EventMethod
if (is.ie5) this.elm.oncontextmenu=3Dfunction() {return =
false}=20
return false=20
}=20
I added the last line "return false" and that appeased Netscape - =
and now the whole program works again - also using loadhtml.js in NS4 =
and IE 4+
Mike=20
-----Original Message-----=20
From: Samuel, Michael M [mailto:Sam...@ed...] =
Sent: Wednesday, 8 November 2000 5:28 PM=20
To: 'dyn...@li...'=20
Subject: RE: [Dynapi-Dev] issues with 11-07 release=20
Sorry for the extensive post of sourcecode. The errors appear =
onload.=20
Where can I get the loadPanel from?=20
Thanks=20
Mike=20
<Script Language=3D"Javascript" =
src=3D"/Include/dynlayer/dynapi.js"></script>=20
<Script Language=3D"Javascript">=20
var strUserLongList =3D <% Response.Write(chr(34) & strResults & =
Chr(34)) %>;=20
function makeUser(strAlias, strFullName, strType, strEdit){=20
this.Alias =3D strAlias;=20
this.FullName =3D strFullName;=20
this.Type =3D strType;=20
this.Edit =3D strEdit;=20
}=20
function loadUserIntoArray(){=20
if (strUserLongList !=3D ""){=20
var arrUserLongList =3D =
strUserLongList.split('&&');=20
var strSelectBox =3D "";=20
var arrUserIndiv;=20
for (var i=3D0;i<arrUserLongList.length;i++){=20
arrUserIndiv =3D =
arrUserLongList[i].split('!!');=20
arrUserList[i] =3D new =
makeUser(arrUserIndiv[0],arrUserIndiv[1],arrUserIndiv[2],arrUserIndiv[3])=
;=20
strSelectBox +=3D "<option =
value=3D'"+i+"'>"+arrUserIndiv[1]+"</option>";=20
}=20
strSelectBox =3D "<form name=3D'frmListUser' =
id=3D'frmListUser' onSubmit=3D'return false'><center><select =
id=3D'selListUser' name=3D'selListUser' =
size=3D'9'>"+strSelectBox+"</select></center></form>";
listLayer.setHTML(strSelectBox)=20
}else{=20
listLayer.setHTML("No results were =
returned.<br><form name=3DfrmListUser id=3DfrmListUser =
onSubmit=3D'return false'><center><select id=3D'selListUser' =
name=3D'selListUser' size=3D'9'><option value=3D''> =
</option></select></center></form>")
}=20
}=20
var arrUserList =3D new Array();=20
var strUserString =3D "";=20
DynAPI.setLibraryPath('/Include/dynlayer/lib')=20
DynAPI.include('dynapi.api.*')=20
DynAPI.include('dynapi.ext.loadhtml.js')=20
DynAPI.onLoad=3Dfunction() {=20
mainLayer =3D new DynLayer(null,0,0,650,410,'#C0C0C0')=20
headingLayer =3D new DynLayer(null,25,10,600,35,null)=20
findLayer =3D new DynLayer(null,25,60,250,25,null)=20
resultsLayer =3D new DynLayer(null,25,105,250,150,null)=20
descriptionLayer =3D new =
DynLayer(null,25,285,250,100,null)=20
descriptionContentsLayer =3D new =
DynLayer(null,5,5,240,90,null)=20
buttonLayer =3D new DynLayer(null,300,123,100,100,null)=20
listContainerLayer =3D new =
DynLayer(null,420,55,205,205,null)=20
listHeadingLayer =3D new DynLayer(null,5,5,195,40,null)=20
listLayer =3D new DynLayer(null,5,50,195,150,null)=20
instructionLayer =3D new =
DynLayer(null,300,285,325,100,null)=20
instructContentsLayer =3D new =
DynLayer(null,5,5,315,90,null)=20
=20
=
mainLayer.moveTo((this.document.getWidth()-mainLayer.w)/2,(this.document.=
getHeight()-mainLayer.h)/2)=20
=20
mainLayer.BorderL=3Dnew =
DynLayer(null,0,0,3,mainLayer.h,'#f0f0f0')=20
mainLayer.BorderT=3Dnew =
DynLayer(null,0,0,mainLayer.w,3,'#f0f0f0')=20
mainLayer.BorderR=3Dnew =
DynLayer(null,mainLayer.w-3,1,3,mainLayer.h-3,'#808080')=20
mainLayer.BorderB=3Dnew =
DynLayer(null,1,mainLayer.h-3,mainLayer.w-3,3,'#808080')=20
mainLayer.addChild(mainLayer.BorderL)=20
mainLayer.addChild(mainLayer.BorderT)=20
mainLayer.addChild(mainLayer.BorderR)=20
mainLayer.addChild(mainLayer.BorderB)=20
instructionLayer.BorderR=3Dnew =
DynLayer(null,0,0,1,instructionLayer.h,'#f0f0f0')=20
instructionLayer.BorderB=3Dnew =
DynLayer(null,0,0,instructionLayer.w,1,'#f0f0f0')=20
instructionLayer.BorderL=3Dnew =
DynLayer(null,instructionLayer.w-1,1,1,instructionLayer.h-1,'#808080')=20
instructionLayer.BorderT=3Dnew =
DynLayer(null,1,instructionLayer.h-1,instructionLayer.w-1,1,'#808080')=20
instructionLayer.addChild(instructionLayer.BorderL)=20
instructionLayer.addChild(instructionLayer.BorderT)=20
instructionLayer.addChild(instructionLayer.BorderR)=20
instructionLayer.addChild(instructionLayer.BorderB)=20
instructionLayer.addChild(instructContentsLayer)=20
descriptionLayer.BorderR=3Dnew =
DynLayer(null,0,0,1,descriptionLayer.h,'#808080')=20
descriptionLayer.BorderB=3Dnew =
DynLayer(null,0,0,descriptionLayer.w,1,'#808080')=20
descriptionLayer.BorderL=3Dnew =
DynLayer(null,descriptionLayer.w-1,1,1,descriptionLayer.h-1,'#f0f0f0')=20
descriptionLayer.BorderT=3Dnew =
DynLayer(null,1,descriptionLayer.h-1,descriptionLayer.w-1,1,'#f0f0f0')=20
descriptionLayer.addChild(descriptionLayer.BorderL)=20
descriptionLayer.addChild(descriptionLayer.BorderT)=20
descriptionLayer.addChild(descriptionLayer.BorderR)=20
descriptionLayer.addChild(descriptionLayer.BorderB)=20
descriptionLayer.addChild(descriptionContentsLayer)=20
listContainerLayer.BorderR=3Dnew =
DynLayer(null,0,0,1,listContainerLayer.h,'#808080')=20
listContainerLayer.BorderB=3Dnew =
DynLayer(null,0,0,listContainerLayer.w,1,'#808080')=20
listContainerLayer.BorderL=3Dnew =
DynLayer(null,listContainerLayer.w-1,1,1,listContainerLayer.h-1,'#f0f0f0'=
)=20
listContainerLayer.BorderT=3Dnew =
DynLayer(null,1,listContainerLayer.h-1,listContainerLayer.w-1,1,'#f0f0f0'=
)=20
listContainerLayer.addChild(listContainerLayer.BorderL)=20
listContainerLayer.addChild(listContainerLayer.BorderT)=20
listContainerLayer.addChild(listContainerLayer.BorderR)=20
listContainerLayer.addChild(listContainerLayer.BorderB)=20
listContainerLayer.addChild(listHeadingLayer)=20
listContainerLayer.addChild(listLayer)=20
headingLayer.setHTML('<h2><center><% =
Response.Write(strHeading) %></center></h2>')=20
findLayer.setHTML('<center><form onsubmit=3D"return =
false"><input type=3Dtext name=3DstrFindString> <input =
type=3Dbutton name=3DbtnFind value=3DFind =
onclick=3DfindUser(strFindString.value)></form></center>')
instructContentsLayer.setHTML('<span =
class=3DsmallFont><b>To find a user:</b><br>Enter a persons name in the =
text box and click Find.<br><br><i><b>Hint:</b> For best results, search =
using Initial and Surname (e.g. J Citizen)</i><span>')
buttonLayer.setHTML('<center><form onsubmit=3D"return =
false"><input type=3Dbutton name=3DbtnAdd value=3D"Add ->" =
onclick=3DmoveUser(1)><br><input type=3Dbutton name=3DbtnRemove =
value=3D"<- Remove" onclick=3DmoveUser(0)><br><input type=3Dbutton =
name=3DbtnSave value=3DSave onClick=3DsaveChanges()></form><center>')
listLayer.setHTML('<span class=3DsmallFont><b>Please =
Wait...</b><br><br>Loading list of users</span>')=20
listHeadingLayer.setHTML('<center><span =
class=3DsmallFont><b><% Response.Write(strUserDescription) =
%></b></span></center>')
mainLayer.addChild(headingLayer)=20
mainLayer.addChild(findLayer)=20
mainLayer.addChild(resultsLayer)=20
mainLayer.addChild(descriptionLayer)=20
mainLayer.addChild(buttonLayer)=20
mainLayer.addChild(instructionLayer)=20
mainLayer.addChild(listContainerLayer)=20
DynAPI.document.addChild(mainLayer)=20
loadUserIntoArray()=20
}=20
-----Original Message-----=20
From: Robert Rainwater [mailto:rra...@ya...]=20
Sent: Wednesday, 8 November 2000 5:29 PM=20
To: Samuel, Michael M=20
Subject: Re: [Dynapi-Dev] issues with 11-07 release=20
Do you have an example where you get these errors (especially in =
the=20
events file)? The loadHTML is not going to be supported in this=20
distribution. It is being replaced with the LoadPanel, so it has =
not=20
been kept up. So, there is a good possibility that it does not =
work.=20
\\Robert=20
--=20
rra...@ya...=20
_______________________________________________=20
Dynapi-Dev mailing list=20
Dyn...@li...=20
http://lists.sourceforge.net/mailman/listinfo/dynapi-dev=20
|
|
From: Samuel, M. M <Sam...@ed...> - 2000-11-09 21:01:17
|
The problem with upgrading to a new version is that in the corporate environment I'm working in, they have set the minimums at IE4.01 and NS4.04. I can't alter that... Once NS6 becomes official -I'll be trying to lobby for that as the new minimum... but until then - I have to work with NS 4.04 Does adding the line return false harm the application? Mike -----Original Message----- From: Pascal Bestebroer [mailto:pa...@dy...] Sent: Friday, 10 November 2000 5:13 AM To: dyn...@li... Subject: RE: [Dynapi-Dev] issues with 11-07 release It's not a bad thing.. the change that is, netscape 4.04 IS a bad thing, there are a few other methods in the DynAPI that will popup the "not always return" message.. you should really try and upgrade to a newer version of Netscape Pascal Bestebroer pa...@dy... http://www.dynamic-core.net <http://www.dynamic-core.net/> -----Oorspronkelijk bericht----- Van: dyn...@li... [mailto:dyn...@li...]Namens Samuel, Michael M Verzonden: donderdag 9 november 2000 1:41 Aan: 'dyn...@li...' Onderwerp: RE: [Dynapi-Dev] issues with 11-07 release Okay - I think I may have fixed the following issue. Can someone tell me if the change I've made is a bad thing? Nutscrape 4.04 was whinging that a particular function in events.js didn't always return a value: DynLayer.prototype.captureMouseEvents=function() { if (!this.eventListeners) this.eventListeners=[] this.hasEventListeners=true if (!this.created) return false var elm=this.elm if (is.ns4) elm.captureEvents(Event.MOUSEDOWN | Event.MOUSEUP | Event.CLICK | Event.DBLCLICK) elm.onmousedown=elm.onmouseup=elm.onmouseover=elm.onmouseout=elm.onclick=elm.ond blclick=DynLayer.prototype.EventMethod if (is.ie5) this.elm.oncontextmenu=function() {return false} return false } I added the last line "return false" and that appeased Netscape - and now the whole program works again - also using loadhtml.js in NS4 and IE 4+ Mike -----Original Message----- From: Samuel, Michael M [ mailto:Sam...@ed... <mailto:Sam...@ed...> ] Sent: Wednesday, 8 November 2000 5:28 PM To: 'dyn...@li...' Subject: RE: [Dynapi-Dev] issues with 11-07 release Sorry for the extensive post of sourcecode. The errors appear onload. Where can I get the loadPanel from? Thanks Mike <Script Language="Javascript" src="/Include/dynlayer/dynapi.js"></script> <Script Language="Javascript"> var strUserLongList = <% Response.Write(chr(34) & strResults & Chr(34)) %>; function makeUser(strAlias, strFullName, strType, strEdit){ this.Alias = strAlias; this.FullName = strFullName; this.Type = strType; this.Edit = strEdit; } function loadUserIntoArray(){ if (strUserLongList != ""){ var arrUserLongList = strUserLongList.split('&&'); var strSelectBox = ""; var arrUserIndiv; for (var i=0;i<arrUserLongList.length;i++){ arrUserIndiv = arrUserLongList[i].split('!!'); arrUserList[i] = new makeUser(arrUserIndiv[0],arrUserIndiv[1],arrUserIndiv[2],arrUserIndiv[3]); strSelectBox += "<option value='"+i+"'>"+arrUserIndiv[1]+"</option>"; } strSelectBox = "<form name='frmListUser' id='frmListUser' onSubmit='return false'><center><select id='selListUser' name='selListUser' size='9'>"+strSelectBox+"</select></center></form>"; listLayer.setHTML(strSelectBox) }else{ listLayer.setHTML("No results were returned.<br><form name=frmListUser id=frmListUser onSubmit='return false'><center><select id='selListUser' name='selListUser' size='9'><option value=''> </option></select></center></form>") } } var arrUserList = new Array(); var strUserString = ""; DynAPI.setLibraryPath('/Include/dynlayer/lib') DynAPI.include('dynapi.api.*') DynAPI.include('dynapi.ext.loadhtml.js') DynAPI.onLoad=function() { mainLayer = new DynLayer(null,0,0,650,410,'#C0C0C0') headingLayer = new DynLayer(null,25,10,600,35,null) findLayer = new DynLayer(null,25,60,250,25,null) resultsLayer = new DynLayer(null,25,105,250,150,null) descriptionLayer = new DynLayer(null,25,285,250,100,null) descriptionContentsLayer = new DynLayer(null,5,5,240,90,null) buttonLayer = new DynLayer(null,300,123,100,100,null) listContainerLayer = new DynLayer(null,420,55,205,205,null) listHeadingLayer = new DynLayer(null,5,5,195,40,null) listLayer = new DynLayer(null,5,50,195,150,null) instructionLayer = new DynLayer(null,300,285,325,100,null) instructContentsLayer = new DynLayer(null,5,5,315,90,null) mainLayer.moveTo((this.document.getWidth()-mainLayer.w)/2,(this.document.getHeig ht()-mainLayer.h)/2) mainLayer.BorderL=new DynLayer(null,0,0,3,mainLayer.h,'#f0f0f0') mainLayer.BorderT=new DynLayer(null,0,0,mainLayer.w,3,'#f0f0f0') mainLayer.BorderR=new DynLayer(null,mainLayer.w-3,1,3,mainLayer.h-3,'#808080') mainLayer.BorderB=new DynLayer(null,1,mainLayer.h-3,mainLayer.w-3,3,'#808080') mainLayer.addChild(mainLayer.BorderL) mainLayer.addChild(mainLayer.BorderT) mainLayer.addChild(mainLayer.BorderR) mainLayer.addChild(mainLayer.BorderB) instructionLayer.BorderR=new DynLayer(null,0,0,1,instructionLayer.h,'#f0f0f0') instructionLayer.BorderB=new DynLayer(null,0,0,instructionLayer.w,1,'#f0f0f0') instructionLayer.BorderL=new DynLayer(null,instructionLayer.w-1,1,1,instructionLayer.h-1,'#808080') instructionLayer.BorderT=new DynLayer(null,1,instructionLayer.h-1,instructionLayer.w-1,1,'#808080') instructionLayer.addChild(instructionLayer.BorderL) instructionLayer.addChild(instructionLayer.BorderT) instructionLayer.addChild(instructionLayer.BorderR) instructionLayer.addChild(instructionLayer.BorderB) instructionLayer.addChild(instructContentsLayer) descriptionLayer.BorderR=new DynLayer(null,0,0,1,descriptionLayer.h,'#808080') descriptionLayer.BorderB=new DynLayer(null,0,0,descriptionLayer.w,1,'#808080') descriptionLayer.BorderL=new DynLayer(null,descriptionLayer.w-1,1,1,descriptionLayer.h-1,'#f0f0f0') descriptionLayer.BorderT=new DynLayer(null,1,descriptionLayer.h-1,descriptionLayer.w-1,1,'#f0f0f0') descriptionLayer.addChild(descriptionLayer.BorderL) descriptionLayer.addChild(descriptionLayer.BorderT) descriptionLayer.addChild(descriptionLayer.BorderR) descriptionLayer.addChild(descriptionLayer.BorderB) descriptionLayer.addChild(descriptionContentsLayer) listContainerLayer.BorderR=new DynLayer(null,0,0,1,listContainerLayer.h,'#808080') listContainerLayer.BorderB=new DynLayer(null,0,0,listContainerLayer.w,1,'#808080') listContainerLayer.BorderL=new DynLayer(null,listContainerLayer.w-1,1,1,listContainerLayer.h-1,'#f0f0f0') listContainerLayer.BorderT=new DynLayer(null,1,listContainerLayer.h-1,listContainerLayer.w-1,1,'#f0f0f0') listContainerLayer.addChild(listContainerLayer.BorderL) listContainerLayer.addChild(listContainerLayer.BorderT) listContainerLayer.addChild(listContainerLayer.BorderR) listContainerLayer.addChild(listContainerLayer.BorderB) listContainerLayer.addChild(listHeadingLayer) listContainerLayer.addChild(listLayer) headingLayer.setHTML('<h2><center><% Response.Write(strHeading) %></center></h2>') findLayer.setHTML('<center><form onsubmit="return false"><input type=text name=strFindString> <input type=button name=btnFind value=Find onclick=findUser(strFindString.value)></form></center>') instructContentsLayer.setHTML('<span class=smallFont><b>To find a user:</b><br>Enter a persons name in the text box and click Find.<br><br><i><b>Hint:</b> For best results, search using Initial and Surname (e.g. J Citizen)</i><span>') buttonLayer.setHTML('<center><form onsubmit="return false"><input type=button name=btnAdd value="Add ->" onclick=moveUser(1)><br><input type=button name=btnRemove value="<- Remove" onclick=moveUser(0)><br><input type=button name=btnSave value=Save onClick=saveChanges()></form><center>') listLayer.setHTML('<span class=smallFont><b>Please Wait...</b><br><br>Loading list of users</span>') listHeadingLayer.setHTML('<center><span class=smallFont><b><% Response.Write(strUserDescription) %></b></span></center>') mainLayer.addChild(headingLayer) mainLayer.addChild(findLayer) mainLayer.addChild(resultsLayer) mainLayer.addChild(descriptionLayer) mainLayer.addChild(buttonLayer) mainLayer.addChild(instructionLayer) mainLayer.addChild(listContainerLayer) DynAPI.document.addChild(mainLayer) loadUserIntoArray() } -----Original Message----- From: Robert Rainwater [ mailto:rra...@ya... <mailto:rra...@ya...> ] Sent: Wednesday, 8 November 2000 5:29 PM To: Samuel, Michael M Subject: Re: [Dynapi-Dev] issues with 11-07 release Do you have an example where you get these errors (especially in the events file)? The loadHTML is not going to be supported in this distribution. It is being replaced with the LoadPanel, so it has not been kept up. So, there is a good possibility that it does not work. \\Robert -- rra...@ya... _______________________________________________ Dynapi-Dev mailing list Dyn...@li... http://lists.sourceforge.net/mailman/listinfo/dynapi-dev <http://lists.sourceforge.net/mailman/listinfo/dynapi-dev> |
175 messages has been excluded from this view by a project administrator.
