dynapi-dev — List related to the current DynAPI Core development

Re: [Dynapi-Dev] DynAPI Makefile/code compression almost complete

[Robert R. <rra...@ya...>]

Sounds great, when CVS is up in running, we can package the project
using a cron job from the sourceforge server, so people can download
daily updates. Currently, sourceforge already creates daily snapshots,
but your build system can be set up on the server to better package
the project.

-- 
// Robert Rainwater

On 12/3/2000, 10:52:29 PM, Dan wrote regarding "[Dynapi-Dev] DynAPI Makefile/code compression almost complete":

> This weekend I took on the task of creating a "build" system for DynAPI.

> First part involved writing my own JavaScript whitespace/comment removal script (in Perl).  It's pretty much complete and as good or better than any others I've seen.  I'm calling it JSPack and
> will release this as a separate program that must be downloaded in order to "build" the DynAPI.

> It not only compresses JS code, it also packages the files together.  And this will be used to create js packages for the DynAPI.  For example, it will create the files dynapi.api.js,
> dynapi.gui.js... which contain all the classes in that subdirectory.  I have to add one more feature to my script that determines the order that the objects should be added to the Package.  For
> example, ScrollPane extends off of ViewPort, so in the dynapi.gui.js file, viewport.js must be added first.  Therefore I plan to add files to the /lib/dynapi/ directories that state the order of
> the files.  These will be named .jspack and will be a simple list of the js files in the order they are to be added to a package.  My JSPack program will take care of the rest.

> Right now JSPack does not parse the JavaScript, so it will not go through each of your lines and fix and incorrect or missing semicolon.  There for it is essential that all files in the DynAPI have
> semi's on each line, as well in the following case:

> f = function() {
> };  // absolutely needed

> Second part is the Makefile.  Up until now we've just been editing our files in /js/.  But now we can use a separate directory /src/.  This is where we edit our files.  Our JavaScripts can contain
> comments, and do not have to be bunched up, because the Makefile will use the /src/ directory, compress all the code, and produce js packages, and jar files, and output it to /js/.

> So the /js/ directory will then contain a compressed release of our code.

> In order to build the DynAPi you need to be using unix/linux or have Cygwin installed in Windows, along with Perl and the JDK (for Jarring the files).  You need  to place JSPack in your path, and
> then type:

> make

> in the /dynapi/ source tree.  This runs the commands in the Makefile which does everything needed to produce the /js/ tree.

> I'm going through all of the existing JS code and putting the necessary semi colons, and will have everything ready to use in another day or 2.  A first run-through of building the DynAPI produced
> a Jar file which 16KB!!!!  (yes the entire DynAPI with the existing widgets can be compressed a lot).

> We can also use GZip to compress the files for use in IE 5, these will be a bit smaller than the Jar files. I don't believe there is any compression we can do for IE 4 though (other than whitespace
> removal).

> over and out,
> Dan

> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

[Dynapi-Dev] CVS in WIndows

[Robert R. <rra...@ya...>]

Here are some quick and dirty instructions for setting up CVS on
windows.

Files
-----

WinCVS:
ftp://sunsite.cnlab-switch.ch/mirror/cvsgui/WinCvs11b17.zip

SSH:
ftp://ftp.dei.uc.pt/.disk2/Crypto/SSH/contrib/ssh-1.2.14-win32bin.zip

Installation
------------
Install WinCVS as per the instructions provided.

- Unzip ssh-1.2.14-win32bin.zip to a directory (ex. c:\ssh).
- Add c:\ssh to the PATH variable.
- Create a HOME directory (ex. c:\home).
- Create environment variable HOME with value c:\home
- Restart

- Start WinCVS.
- It should prompt to enter your CVS Root.  (if not, choose
Admin|Preferences).  Enter the cvs root as:
":ext:<username>@cvs.dynapi.sourceforge.net:/cvsroot/dynapi"
Below CVSRoot, choose SSH Server for authentication.  Then click the
Ports tab and click "Check for alternate rsh name" to enable it.  Then
choose OK and your set.

Also, you can choose View|Browse Location|Change to change to a
working directory, so you will not see your whole hard drive in the
view.  Choose c:\home for example.

Now your set.

To checkout a module, Right click Home and choose checkout and then
you would enter the name of the module.  A DOS box will pop up that
will require your sourceforge password.

Currently, there is no module yet to checkout, but you would normally
checkout "dynapi" to get the latest version.

For more info checkout:
https://sourceforge.net/docman/display_doc.php?docid=766&group_id=1

-- 
// Robert Rainwater

[Dynapi-Dev] CVS

[Robert R. <rra...@ya...>]

Before we start using CVS, I think we should create some sort of
guidelines and goals.  I guess that will be up to Dan if he so
chooses.

Also, in order to have read access to CVS, you do not need to be a
member of the project, otherwise if you will be requiring write
access you must be a member of the project.

I've sent a request to Sourceforge to reset the CVS tree.  That should
be done in a few days.

-- 
// Robert Rainwater

[Dynapi-Dev] DynAPI Makefile/code compression almost complete

[Dan S. <dy...@fu...>]

This weekend I took on the task of creating a "build" system for DynAPI.

First part involved writing my own JavaScript whitespace/comment removal script (in Perl).  It's pretty much complete and as good or better than any others I've seen.  I'm calling it JSPack and will release this as a separate program that must be downloaded in order to "build" the DynAPI.

