Sorry forgot reply to all
-Original Message-
From: Eytan Heidingsfeld [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 19, 2001 10:02 PM
To: Richard Bennett
Subject: RE: [Dynapi-Dev] Fw: widgetspec
Just to clarify:
>>I see Tcomponent looks quite useful, with it's added functionality, b
Hi,
everyone, please click "reply all" (and edit as needed) when replying to
posts on this list, It's very hard to get a conversation going if we have to
wait two days for our posts to show up, even harder if half of them are only
sent to the original poster.
Eytan,
You've really got me puzzled
I'm working with my customized/reduced version of DynAPI. Currently
when I create a dynlayer for NS6 (or compatible) browser I do the
following to get its inner width (I mean the width of its contents):
this.css.height = this.css.width = 'auto';
this.w = this.elm.offsetWidth;
this.h = this.
But doesn't this simply result in abstraction which, in the very theory of the
process, is just wrapping one function in another.
One minute you were suggesting that we remove the dynlayer abstration and
manipulate the layers directly, next you want to add extra levels of code. It
is becoming co
assignElement...
is this a replacment for findLayers in the inline.js extension?
If so, it's about time..
I've already modified my copy of findLayers to index only those inline
layers which had not been made into DynLayers yet..
IE; so I can call findLayers more than once.. But I found that even t
Hi!
szyslak wrote:
>
> I'm working with my customized/reduced version of DynAPI. Currently
> when I create a dynlayer for NS6 (or compatible) browser I do the
> following to get its inner width (I mean the width of its contents):
>
> this.css.height = this.css.width = 'auto';
> this.w = thi
Why don't you just hide/show each layer as need be..
far simpler than scrolling a large frame
- Original Message -
From: "szyslak" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 20, 2001 5:58 AM
Subject: [Dynapi-Dev] offsetWidth : why won't work?
> I'm working with
I want the scrolling effect to work (in fact it works perfectly).
Anyway my question is just how to obtain in NS6 the width of a layer
when not declared especifically (by usign style="width:100px" or by
the Dynlayer method).
>Why don't you just hide/show each layer as need be..
>far simpler than
I'm afraid I have to agree here..
The current structure of the DynAPI is as close to
'proper OO' as on can get with such a OO-challenged scripting language.
I say this with the confidence of experience. - hell, I tought the stuff
(c++,VB(OOish), and even Javascript)
One of the selling points of t
myLayer.slideTo().
looks like scrolling without the headache.
Really, I'm just trying to help you avoid more work, and more pain than
nessesary.
:-)
- Original Message -
From: "szyslak" <[EMAIL PROTECTED]>
To: "Doug Melvin" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, November
I know. But thats not the problem. Sorry, I think I haven´t expressed
myself clear (I can think it in spanish but translating it to english
is a pain :)).
The page's content are not inside a layer. They are just in a frame.
But in this contents I have a layer at an absolute position. I need
to kno
I believe what 8an is trying to say is, there are classes that are not
visual objects, but should be part of the inheritance hierarchy at some
level. (i.e. Dan's layout manager should probably be a class that inherits
certain properties from DynObject, but not from DynLayer, because
DynLayerManage
I've already split the DynObject into 3 separate objects:
DynObject -> EventObject -> DynElement
DynObject now has only a couple methods, setID, new add/removeMethod(), inherit(),
getClassName(), getClass().
EventObject inherits from DynObject and adds the eventlistener system. You can now
c
Bugs item #478986, was opened at 2001-11-06 20:40
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105757&aid=478986&group_id=5757
Category: DynAPI 2 Browser-Specific
Group: None
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Submitted By: Andy Short (sh0rtie)
Ass
I'm written some code that has caused me to
re-think the loadpanel.
run index.html in netscape.
Click the link.
then check out the source of
embed.html..
There is an alert in the Head, in the body, and in
body.onload.
All three are executed apone loading the eternal
file int an ilayer.
Hi,
Since I haven't written some fun JS in a while a tossed up a ObjectPool
because someone here asked for it. I don't remember who did but I wrote it.
I also will start on a whole 8anWidgetPack that is my OO style. It's just a
bit busy at work (still!) so progress will be slow.
Have fun,
8an
O
I noticed to supporting comments on the WidgetSpec are the writers in our
list or just visitors?
8an
___
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
I was playing around the file
dynapi-2.5.6\dynapi\examples\dynapi.ext.inline.htm, when I realized that all
the layers get messup when I resized the browser Netscape® Communicator
4.76. Not only the two original layers are gone, but 3 layers(one is red
even through I have never defined red color
> I have yet to try a similar solution in IE (no
time).
> But this has gotten me thinking that we _must_
be doing something wrong for javascript to _not_ execute in a
loadpanel..
Nothing wrong, you just have to put all code in the body
of the document, as loadpanel parses out everything
Hi,
Why are we doing this:
onload = function() { DynAPI.loadHandler(); };
instead of this:
onload = DynAPI.loadHandler;
in dynapi.js?
I would use the first syntax if values need to be passed, but otherwise the
second seems much leaner, right?
Richard.
__
but Why?!?!
I didn't need to strip out and tags..
the embed.html has and
tags..
And it all works just fine.
- Original Message -
From:
Richard Bennett
To: Doug Melvin ; [EMAIL PROTECTED]
Sent: Tuesday, November 20, 2001 6:29
PM
Subject: Re: [Dynapi-Dev] Loadin
If I understand you right, you're talking about the NS4 resize bug. (FAQ)
We have a "fix" for this browser bug, but it doesn't as yet work for
Dynimages, or inline layers, and on large pages it fails too.
Basically this is a tricky issue that is hard to solve.
Richard.
- Original Message ---
ah, why we are only getting the content from between the body
tags? I don't know.
I adapted your test, and attached to this mail.
It now works in IE/NS/Mozilla.
In all these browsers all alerts show.
So it would seem that a code-loading widget would be pretty
easy, and a lot more robust than l
Actually it does work on inline layers.
You just have to call findLayers every time you dynamically add a layer in
HTML (via setHTML() ect.)
I have a mod that will keep it from re-adding layers it had already found.
I'll post it when I get to the office tomorrow.
- Original Message -
From:
Hi all,
I just noticed Eytan's widget spec proposal is on the site:
http://dynapi.sourceforge.net/doccenter/index.php?EytansWidgetSpec
I had hoped a widget-spec would clear up confusion around the different
existing models, and simplify existing code in use, by dropping things like
getSubClass()
25 matches
Mail list logo
