Add splashscreen support to build system, comm-central part(s)

RESOLVED WONTFIX

Status

SeaMonkey
Build Config
--
enhancement
RESOLVED WONTFIX
9 years ago
5 years ago

People

(Reporter: Philip Chee, Unassigned)

Tracking

Trunk
x86
Windows XP
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
+++ This bug was initially created as a clone of Bug #504750 +++

[quote]
Bug 481494 added optional support for splash screens on slow devices, but didn't integrate with the build system for shipping the bitmap used.

Bug 504750 adds support for a splash.bmp in the build system that's used when a splashscreen is enabled in Firefox Mobile. Bug 502526 will update the splash screens with polished artwork, this patch just includes the Firefox-branded splash vlad made (attached in Bug 502526), and a couple placeholders for the unbranded and nightly branding.
[/quote]
(Reporter)

Updated

9 years ago
Blocks: 467530
Depends on: 481494
(Reporter)

Updated

9 years ago
Blocks: 329742
(Reporter)

Comment 1

8 years ago
From Bug 503469: package splash.bmp on --enable-splashscreen
http://hg.mozilla.org/mozilla-central/rev/167d89514f81
Toolkit and Firefox pushes were to 1.9.2+.

Also, it seems this feature may currently be coded for WinCE only...
Depends on: 503469
Summary: [Port Bug 504750] Add splashscreen support to build system → Add splashscreen support to build system, SeaMonkey part
Whiteboard: [Needs to branch to m-1.9.2+ first]
Target Milestone: --- → Future
Flags: wanted-seamonkey2.1?
Summary: Add splashscreen support to build system, SeaMonkey part → Add splashscreen support to build system, comm-central part(s)
Whiteboard: [Needs to branch to m-1.9.2+ first]
Target Milestone: Future → ---

Comment 3

8 years ago
It's not clear if this is something we want at all, and it's surely not of enough priority to track on any radar, so canceling the request.
Flags: wanted-seamonkey2.1?
I'm moving this bug to SeaMonkey, for the following reasons:

- Bug 481494 doesn't need any work copying to the comm-central build system for it to be used; comm-central's configure will pass the --enable-splashscreen, or alternately adding the appropriate variable in suite/confvars.sh will do what's necessary from a core code perspective.

- Bug 504750 & co appear to be app-specific build config changes

- Thunderbird is unlikely to want this unless there's a reason comes out that a splash screen is really required, which I don't think so especially as Firefox hasn't come up with one yet.
Component: Build Config → Build Config
Product: MailNews Core → SeaMonkey
QA Contact: build-config → build-config
Just for reference, starting point:
http://hg.mozilla.org/mozilla-central/log?rev=splash
->
http://hg.mozilla.org/mozilla-central/rev/31fd342897c7
http://hg.mozilla.org/mozilla-central/rev/6004e947157b
http://hg.mozilla.org/mozilla-central/rev/167d89514f81
http://hg.mozilla.org/mozilla-central/rev/c4678bf7b3fb
Depends on: 653333
(Reporter)

Comment 6

7 years ago
Probably WONTFIX since splash screen support was removed from mozilla-central with the removal of WinCE support.
For reference: The legacy WinCE splashscreen code was removed in bug 653333, so any approach here (if this is still desired) will need to take that into account.

Or as Philip said, perhaps just WONTFIX.
(Reporter)

Updated

5 years ago
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
(Reporter)

Updated

5 years ago
No longer blocks: 467530
You need to log in before you can comment on or make changes to this bug.