It not only compresses JS code, it also packages the files together.  And this will be used to create js packages for the DynAPI.  For example, it will create the files dynapi.api.js, dynapi.gui.js... which contain all the classes in that subdirectory.  I have to add one more feature to my script that determines the order that the objects should be added to the Package.  For example, ScrollPane extends off of ViewPort, so in the dynapi.gui.js file, viewport.js must be added first.  Therefore I plan to add files to the /lib/dynapi/ directories that state the order of the files.  These will be named .jspack and will be a simple list of the js files in the order they are to be added to a package.  My JSPack program will take care of the rest.

Right now JSPack does not parse the JavaScript, so it will not go through each of your lines and fix and incorrect or missing semicolon.  There for it is essential that all files in the DynAPI have semi's on each line, as well in the following case:

f = function() {
};  // absolutely needed

Second part is the Makefile.  Up until now we've just been editing our files in /js/.  But now we can use a separate directory /src/.  This is where we edit our files.  Our JavaScripts can contain comments, and do not have to be bunched up, because the Makefile will use the /src/ directory, compress all the code, and produce js packages, and jar files, and output it to /js/.

So the /js/ directory will then contain a compressed release of our code.

In order to build the DynAPi you need to be using unix/linux or have Cygwin installed in Windows, along with Perl and the JDK (for Jarring the files).  You need  to place JSPack in your path, and then type:

make

in the /dynapi/ source tree.  This runs the commands in the Makefile which does everything needed to produce the /js/ tree.

I'm going through all of the existing JS code and putting the necessary semi colons, and will have everything ready to use in another day or 2.  A first run-through of building the DynAPI produced a Jar file which 16KB!!!!  (yes the entire DynAPI with the existing widgets can be compressed a lot).

We can also use GZip to compress the files for use in IE 5, these will be a bit smaller than the Jar files. I don't believe there is any compression we can do for IE 4 though (other than whitespace removal).

over and out,
Dan

[Dynapi-Dev] Admin - Please read

[Kevin F. <kfr...@id...>]

As a first timer to this post, forgive me if I'm going down a track that has
already been discarded and for the length of this post :ob

My background is web-site development specializing in a Cold Fusion backend
before that a designer and editor.  Like others who have found their way
here, we were all dutifully impressed with the power (and evolving
completeness) of the DynApi.  So here goes ...

There has been a lot of discussion about development co-ordination (here and
the help posts) about contributions being able to be made from any level;
about tangents that may or may not prove beneficial).  Dan has spoken of
introducing CVS and others IRC etc., More documentation is required, so
newbies can quickly come up to speed, the list goes on.

If the administrators choose, I have some webspace available, or a free
CFusion site like cfm-resources.com could be used where I could construct a
database/s that could ... dynamically update and output the authorised
'code', show who is currently working/doing what (alert emails of coarse),
multi-forums and multi-thread forum - one answer could be posted to several
threads (also output as listmail), tasks that could be performed by
'child-devs' (documentation, FAQ's, testing ... re:helplist) on their way to
becoming 'parent-devs', simple/complex search functions, widget libraries
(complete and otherwise).  I have made some other notes on functionality but
I don't want to bog this list down (as I may be well off the mark).
Management could be kept to a minimum with the right design.

Anyway, it's just an offer, if you are interested let me know.  If not, I
won't go away as I believe what is happening here is both significant in
itself and important to the future.

I know sourceforge has many of the above capabilities, but my machine feels
like it has been in the ring with Mike Tyson every time I logon.  :o)

Kevin Francis

Re: Re[2]: [Dynapi-Dev] Lets open CVS again

[Doug M. <do...@cr...>]

Allright then.. I vote Yup to CVS.
:-)
Where does one DL CVS?
Doug
----- Original Message -----
From: "Robert Rainwater" <rra...@ya...>
To: "DynAPI Development List" <dyn...@li...>
Sent: Saturday, December 02, 2000 1:42 PM
Subject: Re[2]: [Dynapi-Dev] Lets open CVS again


>
> CVS is a revision control system that allows multiple users to work on
> a project. The CVS system runs on sourceforge server and requires a
> client in order to check in/out files from CVS. This would allow the
> group to update the files from there own system. It would make getting
> the latest version much easier as well. All you would have to do is a
> checkout and you would have the latest from the project. And for me,
> updating the releases would be much easier as well.
>
> --
> // Robert Rainwater
>
> On Saturday, December 02, 2000, 7:08:38 PM, Doug wrote:
>
> > What exactly is CVS? if it involves file sharing then my employer will
say
> > "not a chance buddy"
> > :-)
> > Doug
> > ----- Original Message -----
> > From: "Robert Rainwater" <rra...@ya...>
> > To: "Dan Steinman" <dyn...@li...>
> > Sent: Friday, December 01, 2000 7:17 PM
> > Subject: Re: [Dynapi-Dev] Lets open CVS again
>
>
> >>
> >> If the group would like, I can give instructions on how to setup CVS
> >> in Windows.  Its really just a matter of downloading and setting up
> >> WinCVS and ssh.  I've never used cvs in linux, but if you do, you need
> >> to make sure you have ssh setup.
> >>
> >> There are also a few howto docs at sourceforge on how to use CVS for
> >> new users.
> >>
> >> --
> >> // Robert Rainwater
> >>
> >> On Saturday, December 02, 2000, 12:17:47 AM, Dan wrote:
> >>
> >> > I really think we should open up CVS again to do our development.  As
it
> > is it's not easy for everyone to contribute code, and Robert is stuck
with
> > the job of collecting everything and making an
> >> > official release.  Using CVS will make it easier on everyone.
> >>
> >> > We can help eachother to get it all set up on local computers, and
make
> > sure we can all release files easily.  There's CVS clients for Windows
> > (CVSWin?) that should be pretty easy to use.
> >>
> >> > It'll also make it easy for non-developers to get the latest code
> > without searching around for everything.
> >>
> >> > This weekend I'll get a Makefile/build scheme working which will
> > compress all the js code, jar it for Netscape, and repackage it all.
And
> > this should be the starting point for the new dynapi CVS
> >> > tree.
> >>
> >> > 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] dynapi-2000.11.07-danwidgets.zip bug report

