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

Re: [Dynapi-Dev] Button/DynImage - I am fixing this

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

I am working on a simple auto resize for DynImage.  It was overly complex the way it was.  It's almost done as I type this email.

Dan

On Sat, Dec 09, 2000 at 05:41:46PM -0500, Robert Rainwater wrote:
> 
> I'm having major problems trying to get the Button widget to work with
> DynImage.  I tried adding a setSize call when the images are loaded to
> fix the problem.  But now in Netscape the images in the buttons
> disappear onload.  Also, it causes NS to crash after you reload
> sometimes.  Any help would be appreciated.
> 
> There was one problem that I think I fixed, is when you say new
> Image(w||0,h||0). If you initialize the image to width or height to 0
> in IE, then the when its finished loading it will stay 0, so I used an
> if statement to fix that so that you don't have to specify the size.
> 
> -- 
> // Robert Rainwater
> 
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

Re[4]: [Dynapi-Dev] compression?

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

Right now, we can't include any of the compressed files in the next
release, until they are fixed.  There seems to be a bug in jspack that
causes some spaces to be removed when they shouldn't (see my other
post).  I guess the next release will not include the compressed files
until that bug is fixed.  I'm sure there are some semicolon problems
too, although these can be easily fixed.

I think including all of the gzip and jar files it will be confusing
as well. I really like the jspack compression, but I think the gzip
and jar files can be confusing. Also, I think they shouldnt be
included in the release, because if somebody is smart enough to know
how to use them, then they will be smart enough to able to create them
themselves, especially with the makefile that is included.

-- 
// Robert Rainwater

On 12/9/2000, 2:46:16 PM EST, Pascal wrote about "[Dynapi-Dev] compression?":

> also, note that not everybody has access to how there server is setup (and
> what encoding/mime types it supports etc..)

> Same with using JAR and gzip, not every one has the freedom to use those
> file types (I personally have never seen it being used on websites)

> The other thing I wanted to mention is the fact that the current
> distribution contains alot of files, it might not be clear enough to which
> files someone should use.  Should the release version contain all these
> packed files aswell?  It might hold people back from using it when there are
> other, more simple looking, api's/libraries available.

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

