Closed Bug 44249 Opened 24 years ago Closed 22 years ago

rename pipnss & pippki to more understandable names

Categories

(Core Graveyard :: Security: UI, enhancement, P3)

1.0 Branch
PowerPC
Mac System 8.5
enhancement

Tracking

(Not tracked)

VERIFIED WONTFIX
Future

People

(Reporter: sfraser_bugs, Assigned: ddrinan0264)

References

Details

(Keywords: intl)

Having a directory at the top level (i.e. in the application folder) called 'UI', 
contining PSM user-interface files, is not good for the user-experience. This 
folder should be moved into a subfolder, either in chrome/, or Essential Files 
(on Mac). Do *not* put it in res/; res/ is going away.
reassign to crypto.
Assignee: mstoltz → ddrinan
Component: Security: General → Security: Crypto
QA Contact: czhang → junruh
Blocks: 48444
Note to self: these files are loaded in mozilla/security/psm/lib/nlslayer/
nlslayer.cpp
For these properties files to be localizable, and change when the user chooses a 
different UI language, the files should be in chrome/locales, methinks. So this 
is a localization bug.
Unless PSM does not use XUL, all XUL files should live in chrome/packages, 
and all locale-sensitive files (*.dtd & *properties) in chrome/locales/.
Setting target release to future.
Target Milestone: --- → Future
This appears to be fixed. There is now a psmdata folder with subfolders UI and 
Doc.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
This bug calls for moving PSM's UI to under chrome/ so we can localize them and
switch them on the fly.

Moving them to psmdata/UI does not fulfill the request. I am reopening the bug
and change summary accordingly.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: PSM UI files should not live in a directory called 'UI' at the top level → PSM UI files should live in chrome\[providerType]
nsbeta1
Keywords: nsbeta1
Keywords: intl
So now PSM2 has "pipnss" and "pippki" jar files in chrome. yipee.

However, I cannot help thinking that these names are meaningless to anyone but 
those working on the code. Please oh please try to come up with user-meaningful 
names for files that the user will see on their system, and bear in mind that on 
some platforms, users *do* go looking around their filesystems, and will get 
worried/confused about weirdly-named files ("Do I have a virus?").
Component: Security: Crypto → Client Library
Product: Browser → PSM
Target Milestone: Future → ---
Version: other → 2.0
Changing summary to reflect the new issue.

Suggestions for better names would be appropriate.  I would suggest 
"cryptonet" and "cryptoui".

Summary: PSM UI files should live in chrome\[providerType] → rename pipnss & pippki to more understandable names
Better, but InterCaps makes them more readable: CryptoNet, CryptoUI. Can we think 
of something better than CryptoNet?
Target Milestone: --- → 2.0
->future
Target Milestone: 2.0 → Future
Mass assigning QA to ckritzer.
QA Contact: junruh → ckritzer
QA Contact: ckritzer → junruh
Blocks: 104166
How important is this renaming? Aren't the files in a private folder of the
Mozilla installation?
Severity: normal → enhancement
Less so now that, on Mac OS X, the app is packaged as a bundle. Still, some
users like to poke around in there, and it will help them to have readable
names. Probably not worth fixing now, but next time you create any file that
goes on disk in the installation, choose a name that makes sense to *users*, not
to *developers*.
Marking wontfix.
Status: REOPENED → RESOLVED
Closed: 24 years ago22 years ago
Resolution: --- → WONTFIX
Verified.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm2.0 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.