[Bill W. <bil...@us...>]

Bug report:
date: 20001203
by: Bill Wheaton
in: dynapi-2000.11.07-danwidgets.zip::dynapi/js/lib/dynapi/gui/label.js
ua: IE5 (v5.00.2314.1003)
symtom: label text is always default (courier new 10pt black) despite changing
with font setting methods.
possible cause:
The Label object's setText method reads:
Label.prototype.setText = function(text) {
  this.text = text || ''
  var styled = '<font point-size='+this.font.size+
   ' family="'+this.font.family+'">'+this.text+'</b>'
  if (this.font.bold) styled = '<b>'+styled+'</b>'
  var width = this.wrap? 'width='+this.w : ''
  var wrap = this.wrap? '':'nowrap'
  this.textFull = '<table '+width+' cellpadding='+this.padding+
   ' cellspacing=0 border=0><td align="'+
   this.align+'" '+wrap+'>'+styled+'</td></table>'
  this.setHTML(this.textFull)
}

I think, that in setting the <font> it should end with </font>, not </b>,
like:
Label.prototype.setText = function(text) {
  this.text = text || ''
  var styled = '<font point-size='+this.font.size+
   ' family="'+this.font.family+'">'+this.text+'</font>'
  if (this.font.bold) styled = '<b>'+styled+'</b>'
  var width = this.wrap? 'width='+this.w : ''
  var wrap = this.wrap? '':'nowrap'
  this.textFull = '<table '+width+' cellpadding='+this.padding+
   ' cellspacing=0 border=0><td align="'+
   this.align+'" '+wrap+'>'+styled+'</td></table>'
  this.setHTML(this.textFull)
}

Also, in the constructor I changed the line that reads:
  this.font = {}
to:
  this.font = {bold : false, size : '9pt', family : "arial"}
to give it some default values, which seems to work better in my IE5
(v5.00.2314.1003)

Suggestion:
Use a style instead of font tags:
Label.prototype.setText = function(text) {
  // set the text if it there is any. if not then leave it alone
  // this will allow myLabel.setText() instead of myLabel.setText
  // (myLabel.text) which should not be allowed . (myLabel.setText
  // (myLabel.getText()) would be ok, but cumbersome.)
  this.text = text||this.text||''
  var styled = '<div style="font-family:' + this.font.family + 
   '; font-size:'+this.font.size +
   (this.bold?';font-weight:bold':'') + 
   '; text-align:' + this.align + ';">' +this.text+'</div>'
  var width = this.wrap? 'width='+this.w : ''
  var wrap = this.wrap? '':'nowrap'
  // probably not much reason to keep textFull around after setHTML call, so
do 'var ' instead of 'this.'.  
  //Also, include the <tr></tr> tags in the table.  NS browsers can be pretty
picky about that.
  var textFull = '<table '+width+' cellpadding='+this.padding+
   ' cellspacing=0 border=0><tr><td align="'+
   this.align+'" '+wrap+'>'+styled+'</td></tr></table>'
  this.setHTML(textFull)
}

The div is needed to make the text-align work, span doesn't cut it.  Perhaps
the table should be dispensed with in favor of doing the whole thing as a
layer with clipping. (unless there is a problem with using a div in which case
you have to use a table... which may have been the original reason)

Side Effects:
I haven't figured out why, when the Label is used as part of the Button, I
can't click on the label portion.  I tried adding a cover, but no go. 
setSelectable didn't seem to do anything.

-bw


____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1

[Dynapi-Dev] Developers reference

[Pascal B. <pa...@dy...>]

I finally found the time to do "some" typing.. and here's the result :)

This developers reference is based on my new (work in progress) DynAPI code,
so it's not correct for the current official DynAPI model, but with some
tweaking it should be a nice reference for anybody needing more inside
information. The main differences are in the DynObject.. basically you could
see all the DynObject stuff as a DynLayer or DynDocument reference. Maybe
some one can change and shuffle the text abit so that it's correct for the
DynAPI model.

I used the W3C stylesheet and reference style, so this should look familiar
to anybody knowing how to read/use those W3C documents :)


Another note I want to make, and this will probably get some people ticked
off, is the fact that this list is great for discussing problems of the
DynAPI, but I think there's way to much discussions going on and not alot of
actual development.

I mean there are discussions running about adding semmicoloms to every line,
or adding comments into the source files.. I don't think that's real
important stuff, and I'm not going to spend time arguing over those "ideas"
when there are still things like widget-creation, debugging and other
important things that can be done. One thing I will say about it is that I
don't understand why people don't take the time to add those ; characters
them selves, or study the code and learn it that way (that's the way we all
learned it).

...sadly, this is probably gonna cause some more discussions about nothing.

