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: Siegel, D. <DS...@ai...> - 2000-11-27 10:09:32
|
Hy!
>There are several ways to strip comments from source code. It
>is easy to
>select a JS compression tool as standard. Or, we can write our own
>script/program to filter out comments of all files recursively under a
>directory. If it is desired, I can contribute it in Perl/Java/C.
I've an Code Stripping System running under PERL. It uses two
directories:
js
js/stripped
All files have to be in both directories. If your running codestripper.pl
in js, it searches all writable files in js/stripped, read the coresponding
file in js, strippe all comments and copy ist to js/stripped. The two
directories are necessary, if your using a revision control system.
The codestripper only touches files which are checked out.
Here is the code (comments are in german :-( ).
Bye
Dirk
#Header:
#$Id: codestripper.pl 1.1 1999/07/23 09:36:32 e567 i.B. $
#$ProjectName: I:\Projekte\ProNet_2_1\source\mks\DEV_Web\ProNet_2_1_dev.pj $
#$ProjectRevision: 1.1 $
#!/usr/bin/perl
# Codestripper für ProNet 2
# Progrmamiert von Dirk Siegel
# Begonnen am 27.05.1998
# Liest alle JavaScript Files eines Verzeichnisses ein
# und entfernt alle Kommentare, um Ladezeit zu sparen.
# Dabei wird jedes File Zeilenweise eingelesen und
# über die Suche mit Regulären Ausdrücken die Kommentar-
# Blöcke von '/*' bid '*/' entfernt. Danach werden alle
# Kommentare ab '//' entfernt.
# Lege das Unterverzeichnis fest
$directory = "./stripped/";
# Lese das aktuelle Verzeichnis ein
opendir(DIR,".");
@javascriptfiles = grep(/\.js/,readdir(DIR));
# print "Folgende Dateien werden gekuerzt:\n";
# print "@javascriptfiles\n\n";
# Führe für jedes JavaScript-File des Verzeichnisses aus:
foreach $arg (@javascriptfiles) {
# Öffne das File
# print "Oeffne das File $arg\n";
open(FILE,$arg) || die "FEHLER: Kann $! nicht oeffnen!\n";
# Erzeuge das Ausgabefile
# Teste, ob das File ausgecheckt ist
if (-w "$directory$arg") {
open(AUS,">$directory$arg") || die "FEHLER: Kann $! nicht
erzeugen!\n";
# print "$arg ist geoeffnet\n";
} else {
next;
}
$zaehler = 0;
$kommentar = 0;
$anzahl_zeilen = 0;
while (<FILE>) {
# print "Lese: $_";
$anzahl_zeilen++;
# Lösche bei Zeilen mit Kommentar alles nach dem '//'
s/(.*)\/\/.*/$1/g;
# Sind wir im Kommentarmode ?
if ( $kommentar == 1 ) {
# Wurde das Ende eines Kommentarblocks erreicht?
if (/\*\//) {
$kommentar = 0;
}
$zaehler++;
} else {
# Wurde der Anfang eines Kommentarblocks erreicht?
if ((/\/\*/) && !(/\/\*\#Header\:/)) {
$kommentar = 1;
$zaehler++;
} else {
# Lösche überflüssige Leerzeichen
s/\ \ */\ /g;
# Lösche alle Tabulatoren
s/\t*//g;
# Schreibe die Zeilen in das temporäre File,
wenn sie keine Leerzeilen sind
if (!( (/^$/) || (/^ $/))) {
print AUS "$_";
} else {
$zaehler++;
}
}
}
}
# Schließe die Files
close AUS;
close FILE;
print "In der Datei $arg wurden von $anzahl_zeilen Zeilen Code
$zaehler Zeilen entfernt\n";
# print "$arg wurde umgewandelt.\n";
}
print "\n\nDas Kuerzen der JavaScript Dateien ist abgeschlossen\n";
|
|
From: filippo <fi...@do...> - 2000-11-27 09:48:34
|
I got into the loading image problem for IE. I was writing a series of
images inside a table inside a layer forcing all the sizes, even if loaded
simply didn't show them up. This problem occur me when I'm showing more then
one image inside a layer.
It seems IE is lazy...so I forced it to reload the table with the images
inside the layer every time the DynAPI.onLoading() was fired. Simply:
DynAPI.onLoading() {
youlayer.setHTML(yourlayer.getHTML())
}
where yourlayer is the DynLayer where you show the images
nasty, but works
filippo della casa
> fi...@do...
>> 3manos X www.doubleyou.com
>>> +34 915223677 ext.16
|
|
From: Guangyi Wu <gua...@al...> - 2000-11-27 09:44:37
|
As a new comer, I feel it could have helped much to start, if there were comments in the scripts. I have to debug in both IE and NS to understand what is going on. On one side, comments waste bandwidth for production. On the other side, uncommented script files make development more and more difficult, as the DynAPI evolves. Further more, rare developers and testers can really try the code on all versions of browsers and platforms, it might be better to document the specific decisions with code, while others may not dig so much into it. DynAPI is much more elegant, and complicated as well, than normal JavaScripts, because OOP is heavily applied and many workarounds for different browsers/platforms are included. Comments will help both in development and bug fixes. There are several ways to strip comments from source code. It is easy to select a JS compression tool as standard. Or, we can write our own script/program to filter out comments of all files recursively under a directory. If it is desired, I can contribute it in Perl/Java/C. Just come into this idea, after I read the discussion about the semicolons. Cheers George |
|
From: Scott A. L. <sc...@sc...> - 2000-11-26 01:03:26
|
I have to agree that Brandon's SuperClass object is great. It automatically manages things like class instances and super methods, so you don't have to worry about overwriting anything. It's very slick, and little more like "real" OOP. I think we need an updated version released, though. ------ scott andrew lepera sc...@sc... web stuff: www.scottandrew.com music stuff: www.walkingbirds.com |
|
From: Doug M. <do...@cr...> - 2000-11-25 23:48:13
|
WE at AllTheWhile.com are interested in adding a Download Link for the = lates Dynapi and DynWidgets on our page, by this I mean a mirror (files = on our server as alternate download site) What say you? Thank you, Doug Melvin Integrated System Solutions: Design, Development, Implementation and = Support Creative-Workshop.com |
|
From: Doug M. <do...@cr...> - 2000-11-25 22:58:31
|
> No, NS is fine. It's pretty bizarre. I've been paring down the page > throughout the day to see if there's a happy medium. > > Darn those low bandwidth people. :-) I have a saying that comes to mind in these situations "Programming would be much easier without the users.. " - Doug Melvin :-) Thank you, Doug Melvin Integrated System Solutions: Design, Development, Implementation and Support Creative-Workshop.com |
|
From: Tim R. <ti...@my...> - 2000-11-25 19:47:51
|
Man, that's exactly what's happening with me... Hmm, I'll keep working on it and if I get any good solutions, I'll reply. That withstanding, I sure do love the DynAPI stuff. There's no way we could have done this site without it and gotten the 'coolness' factor we were told to provide. Tim -----Original Message----- From: dyn...@li... [mailto:dyn...@li...]On Behalf Of Doug Melvin Sent: Saturday, November 25, 2000 2:22 PM To: dyn...@li... Subject: Re: [Dynapi-Dev] Sometimes Loads, Sometimes Not... I have indeed run into this. I load an html document into a loadpanel object, setting the loadpanel's size while I'm at it, and in NS one or more images will often not load. if I press refresh a few time they will eventually show up. Also: I've noticed that IE likes you to load the document into the loadpanel and THEN set the size, whereas NS prefers you Set the size irst THEN load the document.. any suggestions? comments? ----- Original Message ----- From: "Tim Royal" <ti...@my...> To: <dyn...@li...> Sent: Saturday, November 25, 2000 10:57 AM Subject: [Dynapi-Dev] Sometimes Loads, Sometimes Not... > Howdy howdy... > > Has anyone run into an issue where images referenced in the HTML portion of > a dynlayer don't load? the rest of the layer loads, initializes, and > displays, but images contained within simply never arrive? I have been using > DynAPI stuff for several months; loving it. > > Yesterday,w e did some modem testing, and were surprised to find that > instead of being slower (which we expected, obviously), certain elements in > DynLayers simply never loaded at all? What's odd is that it wasn't any > particular DynLayers at any given time (clearing the cache, trying again, > etc.?) > > Anyone else run into this, or am I the lucky one? :-) > > Great stuff, BTW. Soon, I'll be able to send a link, so y'all can see the > site. > > Thanks > > Tim > > Specs: > > Pentium 733 Mhz, 56K Modem, IE 5.0 > > > > > _______________________________________________ Dynapi-Dev mailing list Dyn...@li... http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Tim R. <ti...@my...> - 2000-11-25 19:45:55
|
No, NS is fine. It's pretty bizarre. I've been paring down the page throughout the day to see if there's a happy medium. Darn those low bandwidth people. :-) Tim -----Original Message----- From: dyn...@li... [mailto:dyn...@li...]On Behalf Of Brandon Myers Sent: Saturday, November 25, 2000 11:11 AM To: dyn...@li... Subject: Re: [Dynapi-Dev] Sometimes Loads, Sometimes Not... Does NS do the same thing? I hear that there is an IE bug with image loading inside layers. ----- Original Message ----- From: "Tim Royal" <ti...@my...> To: <dyn...@li...> Sent: Saturday, November 25, 2000 1:57 PM Subject: [Dynapi-Dev] Sometimes Loads, Sometimes Not... > Howdy howdy... > > Has anyone run into an issue where images referenced in the HTML portion of > a dynlayer don't load? the rest of the layer loads, initializes, and > displays, but images contained within simply never arrive? I have been using > DynAPI stuff for several months; loving it. > > Yesterday,w e did some modem testing, and were surprised to find that > instead of being slower (which we expected, obviously), certain elements in > DynLayers simply never loaded at all? What's odd is that it wasn't any > particular DynLayers at any given time (clearing the cache, trying again, > etc.?) > > Anyone else run into this, or am I the lucky one? :-) > > Great stuff, BTW. Soon, I'll be able to send a link, so y'all can see the > site. > > Thanks > > Tim > > Specs: > > Pentium 733 Mhz, 56K Modem, IE 5.0 > > > _______________________________________________ > 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: Doug M. <do...@cr...> - 2000-11-25 19:23:44
|
I have indeed run into this. I load an html document into a loadpanel object, setting the loadpanel's size while I'm at it, and in NS one or more images will often not load. if I press refresh a few time they will eventually show up. Also: I've noticed that IE likes you to load the document into the loadpanel and THEN set the size, whereas NS prefers you Set the size irst THEN load the document.. any suggestions? comments? ----- Original Message ----- From: "Tim Royal" <ti...@my...> To: <dyn...@li...> Sent: Saturday, November 25, 2000 10:57 AM Subject: [Dynapi-Dev] Sometimes Loads, Sometimes Not... > Howdy howdy... > > Has anyone run into an issue where images referenced in the HTML portion of > a dynlayer don't load? the rest of the layer loads, initializes, and > displays, but images contained within simply never arrive? I have been using > DynAPI stuff for several months; loving it. > > Yesterday,w e did some modem testing, and were surprised to find that > instead of being slower (which we expected, obviously), certain elements in > DynLayers simply never loaded at all? What's odd is that it wasn't any > particular DynLayers at any given time (clearing the cache, trying again, > etc.?) > > Anyone else run into this, or am I the lucky one? :-) > > Great stuff, BTW. Soon, I'll be able to send a link, so y'all can see the > site. > > Thanks > > Tim > > Specs: > > Pentium 733 Mhz, 56K Modem, IE 5.0 > > > > > |
|
From: Brandon M. <bnd...@ho...> - 2000-11-25 19:10:11
|
Does NS do the same thing? I hear that there is an IE bug with image loading inside layers. ----- Original Message ----- From: "Tim Royal" <ti...@my...> To: <dyn...@li...> Sent: Saturday, November 25, 2000 1:57 PM Subject: [Dynapi-Dev] Sometimes Loads, Sometimes Not... > Howdy howdy... > > Has anyone run into an issue where images referenced in the HTML portion of > a dynlayer don't load? the rest of the layer loads, initializes, and > displays, but images contained within simply never arrive? I have been using > DynAPI stuff for several months; loving it. > > Yesterday,w e did some modem testing, and were surprised to find that > instead of being slower (which we expected, obviously), certain elements in > DynLayers simply never loaded at all? What's odd is that it wasn't any > particular DynLayers at any given time (clearing the cache, trying again, > etc.?) > > Anyone else run into this, or am I the lucky one? :-) > > Great stuff, BTW. Soon, I'll be able to send a link, so y'all can see the > site. > > Thanks > > Tim > > Specs: > > Pentium 733 Mhz, 56K Modem, IE 5.0 > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Tim R. <ti...@my...> - 2000-11-25 18:58:36
|
Howdy howdy... Has anyone run into an issue where images referenced in the HTML portion of a dynlayer don't load? the rest of the layer loads, initializes, and displays, but images contained within simply never arrive? I have been using DynAPI stuff for several months; loving it. Yesterday,w e did some modem testing, and were surprised to find that instead of being slower (which we expected, obviously), certain elements in DynLayers simply never loaded at all? What's odd is that it wasn't any particular DynLayers at any given time (clearing the cache, trying again, etc.?) Anyone else run into this, or am I the lucky one? :-) Great stuff, BTW. Soon, I'll be able to send a link, so y'all can see the site. Thanks Tim Specs: Pentium 733 Mhz, 56K Modem, IE 5.0 |
|
From: Bart B. <ba...@ho...> - 2000-11-25 16:24:24
|
hmm... well.. actually it's going to be initialized exactly as a dynlayer .. it has some specific functionality yes, but for the most part is, in essense a dynlayer.
I'll explain further:
I'm creating a LayerMap for the API.
That is, a layerwidget that is added on to another layer and functions as a transparent layer you can set "imagemaps" on.
So it will have slightly less functionality then a dynlayer (you can't set HTML nor bgcolor etc.), and some extra stuff( event handling specific to certain areas that you set yourself etc.)
-----Ursprungligt meddelande-----
Från: Pascal Bestebroer <pa...@dy...>
Till: dyn...@li... <dyn...@li...>
Datum: den 25 november 2000 12:33
Ämne: RE: Re: SV: [Dynapi-Dev] Widget constructor
>but how to handle extra arguments specific for a widget?
>the DynAPI arguments are optional, so there are not always 8 arguments for
>the DynLayer (width,height,position,etc)
>
>there for what's the first widget argument ?
>
>Pascal Bestebroer
>pa...@dy...
>http://www.dynamic-core.net
>
>> -----Oorspronkelijk bericht-----
>> Van: dyn...@li...
>> [mailto:dyn...@li...]Namens Bart Bizon
>> Verzonden: zaterdag 25 november 2000 12:09
>> Aan: dyn...@li...
>> Onderwerp: SV: Re: SV: [Dynapi-Dev] Widget constructor
>>
>>
>> Well as I wrote it is done the same way that dynlayer will initialize
>>
>> function widget(){
>> this.construct(arguments)
>> // rest of your code
>> }
>>
>> -----Ursprungligt meddelande-----
>> Från: Pascal Bestebroer <pa...@dy...>
>> Till: dyn...@li... <dyn...@li...>
>> Datum: den 24 november 2000 18:17
>> Ämne: RE: Re: SV: [Dynapi-Dev] Widget constructor
>>
>>
>> >but how would you want to handle widget-specific initialisation?
>> >
>> >
>> >Pascal Bestebroer
>> >pa...@dy...
>> >http://www.dynamic-core.net
>> >
>> >> -----Oorspronkelijk bericht-----
>> >> Van: dyn...@li...
>> >> [mailto:dyn...@li...]Namens Barre Bizon
>> >> Verzonden: vrijdag 24 november 2000 11:35
>> >> Aan: dyn...@li...
>> >> Onderwerp: Re: Re: SV: [Dynapi-Dev] Widget constructor
>> >>
>> >>
>> >> hmm seems kindof obscure..
>> >> It strikes me as having a construct method to be a cleaner
>> >> way of doing initialization.. almost like calling super()
>> >> in Java... hm?
>> >> (The code below should work)
>> >>
>> >> function DynLayer() { this.construct(arguments) }
>> >> DynLayer.prototype.construct=function(){
>> >> var a=arguments[0]
>> >> ........etc.......
>> >>
>> >> function widget(){
>> >> this.construct(arguments)
>> >> }
>> >> widget.prototype=new DynLayer
>> >>
>> >>
>> >> > Forget what I wrote.... it should be this instead:
>> >> >
>> >> > function widget(argarray) {
>> >> > this.DynLayer = DynLayer
>> >> > eval("this.DynLayer("+argarray.join(",")+")")
>> >> > }
>> >> > widget.prototype = new DynLayer
>> >> >
>> >> > /Lunna
>> >> >
>> >> > At 2000-11-24 06:20 , you wrote:
>> >> > >For that particular case, use the array's join() method.
>> >> > >
>> >> > >function widget(argarray) {
>> >> > > this.DynLayer = DynLayer
>> >> > > this.DynLayer(argarray.join(","))
>> >> > >}
>> >> > >widget.prototype = new DynLayer
>> >> > >
>> >> > >/Lunna
>> >> > >
>> >> > >At 2000-11-24 02:07 , you wrote:
>> >> > >>Hmm... does not seem to work at all.
>> >> > >>IE4 says it doesn't support the property or method.
>> >> > >>Could you elaborate, or send me an example of this
>> >> being used somewhere?
>> >> > >>Another problem: DynLayer treats objects sent as the
>> >> first argument as a
>> >> > >>DynLayer object to setStyle after.
>> >> > >>And as arrays(the array arguments in this case) are
>> >> objects and
>> >> > >>correspondingly are identified as such, the setStyle
>> >> method will be called,
>> >> > >>which is not the intent.
>> >> > >>
>> >> > >>/Bart
>> >> > >>
>> >> > >>-----Ursprungligt meddelande-----
>> >> > >>Från: Dan Steinman <dy...@fu...>
>> >> > >>Till: dyn...@li... <dynapi-
>> >> de...@li...>
>> >> > >>Datum: den 24 november 2000 01:37
>> >> > >>Ämne: Re: [Dynapi-Dev] Widget constructor
>> >> > >>
>> >> > >>
>> >> > >>>Just make your widget constructor call the DynLayer as
>> >> a method:
>> >> > >>>
>> >> > >>>function widget(arguments) {
>> >> > >>> this.DynLayer = DynLayer
>> >> > >>> this.Dynlayer(arguments)
>> >> > >>>}
>> >> > >>>widget.prototype = new DynLayer
>> >> > >>>
>> >> > >>>Dan
>> >> > >>>
>> >> > >>>On Fri, Nov 24, 2000 at 12:39:05AM +0100, Bartek wrote:
>> >> > >>>> I was wondering whether it is a good idea to have
>> >> some inheritible
>> >> > >>constructor functionality for DynLayer.
>> >> > >>>> I want to be able to create a widget object that
>> >> extends the DynLayer and
>> >> > >>inherits its initialization, i.e so I wouldn't have to
>> >> rewrite the
>> >> > >>initialization code for the widget but instead do
>> >> something like this:
>> >> > >>>>
>> >> > >>>> ------------------------------------------
>> >> > >>>>
>> >> > >>>> function WidgetLayer(){
>> >> > >>>> this.construct(arguments)
>> >> > >>>> }
>> >> > >>>> WidgetLayer.prototype=new DynLayer
>> >> > >>>>
>> >> > >>>> -----------------------------------------------------
>> >> -
>> >> > >>>>
>> >> > >>>> and it would look something like this for dynlayer:
>> >> > >>>>
>> >> > >>>> -----------------------------------------------------
>> >> ----------------
>> >> > >>>>
>> >> > >>>> function DynLayer(){ this.construct(arguments) }
>> >> > >>>> DynLayer.prototype.construct=function(){
>> >> > >>>> alert()
>> >> > >>>> var a=arguments
>> >> > >>>> if (a.length==1 && a[0]!=null && typeof(a[0])
>> >> =="object")
>> >> > >>this.setStyle(a[0])
>> >> > >>>> else {
>> >> > >>>> this.id=a[0]||"JSDynLayer"+
>> >> (DynLayer.nullCount++)
>> >> > >>>> this.x=a[1]||0
>> >> > >>>> .......etc...
>> >> > >>>> }
>> >> > >>>> }
>> >> > >>>>
>> >> > >>>>
>> >> > ----------------------------------------------------------
>> >> -----------------
>> >> > >>>>
>> >> > >>>> I am trying to implent this as I write, to test it
>> >> out, and I'm having
>> >> > >>some problems.
>> >> > >>>> Maybe there is a better way of doing this... If so ,
>> >> please let me
>> >> > know. :)
>> >> > >>>> Or am I on the right track?
>> >> > >>>>
>> >> > >>>>
>> >> > >>>> /Bart
>> >> > >>>_______________________________________________
>> >> > >>>Dynapi-Dev mailing list
>> >> > >>>Dyn...@li...
>> >> > >>>http://lists.sourceforge.net/mailman/listinfo/dynapi-
>> >> dev
>> >> > >>
>> >> > >>_______________________________________________
>> >> > >>Dynapi-Dev mailing list
>> >> > >>Dyn...@li...
>> >> > >>http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>> >> > >
>> >> > >
>> >> > >_______________________________________________
>> >> > >Dynapi-Dev mailing list
>> >> > >Dyn...@li...
>> >> > >http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > Dynapi-Dev mailing list
>> >> > Dyn...@li...
>> >> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>> >>
>> >>
>> >> _______________________________________________
>> >> Dynapi-Dev mailing list
>> >> Dyn...@li...
>> >> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>> >>
>> >
>> >_______________________________________________
>> >Dynapi-Dev mailing list
>> >Dyn...@li...
>> >http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>>
>> _______________________________________________
>> 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: Pascal B. <pa...@dy...> - 2000-11-25 11:33:23
|
but how to handle extra arguments specific for a widget? the DynAPI arguments are optional, so there are not always 8 arguments for the DynLayer (width,height,position,etc) there for what's the first widget argument ? Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Bart Bizon > Verzonden: zaterdag 25 november 2000 12:09 > Aan: dyn...@li... > Onderwerp: SV: Re: SV: [Dynapi-Dev] Widget constructor > > > Well as I wrote it is done the same way that dynlayer will initialize > > function widget(){ > this.construct(arguments) > // rest of your code > } > > -----Ursprungligt meddelande----- > Från: Pascal Bestebroer <pa...@dy...> > Till: dyn...@li... <dyn...@li...> > Datum: den 24 november 2000 18:17 > Ämne: RE: Re: SV: [Dynapi-Dev] Widget constructor > > > >but how would you want to handle widget-specific initialisation? > > > > > >Pascal Bestebroer > >pa...@dy... > >http://www.dynamic-core.net > > > >> -----Oorspronkelijk bericht----- > >> Van: dyn...@li... > >> [mailto:dyn...@li...]Namens Barre Bizon > >> Verzonden: vrijdag 24 november 2000 11:35 > >> Aan: dyn...@li... > >> Onderwerp: Re: Re: SV: [Dynapi-Dev] Widget constructor > >> > >> > >> hmm seems kindof obscure.. > >> It strikes me as having a construct method to be a cleaner > >> way of doing initialization.. almost like calling super() > >> in Java... hm? > >> (The code below should work) > >> > >> function DynLayer() { this.construct(arguments) } > >> DynLayer.prototype.construct=function(){ > >> var a=arguments[0] > >> ........etc....... > >> > >> function widget(){ > >> this.construct(arguments) > >> } > >> widget.prototype=new DynLayer > >> > >> > >> > Forget what I wrote.... it should be this instead: > >> > > >> > function widget(argarray) { > >> > this.DynLayer = DynLayer > >> > eval("this.DynLayer("+argarray.join(",")+")") > >> > } > >> > widget.prototype = new DynLayer > >> > > >> > /Lunna > >> > > >> > At 2000-11-24 06:20 , you wrote: > >> > >For that particular case, use the array's join() method. > >> > > > >> > >function widget(argarray) { > >> > > this.DynLayer = DynLayer > >> > > this.DynLayer(argarray.join(",")) > >> > >} > >> > >widget.prototype = new DynLayer > >> > > > >> > >/Lunna > >> > > > >> > >At 2000-11-24 02:07 , you wrote: > >> > >>Hmm... does not seem to work at all. > >> > >>IE4 says it doesn't support the property or method. > >> > >>Could you elaborate, or send me an example of this > >> being used somewhere? > >> > >>Another problem: DynLayer treats objects sent as the > >> first argument as a > >> > >>DynLayer object to setStyle after. > >> > >>And as arrays(the array arguments in this case) are > >> objects and > >> > >>correspondingly are identified as such, the setStyle > >> method will be called, > >> > >>which is not the intent. > >> > >> > >> > >>/Bart > >> > >> > >> > >>-----Ursprungligt meddelande----- > >> > >>Från: Dan Steinman <dy...@fu...> > >> > >>Till: dyn...@li... <dynapi- > >> de...@li...> > >> > >>Datum: den 24 november 2000 01:37 > >> > >>Ämne: Re: [Dynapi-Dev] Widget constructor > >> > >> > >> > >> > >> > >>>Just make your widget constructor call the DynLayer as > >> a method: > >> > >>> > >> > >>>function widget(arguments) { > >> > >>> this.DynLayer = DynLayer > >> > >>> this.Dynlayer(arguments) > >> > >>>} > >> > >>>widget.prototype = new DynLayer > >> > >>> > >> > >>>Dan > >> > >>> > >> > >>>On Fri, Nov 24, 2000 at 12:39:05AM +0100, Bartek wrote: > >> > >>>> I was wondering whether it is a good idea to have > >> some inheritible > >> > >>constructor functionality for DynLayer. > >> > >>>> I want to be able to create a widget object that > >> extends the DynLayer and > >> > >>inherits its initialization, i.e so I wouldn't have to > >> rewrite the > >> > >>initialization code for the widget but instead do > >> something like this: > >> > >>>> > >> > >>>> ------------------------------------------ > >> > >>>> > >> > >>>> function WidgetLayer(){ > >> > >>>> this.construct(arguments) > >> > >>>> } > >> > >>>> WidgetLayer.prototype=new DynLayer > >> > >>>> > >> > >>>> ----------------------------------------------------- > >> - > >> > >>>> > >> > >>>> and it would look something like this for dynlayer: > >> > >>>> > >> > >>>> ----------------------------------------------------- > >> ---------------- > >> > >>>> > >> > >>>> function DynLayer(){ this.construct(arguments) } > >> > >>>> DynLayer.prototype.construct=function(){ > >> > >>>> alert() > >> > >>>> var a=arguments > >> > >>>> if (a.length==1 && a[0]!=null && typeof(a[0]) > >> =="object") > >> > >>this.setStyle(a[0]) > >> > >>>> else { > >> > >>>> this.id=a[0]||"JSDynLayer"+ > >> (DynLayer.nullCount++) > >> > >>>> this.x=a[1]||0 > >> > >>>> .......etc... > >> > >>>> } > >> > >>>> } > >> > >>>> > >> > >>>> > >> > ---------------------------------------------------------- > >> ----------------- > >> > >>>> > >> > >>>> I am trying to implent this as I write, to test it > >> out, and I'm having > >> > >>some problems. > >> > >>>> Maybe there is a better way of doing this... If so , > >> please let me > >> > know. :) > >> > >>>> Or am I on the right track? > >> > >>>> > >> > >>>> > >> > >>>> /Bart > >> > >>>_______________________________________________ > >> > >>>Dynapi-Dev mailing list > >> > >>>Dyn...@li... > >> > >>>http://lists.sourceforge.net/mailman/listinfo/dynapi- > >> dev > >> > >> > >> > >>_______________________________________________ > >> > >>Dynapi-Dev mailing list > >> > >>Dyn...@li... > >> > >>http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > >> > > > >> > > > >> > >_______________________________________________ > >> > >Dynapi-Dev mailing list > >> > >Dyn...@li... > >> > >http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > >> > > >> > > >> > _______________________________________________ > >> > Dynapi-Dev mailing list > >> > Dyn...@li... > >> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > >> > >> > >> _______________________________________________ > >> Dynapi-Dev mailing list > >> Dyn...@li... > >> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > >> > > > >_______________________________________________ > >Dynapi-Dev mailing list > >Dyn...@li... > >http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > |
|
From: Bart B. <ba...@ho...> - 2000-11-25 11:11:08
|
Well as I wrote it is done the same way that dynlayer will initialize
function widget(){
this.construct(arguments)
// rest of your code
}
-----Ursprungligt meddelande-----
Från: Pascal Bestebroer <pa...@dy...>
Till: dyn...@li... <dyn...@li...>
Datum: den 24 november 2000 18:17
Ämne: RE: Re: SV: [Dynapi-Dev] Widget constructor
>but how would you want to handle widget-specific initialisation?
>
>
>Pascal Bestebroer
>pa...@dy...
>http://www.dynamic-core.net
>
>> -----Oorspronkelijk bericht-----
>> Van: dyn...@li...
>> [mailto:dyn...@li...]Namens Barre Bizon
>> Verzonden: vrijdag 24 november 2000 11:35
>> Aan: dyn...@li...
>> Onderwerp: Re: Re: SV: [Dynapi-Dev] Widget constructor
>>
>>
>> hmm seems kindof obscure..
>> It strikes me as having a construct method to be a cleaner
>> way of doing initialization.. almost like calling super()
>> in Java... hm?
>> (The code below should work)
>>
>> function DynLayer() { this.construct(arguments) }
>> DynLayer.prototype.construct=function(){
>> var a=arguments[0]
>> ........etc.......
>>
>> function widget(){
>> this.construct(arguments)
>> }
>> widget.prototype=new DynLayer
>>
>>
>> > Forget what I wrote.... it should be this instead:
>> >
>> > function widget(argarray) {
>> > this.DynLayer = DynLayer
>> > eval("this.DynLayer("+argarray.join(",")+")")
>> > }
>> > widget.prototype = new DynLayer
>> >
>> > /Lunna
>> >
>> > At 2000-11-24 06:20 , you wrote:
>> > >For that particular case, use the array's join() method.
>> > >
>> > >function widget(argarray) {
>> > > this.DynLayer = DynLayer
>> > > this.DynLayer(argarray.join(","))
>> > >}
>> > >widget.prototype = new DynLayer
>> > >
>> > >/Lunna
>> > >
>> > >At 2000-11-24 02:07 , you wrote:
>> > >>Hmm... does not seem to work at all.
>> > >>IE4 says it doesn't support the property or method.
>> > >>Could you elaborate, or send me an example of this
>> being used somewhere?
>> > >>Another problem: DynLayer treats objects sent as the
>> first argument as a
>> > >>DynLayer object to setStyle after.
>> > >>And as arrays(the array arguments in this case) are
>> objects and
>> > >>correspondingly are identified as such, the setStyle
>> method will be called,
>> > >>which is not the intent.
>> > >>
>> > >>/Bart
>> > >>
>> > >>-----Ursprungligt meddelande-----
>> > >>Från: Dan Steinman <dy...@fu...>
>> > >>Till: dyn...@li... <dynapi-
>> de...@li...>
>> > >>Datum: den 24 november 2000 01:37
>> > >>Ämne: Re: [Dynapi-Dev] Widget constructor
>> > >>
>> > >>
>> > >>>Just make your widget constructor call the DynLayer as
>> a method:
>> > >>>
>> > >>>function widget(arguments) {
>> > >>> this.DynLayer = DynLayer
>> > >>> this.Dynlayer(arguments)
>> > >>>}
>> > >>>widget.prototype = new DynLayer
>> > >>>
>> > >>>Dan
>> > >>>
>> > >>>On Fri, Nov 24, 2000 at 12:39:05AM +0100, Bartek wrote:
>> > >>>> I was wondering whether it is a good idea to have
>> some inheritible
>> > >>constructor functionality for DynLayer.
>> > >>>> I want to be able to create a widget object that
>> extends the DynLayer and
>> > >>inherits its initialization, i.e so I wouldn't have to
>> rewrite the
>> > >>initialization code for the widget but instead do
>> something like this:
>> > >>>>
>> > >>>> ------------------------------------------
>> > >>>>
>> > >>>> function WidgetLayer(){
>> > >>>> this.construct(arguments)
>> > >>>> }
>> > >>>> WidgetLayer.prototype=new DynLayer
>> > >>>>
>> > >>>> -----------------------------------------------------
>> -
>> > >>>>
>> > >>>> and it would look something like this for dynlayer:
>> > >>>>
>> > >>>> -----------------------------------------------------
>> ----------------
>> > >>>>
>> > >>>> function DynLayer(){ this.construct(arguments) }
>> > >>>> DynLayer.prototype.construct=function(){
>> > >>>> alert()
>> > >>>> var a=arguments
>> > >>>> if (a.length==1 && a[0]!=null && typeof(a[0])
>> =="object")
>> > >>this.setStyle(a[0])
>> > >>>> else {
>> > >>>> this.id=a[0]||"JSDynLayer"+
>> (DynLayer.nullCount++)
>> > >>>> this.x=a[1]||0
>> > >>>> .......etc...
>> > >>>> }
>> > >>>> }
>> > >>>>
>> > >>>>
>> > ----------------------------------------------------------
>> -----------------
>> > >>>>
>> > >>>> I am trying to implent this as I write, to test it
>> out, and I'm having
>> > >>some problems.
>> > >>>> Maybe there is a better way of doing this... If so ,
>> please let me
>> > know. :)
>> > >>>> Or am I on the right track?
>> > >>>>
>> > >>>>
>> > >>>> /Bart
>> > >>>_______________________________________________
>> > >>>Dynapi-Dev mailing list
>> > >>>Dyn...@li...
>> > >>>http://lists.sourceforge.net/mailman/listinfo/dynapi-
>> dev
>> > >>
>> > >>_______________________________________________
>> > >>Dynapi-Dev mailing list
>> > >>Dyn...@li...
>> > >>http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>> > >
>> > >
>> > >_______________________________________________
>> > >Dynapi-Dev mailing list
>> > >Dyn...@li...
>> > >http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>> >
>> >
>> > _______________________________________________
>> > Dynapi-Dev mailing list
>> > Dyn...@li...
>> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>>
>>
>> _______________________________________________
>> Dynapi-Dev mailing list
>> Dyn...@li...
>> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>>
>
>_______________________________________________
>Dynapi-Dev mailing list
>Dyn...@li...
>http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
|
|
From: Brandon M. <bnd...@ho...> - 2000-11-25 01:40:24
|
How to register as a developer?Guys... don't sweat he small stuff. All =
of this has already been completed.
If you go back about 3-4 months ago I wrote a little file called =
SuperClass.js.
Based on this class I have been able to get complete object based =
inheritance to work.
It took a few weeks, but it works. Just look at that code from way back =
when. It needs work as it is, but it's basis is sound.
----- Original Message -----=20
From: Bartek=20
To: dyn...@li...=20
Sent: Thursday, November 23, 2000 6:39 PM
Subject: [Dynapi-Dev] Widget constructor
I was wondering whether it is a good idea to have some inheritible =
constructor functionality for DynLayer.
I want to be able to create a widget object that extends the DynLayer =
and inherits its initialization, i.e so I wouldn't have to rewrite the =
initialization code for the widget but instead do something like this:
=20
------------------------------------------
=20
function WidgetLayer(){
this.construct(arguments)
}
WidgetLayer.prototype=3Dnew DynLayer
=20
------------------------------------------------------
=20
and it would look something like this for dynlayer:
=20
---------------------------------------------------------------------
=20
function DynLayer(){ this.construct(arguments) }
DynLayer.prototype.construct=3Dfunction(){
alert()
var a=3Darguments
if (a.length=3D=3D1 && a[0]!=3Dnull && =
typeof(a[0])=3D=3D"object") this.setStyle(a[0])
else {
this.id=3Da[0]||"JSDynLayer"+(DynLayer.nullCount++)
this.x=3Da[1]||0
.......etc...
}
}
=20
=
-------------------------------------------------------------------------=
--
=20
I am trying to implent this as I write, to test it out, and I'm having =
some problems.
Maybe there is a better way of doing this... If so , please let me =
know. :)
Or am I on the right track?
=20
=20
/Bart
|
|
From: Pascal B. <pa...@dy...> - 2000-11-24 17:20:22
|
I've been doing it like this:
myWidget.prototype._myWidgetSetSize=DynLayer.prototype.setSize
myWidget.prototype.setSize=function(w,h) {
// do your own code here
this._myWidgetSetSize(w,h)
}
Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net
> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Barre Bizon
> Verzonden: vrijdag 24 november 2000 17:32
> Aan: dyn...@li...
> Onderwerp: [Dynapi-Dev] Widget method extending
>
>
> Another thing...
> Is there a way of extending methods?
> Have been struggling with this a couple of hours now... and
> I can't get past the fact that when you create a widget
> that "extends" DynLayer and you want it to extend various
> methods,it seems that you have to rewrite the methods in
> full.
> There should be a better way of doing this also.
>
> /Bart
>
>
> > hmm seems kindof obscure..
> > It strikes me as having a construct method to be a
> cleaner
> > way of doing initialization.. almost like calling super()
> > in Java... hm?
> > (The code below should work)
> >
> > function DynLayer() { this.construct(arguments) }
> > DynLayer.prototype.construct=function(){
> > var a=arguments[0]
> > ........etc.......
> >
> > function widget(){
> > this.construct(arguments)
> > }
> > widget.prototype=new DynLayer
> >
> >
> > > Forget what I wrote.... it should be this instead:
> > >
> > > function widget(argarray) {
> > > this.DynLayer = DynLayer
> > > eval("this.DynLayer("+argarray.join(",")+")")
> > > }
> > > widget.prototype = new DynLayer
> > >
> > > /Lunna
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>
|
|
From: Pascal B. <pa...@dy...> - 2000-11-24 17:17:38
|
but how would you want to handle widget-specific initialisation? Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Barre Bizon > Verzonden: vrijdag 24 november 2000 11:35 > Aan: dyn...@li... > Onderwerp: Re: Re: SV: [Dynapi-Dev] Widget constructor > > > hmm seems kindof obscure.. > It strikes me as having a construct method to be a cleaner > way of doing initialization.. almost like calling super() > in Java... hm? > (The code below should work) > > function DynLayer() { this.construct(arguments) } > DynLayer.prototype.construct=function(){ > var a=arguments[0] > ........etc....... > > function widget(){ > this.construct(arguments) > } > widget.prototype=new DynLayer > > > > Forget what I wrote.... it should be this instead: > > > > function widget(argarray) { > > this.DynLayer = DynLayer > > eval("this.DynLayer("+argarray.join(",")+")") > > } > > widget.prototype = new DynLayer > > > > /Lunna > > > > At 2000-11-24 06:20 , you wrote: > > >For that particular case, use the array's join() method. > > > > > >function widget(argarray) { > > > this.DynLayer = DynLayer > > > this.DynLayer(argarray.join(",")) > > >} > > >widget.prototype = new DynLayer > > > > > >/Lunna > > > > > >At 2000-11-24 02:07 , you wrote: > > >>Hmm... does not seem to work at all. > > >>IE4 says it doesn't support the property or method. > > >>Could you elaborate, or send me an example of this > being used somewhere? > > >>Another problem: DynLayer treats objects sent as the > first argument as a > > >>DynLayer object to setStyle after. > > >>And as arrays(the array arguments in this case) are > objects and > > >>correspondingly are identified as such, the setStyle > method will be called, > > >>which is not the intent. > > >> > > >>/Bart > > >> > > >>-----Ursprungligt meddelande----- > > >>Från: Dan Steinman <dy...@fu...> > > >>Till: dyn...@li... <dynapi- > de...@li...> > > >>Datum: den 24 november 2000 01:37 > > >>Ämne: Re: [Dynapi-Dev] Widget constructor > > >> > > >> > > >>>Just make your widget constructor call the DynLayer as > a method: > > >>> > > >>>function widget(arguments) { > > >>> this.DynLayer = DynLayer > > >>> this.Dynlayer(arguments) > > >>>} > > >>>widget.prototype = new DynLayer > > >>> > > >>>Dan > > >>> > > >>>On Fri, Nov 24, 2000 at 12:39:05AM +0100, Bartek wrote: > > >>>> I was wondering whether it is a good idea to have > some inheritible > > >>constructor functionality for DynLayer. > > >>>> I want to be able to create a widget object that > extends the DynLayer and > > >>inherits its initialization, i.e so I wouldn't have to > rewrite the > > >>initialization code for the widget but instead do > something like this: > > >>>> > > >>>> ------------------------------------------ > > >>>> > > >>>> function WidgetLayer(){ > > >>>> this.construct(arguments) > > >>>> } > > >>>> WidgetLayer.prototype=new DynLayer > > >>>> > > >>>> ----------------------------------------------------- > - > > >>>> > > >>>> and it would look something like this for dynlayer: > > >>>> > > >>>> ----------------------------------------------------- > ---------------- > > >>>> > > >>>> function DynLayer(){ this.construct(arguments) } > > >>>> DynLayer.prototype.construct=function(){ > > >>>> alert() > > >>>> var a=arguments > > >>>> if (a.length==1 && a[0]!=null && typeof(a[0]) > =="object") > > >>this.setStyle(a[0]) > > >>>> else { > > >>>> this.id=a[0]||"JSDynLayer"+ > (DynLayer.nullCount++) > > >>>> this.x=a[1]||0 > > >>>> .......etc... > > >>>> } > > >>>> } > > >>>> > > >>>> > > ---------------------------------------------------------- > ----------------- > > >>>> > > >>>> I am trying to implent this as I write, to test it > out, and I'm having > > >>some problems. > > >>>> Maybe there is a better way of doing this... If so , > please let me > > know. :) > > >>>> Or am I on the right track? > > >>>> > > >>>> > > >>>> /Bart > > >>>_______________________________________________ > > >>>Dynapi-Dev mailing list > > >>>Dyn...@li... > > >>>http://lists.sourceforge.net/mailman/listinfo/dynapi- > dev > > >> > > >>_______________________________________________ > > >>Dynapi-Dev mailing list > > >>Dyn...@li... > > >>http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > > > > > > > >_______________________________________________ > > >Dynapi-Dev mailing list > > >Dyn...@li... > > >http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > |
|
From: Barre B. <ba...@ho...> - 2000-11-24 16:33:10
|
Another thing...
Is there a way of extending methods?
Have been struggling with this a couple of hours now... and
I can't get past the fact that when you create a widget
that "extends" DynLayer and you want it to extend various
methods,it seems that you have to rewrite the methods in
full.
There should be a better way of doing this also.
/Bart
> hmm seems kindof obscure..
> It strikes me as having a construct method to be a
cleaner
> way of doing initialization.. almost like calling super()
> in Java... hm?
> (The code below should work)
>
> function DynLayer() { this.construct(arguments) }
> DynLayer.prototype.construct=function(){
> var a=arguments[0]
> ........etc.......
>
> function widget(){
> this.construct(arguments)
> }
> widget.prototype=new DynLayer
>
>
> > Forget what I wrote.... it should be this instead:
> >
> > function widget(argarray) {
> > this.DynLayer = DynLayer
> > eval("this.DynLayer("+argarray.join(",")+")")
> > }
> > widget.prototype = new DynLayer
> >
> > /Lunna
|
|
From: Simon D. M. <di...@bi...> - 2000-11-24 15:18:19
|
> The problem I've come across is this on the Mac IE 5 getContentHeight
> returns as "NaN" a little exploration and it turns out that
> "this.elm.scrollHeight" which the getContentHeight() call uses returns
> "undefined". Other properties of the "elm", such a visibility return just
> fine. When I create a layer the standard way right in the HTML
> and query the
> scrollHeight Mac IE 5 returns the correct value. It may be a matter of
> timing as when I query the scrollHeight, but I do have the layer existing
> via the addChild call and as I said it works on all the other browser
> platform setups so I'm stumped. Any ideas?
Have you fixed this problem with .elm.scrollHeight yet?
If not, you say that you have wrapping in the layer so I guess
you may have tables in them. If so you could get the height of
the tables instead.
Something like:
MenuOption.prototype.MenuOptiongetContentHeight=DynLayer.prototype.getConten
tHeight
MenuOption.prototype.getContentHeight=function(){
if(is.ie)return this.elm.children[0].clientHeight
else return MenuOptiongetContentHeight()
}
Maybe this would fix your problem, if not DynAPI's.
I found that on IE5/Win, if you reduce the size of the content of a layer,
.elm.scrollHeight doesn't register it. Don't know about other
versions/platforms.
Maybe you could try .elm.offsetHeight - it doesn't work any better than
.elm.scrollHeight on IE5/Win but it works differently on a Mac.
> Okay I'm building a menuing system using DynAPI, everything is
> working great
> on window ie v5 and netscape v4, and mac netscape v4 but in testing the
> thing out on mac ie 5 I've run into an annoying problem.
>
> The menu is being built on the fly, I'm never sure how many lines of text
> will be in a menu entry because of the length of some item we
> wrap the text.
> Also the system is such that images can be substituted in for
> HTML text and
> it will work just fine, again image size from entry to entry may vary. So
> I've built the system such that each menu item is its own layer and as the
> content is added to the layer the height of the layer is determined using
> "getContentHeight()" and this value is tracked by the menu
> manager so it can
> work out where to position then next menu item.
>
|
|
From: Barre B. <ba...@ho...> - 2000-11-24 10:36:31
|
hmm seems kindof obscure..
It strikes me as having a construct method to be a cleaner
way of doing initialization.. almost like calling super()
in Java... hm?
(The code below should work)
function DynLayer() { this.construct(arguments) }
DynLayer.prototype.construct=function(){
var a=arguments[0]
........etc.......
function widget(){
this.construct(arguments)
}
widget.prototype=new DynLayer
> Forget what I wrote.... it should be this instead:
>
> function widget(argarray) {
> this.DynLayer = DynLayer
> eval("this.DynLayer("+argarray.join(",")+")")
> }
> widget.prototype = new DynLayer
>
> /Lunna
>
> At 2000-11-24 06:20 , you wrote:
> >For that particular case, use the array's join() method.
> >
> >function widget(argarray) {
> > this.DynLayer = DynLayer
> > this.DynLayer(argarray.join(","))
> >}
> >widget.prototype = new DynLayer
> >
> >/Lunna
> >
> >At 2000-11-24 02:07 , you wrote:
> >>Hmm... does not seem to work at all.
> >>IE4 says it doesn't support the property or method.
> >>Could you elaborate, or send me an example of this
being used somewhere?
> >>Another problem: DynLayer treats objects sent as the
first argument as a
> >>DynLayer object to setStyle after.
> >>And as arrays(the array arguments in this case) are
objects and
> >>correspondingly are identified as such, the setStyle
method will be called,
> >>which is not the intent.
> >>
> >>/Bart
> >>
> >>-----Ursprungligt meddelande-----
> >>Från: Dan Steinman <dy...@fu...>
> >>Till: dyn...@li... <dynapi-
de...@li...>
> >>Datum: den 24 november 2000 01:37
> >>Ämne: Re: [Dynapi-Dev] Widget constructor
> >>
> >>
> >>>Just make your widget constructor call the DynLayer as
a method:
> >>>
> >>>function widget(arguments) {
> >>> this.DynLayer = DynLayer
> >>> this.Dynlayer(arguments)
> >>>}
> >>>widget.prototype = new DynLayer
> >>>
> >>>Dan
> >>>
> >>>On Fri, Nov 24, 2000 at 12:39:05AM +0100, Bartek wrote:
> >>>> I was wondering whether it is a good idea to have
some inheritible
> >>constructor functionality for DynLayer.
> >>>> I want to be able to create a widget object that
extends the DynLayer and
> >>inherits its initialization, i.e so I wouldn't have to
rewrite the
> >>initialization code for the widget but instead do
something like this:
> >>>>
> >>>> ------------------------------------------
> >>>>
> >>>> function WidgetLayer(){
> >>>> this.construct(arguments)
> >>>> }
> >>>> WidgetLayer.prototype=new DynLayer
> >>>>
> >>>> -----------------------------------------------------
-
> >>>>
> >>>> and it would look something like this for dynlayer:
> >>>>
> >>>> -----------------------------------------------------
----------------
> >>>>
> >>>> function DynLayer(){ this.construct(arguments) }
> >>>> DynLayer.prototype.construct=function(){
> >>>> alert()
> >>>> var a=arguments
> >>>> if (a.length==1 && a[0]!=null && typeof(a[0])
=="object")
> >>this.setStyle(a[0])
> >>>> else {
> >>>> this.id=a[0]||"JSDynLayer"+
(DynLayer.nullCount++)
> >>>> this.x=a[1]||0
> >>>> .......etc...
> >>>> }
> >>>> }
> >>>>
> >>>>
> ----------------------------------------------------------
-----------------
> >>>>
> >>>> I am trying to implent this as I write, to test it
out, and I'm having
> >>some problems.
> >>>> Maybe there is a better way of doing this... If so ,
please let me
> know. :)
> >>>> Or am I on the right track?
> >>>>
> >>>>
> >>>> /Bart
> >>>_______________________________________________
> >>>Dynapi-Dev mailing list
> >>>Dyn...@li...
> >>>http://lists.sourceforge.net/mailman/listinfo/dynapi-
dev
> >>
> >>_______________________________________________
> >>Dynapi-Dev mailing list
> >>Dyn...@li...
> >>http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
> >
> >
> >_______________________________________________
> >Dynapi-Dev mailing list
> >Dyn...@li...
> >http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
|
|
From: Joachim L. <lu...@ho...> - 2000-11-24 07:22:06
|
Forget what I wrote.... it should be this instead:
function widget(argarray) {
this.DynLayer = DynLayer
eval("this.DynLayer("+argarray.join(",")+")")
}
widget.prototype = new DynLayer
/Lunna
At 2000-11-24 06:20 , you wrote:
>For that particular case, use the array's join() method.
>
>function widget(argarray) {
> this.DynLayer = DynLayer
> this.DynLayer(argarray.join(","))
>}
>widget.prototype = new DynLayer
>
>/Lunna
>
>At 2000-11-24 02:07 , you wrote:
>>Hmm... does not seem to work at all.
>>IE4 says it doesn't support the property or method.
>>Could you elaborate, or send me an example of this being used somewhere?
>>Another problem: DynLayer treats objects sent as the first argument as a
>>DynLayer object to setStyle after.
>>And as arrays(the array arguments in this case) are objects and
>>correspondingly are identified as such, the setStyle method will be called,
>>which is not the intent.
>>
>>/Bart
>>
>>-----Ursprungligt meddelande-----
>>Från: Dan Steinman <dy...@fu...>
>>Till: dyn...@li... <dyn...@li...>
>>Datum: den 24 november 2000 01:37
>>Ämne: Re: [Dynapi-Dev] Widget constructor
>>
>>
>>>Just make your widget constructor call the DynLayer as a method:
>>>
>>>function widget(arguments) {
>>> this.DynLayer = DynLayer
>>> this.Dynlayer(arguments)
>>>}
>>>widget.prototype = new DynLayer
>>>
>>>Dan
>>>
>>>On Fri, Nov 24, 2000 at 12:39:05AM +0100, Bartek wrote:
>>>> I was wondering whether it is a good idea to have some inheritible
>>constructor functionality for DynLayer.
>>>> I want to be able to create a widget object that extends the DynLayer and
>>inherits its initialization, i.e so I wouldn't have to rewrite the
>>initialization code for the widget but instead do something like this:
>>>>
>>>> ------------------------------------------
>>>>
>>>> function WidgetLayer(){
>>>> this.construct(arguments)
>>>> }
>>>> WidgetLayer.prototype=new DynLayer
>>>>
>>>> ------------------------------------------------------
>>>>
>>>> and it would look something like this for dynlayer:
>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>> function DynLayer(){ this.construct(arguments) }
>>>> DynLayer.prototype.construct=function(){
>>>> alert()
>>>> var a=arguments
>>>> if (a.length==1 && a[0]!=null && typeof(a[0])=="object")
>>this.setStyle(a[0])
>>>> else {
>>>> this.id=a[0]||"JSDynLayer"+(DynLayer.nullCount++)
>>>> this.x=a[1]||0
>>>> .......etc...
>>>> }
>>>> }
>>>>
>>>>
---------------------------------------------------------------------------
>>>>
>>>> I am trying to implent this as I write, to test it out, and I'm having
>>some problems.
>>>> Maybe there is a better way of doing this... If so , please let me
know. :)
>>>> Or am I on the right track?
>>>>
>>>>
>>>> /Bart
>>>_______________________________________________
>>>Dynapi-Dev mailing list
>>>Dyn...@li...
>>>http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>>
>>_______________________________________________
>>Dynapi-Dev mailing list
>>Dyn...@li...
>>http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>
>
>_______________________________________________
>Dynapi-Dev mailing list
>Dyn...@li...
>http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
|
|
From: Joachim L. <lu...@ho...> - 2000-11-24 05:20:34
|
For that particular case, use the array's join() method.
function widget(argarray) {
this.DynLayer = DynLayer
this.DynLayer(argarray.join(","))
}
widget.prototype = new DynLayer
/Lunna
At 2000-11-24 02:07 , you wrote:
>Hmm... does not seem to work at all.
>IE4 says it doesn't support the property or method.
>Could you elaborate, or send me an example of this being used somewhere?
>Another problem: DynLayer treats objects sent as the first argument as a
>DynLayer object to setStyle after.
>And as arrays(the array arguments in this case) are objects and
>correspondingly are identified as such, the setStyle method will be called,
>which is not the intent.
>
>/Bart
>
>-----Ursprungligt meddelande-----
>Från: Dan Steinman <dy...@fu...>
>Till: dyn...@li... <dyn...@li...>
>Datum: den 24 november 2000 01:37
>Ämne: Re: [Dynapi-Dev] Widget constructor
>
>
>>Just make your widget constructor call the DynLayer as a method:
>>
>>function widget(arguments) {
>> this.DynLayer = DynLayer
>> this.Dynlayer(arguments)
>>}
>>widget.prototype = new DynLayer
>>
>>Dan
>>
>>On Fri, Nov 24, 2000 at 12:39:05AM +0100, Bartek wrote:
>>> I was wondering whether it is a good idea to have some inheritible
>constructor functionality for DynLayer.
>>> I want to be able to create a widget object that extends the DynLayer and
>inherits its initialization, i.e so I wouldn't have to rewrite the
>initialization code for the widget but instead do something like this:
>>>
>>> ------------------------------------------
>>>
>>> function WidgetLayer(){
>>> this.construct(arguments)
>>> }
>>> WidgetLayer.prototype=new DynLayer
>>>
>>> ------------------------------------------------------
>>>
>>> and it would look something like this for dynlayer:
>>>
>>> ---------------------------------------------------------------------
>>>
>>> function DynLayer(){ this.construct(arguments) }
>>> DynLayer.prototype.construct=function(){
>>> alert()
>>> var a=arguments
>>> if (a.length==1 && a[0]!=null && typeof(a[0])=="object")
>this.setStyle(a[0])
>>> else {
>>> this.id=a[0]||"JSDynLayer"+(DynLayer.nullCount++)
>>> this.x=a[1]||0
>>> .......etc...
>>> }
>>> }
>>>
>>> ---------------------------------------------------------------------------
>>>
>>> I am trying to implent this as I write, to test it out, and I'm having
>some problems.
>>> Maybe there is a better way of doing this... If so , please let me know. :)
>>> Or am I on the right track?
>>>
>>>
>>> /Bart
>>_______________________________________________
>>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: Bart B. <ba...@ho...> - 2000-11-24 01:10:07
|
Hmm... does not seem to work at all.
IE4 says it doesn't support the property or method.
Could you elaborate, or send me an example of this being used somewhere?
Another problem: DynLayer treats objects sent as the first argument as a DynLayer object to setStyle after.
And as arrays(the array arguments in this case) are objects and correspondingly are identified as such, the setStyle method will be called, which is not the intent.
/Bart
-----Ursprungligt meddelande-----
Från: Dan Steinman <dy...@fu...>
Till: dyn...@li... <dyn...@li...>
Datum: den 24 november 2000 01:37
Ämne: Re: [Dynapi-Dev] Widget constructor
>Just make your widget constructor call the DynLayer as a method:
>
>function widget(arguments) {
> this.DynLayer = DynLayer
> this.Dynlayer(arguments)
>}
>widget.prototype = new DynLayer
>
>Dan
>
>On Fri, Nov 24, 2000 at 12:39:05AM +0100, Bartek wrote:
>> I was wondering whether it is a good idea to have some inheritible constructor functionality for DynLayer.
>> I want to be able to create a widget object that extends the DynLayer and inherits its initialization, i.e so I wouldn't have to rewrite the initialization code for the widget but instead do something like this:
>>
>> ------------------------------------------
>>
>> function WidgetLayer(){
>> this.construct(arguments)
>> }
>> WidgetLayer.prototype=new DynLayer
>>
>> ------------------------------------------------------
>>
>> and it would look something like this for dynlayer:
>>
>> ---------------------------------------------------------------------
>>
>> function DynLayer(){ this.construct(arguments) }
>> DynLayer.prototype.construct=function(){
>> alert()
>> var a=arguments
>> if (a.length==1 && a[0]!=null && typeof(a[0])=="object") this.setStyle(a[0])
>> else {
>> this.id=a[0]||"JSDynLayer"+(DynLayer.nullCount++)
>> this.x=a[1]||0
>> .......etc...
>> }
>> }
>>
>> ---------------------------------------------------------------------------
>>
>> I am trying to implent this as I write, to test it out, and I'm having some problems.
>> Maybe there is a better way of doing this... If so , please let me know. :)
>> Or am I on the right track?
>>
>>
>> /Bart
>_______________________________________________
>Dynapi-Dev mailing list
>Dyn...@li...
>http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
|
|
From: Dan S. <dy...@fu...> - 2000-11-24 00:37:04
|
Just make your widget constructor call the DynLayer as a method:
function widget(arguments) {
this.DynLayer = DynLayer
this.Dynlayer(arguments)
}
widget.prototype = new DynLayer
Dan
On Fri, Nov 24, 2000 at 12:39:05AM +0100, Bartek wrote:
> I was wondering whether it is a good idea to have some inheritible constructor functionality for DynLayer.
> I want to be able to create a widget object that extends the DynLayer and inherits its initialization, i.e so I wouldn't have to rewrite the initialization code for the widget but instead do something like this:
>
> ------------------------------------------
>
> function WidgetLayer(){
> this.construct(arguments)
> }
> WidgetLayer.prototype=new DynLayer
>
> ------------------------------------------------------
>
> and it would look something like this for dynlayer:
>
> ---------------------------------------------------------------------
>
> function DynLayer(){ this.construct(arguments) }
> DynLayer.prototype.construct=function(){
> alert()
> var a=arguments
> if (a.length==1 && a[0]!=null && typeof(a[0])=="object") this.setStyle(a[0])
> else {
> this.id=a[0]||"JSDynLayer"+(DynLayer.nullCount++)
> this.x=a[1]||0
> .......etc...
> }
> }
>
> ---------------------------------------------------------------------------
>
> I am trying to implent this as I write, to test it out, and I'm having some problems.
> Maybe there is a better way of doing this... If so , please let me know. :)
> Or am I on the right track?
>
>
> /Bart
|
|
From: Bartek <ba...@ho...> - 2000-11-23 23:41:34
|
I was wondering whether it is a good idea to have some inheritible =
constructor functionality for DynLayer.
I want to be able to create a widget object that extends the DynLayer =
and inherits its initialization, i.e so I wouldn't have to rewrite the =
initialization code for the widget but instead do something like this:
------------------------------------------
function WidgetLayer(){
this.construct(arguments)
}
WidgetLayer.prototype=3Dnew DynLayer
------------------------------------------------------
and it would look something like this for dynlayer:
---------------------------------------------------------------------
function DynLayer(){ this.construct(arguments) }
DynLayer.prototype.construct=3Dfunction(){
alert()
var a=3Darguments
if (a.length=3D=3D1 && a[0]!=3Dnull && typeof(a[0])=3D=3D"object") =
this.setStyle(a[0])
else {
this.id=3Da[0]||"JSDynLayer"+(DynLayer.nullCount++)
this.x=3Da[1]||0
.......etc...
}
}
-------------------------------------------------------------------------=
--
I am trying to implent this as I write, to test it out, and I'm having =
some problems.
Maybe there is a better way of doing this... If so , please let me know. =
:)
Or am I on the right track?
/Bart
|
175 messages has been excluded from this view by a project administrator.
