Closed
Bug 72142
Opened 25 years ago
Closed 25 years ago
Add XSLT component to installers
Categories
(Core :: XSLT, defect, P2)
Core
XSLT
Tracking
()
VERIFIED
FIXED
mozilla0.9.1
People
(Reporter: hjtoi-bugzilla, Assigned: peterv)
References
Details
(Whiteboard: [fixinhand])
Attachments
(1 file)
|
1.85 KB,
patch
|
Details | Diff | Splinter Review |
ASAP.
| Reporter | ||
Comment 1•25 years ago
|
||
Over to Peter.
See how I did this for XML Extras:
http://bugscape/show_bug.cgi?id=3734
(there is a patch in the comments - it is just a couple of lines per file):
mozilla/xpinstall/packager/packages-*
Assignee: kvisco → peterv
Keywords: mozilla0.9
| Reporter | ||
Comment 2•25 years ago
|
||
On second thought, XSLT is so big and not everyone will need it, I think it
should be configurable in the installer (a la Chatzilla). It should be on by
default, however, so that people who do a typical install will get it.
I know of only one browser that has support for XSLT, and that is IE, so that is
our model and competition here. Almost weekly I read a message from someone
complaining that Mozilla/Netscape 6 does not support XML, yet when I read the
message it is clear it is the XSLT support that is missing. But for the users it
feels like there is no XML support. MS has done a good job in convincing people
XML is useless with XSLT. We need to support it.
| Reporter | ||
Updated•25 years ago
|
Target Milestone: --- → mozilla0.9
| Reporter | ||
Comment 3•25 years ago
|
||
Sean, could you help Peter here?
Once Peterv has checked in patches to the all the appropriate
packages-[platform], I can help with creating the .xpi files for them.
Are you *sure* you want to have the XSLT files in their own .xpi files? Please
confirm before any work begins. Do we need input from marketing folks as well?
Comment 5•25 years ago
|
||
If it's big (> 500K?) we may well want it optional so the "browser only"
download size is kept smaller. Easy enough either way, this is more of a
marketing type call.
We can also do it differently for the Netscape vs. Mozilla release if there are
strong feelings in two different directions, but of course it would be easiest
if they are the same.
| Reporter | ||
Comment 6•25 years ago
|
||
I don't have optmized bits around, but the debug DLL size on Windows is 329kb +
1kb for the typelib.
Personally I wouldn't mind if it always gets installed.
But it would be nice if ALL of the noncritical parts would be configurable. They
are not now, so dunno how important this is.
Comment 7•25 years ago
|
||
A few comments:
code size may change. We didn't look at codesize yet, and there has been no
effort up to now to remove unused code.
libtransformiix.so is 1.169kB on sparc solaris, optimized&stripped. i386 code
is less, here the stuff from the win32 bins by peterv:
114688 transformiix.dll
397 transformiix.xpt
Axel
It looks like it will have to be a seperate .xpi given the indicated size.
Peverv, do you need help with patching the packages-[platform] files?
(added kmurray so someone in marketing is in the loop)
Comment 9•25 years ago
|
||
It would be great to know how pervasive the use of XSLT is today, and what the
trend is for tomorrow. Do many sites use this? It probably makes sense to have
this *off* by default in the typical config, but checked *on* in the custom
config. Is there a compelling reason that we should add download size on typical
for something like this? PLease provide examples of sites that currently employ
this, and what the long term user benefit will be.
Comment 10•25 years ago
|
||
My worry is that no end user would be able to understand what they are getting
if we offer them "XSLT" in some, but not all, installation packages.
Any progress on determining whether the code size can be reduced?
| Reporter | ||
Comment 11•25 years ago
|
||
As I said earlier, the "marketing" reason would be that without XSLT support
most users think there is no XML support in Mozilla/Netscape 6. The reason is
that IE does that, and Microsoft has convinced most people that they can only
use XML if they use XSLT transformation to convert it to HTML (which is totally
bogus, but we can't do much about that now).
So my take is: either have it installed always, or make it optional but have it
on by default (because of the above reasons).
Comment 12•25 years ago
|
||
trying to shut down 0.9 so we can open the tree for 0.9.1 development
Target Milestone: mozilla0.9 → mozilla0.9.1
| Assignee | ||
Comment 13•25 years ago
|
||
I am attaching a patch. I haven't put it in it's own jar, I think that this is
too technical to have as an install option. Zipped sizes of the binaries are
112k on Linux, 108k on Mac and 59k on Windows.
Status: NEW → ASSIGNED
Priority: -- → P2
| Assignee | ||
Comment 14•25 years ago
|
||
Comment 15•25 years ago
|
||
Assuming no chrome is needed, r=sgehani. If chrome is need, please attach the
jar.mn changes.
| Assignee | ||
Comment 16•25 years ago
|
||
No chrome.
Comment 17•25 years ago
|
||
r=nisheeth
Comment 18•25 years ago
|
||
sr=jst
| Assignee | ||
Comment 19•25 years ago
|
||
Partially checked in. Due to Linux bustage, we are not in the default build for
Linux. (See bug 72141)
| Reporter | ||
Updated•25 years ago
|
Whiteboard: [fixinhand]
Comment 20•25 years ago
|
||
I just checked in the patches to enable Transformiix on Linux. For now, OS/2
doesn't build Linux. Once bug 53518 is fixed, we'll enable Transformiix on OS/2
also.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•