Cya!

Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net

Re: [Dynapi-Dev] Beta Relase 12.01.2000

[Richard :o <ma...@ri...>]

hi,
First and foremost, thank you  for all your hard work.
I had a look at this release, but found the same small bugs(?) in the
examples as in Dan's release, which I had just posted a buglist for, maybe
it's not up to you to look these over, but here they are again:

* Button:  needs cover layer for text
* DynImage: declaring "uimg" and DynImage.getImage has to come after
DynAPI.onLoad
* Label:  unwrap causes error.
* PushPanel: labels are deleted on changing, and thus can only be used once.
   Scroll doesn't stop.
* ScrollPane: The word "scroll has to be replaced by f.i. ScrollBar
   for some reason declaring "MetalScrollPaneURL =" has to come after
DynAPI.onload
* ViewPort: labels are deleted on changing, and thus can only be used once.
   Scroll doesn't stop.
* Image Animation:Declaring "arrows" and DynImage.getImage has to come after
DynAPI.onLoad

A major bug in this release seems to be a document level onmousemove event
which stops all animations if you move the mouse anywhere. This does not
happen in Dan's 11.12 release.

Buglists always sound like we're wining, but I'm just trying to help.
cheers,
Richard :o

----- Original Message -----
From: "Robert Rainwater" <rra...@ya...>
To: <dyn...@li...>
Sent: Friday, December 01, 2000 4:18 PM
Subject: [Dynapi-Dev] Beta Relase 12.01.2000


>
> I've uploaded the beta release to
http://dynapi.sourceforge.net/beta/dynapi-12.01-beta.zip.
> It includes Dan's new animation widgets.  Please reply with any bugs to
> this thread.
>
> Known Bug:  The DynAPI.addLibrary() calls in dynapi.js need to be
> changed to reflect the new files and organization.
>
> --
> // Robert Rainwater
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
> ____________________________________________________________
> Get your FREE personal .com domain name and
> NAMEzero Personal Portal at: http://www.namezero.com.
> For customer service, mailto:cus...@na....
>
>

Re: [Dynapi-Dev] My new Object

[Eytan H. <ey...@tr...>]

I managed to fix the problem by making the FreeObj method external. The =
problm was that the scope was still in the object and then it could not =
be deleted.

Thanx, 8an

Re: [Dynapi-Dev] My new Object

[Joachim L. <lu...@ho...>]

JavaScript objects are destroyed when all references to it are removed.
The problem is that the HTML file still has a valid reference to the object.

/Lunna

At 2000-12-03 11:23 , you wrote: 
>
> I'm trying to write this new OO aproach to OOJS. The problem is the freeing
> of an object. Included I have the example that doesn't work. As you will see
> in the scope of the method FreeObj the object is null but when I alert the
> classname instead of getting undifined I get the classname. What's going on?
>  
> Eytan

[Dynapi-Dev] Multiple Inheritence

[Eytan H. <ey...@tr...>]

I wrote a function inherit that can do multipule inheritence. The only =
problem is that any methods/properties that you want to let other =
objects inherit must be included in an array called oInterface. I know =
this is all vague. If anyone want the code just email me offlist.
8an

SV: Re: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff

[Bart B. <ba...@ho...>]

Well , try reading the netscape tutorial at:

http://developer.netscape.com/docs/manuals/js/client/jsguide/obj2.htm


-----Ursprungligt meddelande-----
Från: Eytan Heidingsfeld <ey...@tr...>
Till: dyn...@li... <dyn...@li...>
Datum: den 3 december 2000 10:37
Ämne: Re: Re: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff


>I too have found the code very complicated. For that reason I wanted to
>simplfy it and make it even more OOP. To do that I wanted to create a simple
>type MyObject. Which would be an empty object that all other non-visual
>widgets inherit from. And then create one widget Component which would
>inherit from object. Component would have a DynLayer property and on it all
>the visual parts would be drawn. The only problem is I keep trying to do
>inheritence in different wayys and it always fails. How do you do simple JS
>inheritence.
>
>Eytan
>
>_______________________________________________
>Dynapi-Dev mailing list
>Dyn...@li...
>http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

[Dynapi-Dev] My new Object

[Eytan H. <ey...@tr...>]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<html>
<head>
	<title>Test OOJS</title>
<script src="oojsMain.js"></script>
<script>
var MyNewObject;
MyNewObject = new TObject();
function TestEvent(Sender){
	alert("yo");
}
MyNewObject.onCreate = TestEvent;
MyNewObject.create();
MyNewObject.destroy();
alert(MyNewObject.classname);
</script>
</head>

<body>



</body>
</html>

Re: Re: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff

[Eytan H. <ey...@tr...>]

I too have found the code very complicated. For that reason I wanted to
simplfy it and make it even more OOP. To do that I wanted to create a simple
type MyObject. Which would be an empty object that all other non-visual
widgets inherit from. And then create one widget Component which would
inherit from object. Component would have a DynLayer property and on it all
the visual parts would be drawn. The only problem is I keep trying to do
inheritence in different wayys and it always fails. How do you do simple JS
inheritence.

Eytan

[Dynapi-Dev] IRC #dynapi

[Alexey M. <ma...@ca...>]

	I just like to establish IRC channnel
 #dynapi on irc.forestnet.org , port = 7777
	so we could communicate faster 

	(ok you know what is irc for :)

			Malx

Re: [Dynapi-Dev] DynAPI.include() and Libraries

