Opened 13 years ago

Closed 11 years ago

#2165 closed enhancement (wontfix)

Making ShrinkSafe more useful

Reported by: ilia Owned by: alex
Priority: high Milestone: 1.2
Component: ShrinkSafe Version: 0.4.1
Keywords: Cc:
Blocked By: Blocking:

Description (last modified by Adam Peller)

Currently, Rhino shortens only truly private variables, making compression 100%-safe.

But most of time, there is a *bunch* of internal code that is never called from outside, e.g dojo DOM-manipulation functions, many internal processing methods, etc etc.

Let Rhino compress all that stuff, making only *few* methods for public calls. In my projects I can list such methods explicitly.

This will make JS shorter and programs run faster, because short names are easier for JavaScript? to interpret.

Change History (9)

comment:1 Changed 13 years ago by ilia

Description: modified (diff)

comment:2 Changed 13 years ago by tk

Owner: changed from slightlyoff to alex

comment:3 Changed 13 years ago by dylan

Milestone: 0.9
Version: 0.90.4.1

comment:4 Changed 12 years ago by Adam Peller

Keywords: shrinksafe added
Milestone: 0.9
Summary: Making custom Rhino more usefulMaking ShrinkSafe more useful

sounds a bit like the jslinker project... is there any intention to add this to shrinksafe? I'm taking the 0.9 milestone off.

comment:5 Changed 12 years ago by Adam Peller

Component: BuildToolsShrinkSafe
Keywords: shrinksafe removed

comment:6 Changed 12 years ago by alex

Milestone: 1.1
Status: newassigned

comment:7 Changed 12 years ago by dylan

Milestone: 1.11.2

moving shrinksafe bugs to 1.2

comment:8 Changed 11 years ago by Adam Peller

Description: modified (diff)

future? wontfix?

comment:9 Changed 11 years ago by James Burke

Resolution: wontfix
Status: assignedclosed

Marking as wontfix: if you want this behavior and the functions are really private, wrap them in a code in a (function(){})(); call. This should make it possible to shorten the variables.

Note: See TracTickets for help on using tickets.