Make WordPress Core

Opened 18 years ago

Closed 16 years ago

#3259 closed enhancement (wontfix)

Should compress javascripts to save space

Reported by: alexkingorg's profile alexkingorg Owned by: markjaquith's profile markjaquith
Milestone: Priority: normal
Severity: normal Version: 2.1
Component: General Keywords:
Focuses: Cc:

Description (last modified by foolswisdom)

Should compress javascripts to save space

Change History (18)

#1 @markjaquith
18 years ago

  • Owner changed from anonymous to markjaquith
  • Status changed from new to assigned

Paging Andy Skelton:

Would this make Prototype upgrades more difficult? Any objections?

#2 @andy
18 years ago

As long as the only changes from the original script are whitespace, I wouldn't worry about code maintenance issues here.

#3 @matt
18 years ago

We never make any local mods or fork our JS libraries outside of our TinyMCE plugins.

I know the Dojo Toolkit folks and Alex Russell have a really kickass JS compression thing based on Rhino, perhaps we should run Prototype, DBX, and others through that to cut down on load times?

Online tools:

Someone should test to see which works best and we'll use it.

#4 @masquerade
18 years ago

Another library I've been using lately gets great compression by running their downloads through this class, and hasn't had any errors as some other compressors have been known to have.

http://www.phpclasses.org/browse/package/3158.html

#5 @matt
17 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

Addressed in [4566].

#6 @foolswisdom
17 years ago

  • Summary changed from Prototype script, spaces to tabs to Should compress javascripts to save space

#7 @foolswisdom
17 years ago

#3414 custom image header cropper error "_163 has no properties" in prototype.compress.js

#8 follow-up: @alexkingorg
17 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

#9 follow-up: @alexkingorg
17 years ago

Also, I think the copyright info should be added back to the compressed versions.

#10 in reply to: ↑ 9 @shorty114
17 years ago

Replying to alexkingorg:

Also, I think the copyright info should be added back to the compressed versions.

Yes, if anything keep the header intact.

#11 @Nazgul
17 years ago

Because of the problems associated with this ticket, I suggest to push it out of scope for 2.1 and take a new look at it for the next release.

If we do push it out of scope I think we should take out prototype.compressed.js for now as well.

#12 in reply to: ↑ 8 @foolswisdom
17 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

Marking FIXED for 2.1 .

Replying to Nazgul:

Because of the problems associated with this ticket, I suggest to push it out of scope for 2.1 and take a new look at it for the next release.

That would upset me because this ticket has already resulted in changes. Better to have a new ticket for the next cycle of work.

If we do push it out of scope I think we should take out prototype.compressed.js for now as well.

prototype.compressed.js was already removed in [4592]

Replying to alexkingorg:

Also, I think the copyright info should be added back to the compressed versions.

I disagree. The original "source" version is in the same folder and the file naming is appropriate. Source is easy to locate in the distribution and on the net. I don't think authors will find this offensive.

Replying to alexkingorg:

This version gets it down to 25k:

Awesome! Something to explore for 2.2 . Will other libraries still be being considered?

#13 @foolswisdom
17 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

[4769] [4770] removed all the compression files. First removed quicktags.compressed.js because people have customized quicktags.js , and then all (it seems) because there are enough other big variables in this release.

#14 @foolswisdom
17 years ago

  • Milestone changed from 2.1 to 2.2

#15 @foolswisdom
17 years ago

  • Description modified (diff)

#16 @foolswisdom
17 years ago

  • Milestone changed from 2.2 to 2.4

#17 @pishmishy
16 years ago

  • Milestone changed from 2.5 to 2.6

Feature request so bumping to 2.6 for feature freeze.

#18 @azaozz
16 years ago

  • Milestone 2.9 deleted
  • Resolution set to wontfix
  • Status changed from reopened to closed

No traction since 2.1, also it seems it's better to capture all js files with Gears instead of compressing them.

Note: See TracTickets for help on using tickets.