[Alexey M. <ma...@ca...>]

> Does anyone here name their javascript files with any extension other
> than .js?
> does make it alot more "MS User" friendly. (what, the files have
> extensions? : P )

	But in contrary for Unix user it would be very strange.
 Becouse unix have no extensions , so "name.js" is just a file name
 like "other.file.name.". And it is strange not to write part of
 file name.
	:)))))

				Malx
-- 
All our life is digging in memories. Some of them 0.01 sec old.

Re[2]: [Dynapi-Dev] Lets open CVS again

[Robert R. <rra...@ya...>]

CVS is a revision control system that allows multiple users to work on
a project. The CVS system runs on sourceforge server and requires a
client in order to check in/out files from CVS. This would allow the
group to update the files from there own system. It would make getting
the latest version much easier as well. All you would have to do is a
checkout and you would have the latest from the project. And for me,
updating the releases would be much easier as well.

-- 
// Robert Rainwater

On Saturday, December 02, 2000, 7:08:38 PM, Doug wrote:

> What exactly is CVS? if it involves file sharing then my employer will say
> "not a chance buddy"
> :-)
> Doug
> ----- Original Message -----
> From: "Robert Rainwater" <rra...@ya...>
> To: "Dan Steinman" <dyn...@li...>
> Sent: Friday, December 01, 2000 7:17 PM
> Subject: Re: [Dynapi-Dev] Lets open CVS again


>>
>> If the group would like, I can give instructions on how to setup CVS
>> in Windows.  Its really just a matter of downloading and setting up
>> WinCVS and ssh.  I've never used cvs in linux, but if you do, you need
>> to make sure you have ssh setup.
>>
>> There are also a few howto docs at sourceforge on how to use CVS for
>> new users.
>>
>> --
>> // Robert Rainwater
>>
>> On Saturday, December 02, 2000, 12:17:47 AM, Dan wrote:
>>
>> > I really think we should open up CVS again to do our development.  As it
> is it's not easy for everyone to contribute code, and Robert is stuck with
> the job of collecting everything and making an
>> > official release.  Using CVS will make it easier on everyone.
>>
>> > We can help eachother to get it all set up on local computers, and make
> sure we can all release files easily.  There's CVS clients for Windows
> (CVSWin?) that should be pretty easy to use.
>>
>> > It'll also make it easy for non-developers to get the latest code
> without searching around for everything.
>>
>> > This weekend I'll get a Makefile/build scheme working which will
> compress all the js code, jar it for Netscape, and repackage it all.  And
> this should be the starting point for the new dynapi CVS
>> > tree.
>>
>> > 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

Re: [Dynapi-Dev] Is there a "loadHTML" for the latest release?

[b0n3z <b0...@go...>]

