Ticket #2165 (closed enhancement: wontfix)

Opened 2 years ago

Last modified 4 months ago

Making ShrinkSafe more useful

Reported by: ilia Owned by: alex
Priority: normal Milestone: 1.2
Component: ShrinkSafe Version: 0.4.1
Severity: normal Keywords:
Cc:

Description (last modified by peller) (diff)

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

Changed 2 years ago by ilia

  • description modified (diff)

Changed 23 months ago by tk

  • owner changed from slightlyoff to alex

Changed 22 months ago by dylan

  • version changed from 0.9 to 0.4.1
  • milestone set to 0.9

Changed 16 months ago by peller

  • keywords shrinksafe added
  • summary changed from Making custom Rhino more useful to Making ShrinkSafe more useful
  • milestone deleted

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

Changed 14 months ago by peller

  • keywords shrinksafe removed
  • component changed from BuildTools to ShrinkSafe

Changed 13 months ago by alex

  • status changed from new to assigned
  • milestone set to 1.1

Changed 9 months ago by dylan

  • milestone changed from 1.1 to 1.2

moving shrinksafe bugs to 1.2

Changed 4 months ago by peller

  • description modified (diff)

future? wontfix?

Changed 4 months ago by jburke

  • status changed from assigned to closed
  • resolution set to wontfix

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.