Closed
Bug 150800
Opened 22 years ago
Closed 16 years ago
Enable splash screen on Linux
Categories
(SeaMonkey :: General, enhancement)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sly, Unassigned)
References
Details
(Keywords: platform-parity)
Attachments
(1 file, 1 obsolete file)
574 bytes,
patch
|
Details | Diff | Splinter Review |
I think the splash screen should be enabled on Linux.
Comment 1•22 years ago
|
||
Build ID ? Do you use a mozilla.org build ? We have a splash screen on linux (bug 27446)
This patch adds "-splash" to the command line if the option isn't already there. The splash screen appears only when there isn't already a running instance. Is a Good Thing to enable the splash screen? Maybe there should be a way to disable it?
Matti, I know about the "-splash" option. I'm using 1.0.0 on Red Hat 7.2, and the option isn't enabled by default. I could type "mozilla -splash" to get the splash screen, but then it would cause problems if there's already a running instance. The profile selector would come up. So I can't just make an icon that invokes "mozilla -splash". The patch I proposed always tacks on the "-splash" option. Some people may not like this. If that's the case, I can change it so that the default is no splash. Additionally, it would also strip off the "-splash" option if there's already a running instance.
Mozilla ignores other command line arguments when -splash is present. The new patch adds the -splash option only when there are no other arguments. And only when there are no running instance. There isn't much to look at. It's just a one-liner.
Attachment #87177 -
Attachment is obsolete: true
Attachment #90108 -
Attachment description: Add -splash option only when script is wrong without arguments → Add -splash option only when there are no other arguments
Comment 6•22 years ago
|
||
I agree that the splash screen should be on by default, but I'm not sure this is the best way to do it. Looks like a good workaround though. Is there a -nosplash option? See bug 152464.
Comment 7•22 years ago
|
||
bah! go away with the splash!
I'm not so sure my patch is the best way to do it, but the splash screen serves a purpose. It lets you know that a new browser session is starting, and that the previous session cookies have been invalidated. That's very useful when you have many virtual desktops. You never know when there's a hidden Mozilla window somewhere. (Obviously, there are other ways around this, e.g. ps(1) or the GNOME tasklist. I just think a splash screen is the simplest way.) Another argument is that it's on MS Windows. Why not Linux?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 9•22 years ago
|
||
IMO this should be done in the binary itself. And not only if there's no options, there are several options that has no conflict at all with the splash screen.
Keywords: pp
Hardware: PC → DEC
Comment 10•22 years ago
|
||
I guess it's a matter of simply find out which options conflict with the splash screen and edit here: http://lxr.mozilla.org/seamonkey/source/xpfe/bootstrap/nsAppRunner.cpp#1732
Hardware: DEC → All
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 11•18 years ago
|
||
Andrew, wdy think?
Assignee: blizzard → general
QA Contact: imajes-qa → general
Comment 12•16 years ago
|
||
WONTFIX as we don't support splash screens on any platform on trunk.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•