Thanks for the resource!!! I didn't know this existed. Is it possible to
have a loadPanel for the ViewPort? I noticed this line in viewport.js - but
I still can't figure out how to use it.

 this.contentResizeListener.onload = function(e) {  // for loadpanel

Thanks,

Ken

----- Original Message -----
From: "Robert Rainwater" <rra...@ya...>
To: "b0n3z" <dyn...@li...>
Sent: Saturday, December 02, 2000 11:08 AM
Subject: Re: [Dynapi-Dev] Is there a "loadHTML" for the latest release?


>
> The loadHTML is no longer a part of the DynAPI.  In the latest beta
> (http://dynapi.sourceforge.net/beta/, you will find the loadPanel
> which is probaly what you need.  Of course the loadPanel is still beta
> (has some problems with IE4).
>
> --
> // Robert Rainwater
>
> On Saturday, December 02, 2000, 2:00:09 PM, b0n3z wrote:
>
> > I have been trying to find or port over the loadhtml.js for the latest
> > release of dynapi-2000.11.05.zip , 06, or 07.
>
> >  I desperatly need one - please.
>
> >  Thanks,
>
> >  Ken
>
> >  Here was the older one that I have from somewhere:
> > -----------------------------------------------------
>
> > /*
> >    Core DynAPI Distribution
> >    loadURL extension
> > */
>
> > if (is.ie5) document.write('<DIV ID="downLoadContent"
> > STYLE="behavior:url(#default#download)" style="display: none;"></DIV>');
> > else if (is.ie) document.write('<IFRAME ID="downLoadContent"
> > STYLE="visibility: hidden; display: none;"
onLoad="alert(\'complete\');if
> > (DynAPI.setURL.current) DynAPI.setURL.current.onLoad(this)"></IFRAME>');
>
> > // Set ourselves up to start loading layers after the document loads.
> > lqLoadEvent=new EventListener();
> > lqLoadEvent.onafterload=function(){ DynAPI.setURL() }
>
> > DynAPI.document.addEventListener(lqLoadEvent)
>
> > DynLayer.prototype.onLoad=function(e) {
> >  var lyr
> >  if (is.ie)
>
> >   lyr=document.all[DynLayer.prototype.setURL.current].lyrobj
> >   lyr.elm.innerHTML=e
> >  } else if (is.dom) {
> >  // alert(loaded);
> >   lyr=DynLayer.setURL.current
> >   DOMShortcuts.setInnerHTML(lyr.elm,DOMShortcuts.getInnerHTML(e))
> >  } else if (is.ns4)
>
> >   lyr=DynLayer.prototype.setURL.current
> >   lyr.elm.onload=function(){}
> >   this.onload=function(){}
> >  }
> >  lyr.invokeEvent('load'); // invoke the event for others to catch.
> >  DynLayer.prototype.setURL.current=null;
> >  if (DynLayer.prototype.setURL.loadList.length>0) lyr.setURL()
> >  return true
> > }
>
> > DynLayer.prototype.setURL=function(url)
>
> >  var cLyr=this
> >  if (!url)
>
> >   if (DynAPI.setURL.loadList.length<=0) return
> >   var l=DynAPI.setURL.loadList
> >   url=l[l.length-1]
> >   l.length--
> >   cLyr=l[l.length-1]
> >   l.length--
> >  }
> >  if ((is.ns4 && !DynAPI.loaded) || DynAPI.setURL.current!=null)
>
> >   var l=DynAPI.setURL.loadList
> >   l[l.length]=cLyr
> >   l[l.length]=url
> >   if ((is.ns && !DynAPI.loaded) || DynAPI.setURL.current!=null) return
> >   else l.length-=2
> >  }
> >  DynAPI.setURL.current=cLyr.elm.id
> >  cLyr.invokeEvent('beforeload') // invoke beforeload event for others to
> > catch.
> >  if (is.ns4)
>
> >   DynAPI.setURL.current=cLyr
> >   if (cLyr.elm.parentLayer!=window)
>
> >    var l=cLyr.elm
> >    while (l.parentLayer!=window) l=l.parentLayer
> >    l.onload=cLyr.onLoad
> >   }
> >   cLyr.elm.onload=cLyr.onLoad
> >   cLyr.elm.src=url
> >  } else
> >  if (is.ie5) document.all.downLoadContent.startDownload(url,this.onLoad)
> >  else if (is.ie) {
> >   // Bug fix on IE4, IFRAME doesn't issue onLoad event.
> >   cLyr.timerID=setInterval("if
> > (document.all.downLoadContent.readyState=='complete')
> >
{clearInterval("+cLyr.toString()+".timerID);"+cLyr.toString()+".onLoad(docum
> > ent.frames['downLoadContent'].document.innerHTML)}",250);
> >   document.all.downLoadContent.src=url
> >  } else if (is.dom) {
> >    var e=document.getElementById('downLoadContent')
> >    if (!e) {
> >     e=document.createElement('DIV')
> >     e.setAttribute('id','downloadContent')
> >     document.body.addChild(e)
> >    }
> >    e.setAttribute("style","content: "+url)
> >    e.onload=this.onLoad
> >    DynAPI.setURL.current=cLyr
> > //            cLyr.timerID=setInterval("if
> > (document.all.downLoadContent.readyState=='complete')
> >
{clearInterval("+cLyr.toString()+".timerID);"+cLyr.toString()+".onLoad(docum
> > ent.frames['downLoadContent'].document.innerHTML)}",250);
> >    e.src=url
> >  }
> >  this.url=url
> > }
> > DynAPI.setURL=DynLayer.prototype.setURL
> > DynAPI.setURL.loadList=[];
> > DynAPI.setURL.current=null;
>
>
> > _______________________________________________
> > 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
>

Re: [Dynapi-Dev] Lets open CVS again

[Doug M. <do...@cr...>]

What exactly is CVS? if it involves file sharing then my employer will say
"not a chance buddy"
:-)
Doug
----- Original Message -----
From: "Robert Rainwater" <rra...@ya...>
To: "Dan Steinman" <dyn...@li...>
Sent: Friday, December 01, 2000 7:17 PM
Subject: Re: [Dynapi-Dev] Lets open CVS again


>
> If the group would like, I can give instructions on how to setup CVS
> in Windows.  Its really just a matter of downloading and setting up
> WinCVS and ssh.  I've never used cvs in linux, but if you do, you need
> to make sure you have ssh setup.
>
> There are also a few howto docs at sourceforge on how to use CVS for
> new users.
>
> --
> // Robert Rainwater
>
> On Saturday, December 02, 2000, 12:17:47 AM, Dan wrote:
>
> > I really think we should open up CVS again to do our development.  As it
is it's not easy for everyone to contribute code, and Robert is stuck with
the job of collecting everything and making an
> > official release.  Using CVS will make it easier on everyone.
>
> > We can help eachother to get it all set up on local computers, and make
sure we can all release files easily.  There's CVS clients for Windows
(CVSWin?) that should be pretty easy to use.
>
> > It'll also make it easy for non-developers to get the latest code
without searching around for everything.
>
> > This weekend I'll get a Makefile/build scheme working which will
compress all the js code, jar it for Netscape, and repackage it all.  And
this should be the starting point for the new dynapi CVS
> > tree.
>
> > Dan
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>
>
>

Re: [Dynapi-Dev] Is there a "loadHTML" for the latest release?

[Robert R. <rra...@ya...>]

