shouldn't we use the built-in doxygen-commands, like:
/**
* \class DynLayer
* \package dynapi.api
* \bried This class is used to manipulate Layers
* \example dynlayer.create.html
* \author ()
* \version 1.0
* \bug ()
* \deprecated (...)
* \param int clip[]
* return void
*/
or
I haven't had a chance to set up doxygen yet. But to answer your question,
yes. Since we decided to use doxygen, we should use the built-in doxygen
commands as you recommended. But to be clear, are we still commenting the
JavaScript source, or are we only commenting in doxygen the Java mirror?
Na
Well, yes we could, but is.res640x480 looks much
better.
How about a screen.js adding to the core? In this way
we could add the screen resolution detect code and
possible add showHourGlass() and hideHourGlass()
methods.
At times it becomes very necessary for a programmer to
show the viewer tha
Hello,
Since Dan is at work on a layer manager, how about
adding a pool manager? In other words , a pool manager
can be used to create a set number of layers when the
system is idle, and release them from the pool when
the new DynLayer() function is called. This should
make layers appear much fas
Good idea IMHO..
- Original Message -
From: "Raymond Irving" <[EMAIL PROTECTED]>
To: "DynAPI-Dev" <[EMAIL PROTECTED]>
Sent: Monday, November 19, 2001 10:42 AM
Subject: [Dynapi-Dev] Layer Pool Manager
> Hello,
>
> Since Dan is at work on a layer manager, how about
> adding a pool manage
Agreed. This doesn't look vary hard to do,
and the resulting documentation will make it
far more than worth it.
- Original Message -
From: "martin ström" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 19, 2001 4:15 AM
Subject: RE: [Dynapi-Dev] dynapi documentation
> s
The source needs to be commented. Period.
That is simply correct programming practice. Period.
:-)
- Original Message -
From: "Laszlo Teglas" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 19, 2001 10:12 AM
Subject: RE: [Dynapi-Dev] dynapi documentation
> I haven't ha
Bugs item #463584, was opened at 2001-09-21 08:34
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105757&aid=463584&group_id=5757
Category: DynAPI 2 API
Group: Verified
>Status: Closed
Resolution: Fixed
Priority: 7
Submitted By: Tom Mach (machu)
Assigned to: Richard
Translation to Spanish would be very cool,
I'll see If I can talk my roomate into translating to French (no promises)
If you do choose to translate the documentation, I think you should wait
until after Chrismass
(IMHO) as I will be making a major update to the documentation over the
holidays.
-
--- Dan Steinman <[EMAIL PROTECTED]> wrote:
> Some of my changes in 2.6 are costmetic also, such
> as setLocation() replacing moveTo().
It just hit me. Why change moveTo() to setLocation()?
moveTo() consist of only 6 characters while
setLocation() consist of 11 characters. In essence
setLocatio
Agreed. Not only that but, why in hells name would we want to change the
implementation of a function?
For gramerrical reasons? This isn't english 101.. I have no intention of
having to modify every application and widget I ever wrote with DynAPI 2
just to accomadate a grammerical correction.
isn't there any possibilities to generate the docs right out of
javascript-source and therefore skip the need to update two files
every time?
/martin
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of
> Laszlo Teglas
> Sent: den 19 november 2001 16
If you wish to make a resizeLayer extension, please feel free.
- Original Message -
From: "Matt Fair" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 15, 2001 6:00 PM
Subject: [Dynapi-Dev] resize layer method
> I think we should have a resize layer method that will
Um.. loadpanel is an IFRAME/ILAYER.. these have a
.src property which relates to a file.
so:
var fileNames = new Array();
fileNames[0] = "www.google.com"
fileNames[1] = "www.hotbot.com"
fileNames[2] = "www.lycos.com"
function showPage(intPageINdex){
myLoadPanel.setURL(fileNames[intPa
I agree that tha can be done but,
There is still no reason to change the implimentation.
Done.
Period.
Prove me wrong.
- Original Message -
From: "Jordi Ministral" <[EMAIL PROTECTED]>
To: "Doug Melvin" <[EMAIL PROTECTED]>
Sent: Monday, November 19, 2001 12:45 PM
Subject: Re: [Dynapi-Dev]
The reason I changed to setLocation is because moveBy and moveTo were very out of
place next to all the other methods of DynLayer: setX() setY() setSize() moveTo() just
doesn't make sense.
And plus there are endless numbers of ways to get your 5 bytes back.
My new anchoring system (which total
Raymond Irving wrote:
> Since Dan is at work on a layer manager, how about
> adding a pool manager?
Isn't this what the recycled[] collection does? I noticed that it's
been moved into the NS4 branch of specificCreate().
scottandrew
--
scott andrew lepera
[EMAIL PROTECTED]
web stuff: www.sc
The recycled[] collection reuses deleted layers when new layers are
created. Its done only in NS since you can't really delete the layers
in ns4 (so we reuse them to keep memory usage down). I'm not sure
there would be a benefit of this in other browsers since we can safely
delete layers in the
my suggestion is to call that method setPos().
same bytesize as moveTo() and consistent with the getXXX() and setXXX()
philosophy.
anybody?
--
Michael Buerge
> From: Dan Steinman <[EMAIL PROTECTED]>
> Date: Mon, 19 Nov 2001 13:12:35 -0500
> To: [EMAIL PROTECTED]
> Subject: Re: [Dynapi-Dev] Propo
Yes, I'm all for that
--- Michael Bürge <[EMAIL PROTECTED]> wrote:
> my suggestion is to call that method setPos().
> same bytesize as moveTo() and consistent with the
> getXXX() and setXXX()
> philosophy.
> anybody?
>
> --
> Michael Buerge
>
> > From: Dan Steinman <[EMAIL PROTECTED]>
> > Dat
I apologize if this recommendation sounds like something that is already done, but
here is my opinion.
If a change like this is going to be made, I highly recommend that moveTo still be
supported for some time, but listed as deprecated in any documentation or
instructions. That way no develop
In short. No. Not having used doxygen before, it is my understanding that it
only works with Java, and not with JavaScript. I can see why we don't have a
similar tool for JavaScript. JavaScript is not as strict as Java, therefore
it would be difficult to recognize anything other than simple functi
I'd like to reserve setPosition() to allow relative vs absolute positioning, and
obviously it wouldn't make sense to have both setPos() and setPosition().
I'd rather not get into an argument over saving a few bytes here and there as I've
never felt it to be of significant importance. My total
> If you want to save file size that badly you're better off renaming all
the fucntions and properties to stuff like this.sp(x,y) this.ss(w,h). You
can make >big changes like this to the DynAPI very easily with a global
search and replace function like that in the HomeSite html editor.
Taht coul
None of my posts from 12 hours ago got through, so I'm reposting them:
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,
Hi,
Nice to have you on board, there's quite a few people from your end of the
world here, so you should feel at home.
Remember, if you reply to a post on this list, clicking "reply" will not
post to the list, only to the sender, so you should click "reply all" and
edit as needed.
This is a Sourc
You could easily create a perl program to strip out all comments inline or
otherwise. I believe Dan already has such a beast. You could also include
replace code:
$mystring =~ s/pattern/replacement/;
to compress anything (ie moveTo --> mt)
NanoFace =;^)
-Original Message-
From: [EMAIL
I tried the following but the layer 'myLayer' didn't get hidden. Any idea
what can I do to make it hidden?