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: b0n3z <b0...@go...> - 2000-12-22 22:17:03
|
Using loadpanel with Netscape 4.08 on Win2k seems to be broke.. and I'm sure it's on other platforms and NS versions. (don't know about 6 yet) Here is a sample - Please View through Netscape 4x or higher: http://www.gotapex.com/_beta/loadpanel.html this should work fine as the loadpanel are not loaded... But when they are - NS will ussually foul up and not load beyond the first loadpanel. Here is an example of this: http://www.gotapex.com/_beta/loadpanel_loaded.html If ANYONE can help solve this bug.. I would be greatfull. Thanks, Ken Jones (aka b0n3z) b0...@go... |
|
From: Richard :o <ma...@ri...> - 2000-12-21 14:09:23
|
Hi,
Il Maestro posted the solution for dragging in frames last week, but it =
seems when done like that:
tdoc =3D new DynDocument(parent.treeFrame);
myLayer=3Dnew DynLayer(null,100,100,100,100,'#c0c0c0')
tdoc.addChild(myLayer);
DragEvent.setDragBoundary(myLayer, 0, 300, 300, 0)
DragEvent.enableDragEvents(tdoc,myLayer)
You get an error if you click on the frame.
To avoid this I had to add the line:
DragEvent.disableDragEvents(tdoc)
which seems a bit of a hack, either we should hard code it in =
dragevents.js i.e.:
if(thing.constructor!=3DDynDocument);
blah blah
var lyr=3Dthing.getComponent();
lyr.removeEventListener(DragEvent.lyrListener);
=20
or something like that, or there's a bug in the code somewhere else.
Cheers,
Richard :o
ma...@ri...
www.richardinfo.com
(Everything running on, and ported to the 19/12/2000 snapshot of =
DynAPI2)
=20
|
|
From: Richard :o <ma...@ri...> - 2000-12-20 22:33:35
|
<html>=0A=
<head>=0A=
<title>DynAPI Examples - ScrollPane</title>=0A=
<script language=3D"JavaScript" src=3D"../src/dynapi.js"></script>=0A=
<script language=3D"Javascript">=0A=
=0A=
DynAPI.setLibraryPath('../src/lib/');=0A=
DynAPI.include('dynapi.api.*');=0A=
DynAPI.include('dynapi.util.thread.js');=0A=
DynAPI.include('dynapi.util.pathanim.js');=0A=
DynAPI.include('dynapi.gui.buttonimage.js');=0A=
DynAPI.include('dynapi.gui.scrollbar.js');=0A=
DynAPI.include('dynapi.gui.viewport.js');=0A=
DynAPI.include('dynapi.gui.scrollpane.js');=0A=
DynAPI.include('dynapi.gui.dynimage.js');=0A=
=0A=
DynAPI.include('dynapi.gui.label.js');=0A=
=0A=
DynAPI.onLoad =3D function() {=0A=
=0A=
// this should be replaced with a default image location based on =
DynAPI.librarypath=0A=
MetalScrollPaneURL =3D DynAPI.librarypath+"/dynapi/images/scrollpane/"=0A=
=0A=
label1 =3D new Label('<table border=3D1><tr><td width=3D160 =
height=3D160>label 1 alk jskj slkj k dkjkj dk skslkdjf lskd =
f</td></tr></table>')=0A=
label1.setWrap(false)=0A=
label1.setPadding(5)=0A=
label1.setBgColor('cyan')=0A=
label1.setSize(160,160)=0A=
=0A=
label2 =3D new Label('<table border=3D1><tr><td width=3D200>label 2 =
aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd =
kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk =
fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds =
lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf =
lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk =
aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd =
kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk =
fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds =
lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf =
lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk =
aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd =
kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk =
fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds =
lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf =
lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk =
aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd =
kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk =
fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds =
lkdjf ksdjf lskdf jsdlk</td></tr></table>')=0A=
label2.setWidth(200)=0A=
label2.setWrap(false)=0A=
label2.setPadding(5)=0A=
label2.setBgColor('yellow')=0A=
label2.pack()=0A=
=0A=
label3 =3D new Label('label 3 aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf =
ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf =
jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk =
asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf =
dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd =
kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf =
ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf =
jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk =
asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf =
dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd =
kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf =
kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk =
fjd kfjds kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd =
kfdjf dk dk fjd kfjds ')=0A=
label3.setWrap(true)=0A=
label3.setPadding(5)=0A=
label3.setWidth(100)=0A=
label3.packHeight()=0A=
label3.setBgColor('magenta')=0A=
=0A=
label4 =3D new Label('<table border=3D1><tr><td width=3D600>label 4 =
aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd =
kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk =
fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds =
lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf =
lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk =
aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd =
kfdjf dk dk fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk =
fjd kfjds lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds =
lkdjf ksdjf lskdf jsdlk aslk asdkfjd kfdjf dk dk fjd kfjds lkdjf ksdjf =
lskdf jsdlk aslk</td></tr></table>')=0A=
label4.setPadding(5)=0A=
label4.setBgColor('00eeb0')=0A=
label4.pack()=0A=
=0A=
scrollobj =3D new ScrollPane(label1) // label1 will be set as the =
content=0A=
scrollobj.setSize(150,150)=0A=
scrollobj.moveTo(250,50)=0A=
scrollobj.setBgColor('#c0c0c0')=0A=
=0A=
DynAPI.document.addChild(scrollobj)=0A=
}=0A=
=0A=
//-->=0A=
</script>=0A=
</head>=0A=
<body bgcolor=3D"#ffffff">=0A=
=0A=
<br>set scroll size: <a =
href=3D"javascript:scrollobj.setSize(150,150)">150</a>, <a =
href=3D"javascript:scrollobj.setSize(250,250)">250</a>, <a =
href=3D"javascript:scrollobj.setSize(350,350)">350</a>=0A=
<br>set label1 size: <a =
href=3D"javascript:label1.setSize(100,100)">100</a>, <a =
href=3D"javascript:label1.setSize(140,140)">140</a>, <a =
href=3D"javascript:label1.setSize(200,200)">200</a>=0A=
=0A=
<p><a href=3D"javascript:scrollobj.setContent(label1)">Add Label #1 to =
ScrollPane</a>=0A=
<br><a href=3D"javascript:scrollobj.setContent(label2)">Add Label #2 to =
ScrollPane</a>=0A=
<br><a href=3D"javascript:scrollobj.setContent(label3)">Add Label #3 to =
ScrollPane</a>=0A=
<br><a href=3D"javascript:scrollobj.setContent(label4)">Add Label #4 to =
ScrollPane</a>=0A=
=0A=
</body>=0A=
</html>=0A=
|
|
From: Jared N. <ja...@aa...> - 2000-12-20 19:31:55
|
Is this still working? Just wanted to make sure - sorry for not having contributed much so far (nothing!) but I'm still going through all the code to see what's going on. |
|
From: Dan S. <dy...@fu...> - 2000-12-17 16:00:19
|
No difference to me whether it's DynLayer_create or DynLayer.create, you should never ever have to call that function manually. If anyone decides to change it just be sure to update the related files: dyndoc, events, inline.
Dan
On Sun, Dec 17, 2000 at 04:32:00PM +0100, Bart Bizon wrote:
> I totally agree. General functions should be kept static as far as possible.
> It doesn't make sense to have every Dynlayer object inherit all that generic functionality.
> Total waste of space :)
>
> -----Ursprungligt meddelande-----
> Från: Robert Rainwater <rra...@ya...>
> Till: dyn...@li... <dyn...@li...>
> Datum: den 16 december 2000 05:32
> Ämne: Re: [Dynapi-Dev] Large number of updates/fixes
>
>
> >I haven't seen the new code yet but wouldn't it be
> >better if the new global functions were static methods
> >of the DynLayer. Like:
> >
> >DynLayer.createElement = function(dlyr) {}
> >
> >This way you would say DynLayer.createElement(). I
> >think this would make it more clear what the intent of
> >the functions were if they were static. I don't think
> >this would require any more memory than a global
> >function. For users looking at the code, I think a
> >static method would be more obvious. Of course, it
> >would not change the way it works.
> >
> >Rob
> >
> >--- Dan Steinman <dy...@fu...> wrote:
> >> Just change the .createElement() call to
> >> DynLayer_createElement(dlyr).
> >>
> >
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Yahoo! Shopping - Thousands of Stores. Millions of Products.
> >http://shopping.yahoo.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
|
|
From: Bart B. <ba...@ho...> - 2000-12-17 15:34:14
|
I totally agree. General functions should be kept static as far as =
possible.
It doesn't make sense to have every Dynlayer object inherit all that =
generic functionality.
Total waste of space :)
-----Ursprungligt meddelande-----
Fr=E5n: Robert Rainwater <rra...@ya...>
Till: dyn...@li... =
<dyn...@li...>
Datum: den 16 december 2000 05:32
=C4mne: Re: [Dynapi-Dev] Large number of updates/fixes
>I haven't seen the new code yet but wouldn't it be
>better if the new global functions were static methods
>of the DynLayer. Like:
>
>DynLayer.createElement =3D function(dlyr) {}
>
>This way you would say DynLayer.createElement(). I
>think this would make it more clear what the intent of
>the functions were if they were static. I don't think
>this would require any more memory than a global
>function. For users looking at the code, I think a
>static method would be more obvious. Of course, it
>would not change the way it works.
>
>Rob
>
>--- Dan Steinman <dy...@fu...> wrote:
>> Just change the .createElement() call to
>> DynLayer_createElement(dlyr).
>>=20
>
>
>__________________________________________________
>Do You Yahoo!?
>Yahoo! Shopping - Thousands of Stores. Millions of Products.
>http://shopping.yahoo.com/
>
>_______________________________________________
>Dynapi-Dev mailing list
>Dyn...@li...
>http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>
|
|
From: Brandon M. <bnd...@ho...> - 2000-12-16 20:56:40
|
PHP is a server side scripting language with pseudo object oriented style. It is mostly a procedural language with it's symantics developed over time. If you know perl, and are willing to bend a bit on structure, PHP is a right powerfull language to use. I've used it in a few apps, and for rapid prototyping, it's a great language. goto php.net.. or phpwizzard.net those are good sites for direct PHP stuff. -----Original Message----- From: dyn...@li... [mailto:dyn...@li...]On Behalf Of Doug Melvin Sent: Saturday, December 16, 2000 6:17 PM To: dyn...@li...; dynapi-help Subject: [Dynapi-Dev] PHP What exactly is PHP? What is the benifits of using it? What are the draw-backs? I would appreciate more info on this.. I have come acros an increaing number of sites that use this and have become quite curious.. Anyone who played Tradewars Back in the day of BBS's might want to check this out: http://blacknova.net |
|
From: Doug M. <do...@cr...> - 2000-12-16 20:18:10
|
What exactly is PHP?=20 What is the benifits of using it? What are the draw-backs? I would appreciate more info on this.. I have come acros an increaing number of sites that use this and have become quite curious.. Anyone who played Tradewars Back in the day of BBS's might want to check this out: http://blacknova.net |
|
From: Michael P. <mp...@ph...> - 2000-12-16 14:11:31
|
<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> <body bgcolor="#FFFFFF"> I'm sorry about the lack of comments in my code. It is still a WIP. <p>As for all the resizing, that is not required. All resixing of child layers is done using the resize event listener attached to the object. <p>I wanted to create an object that I could use everywhere without the need for a series of individual object with specialist functions. <p>The lyrcaption layer is required so that the borders are not lost when you change the label text. If you want to so a series of test that enable the use of sethtml when there are no borders, feel free. I just wanted to make a simple widget that enabled we to use a single object on whch to base my tables, my buttons, my nodes and everything else that required formatted text. <p>If you want, you can trim the code back to remove the borders. I personally like them to be there when I need then without having to write a second widget to do that. That would result in: <br><tt> DynLayer</tt> <br><tt> --> Cell</tt> <br><tt> --> BorderCell</tt> <br><tt> --> Button</tt> <p>I want to keep the inheritance to a minimum if at all possible. <br>-- <br>Michael Pemberton <br>mp...@ph... <br>ICQ: 12107010 </body> </html> |
|
From: Robert R. <rra...@ya...> - 2000-12-16 04:32:02
|
I haven't seen the new code yet but wouldn't it be
better if the new global functions were static methods
of the DynLayer. Like:
DynLayer.createElement = function(dlyr) {}
This way you would say DynLayer.createElement(). I
think this would make it more clear what the intent of
the functions were if they were static. I don't think
this would require any more memory than a global
function. For users looking at the code, I think a
static method would be more obvious. Of course, it
would not change the way it works.
Rob
--- Dan Steinman <dy...@fu...> wrote:
> Just change the .createElement() call to
> DynLayer_createElement(dlyr).
>
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
|
|
From: Nuno F. <nun...@wi...> - 2000-12-16 02:59:31
|
Come on guys! A Flame war is the least we need on this list... best, NunoF -----Original Message----- From: dyn...@li... [mailto:dyn...@li...]On Behalf Of Doug Melvin Sent: sexta-feira, 15 de Dezembro de 2000 22:39 To: dyn...@li... Subject: Re: [Dynapi-Dev] Mozilla & Opera So I used the wrong word. your sarcasm is quite uncalled for. ----- Original Message ----- From: "Brandon Myers" <bnd...@ho...> To: <dyn...@li...> Sent: Friday, December 15, 2000 10:55 AM Subject: RE: [Dynapi-Dev] Mozilla & Opera > Hey doug... gota a news flash for ya.. > > Nothing can render javascript! Only HTML. > -----Original Message----- > From: dyn...@li... > [mailto:dyn...@li...]On Behalf Of Doug Melvin > Sent: Friday, December 15, 2000 2:54 PM > To: dyn...@li... > Subject: Re: [Dynapi-Dev] Mozilla & Opera > > > > > > > Before I found DynAPI and I was stumbling along trying to create inline code > that handles all browsers - I went through the Opera site and couldn't find > anything to do with their implementation of CSS or the DOM or anything else. > Has anyone been able to find documents on their site that give developers > more of an idea? > > The impression I've gotten is that there is none. > > BTW - I think the major difference between 4 and 5 is the free-ness and the > inclusion of ads in the interface - obviously bug fixes and stuff - but > mostly that... With Opera being free - maybe we'll see an increase in it's > usage > > Not if it can't render JavaScript.. :-) > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Doug M. <do...@cr...> - 2000-12-15 21:07:07
|
Maybe I should apologize as well. I'm a bit stressed out by the current project. The dumb F**k refuses to pay us for work to-date.. My phone got disconnected last week and my power will be disconnected as of five PM today... Doug Melvin ----- Original Message ----- From: "Brandon Myers" <bnd...@ho...> To: <dyn...@li...> Sent: Friday, December 15, 2000 12:37 PM Subject: RE: [Dynapi-Dev] Mozilla & Opera > Sorry. > I apologize. Was only ment in jest. > > > -----Original Message----- > > From: dyn...@li... > > [mailto:dyn...@li...]On Behalf Of Doug Melvin > > Sent: Friday, December 15, 2000 5:39 PM > > To: dyn...@li... > > Subject: Re: [Dynapi-Dev] Mozilla & Opera > > > > > > So I used the wrong word. > > your sarcasm is quite uncalled for. > > ----- Original Message ----- > > From: "Brandon Myers" <bnd...@ho...> > > To: <dyn...@li...> > > Sent: Friday, December 15, 2000 10:55 AM > > Subject: RE: [Dynapi-Dev] Mozilla & Opera > > > > > > > Hey doug... gota a news flash for ya.. > > > > > > Nothing can render javascript! Only HTML. > > > -----Original Message----- > > > From: dyn...@li... > > > [mailto:dyn...@li...]On Behalf Of Doug Melvin > > > Sent: Friday, December 15, 2000 2:54 PM > > > To: dyn...@li... > > > Subject: Re: [Dynapi-Dev] Mozilla & Opera > > > > > > > > > > > > > > > > > > > > > Before I found DynAPI and I was stumbling along trying to create inline > > code > > > that handles all browsers - I went through the Opera site and couldn't > > find > > > anything to do with their implementation of CSS or the DOM or anything > > else. > > > Has anyone been able to find documents on their site that give > > developers > > > more of an idea? > > > > > > The impression I've gotten is that there is none. > > > > > > BTW - I think the major difference between 4 and 5 is the free-ness and > > the > > > inclusion of ads in the interface - obviously bug fixes and stuff - but > > > mostly that... With Opera being free - maybe we'll see an > > increase in it's > > > usage > > > > > > Not if it can't render JavaScript.. :-) > > > > > > _______________________________________________ > > > 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-12-15 20:34:59
|
Sorry. I apologize. Was only ment in jest. > -----Original Message----- > From: dyn...@li... > [mailto:dyn...@li...]On Behalf Of Doug Melvin > Sent: Friday, December 15, 2000 5:39 PM > To: dyn...@li... > Subject: Re: [Dynapi-Dev] Mozilla & Opera > > > So I used the wrong word. > your sarcasm is quite uncalled for. > ----- Original Message ----- > From: "Brandon Myers" <bnd...@ho...> > To: <dyn...@li...> > Sent: Friday, December 15, 2000 10:55 AM > Subject: RE: [Dynapi-Dev] Mozilla & Opera > > > > Hey doug... gota a news flash for ya.. > > > > Nothing can render javascript! Only HTML. > > -----Original Message----- > > From: dyn...@li... > > [mailto:dyn...@li...]On Behalf Of Doug Melvin > > Sent: Friday, December 15, 2000 2:54 PM > > To: dyn...@li... > > Subject: Re: [Dynapi-Dev] Mozilla & Opera > > > > > > > > > > > > > > Before I found DynAPI and I was stumbling along trying to create inline > code > > that handles all browsers - I went through the Opera site and couldn't > find > > anything to do with their implementation of CSS or the DOM or anything > else. > > Has anyone been able to find documents on their site that give > developers > > more of an idea? > > > > The impression I've gotten is that there is none. > > > > BTW - I think the major difference between 4 and 5 is the free-ness and > the > > inclusion of ads in the interface - obviously bug fixes and stuff - but > > mostly that... With Opera being free - maybe we'll see an > increase in it's > > usage > > > > Not if it can't render JavaScript.. :-) > > > > _______________________________________________ > > 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-12-15 19:40:30
|
So I used the wrong word. your sarcasm is quite uncalled for. ----- Original Message ----- From: "Brandon Myers" <bnd...@ho...> To: <dyn...@li...> Sent: Friday, December 15, 2000 10:55 AM Subject: RE: [Dynapi-Dev] Mozilla & Opera > Hey doug... gota a news flash for ya.. > > Nothing can render javascript! Only HTML. > -----Original Message----- > From: dyn...@li... > [mailto:dyn...@li...]On Behalf Of Doug Melvin > Sent: Friday, December 15, 2000 2:54 PM > To: dyn...@li... > Subject: Re: [Dynapi-Dev] Mozilla & Opera > > > > > > > Before I found DynAPI and I was stumbling along trying to create inline code > that handles all browsers - I went through the Opera site and couldn't find > anything to do with their implementation of CSS or the DOM or anything else. > Has anyone been able to find documents on their site that give developers > more of an idea? > > The impression I've gotten is that there is none. > > BTW - I think the major difference between 4 and 5 is the free-ness and the > inclusion of ads in the interface - obviously bug fixes and stuff - but > mostly that... With Opera being free - maybe we'll see an increase in it's > usage > > Not if it can't render JavaScript.. :-) > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Brandon M. <bnd...@ho...> - 2000-12-15 18:52:57
|
Hey doug... gota a news flash for ya..
Nothing can render javascript! Only HTML.
-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Doug Melvin
Sent: Friday, December 15, 2000 2:54 PM
To: dyn...@li...
Subject: Re: [Dynapi-Dev] Mozilla & Opera
Before I found DynAPI and I was stumbling along trying to create inline code
that handles all browsers - I went through the Opera site and couldn't find
anything to do with their implementation of CSS or the DOM or anything else.
Has anyone been able to find documents on their site that give developers
more of an idea?
The impression I've gotten is that there is none.
BTW - I think the major difference between 4 and 5 is the free-ness and the
inclusion of ads in the interface - obviously bug fixes and stuff - but
mostly that... With Opera being free - maybe we'll see an increase in it's
usage
Not if it can't render JavaScript.. :-)
|
|
From: Josep M. i T. <jm...@ne...> - 2000-12-15 17:57:55
|
And DynLayer_flagDeleteChildren has to be changed to (see the last Re:
dynimage.js (gui) please)
function DynLayer_flagDeleteChildren(dlyr){
for (var i=0; i<dlyr.children.length; i++) {
if (dlyr.children[i].created) dlyr.children[i].deleteElement();
}
};
Josep
-----Mensaje original-----
De: Dan Steinman <dy...@fu...>
Para: dyn...@li... <dyn...@li...>
Fecha: viernes 15 de diciembre de 2000 15:51
Asunto: Re: [Dynapi-Dev] Large number of updates/fixes
>Just change the .createElement() call to DynLayer_createElement(dlyr).
>
>I changed the theme functions for Button, ScrollBar, PushPanel, and
Scrollpane to default to the standard images. I should have put a (url)
parameter in those functions. This can be changed quite easily:
>
>function MetalScrollPane(url) {
> if (!url) url = DynAPI.librarypath+'images/scrollpane/';
> ...
>}
>
>I mentioned I didn't update List yet. It probably just has to be slightly
modified in relation to the create and precreate events.
>
>Dan
>
>On Fri, Dec 15, 2000 at 08:20:48PM +1100, Peter Luxmore wrote:
>> Dan
>>
>> Just been testing what you have currently in CVS. I am using scrollpane
and loadpanel and the code is below.
>>
>> 1. In NS4.7 if you resize the browser window with the mouse, (especially
making it larger), results in the following error:
>>
>> JavaScript Error:
>> http://localhost/dynapi/src/lib/dynapi/api/dyndocument.js,
>> line 53:
>>
>> this.children[i].createElement is not a function.
>>
>> 2. MetalScrollPaneURL is not working in NS4.7 or IE5.1 and the default
scrollbar images are displayed.
>>
>> 3. The list widget is broken. Produces the following error in IE5.1:
>>
>> Line: 33
>> Char: 5
>> Error: 'css' is not an object
>> Code: 0
>> URL: http://localhost/CFCalc2/washerSelect.cfm
>>
>> -------------------------------------------------------------------------
------------------------------
>> <script language="JavaScript" src="../dynapi/src/dynapi.js"></script>
>> <script language="Javascript">
>> DynAPI.setLibraryPath('../dynapi/src/lib/');
>> DynAPI.include('dynapi.api.*');
>> DynAPI.include('dynapi.util.thread.js');
>> DynAPI.include('dynapi.util.pathanim.js');
>> DynAPI.include('dynapi.gui.dynimage.js');
>> DynAPI.include('dynapi.gui.button.js');
>> DynAPI.include('dynapi.gui.scrollbar.js');
>> DynAPI.include('dynapi.gui.viewport.js');
>> DynAPI.include('dynapi.gui.scrollpane.js');
>> DynAPI.include('dynapi.gui.label.js');
>> DynAPI.include('dynapi.gui.list.js');
>> DynAPI.include('dynapi.gui.loadpanel.js');
>>
>> // this should be replaced with a default image location based on
DynAPI.librarypath
>> MetalScrollPaneURL = DynAPI.librarypath+"dynapi/images/mypane/"
>>
>> </script>
>> <script language="Javascript">
>>
>> DynAPI.onLoad = function() {
>> MetalScrollPaneURL = DynAPI.librarypath+"dynapi/images/mypane/"
>>
>> infoPanel = new LoadPanel()
>> infoPanel.setSize(220,233)
>> infoPanel.moveTo(478,197)
>>
>> scroller = new ScrollPane(infoPanel)
>> scroller.setSize(245,263)
>> scroller.moveTo(478,197)
>>
>> menulist = new List()
>> menulist.moveTo(5,230)
>> menulist.setWidth(160)
>> menulist.setBgColor('#000000')
>> menulist.boldOnSelect(true)
>> menulist.setSelectionMode(false)
>>
>> <cfoutput query="baseprofile">
>> menulist.add("#Brand# #Model#")
>> </cfoutput>
>>
>> DynAPI.document.addChild(scroller)
>>
>> <cfoutput query="DataSheet">
>> infoPanel.setURL('_inc.cfm?washerCode=#washerCode#')
>> </cfoutput>
>>
>> DynAPI.document.addChild(menulist)
>> }
>> //-->
>> </script>
>>
>> Regards
>> Peter Luxmore
>>
>> Dan Steinman wrote:
>>
>> > I've posted all my updates to CVS. I think touched every file.
>> >
>> > The significant changes were:
>> >
>> > - inline creation system for Netscape now worked directly into DynLayer
>> > - DynImage auto-resizing, this effected everything that was using
DynImage
>> > - some changes to how the "precreate", "create", and "resize" events
are handled
>> >
>> > The events took a while to work out. I didn't like how it was setup
before because it wasn't quite right when dealing with the new create
system.
>> > "precreate" should be used in widgets for doing most of the final
layout for a widget as well as setting images for the layers. Most of that
stuff used to be in the "create" event, but now with the inline creation
it's more effecient to do it in "precreate" because when you set the
size/location/images of the layers you won't be working with true DIV
elements rather with just the JS objects. The goal is to do as little work
with div's as possible before you create, so that by the time DynLayer
creates the layers it already knows the size and content of them.
>> >
>> > You still need the "create" event to check for content size, and that
sort of stuff.
>> >
>> > I had to remove all the checks for this.created from within the
DynLayer and replace them with checks for this.css!=null. The
"this.created" flag is now true once the layer/div element is created, and
final position/size has been set, AND all it's children are created also.
Peviously this.created was set to true before the children were created
which conflicts with the way the inline creation system is supposed to work.
I updated all the widgets to make sure everything was working ok with this
change.
>> >
>> > I made a few DynLayer methods into simple functions, create()
assignElement, flagChildren etc. These don't have to be methods because
they are never used manually.
>> >
>> > Also you now have to include browser.js BEFORE dynlayer.js because in
dynlayer I'm doing a check for Netscape/IE. I updated the dynapi include
list for this, but if you have any pages that don't do
include('dynapi.api.*') you will have to change the order yourself.
>> >
>> > DynImage.getImage() can be used before onLoad, the reason there was a
problem in IE is you need a break point between the include()'s and the rest
of the page. I updated all the examples so they look like this:
>> >
>> > <script src=dynapi.js>
>> > <script>
>> > DynAPI.setLibraryPath('../src/lib');
>> > DynAPI.include('dynapi.api.*');
>> > ...
>> > </script>
>> > <script>
>> >
>> > rest of code....
>> >
>> > </script>
>> >
>> > Some other minor changes I can remember is the setSize/Width/Height, I
made setSize call setWidth and setHeight, and in those I rearranged a few
things. I removed all references to getComponent() cause it's not needed
anymore. And DynImage.getImage won't return an Image object with .w and .h
tacked on, it's unecessary - if you have any code that uses the .w and .h,
just replace it with .width and .height.
>> >
>> > What is no longer working:
>> > - inline.js, I think something was wrong in IE
>> > - List - Scott A, sorry I didn't get around to fixing this one, I
checked it out in IE before all my changes and worked fantastic, I'd like to
get it working again. Probably just needs some precreate/create changes. I
broke it, so I'll fix it unless you want to take a stab at it.
>> >
>> > Major bugs we should fix before a stable release:
>> > - Loadpanel isn't working in IE4.
>> > - Label/button setSelectable still isn't working, anyone know what
changes are needed?
>> > - Inline creation system for IE - I could do this eventually but I want
to work on some other things first so if anyone else wants to give it a shot
you're welcome, it should be fairly easy now that the NS code has been
finalized.
>> >
>> > Dan
>> > _______________________________________________
>> > 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: Darin K. <dka...@ef...> - 2000-12-15 17:56:04
|
Well, the IPO just collasped today :( if anyone knows of any opportunities in the Bay area for a Delphi/Coldfusion head.. let me know! -----Original Message----- From: Doug Melvin [mailto:do...@cr...] Sent: Friday, December 15, 2000 12:45 PM To: dyn...@li... Subject: Re: [Dynapi-Dev] Label Problems... arg.. "you will still see a try" == "you will still see a tree" ----- Original Message ----- From: Doug Melvin <mailto:do...@cr...> To: dyn...@li... <mailto:dyn...@li...> Sent: Friday, December 15, 2000 12:29 PM Subject: Re: [Dynapi-Dev] Label Problems... You know.. it would be nice if people would COMMENT their code.. But, don't worry Mr. Michael <mailto:mp...@ph...> Pemberton , I'm sure I'll figure it out quickly enough.. looks like I have to resize, the caption layer as well as the multiple style/appearance layers.... Does there need to be so many layers? I hope not.. I'll post a trimmed version with Pack() ASAP.. (assuming you don't mind of course) PS: if you go to the address below in IE you will still see a try, but it will be an applet.. ----- Original Message ----- From: Doug Melvin <mailto:do...@cr...> To: dyn...@li... <mailto:dyn...@li...> Sent: Friday, December 15, 2000 12:18 PM Subject: Re: [Dynapi-Dev] Label Problems... It's quit nice dude! Mind you I'm goinna have to implement packwidth and packheight.. Or maybe I'll just make one Pack() function.. I'll let you know once it's implemented into my tree.. to check out this tree I've been crying about: (NS ONLY) 206.75.45.190/catalog/begin.htm click on catalogue.. ----- Original Message ----- From: Michael Pemberton <mailto:mp...@ph...> To: dyn...@li... <mailto:dyn...@li...> Sent: Thursday, December 14, 2000 6:41 PM Subject: [Dynapi-Dev] Label Problems... I have noticed alot of talk about problems with the Label widget. I have made my own widget that I needed for use as a general textbox and thought it may be of use. I have put a modified version of the label's setSelectable method in there ans it seems to work ok. Anyway, here it is. -- Michael Pemberton mp...@ph... <mailto:mp...@ph...> ICQ: 12107010 _____ |
|
From: Doug M. <do...@cr...> - 2000-12-15 17:46:51
|
AfroAPI Examples - core.afro.fatcell.jsarg..
"you will still see a try" =3D=3D "you will still see a tree"
----- Original Message -----=20
From: Doug Melvin=20
To: dyn...@li...=20
Sent: Friday, December 15, 2000 12:29 PM
Subject: Re: [Dynapi-Dev] Label Problems...
You know.. it would be nice if people would COMMENT their code..
But, don't worry Mr. Michael Pemberton , I'm sure I'll figure it out =
quickly
enough.. looks like I have to resize, the caption layer as well as the =
multiple
style/appearance layers....
Does there need to be so many layers? I hope not..
I'll post a trimmed version with Pack() ASAP..
(assuming you don't mind of course)
PS: if you go to the address below in IE you will still see a try, but =
it will be an applet..
----- Original Message -----=20
From: Doug Melvin=20
To: dyn...@li...=20
Sent: Friday, December 15, 2000 12:18 PM
Subject: Re: [Dynapi-Dev] Label Problems...
It's quit nice dude!
Mind you I'm goinna have to implement packwidth and packheight..
Or maybe I'll just make one Pack() function..
I'll let you know once it's implemented into my tree..
to check out this tree I've been crying about:
(NS ONLY)
206.75.45.190/catalog/begin.htm
click on catalogue..
----- Original Message -----=20
From: Michael Pemberton=20
To: dyn...@li...=20
Sent: Thursday, December 14, 2000 6:41 PM
Subject: [Dynapi-Dev] Label Problems...
I have noticed alot of talk about problems with the Label =
widget.
I have made my own widget that I needed for use as a general =
textbox and
thought it may be of use. I have put a modified version of the =
label's
setSelectable method in there ans it seems to work ok.
Anyway, here it is.
--
Michael Pemberton
mp...@ph...
ICQ: 12107010
------------------------------------------------------------------------
|
|
From: Doug M. <do...@cr...> - 2000-12-15 17:31:17
|
AfroAPI Examples - core.afro.fatcell.jsYou know.. it would be nice if =
people would COMMENT their code..
But, don't worry Mr. Michael Pemberton , I'm sure I'll figure it out =
quickly
enough.. looks like I have to resize, the caption layer as well as the =
multiple
style/appearance layers....
Does there need to be so many layers? I hope not..
I'll post a trimmed version with Pack() ASAP..
(assuming you don't mind of course)
PS: if you go to the address below in IE you will still see a try, but =
it will be an applet..
----- Original Message -----=20
From: Doug Melvin=20
To: dyn...@li...=20
Sent: Friday, December 15, 2000 12:18 PM
Subject: Re: [Dynapi-Dev] Label Problems...
It's quit nice dude!
Mind you I'm goinna have to implement packwidth and packheight..
Or maybe I'll just make one Pack() function..
I'll let you know once it's implemented into my tree..
to check out this tree I've been crying about:
(NS ONLY)
206.75.45.190/catalog/begin.htm
click on catalogue..
----- Original Message -----=20
From: Michael Pemberton=20
To: dyn...@li...=20
Sent: Thursday, December 14, 2000 6:41 PM
Subject: [Dynapi-Dev] Label Problems...
I have noticed alot of talk about problems with the Label widget.
I have made my own widget that I needed for use as a general =
textbox and
thought it may be of use. I have put a modified version of the =
label's
setSelectable method in there ans it seems to work ok.
Anyway, here it is.
--
Michael Pemberton
mp...@ph...
ICQ: 12107010
-------------------------------------------------------------------------=
-
|
|
From: Doug M. <do...@cr...> - 2000-12-15 17:19:24
|
AfroAPI Examples - core.afro.fatcell.jsIt's quit nice dude! Mind you I'm goinna have to implement packwidth and packheight.. Or maybe I'll just make one Pack() function.. I'll let you know once it's implemented into my tree.. to check out this tree I've been crying about: (NS ONLY) 206.75.45.190/catalog/begin.htm click on catalogue.. ----- Original Message -----=20 From: Michael Pemberton=20 To: dyn...@li...=20 Sent: Thursday, December 14, 2000 6:41 PM Subject: [Dynapi-Dev] Label Problems... I have noticed alot of talk about problems with the Label widget. I have made my own widget that I needed for use as a general textbox = and thought it may be of use. I have put a modified version of the = label's setSelectable method in there ans it seems to work ok. Anyway, here it is. -- Michael Pemberton mp...@ph... ICQ: 12107010 -------------------------------------------------------------------------= ----- |
|
From: Doug M. <do...@cr...> - 2000-12-15 16:55:01
|
RE: [Dynapi-Dev] Mozilla & Opera
Before I found DynAPI and I was stumbling along trying to create =
inline code that handles all browsers - I went through the Opera site =
and couldn't find anything to do with their implementation of CSS or the =
DOM or anything else.
Has anyone been able to find documents on their site that give =
developers more of an idea?=20
=20
The impression I've gotten is that there is none.
=20
BTW - I think the major difference between 4 and 5 is the free-ness =
and the inclusion of ads in the interface - obviously bug fixes and =
stuff - but mostly that... With Opera being free - maybe we'll see an =
increase in it's usage
Not if it can't render JavaScript.. :-)
|
|
From: Dan S. <dy...@fu...> - 2000-12-15 14:49:34
|
Just change the .createElement() call to DynLayer_createElement(dlyr).
I changed the theme functions for Button, ScrollBar, PushPanel, and Scrollpane to default to the standard images. I should have put a (url) parameter in those functions. This can be changed quite easily:
function MetalScrollPane(url) {
if (!url) url = DynAPI.librarypath+'images/scrollpane/';
...
}
I mentioned I didn't update List yet. It probably just has to be slightly modified in relation to the create and precreate events.
Dan
On Fri, Dec 15, 2000 at 08:20:48PM +1100, Peter Luxmore wrote:
> Dan
>
> Just been testing what you have currently in CVS. I am using scrollpane and loadpanel and the code is below.
>
> 1. In NS4.7 if you resize the browser window with the mouse, (especially making it larger), results in the following error:
>
> JavaScript Error:
> http://localhost/dynapi/src/lib/dynapi/api/dyndocument.js,
> line 53:
>
> this.children[i].createElement is not a function.
>
> 2. MetalScrollPaneURL is not working in NS4.7 or IE5.1 and the default scrollbar images are displayed.
>
> 3. The list widget is broken. Produces the following error in IE5.1:
>
> Line: 33
> Char: 5
> Error: 'css' is not an object
> Code: 0
> URL: http://localhost/CFCalc2/washerSelect.cfm
>
> -------------------------------------------------------------------------------------------------------
> <script language="JavaScript" src="../dynapi/src/dynapi.js"></script>
> <script language="Javascript">
> DynAPI.setLibraryPath('../dynapi/src/lib/');
> DynAPI.include('dynapi.api.*');
> DynAPI.include('dynapi.util.thread.js');
> DynAPI.include('dynapi.util.pathanim.js');
> DynAPI.include('dynapi.gui.dynimage.js');
> DynAPI.include('dynapi.gui.button.js');
> DynAPI.include('dynapi.gui.scrollbar.js');
> DynAPI.include('dynapi.gui.viewport.js');
> DynAPI.include('dynapi.gui.scrollpane.js');
> DynAPI.include('dynapi.gui.label.js');
> DynAPI.include('dynapi.gui.list.js');
> DynAPI.include('dynapi.gui.loadpanel.js');
>
> // this should be replaced with a default image location based on DynAPI.librarypath
> MetalScrollPaneURL = DynAPI.librarypath+"dynapi/images/mypane/"
>
> </script>
> <script language="Javascript">
>
> DynAPI.onLoad = function() {
> MetalScrollPaneURL = DynAPI.librarypath+"dynapi/images/mypane/"
>
> infoPanel = new LoadPanel()
> infoPanel.setSize(220,233)
> infoPanel.moveTo(478,197)
>
> scroller = new ScrollPane(infoPanel)
> scroller.setSize(245,263)
> scroller.moveTo(478,197)
>
> menulist = new List()
> menulist.moveTo(5,230)
> menulist.setWidth(160)
> menulist.setBgColor('#000000')
> menulist.boldOnSelect(true)
> menulist.setSelectionMode(false)
>
> <cfoutput query="baseprofile">
> menulist.add("#Brand# #Model#")
> </cfoutput>
>
> DynAPI.document.addChild(scroller)
>
> <cfoutput query="DataSheet">
> infoPanel.setURL('_inc.cfm?washerCode=#washerCode#')
> </cfoutput>
>
> DynAPI.document.addChild(menulist)
> }
> //-->
> </script>
>
> Regards
> Peter Luxmore
>
> Dan Steinman wrote:
>
> > I've posted all my updates to CVS. I think touched every file.
> >
> > The significant changes were:
> >
> > - inline creation system for Netscape now worked directly into DynLayer
> > - DynImage auto-resizing, this effected everything that was using DynImage
> > - some changes to how the "precreate", "create", and "resize" events are handled
> >
> > The events took a while to work out. I didn't like how it was setup before because it wasn't quite right when dealing with the new create system.
> > "precreate" should be used in widgets for doing most of the final layout for a widget as well as setting images for the layers. Most of that stuff used to be in the "create" event, but now with the inline creation it's more effecient to do it in "precreate" because when you set the size/location/images of the layers you won't be working with true DIV elements rather with just the JS objects. The goal is to do as little work with div's as possible before you create, so that by the time DynLayer creates the layers it already knows the size and content of them.
> >
> > You still need the "create" event to check for content size, and that sort of stuff.
> >
> > I had to remove all the checks for this.created from within the DynLayer and replace them with checks for this.css!=null. The "this.created" flag is now true once the layer/div element is created, and final position/size has been set, AND all it's children are created also. Peviously this.created was set to true before the children were created which conflicts with the way the inline creation system is supposed to work. I updated all the widgets to make sure everything was working ok with this change.
> >
> > I made a few DynLayer methods into simple functions, create() assignElement, flagChildren etc. These don't have to be methods because they are never used manually.
> >
> > Also you now have to include browser.js BEFORE dynlayer.js because in dynlayer I'm doing a check for Netscape/IE. I updated the dynapi include list for this, but if you have any pages that don't do include('dynapi.api.*') you will have to change the order yourself.
> >
> > DynImage.getImage() can be used before onLoad, the reason there was a problem in IE is you need a break point between the include()'s and the rest of the page. I updated all the examples so they look like this:
> >
> > <script src=dynapi.js>
> > <script>
> > DynAPI.setLibraryPath('../src/lib');
> > DynAPI.include('dynapi.api.*');
> > ...
> > </script>
> > <script>
> >
> > rest of code....
> >
> > </script>
> >
> > Some other minor changes I can remember is the setSize/Width/Height, I made setSize call setWidth and setHeight, and in those I rearranged a few things. I removed all references to getComponent() cause it's not needed anymore. And DynImage.getImage won't return an Image object with .w and .h tacked on, it's unecessary - if you have any code that uses the .w and .h, just replace it with .width and .height.
> >
> > What is no longer working:
> > - inline.js, I think something was wrong in IE
> > - List - Scott A, sorry I didn't get around to fixing this one, I checked it out in IE before all my changes and worked fantastic, I'd like to get it working again. Probably just needs some precreate/create changes. I broke it, so I'll fix it unless you want to take a stab at it.
> >
> > Major bugs we should fix before a stable release:
> > - Loadpanel isn't working in IE4.
> > - Label/button setSelectable still isn't working, anyone know what changes are needed?
> > - Inline creation system for IE - I could do this eventually but I want to work on some other things first so if anyone else wants to give it a shot you're welcome, it should be fairly easy now that the NS code has been finalized.
> >
> > Dan
> > _______________________________________________
> > 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: Jordi 'I. M. <jmi...@or...> - 2000-12-15 13:55:51
|
Wow, this stuff never ceases to surprise me. I'll add this via CVS now Thomas Hering wrote: > Hi! > > Due to the discussion about to detect Opera 5 properly, i remember > that there is also a problem to detect all Netscape's properly: > > The original code in browser.js > > > var b=navigator.appName; > > if (b=="Netscape") this.b="ns"; > > isn't able to detect the NS 4.7 shipped with the german T-Online 3.0 > software (perhaps 500.000 or 1 Million users). > This special NS identifies itself as "Netscape von T-Online" (or > something else). > > To fix this problem, i added one line to browser.js (not the best > solution, but it works): > > > var b=navigator.appName; > if (b.match(/Netscape/)) b="Netscape" //added. > > if (b=="Netscape") this.b="ns"; > > Greetings, Thomas. > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Thomas H. <t.h...@fi...> - 2000-12-15 13:45:45
|
Hi! Due to the discussion about to detect Opera 5 properly, i remember that there is also a problem to detect all Netscape's properly: The original code in browser.js > var b=navigator.appName; > if (b=="Netscape") this.b="ns"; isn't able to detect the NS 4.7 shipped with the german T-Online 3.0 software (perhaps 500.000 or 1 Million users). This special NS identifies itself as "Netscape von T-Online" (or something else). To fix this problem, i added one line to browser.js (not the best solution, but it works): > var b=navigator.appName; if (b.match(/Netscape/)) b="Netscape" //added. > if (b=="Netscape") this.b="ns"; Greetings, Thomas. |
|
From: Richard :o <ma...@ri...> - 2000-12-15 10:26:13
|
hi,
dynapi.gui.scrollpane.html doesn't work in IE5.5 unless you define =
MetalScrollPaneURL after DynAPI.onLoad, i.e.:
DynAPI.onLoad =3D function() {
MetalScrollPaneURL =3D DynAPI.librarypath+"/dynapi/images/scrollpane/"
Richard :o
|
175 messages has been excluded from this view by a project administrator.