The loadHTML is no longer a part of the DynAPI.  In the latest beta
(http://dynapi.sourceforge.net/beta/, you will find the loadPanel
which is probaly what you need.  Of course the loadPanel is still beta
(has some problems with IE4).

-- 
// Robert Rainwater

On Saturday, December 02, 2000, 2:00:09 PM, b0n3z wrote:

> I have been trying to find or port over the loadhtml.js for the latest
> release of dynapi-2000.11.05.zip , 06, or 07.

>  I desperatly need one - please.

>  Thanks,

>  Ken

>  Here was the older one that I have from somewhere:
> -----------------------------------------------------

> /*
>    Core DynAPI Distribution
>    loadURL extension
> */

> if (is.ie5) document.write('<DIV ID="downLoadContent"
> STYLE="behavior:url(#default#download)" style="display: none;"></DIV>');
> else if (is.ie) document.write('<IFRAME ID="downLoadContent"
> STYLE="visibility: hidden; display: none;" onLoad="alert(\'complete\');if
> (DynAPI.setURL.current) DynAPI.setURL.current.onLoad(this)"></IFRAME>');

> // Set ourselves up to start loading layers after the document loads.
> lqLoadEvent=new EventListener();
> lqLoadEvent.onafterload=function(){ DynAPI.setURL() }

> DynAPI.document.addEventListener(lqLoadEvent)

> DynLayer.prototype.onLoad=function(e) {
>  var lyr
>  if (is.ie)

>   lyr=document.all[DynLayer.prototype.setURL.current].lyrobj
>   lyr.elm.innerHTML=e
>  } else if (is.dom) {
>  // alert(loaded);
>   lyr=DynLayer.setURL.current
>   DOMShortcuts.setInnerHTML(lyr.elm,DOMShortcuts.getInnerHTML(e))
>  } else if (is.ns4)

>   lyr=DynLayer.prototype.setURL.current
>   lyr.elm.onload=function(){}
>   this.onload=function(){}
>  }
>  lyr.invokeEvent('load'); // invoke the event for others to catch.
>  DynLayer.prototype.setURL.current=null;
>  if (DynLayer.prototype.setURL.loadList.length>0) lyr.setURL()
>  return true
> }

> DynLayer.prototype.setURL=function(url)

>  var cLyr=this
>  if (!url)

>   if (DynAPI.setURL.loadList.length<=0) return
>   var l=DynAPI.setURL.loadList
>   url=l[l.length-1]
>   l.length--
>   cLyr=l[l.length-1]
>   l.length--
>  }
>  if ((is.ns4 && !DynAPI.loaded) || DynAPI.setURL.current!=null)

>   var l=DynAPI.setURL.loadList
>   l[l.length]=cLyr
>   l[l.length]=url
>   if ((is.ns && !DynAPI.loaded) || DynAPI.setURL.current!=null) return
>   else l.length-=2
>  }
>  DynAPI.setURL.current=cLyr.elm.id
>  cLyr.invokeEvent('beforeload') // invoke beforeload event for others to
> catch.
>  if (is.ns4)

>   DynAPI.setURL.current=cLyr
>   if (cLyr.elm.parentLayer!=window)

>    var l=cLyr.elm
>    while (l.parentLayer!=window) l=l.parentLayer
>    l.onload=cLyr.onLoad
>   }
>   cLyr.elm.onload=cLyr.onLoad
>   cLyr.elm.src=url
>  } else
>  if (is.ie5) document.all.downLoadContent.startDownload(url,this.onLoad)
>  else if (is.ie) {
>   // Bug fix on IE4, IFRAME doesn't issue onLoad event.
>   cLyr.timerID=setInterval("if
> (document.all.downLoadContent.readyState=='complete')
> {clearInterval("+cLyr.toString()+".timerID);"+cLyr.toString()+".onLoad(docum
> ent.frames['downLoadContent'].document.innerHTML)}",250);
>   document.all.downLoadContent.src=url
>  } else if (is.dom) {
>    var e=document.getElementById('downLoadContent')
>    if (!e) {
>     e=document.createElement('DIV')
>     e.setAttribute('id','downloadContent')
>     document.body.addChild(e)
>    }
>    e.setAttribute("style","content: "+url)
>    e.onload=this.onLoad
>    DynAPI.setURL.current=cLyr
> //            cLyr.timerID=setInterval("if
> (document.all.downLoadContent.readyState=='complete')
> {clearInterval("+cLyr.toString()+".timerID);"+cLyr.toString()+".onLoad(docum
> ent.frames['downLoadContent'].document.innerHTML)}",250);
>    e.src=url
>  }
>  this.url=url
> }
> DynAPI.setURL=DynLayer.prototype.setURL
> DynAPI.setURL.loadList=[];
> DynAPI.setURL.current=null;


> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

[Dynapi-Dev] Is there a "loadHTML" for the latest release?

[b0n3z <b0...@go...>]

I have been trying to find or port over the loadhtml.js for the latest
release of dynapi-2000.11.05.zip , 06, or 07.

 I desperatly need one - please.

 Thanks,

 Ken

 Here was the older one that I have from somewhere:
-----------------------------------------------------

/*
   Core DynAPI Distribution
   loadURL extension
*/

if (is.ie5) document.write('<DIV ID="downLoadContent"
STYLE="behavior:url(#default#download)" style="display: none;"></DIV>');
else if (is.ie) document.write('<IFRAME ID="downLoadContent"
STYLE="visibility: hidden; display: none;" onLoad="alert(\'complete\');if
(DynAPI.setURL.current) DynAPI.setURL.current.onLoad(this)"></IFRAME>');

// Set ourselves up to start loading layers after the document loads.
lqLoadEvent=new EventListener();
lqLoadEvent.onafterload=function(){ DynAPI.setURL() }

DynAPI.document.addEventListener(lqLoadEvent)

DynLayer.prototype.onLoad=function(e) {
 var lyr
 if (is.ie)

  lyr=document.all[DynLayer.prototype.setURL.current].lyrobj
  lyr.elm.innerHTML=e
 } else if (is.dom) {
 // alert(loaded);
  lyr=DynLayer.setURL.current
  DOMShortcuts.setInnerHTML(lyr.elm,DOMShortcuts.getInnerHTML(e))
 } else if (is.ns4)

  lyr=DynLayer.prototype.setURL.current
  lyr.elm.onload=function(){}
  this.onload=function(){}
 }
 lyr.invokeEvent('load'); // invoke the event for others to catch.
 DynLayer.prototype.setURL.current=null;
 if (DynLayer.prototype.setURL.loadList.length>0) lyr.setURL()
 return true
}