>> -----Oorspronkelijk bericht-----
>> Van: dyn...@li...
>> [mailto:dyn...@li...]Namens Brandon Myers
>> Verzonden: zaterdag 9 december 2000 20:10
>> Aan: dyn...@li...
>> Onderwerp: Re: Re[2]: [Dynapi-Dev] compression?
>>
>>
>> Will netscape understand it as well?
>>
>> ----- Original Message -----
>> From: "Alexey Medvedev" <ma...@ca...>
>> To: "DynAPI Development List" <dyn...@li...>
>> Sent: Saturday, December 09, 2000 6:23 AM
>> Subject: Re: Re[2]: [Dynapi-Dev] compression?
>>
>>
>> > > One thing I don't understand are the JAR and gzip compressed files. It
>> > > seems there are very little cases where you could use them. Most users
>> >
>> > Why?
>> >
>> > > that the gzipped files even work in IE 5 (they don't seem to). Aren't
>> >
>> > If you will put them to Apache Web Server (and other imho).
>> >   Server will send header:
>> > Content-Encoding: gzip
>> > IE5 understands it.
>> >
>> > Malx
>> >
>> > _______________________________________________
>> > Dynapi-Dev mailing list
>> > Dyn...@li...
>> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>>
>> _______________________________________________
>> Dynapi-Dev mailing list
>> Dyn...@li...
>> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>>

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

[Dynapi-Dev] Button/DynImage

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

I'm having major problems trying to get the Button widget to work with
DynImage.  I tried adding a setSize call when the images are loaded to
fix the problem.  But now in Netscape the images in the buttons
disappear onload.  Also, it causes NS to crash after you reload
sometimes.  Any help would be appreciated.

There was one problem that I think I fixed, is when you say new
Image(w||0,h||0). If you initialize the image to width or height to 0
in IE, then the when its finished loading it will stay 0, so I used an
if statement to fix that so that you don't have to specify the size.

-- 
// Robert Rainwater

[Dynapi-Dev] PathAnim fixed

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

Updated in CVS, 2 small bugs in PathAnim were effecting Scrollbar and ViewPort.

In PathAnimation.line():

if (path[i*2-2] != x2 || path[i*2-1] != y2) {  // was &&, should be ||

And in run():

if (anim.frame>=anim.length/2+1) {  // needed a +1

Scrollbar, ViewPort, and ScrollPane all work fine now.

Dan

Re[2]: [Dynapi-Dev] Label text selection

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

> Just changing the cursor didn't turn off selection on my IE5/Win

No, but I did allow events to take place over the text, which was the
major problem with IE.


-- 
// Robert Rainwater

RE: Re[2]: [Dynapi-Dev] compression?

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

also, note that not everybody has access to how there server is setup (and
what encoding/mime types it supports etc..)

Same with using JAR and gzip, not every one has the freedom to use those
file types (I personally have never seen it being used on websites)

The other thing I wanted to mention is the fact that the current
distribution contains alot of files, it might not be clear enough to which
files someone should use.  Should the release version contain all these
packed files aswell?  It might hold people back from using it when there are
other, more simple looking, api's/libraries available.

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

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Brandon Myers
> Verzonden: zaterdag 9 december 2000 20:10
> Aan: dyn...@li...
> Onderwerp: Re: Re[2]: [Dynapi-Dev] compression?
>
>
> Will netscape understand it as well?
>
> ----- Original Message -----
> From: "Alexey Medvedev" <ma...@ca...>
> To: "DynAPI Development List" <dyn...@li...>
> Sent: Saturday, December 09, 2000 6:23 AM
> Subject: Re: Re[2]: [Dynapi-Dev] compression?
>
>
> > > One thing I don't understand are the JAR and gzip compressed files. It
> > > seems there are very little cases where you could use them. Most users
> >
> > Why?
> >
> > > that the gzipped files even work in IE 5 (they don't seem to). Aren't
> >
> > If you will put them to Apache Web Server (and other imho).
> >   Server will send header:
> > Content-Encoding: gzip
> > IE5 understands it.
> >
> > Malx
> >
> > _______________________________________________
> > 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: Re[2]: [Dynapi-Dev] compression?

[Brandon M. <bnd...@ho...>]

Will netscape understand it as well?

----- Original Message ----- 
From: "Alexey Medvedev" <ma...@ca...>
To: "DynAPI Development List" <dyn...@li...>
Sent: Saturday, December 09, 2000 6:23 AM
Subject: Re: Re[2]: [Dynapi-Dev] compression?


> > One thing I don't understand are the JAR and gzip compressed files. It
> > seems there are very little cases where you could use them. Most users
> 
> Why?
> 
> > that the gzipped files even work in IE 5 (they don't seem to). Aren't
> 
> If you will put them to Apache Web Server (and other imho).
>   Server will send header:
> Content-Encoding: gzip
> IE5 understands it.
> 
> Malx
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

Re: [Dynapi-Dev] compression?

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

When we release a "stable" version, it will already come with all the packed versions of the js files.  So even if you just want to use the individual files.  I'll fix any bugs that exist in jspack until it's rock solid, and can be used reliably.

Also for the jar/gzips, they are completely optional.  The include() method could be alterted so that it could seamlessly include those files, when you do this:

DynAPI.include(dynapi.api.*); // it'll include the .jar instead

Or something like that.  I'll play around with that once the jars are fully working.

Dan


On Fri, Dec 08, 2000 at 07:22:31PM +0100, Pascal Bestebroer wrote:
> As I said, I might be missing the advantage here, but having one short file
> would indeed make it easy to distribute things.. still I don't think jar and
> gzip are of any use if not all browser can handle them safely. I know you
> could use a combination of JAR for NS and gzip for IE5+ and a js file for
> ie4, but personally I don't see the usage of it ;)
> 
> maybe I should give it a closer look and, very maybe, I'll make a win32 app
> to do the jspacking because using that perl stuff is to linux for me :)
> 
> 
> 
> Pascal Bestebroer
> pa...@dy...
> http://www.dynamic-core.net
> 
> > -----Oorspronkelijk bericht-----
> > Van: dyn...@li...
> > [mailto:dyn...@li...]Namens Dan Steinman
> > Verzonden: vrijdag 8 december 2000 21:33
> > Aan: dyn...@li...
> > Onderwerp: Re: [Dynapi-Dev] compression?
> >
> >
> > Pascal, initially I wasn't so hot to trot with whitespace
> > compression either, but after playing around with it it's really
> > quite cool, and I'm glad I put in the time to create my little
> > jspack util.  If you check again, the compression ratio is closer
> > to about 30%, more or less depending on how many comments you put
> > in there.  All the /api/ files were "manually" compress.  I don't
> > particularly enjoy reading code that is like this:
> >
> > if(b)c=2
> > else if(a&&b||c&&d<=4)method()
> > else {method();return false}
> >
> > And with the system set up now, we won't have to.  You just write
> > your code, putting in all the comments and whitespace you want,
> > and (as long as the ;'s are correct) it will all be squished down
> > for you in a build release.
> >
> > Also, jspack compresses stuff that gzip/jar's can't do much with,
> > like the following:
> >
> > if (a) {
> >
> > }
> > else if (b || c) {
> >
> > }
> >
> > The spaces and line breaks have to be maintained.  But in a
> > jspacked version:
> >
> > if(a){}else if(b||c){}
> >
> > It's already taken care of.  After you jspack, and jar/gzip it,
> > you're up to over 80% compression (85% for dynapi2 currently).
> > Whereas gzip on it's own can only do about 60%.  Plus by
> > whitespace compression, each individual file can be compressed,
> > whereas there's no point in having an individual gzip/jar file
> > for each js file because you don't gain much in small files.
> >
> > Another thing that's kinda cool, imagine when you build a game,
> > or standalone app in JS.  When you want to release the app to the
> > public, you can build your own JS pack file with the code you
> > need all in there (GPL license allows u to do this if the program
> > you wrote is also GPL).  I'm rewriting my tetris game, so I'd
> > make a jspack for it with:
> >
> > jspack -o tetris-packed.js tetris.js ../dynapi/dynapi.js
> > ../dynapi/api/ ../dynapi/gui/image.js
> >
> > That produces a single js file with all the code I need squished
> > together.  This is an ideal way to publish js apps or games IMO
> > because you no longer need to include the entire dynapi with your
> > app (or copy select files along .
> >
> > Dan
> >
> >
> > On Fri, Dec 08, 2000 at 12:49:06PM +0100, Pascal Bestebroer wrote:
> > > Not to be raving on anybodys parade, but whitespace compressions isn't
> > > really worth it is it?  You only stripped about 4kb off the
> > complete api/
> > > folder (dynlayer,dyndocument,etc..) if you remove all comments and
> > > semi-colons from the un-"compressed" files, you will probably
> > end up with
> > > even less "compression".
> > >
> > > I know that compression on all widgets might give more
> > advantage, but then
> > > again when will you be actually using all widgets?
> > >
> > > I think the jar and gzip are great, but jar won't work in IE,
> > and I don't
> > > think gzip works in ie4 (and how about IE on Macs?)
> > >
> > > Am I missing some advantage in this?
> > >
> > >
> > >
> > > Pascal Bestebroer
> > > pb...@oi...
> > > http://www.oibv.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
> >
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

Re: Re[2]: [Dynapi-Dev] compression?

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

> One thing I don't understand are the JAR and gzip compressed files. It
> seems there are very little cases where you could use them. Most users

	Why?

> that the gzipped files even work in IE 5 (they don't seem to). Aren't

	If you will put them to Apache Web Server (and other imho).
  Server will send header:
	Content-Encoding: gzip
	IE5 understands it.

				Malx

RE: [Dynapi-Dev] Label text selection

[Simon D. M. <di...@bi...>]

> Why not just disable selection events all together. It was done in the
> dragEvent object way-back when.
> Simply put:
>     if (is.ie) // Prevents text selection when dragging.
>         document.onselectstart = function () { return false; };
> That stopped IE from selecting other text on the screen when a layer was
> being dragged.

So presumably you'd have to reverse the change onmouseout or onmouseup.

If you you use:

        if (is.ie) document.selection.clear();

you don't need to do that.

>The cancelBrowseEvent is not even needed in the label widget for it to
>work correctly.  The setting of the cursor (which is done too) seems
>to do excactly the same thing.  I removed the cancelBrowseEvent in IE
>5 and had no troubles with the examples.

Just changing the cursor didn't turn off selection on my IE5/Win

Dicon

[Dynapi-Dev] Bug in JSPACK

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

It appears jspack has a problem with else's.

If you look at the dynapi.js compressed file you will see that it
turns the "else alert..." in DynAPI.include into this:
elsealert

I haven't checked other places, but I'm sure they exist.  Anyway to
fix this?

-- 
// Robert Rainwater

Re: [Dynapi-Dev] Label text selection

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

Another problem witht the list/label widgets is the many calls to
setText.  In ListItem, the onmouseout and mousemouse over makes to
different calls to change the font (forecolor, textcolor).  Each one
of these calls, calls setText which sets the html.

Maybe we should pass a boolean to the font change functions, that
decides whether or not to call setText.

-- 
// Robert Rainwater

On 12/8/2000, 6:37:49 PM EST, Scott wrote about "[Dynapi-Dev] Label text selection":

> There's a small snag in Label.  In IE, when you use setSelectable to
> prevent text from being selected with the mouse, you're also cancelling
> the browser event.  This can also cancel events on the label itself. 
> For example, if you build a list item out of a label with rollover color
> change events, sometimes the label text will cancel the onmouseout
> event.  If you mouseover the list fast enough you may end up with
> several items stuck in the rollover position.  This could cause problems
> with other widgets that use Label.

> In light of this, I'm wondering if we should restore the optional
> addCover() method that uses a physical layer to cover text.  If you
> don't need it, just use setSelectable.

Re: [Dynapi-Dev] Label text selection

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

The cancelBrowseEvent is not even needed in the label widget for it to
work correctly.  The setting of the cursor (which is done too) seems
to do excactly the same thing.  I removed the cancelBrowseEvent in IE
5 and had no troubles with the examples.

-- 
// Robert Rainwater

On 12/8/2000, 6:37:49 PM EST, Scott wrote about "[Dynapi-Dev] Label text selection":

> There's a small snag in Label.  In IE, when you use setSelectable to
> prevent text from being selected with the mouse, you're also cancelling
> the browser event.  This can also cancel events on the label itself. 
> For example, if you build a list item out of a label with rollover color
> change events, sometimes the label text will cancel the onmouseout
> event.  If you mouseover the list fast enough you may end up with
> several items stuck in the rollover position.  This could cause problems
> with other widgets that use Label.

> In light of this, I'm wondering if we should restore the optional
> addCover() method that uses a physical layer to cover text.  If you
> don't need it, just use setSelectable.

Re: [Dynapi-Dev] Label text selection

[Brandon M. <bnd...@ho...>]

Why not just disable selection events all together. It was done in the
dragEvent object way-back when.
Simply put:
    if (is.ie) // Prevents text selection when dragging.
        document.onselectstart = function () { return false; };
That stopped IE from selecting other text on the screen when a layer was
being dragged.
easy enough to redirect the selectstart of the target object to either
click, or simply return false.

I haven't had time to test this, but it seems like a way to solve the
selection problem.

----- Original Message -----
From: "Scott Andrew LePera" <sc...@sc...>
To: <dyn...@li...>
Sent: Friday, December 08, 2000 6:37 PM
Subject: [Dynapi-Dev] Label text selection


> There's a small snag in Label.  In IE, when you use setSelectable to
> prevent text from being selected with the mouse, you're also cancelling
> the browser event.  This can also cancel events on the label itself.
> For example, if you build a list item out of a label with rollover color
> change events, sometimes the label text will cancel the onmouseout
> event.  If you mouseover the list fast enough you may end up with
> several items stuck in the rollover position.  This could cause problems
> with other widgets that use Label.
>
> In light of this, I'm wondering if we should restore the optional
> addCover() method that uses a physical layer to cover text.  If you
> don't need it, just use setSelectable.
>
> --
> scott andrew lepera
> -----------------------------------
> web stuff:     www.scottandrew.com
> music stuff:   www.walkingbirds.com
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

[Dynapi-Dev] Label text selection

[Scott A. L. <sc...@sc...>]

There's a small snag in Label.  In IE, when you use setSelectable to
prevent text from being selected with the mouse, you're also cancelling
the browser event.  This can also cancel events on the label itself. 
For example, if you build a list item out of a label with rollover color
change events, sometimes the label text will cancel the onmouseout
event.  If you mouseover the list fast enough you may end up with
several items stuck in the rollover position.  This could cause problems
with other widgets that use Label.

In light of this, I'm wondering if we should restore the optional
addCover() method that uses a physical layer to cover text.  If you
don't need it, just use setSelectable.

-- 
scott andrew lepera
-----------------------------------
web stuff:     www.scottandrew.com
music stuff:   www.walkingbirds.com

[Dynapi-Dev] Current Issues

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

Here are some of the current issues that I have seen:

- The Scrollbar widget does not work in NS.  It never appears.  I
believe this is due to the DynImage/Button widgets.  Thus scrollpane
is broken as well.  Oddly though, pushpanel seems to work

- The new list widget (in CVS) has some selection problems.  When you
select a list item, sometimes the wrong item is bolded.

All of these are based on the latest files in CVS, not the snapshot
(hasn't updated yet).

Please take a look at the issues, especially the scrollbar problem
because I am perplexed with that one.

-- 
// Robert Rainwater

RE: [Dynapi-Dev] RE: Dynapi-Dev digest, Vol 1 #71 - 16 msgs

[Nuno F. <nun...@wi...>]

<img> doesn't work in NS4 though. :(

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Alexey
Medvedev
Sent: sexta-feira, 8 de Dezembro de 2000 19:14
To: dyn...@li...
Subject: Re: [Dynapi-Dev] RE: Dynapi-Dev digest, Vol 1 #71 - 16 msgs



> <TABLE ID=whatever STYLE="position: absolute;visibility:
> Basically the <Table> tag has now all the properties of a Layer.

	It is not a strange thing.
  The layer is not a <div> !
	The layer is _any_ tag with style="position: absolute;..."
	(Or may be any block element)

	It could be <p>,<img>  ..etc.

				Malx

Re: [Dynapi-Dev] RE: Dynapi-Dev digest, Vol 1 #71 - 16 msgs

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

> <TABLE ID=whatever STYLE="position: absolute;visibility:
> Basically the <Table> tag has now all the properties of a Layer.

	It is not a strange thing.
  The layer is not a <div> !
	The layer is _any_ tag with style="position: absolute;..."
	(Or may be any block element)

	It could be <p>,<img>  ..etc.

				Malx

Re[2]: [Dynapi-Dev] compression?

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

There is a good article about gzip encoding:
http://www.webreference.com/internet/software/servers/http/compression/

Meaning: you should still reference the .js file - if the server can send
the .js.gz file (according to headers in the client request) it tries to do so.

(I left out the discussion about the JAR file which is a totally different
matter.)

/Lunna


At 2000-12-08 18:30 , you wrote:
>
>One thing I don't understand are the JAR and gzip compressed files. It
>seems there are very little cases where you could use them. Most users
>will see these files and not know what to do with them. I'm not sure
>that the gzipped files even work in IE 5 (they don't seem to). Aren't
>those files something that users could create themselves in the rare
>case that they would need them.
>
>-- 
>// Robert Rainwater

Re: [Dynapi-Dev] core api -- DynLayer Questions

[Brandon M. <bnd...@ho...>]

Not really.. if we use the remove/delete it actually removes the object from
the document structure. But is the object actually gone from the variable
"cloud"? maybe not. Even if all references are removed from them, the
garbage collector has to run and recover the freed space. From my readings,
the garbage collector doesn't run untill the page is unloaded, at least in
NS. At that point, all references are moot anyway.

I believe that is one of the reasons for the recycling of Netscape layers.
Even though the layer is removed, and all references are gone... the layer
still exists. Errors popup mysteriously.. Other than performing a "setHTML"
the layers persist.

----- Original Message -----
From: "Pascal Bestebroer" <pb...@oi...>
To: <dyn...@li...>
Sent: Friday, December 08, 2000 2:40 AM
Subject: RE: [Dynapi-Dev] core api -- DynLayer Questions


> maybe using the document.all  (real browser document.all array) or
> getElementById for DOM browsers .. if it returns a null value then the
> element is really gone, otherwise the browser still things it's there.
>
>
>
> Pascal Bestebroer
> pb...@oi...
> http://www.oibv.com
>
>
> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Scott Andrew
> LePera
> Verzonden: vrijdag 8 december 2000 8:35
> Aan: dyn...@li...
> Onderwerp: Re: [Dynapi-Dev] core api -- DynLayer Questions
>
>
>
> The major difference between the two is that remove methods simply
> remove the DynLayer but do not destroy it.  You can remove a DynLayer
> and then add it back, possibly to a new parent.  When a DynLayer is
> removed, it returns to the "unassigned" state (meaning it has no parent
> and no DynDocument).
>
> The delete methods remove the DynLayer and destroy all internal
> references to it.  When you delete a DynLayer, you cannot add it back.
> It's gone.  You have to create a new one.
>
> That said, I wish there was some way to ensure that all references to a
> DynLayer object were destroyed -- as long as even one reference remains,
> the DynLayer will still exist, and the resources it uses will not be
> released.  I don't think one exists; there's no way that I know of to
> automatically detect all references to an object and destroy them.  Or
> is there?
>
> --
> scott andrew lepera
> -----------------------------------
> web stuff:     www.scottandrew.com
> music stuff:   www.walkingbirds.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

RE: [Dynapi-Dev] compression?

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

As I said, I might be missing the advantage here, but having one short file
would indeed make it easy to distribute things.. still I don't think jar and
gzip are of any use if not all browser can handle them safely. I know you
could use a combination of JAR for NS and gzip for IE5+ and a js file for
ie4, but personally I don't see the usage of it ;)

maybe I should give it a closer look and, very maybe, I'll make a win32 app
to do the jspacking because using that perl stuff is to linux for me :)



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

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Dan Steinman
> Verzonden: vrijdag 8 december 2000 21:33
> Aan: dyn...@li...
> Onderwerp: Re: [Dynapi-Dev] compression?
>
>
> Pascal, initially I wasn't so hot to trot with whitespace
> compression either, but after playing around with it it's really
> quite cool, and I'm glad I put in the time to create my little
> jspack util.  If you check again, the compression ratio is closer
> to about 30%, more or less depending on how many comments you put
> in there.  All the /api/ files were "manually" compress.  I don't
> particularly enjoy reading code that is like this:
>
> if(b)c=2
> else if(a&&b||c&&d<=4)method()
> else {method();return false}
>
> And with the system set up now, we won't have to.  You just write
> your code, putting in all the comments and whitespace you want,
> and (as long as the ;'s are correct) it will all be squished down
> for you in a build release.
>
> Also, jspack compresses stuff that gzip/jar's can't do much with,
> like the following:
>
> if (a) {
>
> }
> else if (b || c) {
>
> }
>
> The spaces and line breaks have to be maintained.  But in a
> jspacked version:
>
> if(a){}else if(b||c){}
>
> It's already taken care of.  After you jspack, and jar/gzip it,
> you're up to over 80% compression (85% for dynapi2 currently).
> Whereas gzip on it's own can only do about 60%.  Plus by
> whitespace compression, each individual file can be compressed,
> whereas there's no point in having an individual gzip/jar file
> for each js file because you don't gain much in small files.
>
> Another thing that's kinda cool, imagine when you build a game,
> or standalone app in JS.  When you want to release the app to the
> public, you can build your own JS pack file with the code you
> need all in there (GPL license allows u to do this if the program
> you wrote is also GPL).  I'm rewriting my tetris game, so I'd
> make a jspack for it with:
>
> jspack -o tetris-packed.js tetris.js ../dynapi/dynapi.js
> ../dynapi/api/ ../dynapi/gui/image.js
>
> That produces a single js file with all the code I need squished
> together.  This is an ideal way to publish js apps or games IMO
> because you no longer need to include the entire dynapi with your
> app (or copy select files along .
>
> Dan
>
>
> On Fri, Dec 08, 2000 at 12:49:06PM +0100, Pascal Bestebroer wrote:
> > Not to be raving on anybodys parade, but whitespace compressions isn't
> > really worth it is it?  You only stripped about 4kb off the
> complete api/
> > folder (dynlayer,dyndocument,etc..) if you remove all comments and
> > semi-colons from the un-"compressed" files, you will probably
> end up with
> > even less "compression".
> >
> > I know that compression on all widgets might give more
> advantage, but then
> > again when will you be actually using all widgets?
> >
> > I think the jar and gzip are great, but jar won't work in IE,
> and I don't
> > think gzip works in ie4 (and how about IE on Macs?)
> >
> > Am I missing some advantage in this?
> >
> >
> >
> > Pascal Bestebroer
> > pb...@oi...
> > http://www.oibv.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
>

[Dynapi-Dev] RE: Dynapi-Dev digest, Vol 1 #71 - 16 msgs

[Nuno F. <nun...@wi...>]

Hi,

Can anybody explain how to use the
.jar files in Netscape, and the .gzip in Explorer?

Does it work on N6 and IE4?

best,
NunoF

Re[2]: [Dynapi-Dev] compression?

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

One thing I don't understand are the JAR and gzip compressed files. It
seems there are very little cases where you could use them. Most users
will see these files and not know what to do with them. I'm not sure
that the gzipped files even work in IE 5 (they don't seem to). Aren't
those files something that users could create themselves in the rare
case that they would need them.

-- 
// Robert Rainwater

On 12/8/2000, 3:33:12 PM EST, Dan wrote about "[Dynapi-Dev] compression?":

> Pascal, initially I wasn't so hot to trot with whitespace compression either, but after playing around with it it's really quite cool, and I'm glad I put in the time to create my little jspack
> util.  If you check again, the compression ratio is closer to about 30%, more or less depending on how many comments you put in there.  All the /api/ files were "manually" compress.  I don't
> particularly enjoy reading code that is like this:

> if(b)c=2
> else if(a&&b||c&&d<=4)method()
> else {method();return false}

> And with the system set up now, we won't have to.  You just write your code, putting in all the comments and whitespace you want, and (as long as the ;'s are correct) it will all be squished down
> for you in a build release.

> Also, jspack compresses stuff that gzip/jar's can't do much with, like the following:

> if (a) {

> }
> else if (b || c) {

> }

> The spaces and line breaks have to be maintained.  But in a jspacked version:

> if(a){}else if(b||c){}

> It's already taken care of.  After you jspack, and jar/gzip it, you're up to over 80% compression (85% for dynapi2 currently).  Whereas gzip on it's own can only do about 60%.  Plus by whitespace
> compression, each individual file can be compressed, whereas there's no point in having an individual gzip/jar file for each js file because you don't gain much in small files. 

> Another thing that's kinda cool, imagine when you build a game, or standalone app in JS.  When you want to release the app to the public, you can build your own JS pack file with the code you need
> all in there (GPL license allows u to do this if the program you wrote is also GPL).  I'm rewriting my tetris game, so I'd make a jspack for it with:

> jspack -o tetris-packed.js tetris.js ../dynapi/dynapi.js ../dynapi/api/ ../dynapi/gui/image.js

> That produces a single js file with all the code I need squished together.  This is an ideal way to publish js apps or games IMO because you no longer need to include the entire dynapi with your
> app (or copy select files along .

> Dan


> On Fri, Dec 08, 2000 at 12:49:06PM +0100, Pascal Bestebroer wrote:
>> Not to be raving on anybodys parade, but whitespace compressions isn't
>> really worth it is it?  You only stripped about 4kb off the complete api/
>> folder (dynlayer,dyndocument,etc..) if you remove all comments and
>> semi-colons from the un-"compressed" files, you will probably end up with
>> even less "compression".
>> 
>> I know that compression on all widgets might give more advantage, but then
>> again when will you be actually using all widgets?
>> 
>> I think the jar and gzip are great, but jar won't work in IE, and I don't
>> think gzip works in ie4 (and how about IE on Macs?)
>> 
>> Am I missing some advantage in this?
>> 
>> 
>> 
>> Pascal Bestebroer
>> pb...@oi...
>> http://www.oibv.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

Re: [Re: [Dynapi-Dev] compression?]

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

I know it would take a better programmer than I am to do this.
I had a program that would syntax parse a js file, and replace all variable
names with aliases. For example, 'DynDocument' might become 'aXn' etc.  Next,
it takes things like this:
 if (fooBar2){
  doOneLine()
  alert('hello')
 }else{
  doAnotherLine()
 }
 var x = 10
to:
if(xTa){bFg();alert('hello')}else bFh();var x=10

Note, that it puts in the semi's by itself, renames functions to shorter
names, gets rid of senseless braces for one liners, gets rid of all comments,
and allows you to add copyright comments as an include when you run it.
http://www.geocities.com/SiliconValley/Vista/5233/jmyth.htm

-bw

Dan Steinman <dy...@fu...> wrote:
> Pascal, initially I wasn't so hot to trot with whitespace compression
either, but after playing around with it it's really quite cool, and I'm glad
I put in the time to create my little jspack util.  If you check again, the
compression ratio is closer to about 30%, more or less depending on how many
comments you put in there.  All the /api/ files were "manually" compress.  I
don't particularly enjoy reading code that is like this:
> 
> if(b)c=2
> else if(a&&b||c&&d<=4)method()
> else {method();return false}
> 
> And with the system set up now, we won't have to.  You just write your code,
putting in all the comments and whitespace you want, and (as long as the ;'s
are correct) it will all be squished down for you in a build release.
> 
> Also, jspack compresses stuff that gzip/jar's can't do much with, like the
following:
> 
> if (a) {
> 
> }
> else if (b || c) {
> 
> }
> 
> The spaces and line breaks have to be maintained.  But in a jspacked
version:
> 
> if(a){}else if(b||c){}
> 
> It's already taken care of.  After you jspack, and jar/gzip it, you're up to
over 80% compression (85% for dynapi2 currently).  Whereas gzip on it's own
can only do about 60%.  Plus by whitespace compression, each individual file
can be compressed, whereas there's no point in having an individual gzip/jar
file for each js file because you don't gain much in small files. 
> 
> Another thing that's kinda cool, imagine when you build a game, or
standalone app in JS.  When you want to release the app to the public, you can
build your own JS pack file with the code you need all in there (GPL license
allows u to do this if the program you wrote is also GPL).  I'm rewriting my
tetris game, so I'd make a jspack for it with:
> 
> jspack -o tetris-packed.js tetris.js ../dynapi/dynapi.js ../dynapi/api/
../dynapi/gui/image.js
> 
> That produces a single js file with all the code I need squished together. 
This is an ideal way to publish js apps or games IMO because you no longer
need to include the entire dynapi with your app (or copy select files along .
> 
> Dan
> 
> 
> On Fri, Dec 08, 2000 at 12:49:06PM +0100, Pascal Bestebroer wrote:
> > Not to be raving on anybodys parade, but whitespace compressions isn't
> > really worth it is it?  You only stripped about 4kb off the complete api/
> > folder (dynlayer,dyndocument,etc..) if you remove all comments and
> > semi-colons from the un-"compressed" files, you will probably end up with
> > even less "compression".
> > 
> > I know that compression on all widgets might give more advantage, but
then
> > again when will you be actually using all widgets?
> > 
> > I think the jar and gzip are great, but jar won't work in IE, and I don't
> > think gzip works in ie4 (and how about IE on Macs?)
> > 
> > Am I missing some advantage in this?
> > 
> > 
> > 
> > Pascal Bestebroer
> > pb...@oi...
> > http://www.oibv.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


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

[Dynapi-Dev] RE: Dynapi-Dev digest, Vol 1 #71 - 16 msgs

[Nuno F. <nun...@wi...>]

This maybe totally useless but,
I discovered that the following line:

<TABLE ID=whatever STYLE="position: absolute;visibility:
hidden;layer-background-color: lightgrey; background-color:
lightgrey;z-index:2;" cellspacing=0 cellpadding=0>

Works both in IE and Netscape.

Basically the <Table> tag has now all the properties of a Layer.

probably useless but...


best,
NunoF