DynLayer.prototype.setURL=function(url)

 var cLyr=this
 if (!url)

  if (DynAPI.setURL.loadList.length<=0) return
  var l=DynAPI.setURL.loadList
  url=l[l.length-1]
  l.length--
  cLyr=l[l.length-1]
  l.length--
 }
 if ((is.ns4 && !DynAPI.loaded) || DynAPI.setURL.current!=null)

  var l=DynAPI.setURL.loadList
  l[l.length]=cLyr
  l[l.length]=url
  if ((is.ns && !DynAPI.loaded) || DynAPI.setURL.current!=null) return
  else l.length-=2
 }
 DynAPI.setURL.current=cLyr.elm.id
 cLyr.invokeEvent('beforeload') // invoke beforeload event for others to
catch.
 if (is.ns4)

  DynAPI.setURL.current=cLyr
  if (cLyr.elm.parentLayer!=window)

   var l=cLyr.elm
   while (l.parentLayer!=window) l=l.parentLayer
   l.onload=cLyr.onLoad
  }
  cLyr.elm.onload=cLyr.onLoad
  cLyr.elm.src=url
 } else
 if (is.ie5) document.all.downLoadContent.startDownload(url,this.onLoad)
 else if (is.ie) {
  // Bug fix on IE4, IFRAME doesn't issue onLoad event.
  cLyr.timerID=setInterval("if
(document.all.downLoadContent.readyState=='complete')
{clearInterval("+cLyr.toString()+".timerID);"+cLyr.toString()+".onLoad(docum
ent.frames['downLoadContent'].document.innerHTML)}",250);
  document.all.downLoadContent.src=url
 } else if (is.dom) {
   var e=document.getElementById('downLoadContent')
   if (!e) {
    e=document.createElement('DIV')
    e.setAttribute('id','downloadContent')
    document.body.addChild(e)
   }
   e.setAttribute("style","content: "+url)
   e.onload=this.onLoad
   DynAPI.setURL.current=cLyr
//            cLyr.timerID=setInterval("if
(document.all.downLoadContent.readyState=='complete')
{clearInterval("+cLyr.toString()+".timerID);"+cLyr.toString()+".onLoad(docum
ent.frames['downLoadContent'].document.innerHTML)}",250);
   e.src=url
 }
 this.url=url
}
DynAPI.setURL=DynLayer.prototype.setURL
DynAPI.setURL.loadList=[];
DynAPI.setURL.current=null;

Re[2]: [Dynapi-Dev] DynAPI.include() and Libraries

[Robert R. <rra...@ya...>]

The addLibrary is rarely used by the users. The only other place that
it would probaly ever be used is in widgets. Also, its not the size of
the string that matters. The only time the library array is used is
when you say dynapi.api.*. But if you left out the .js in the
addLibrary you would have to concatenate a .js on each string. This
isn't necessary.

The .js is not required in the include method, so I see no problem
here.  I'm not quite sure I see the need to add more to the methods
that will make include methods slower, just because you rarely even
use the addLibrary.  The addLibrary is mainly an internal method,
anyways.

-- 
// Robert Rainwater

On Thursday, November 02, 2000, 7:01:41 AM, Michael wrote:

> I've found that it is easier to read (and also looks more java-like) if
> your code pages don't need to have .js everywhere.

> Isn't it better to expect people to leave the .js off rather than treat
> it like and error and compensate for it?

> It also reduces the need to have it at the end of every library entry.
> As for speed, if it reduces the string sizes and treats the shorter
> annotation as the correct one, doesn't this make it faster.  It means
> that those of us who leave off the .js don't have to get the DynAPI to
> append the .js before it generates the <script> entry.  Again, the one
> line of code is faster than the two.
> --
> Michael Pemberton
> mp...@ph...
> ICQ: 12107010


> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

RE: [Dynapi-Dev] DynAPI.include() and Libraries

[Michael P. <mp...@ph...>]

I've found that it is easier to read (and also looks more java-like) if
your code pages don't need to have .js everywhere.

Isn't it better to expect people to leave the .js off rather than treat
it like and error and compensate for it?

It also reduces the need to have it at the end of every library entry.
As for speed, if it reduces the string sizes and treats the shorter
annotation as the correct one, doesn't this make it faster.  It means
that those of us who leave off the .js don't have to get the DynAPI to
append the .js before it generates the <script> entry.  Again, the one
line of code is faster than the two.
--
Michael Pemberton
mp...@ph...
ICQ: 12107010

[Dynapi-Dev] events

[Pascal B. <pa...@dy...>]

I've been playing with events, and I'm a bit out of the loop here.

I have this setup:

a dynlayer on a document.
an eventlistener that has the document as a target
the eventlistener is attached to the document.

When I click the layer, the event is triggered on the document.. this
shouldn't be correct should it?  I'm not sure if this behaviour has always
been this way, but it just doesn't seem right.

any thoughts?

Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net