Closed
Bug 289483
Opened 20 years ago
Closed 20 years ago
use <deck> to permit extensions to tbird display model
Categories
(Thunderbird :: Mail Window Front End, defect)
Thunderbird
Mail Window Front End
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: shaver, Assigned: shaver)
Details
Attachments
(1 file, 2 obsolete files)
|
7.35 KB,
patch
|
mscott
:
review+
caillon
:
approval-aviary1.1a1+
|
Details | Diff | Splinter Review |
I've got a patch that does two main things: - use a <deck> to wrap the threadPane and accountCentral boxes - use the onselect notifications from that deck to drive the collapsing or showing of other UI elements, like the messagePane, searchBox, etc. I've tested it lightly, seems to do all the things I expect and none I don't. An extension which adds a new deck-child and causes it to be selected in the same way (showing when they are picked, hiding when they are not) works as I would expect as well, so I'm going to attach it here for review and feedback! I'd really, really like to get this into Tbird 1.1a, so that we have the ability to ship test builds of lightning against a more solid target than the nightly trunk, if possible.
| Assignee | ||
Comment 1•20 years ago
|
||
There are some other light cleanups in here, mainly removing the never-possible FakeAccount call, and renaming HideAccountCentral to ShowThreadPane, since that's really what the function does (and that it had to hide the accountCentralBox was just a quirk of the implementation).
| Assignee | ||
Updated•20 years ago
|
Attachment #179987 -
Flags: review?(mscott)
Comment 2•20 years ago
|
||
This isn't Mac-specific, is it? Have you removed all the calls to HideAccountCentral() and HideFakeAccountPage() ? If so, shouldn't you remove their definitions as well? I assume you'll remove the dump() statements...? Any idea why Bonsai Watch is showing a check-in for this bug?
| Assignee | ||
Comment 3•20 years ago
|
||
No, it's not Mac specific; that's just annoying Bugzilla behaviour that I can't suppress. Do you see other calls to HideAccountCentral in Thunderbird? I don't and I don't see a lingering definition. I never found _any_ definition of HideFakeAccountPage; I'd be happy to be pointed to one, though, if grep and lxr are both lying to me. I might remove the dump calls; they're pretty handy for diagnosing state-change issues, and I suspect there will be a follow-on bug or two -- do you have a reason to object to them? They are low frequency, though I could condense them to a single line without too much difficulty. Bonsai Watch was probably triggered by the fact that I referenced the bug number in a checkin in Lightning, but you might do better either a) reading Bonsai output for the bug number, or b) asking the Bonsai Watch people if you want to find out.
OS: MacOS X → All
Hardware: Macintosh → All
Comment 4•20 years ago
|
||
(In reply to comment #3) > Do you see other calls to HideAccountCentral in Thunderbird? I was only looking at the patch, not at the source. You're certainly more on top of it than I am. > do you have a reason to object to them? Not necessarily -- I now vaguely recall that dump only generates output if you're set up for it (right?); my only reason to object would be for output in the JS console for generic installs.
| Assignee | ||
Updated•20 years ago
|
Flags: blocking-aviary1.1?
Comment 5•20 years ago
|
||
I get JS errors in the console when I try to dynamically change the pane layout and then displaying a message: displayDeck changed! JavaScript error: chrome://messenger/content/mailWindow.js, line 547: deck.selec tedPanel has no properties also I noticed several dump statements in the patch which should be removed before checking in.
Comment 6•20 years ago
|
||
quick search doesn't seem to work for me either with this patch but maybe that's just because of the JS error reported above.
| Assignee | ||
Comment 7•20 years ago
|
||
Comment on attachment 179987 [details] [diff] [review] Make a deck (threadPane, accountCentral) the central pivot for UI mode changes I see that selectedPanel error now, and see how to fix it; I'll put a new patch up tomorrow. I mismodeled the way the pane switch mutates the box layout, apparently, because my diagrams don't match what DOMi shows me. Thanks.
Attachment #179987 -
Attachment is obsolete: true
| Assignee | ||
Updated•20 years ago
|
Attachment #179987 -
Flags: review?(mscott)
| Assignee | ||
Comment 8•20 years ago
|
||
event.target in the deck-switch observer wasn't always what I expected it to be, though I'm still not really sure why. Using document.getElementById() in there made a lot of things better. I sometimes get an error (reloading the db view is returning NS_ERROR_FAILURE) when switching to wide view with a message selected and quick-search active, but not always, and I'm not entirely convinced that this patch causes it. Quick search works a charm now, too.
Attachment #180504 -
Flags: review?(mscott)
| Assignee | ||
Comment 9•20 years ago
|
||
Comment on attachment 180504 [details] [diff] [review] Fixed view-switch and cleaned up dumps This breaks the standalone message window, I just discovered.
Attachment #180504 -
Attachment is obsolete: true
Attachment #180504 -
Flags: review?(mscott)
| Assignee | ||
Comment 10•20 years ago
|
||
I dunno why I added a ShowThreadPane call to messageWindow.js's delayedOnLoad, but it sure wasn't ever going to do anything useful. All better now, though.
Attachment #180796 -
Flags: review?(mscott)
Comment 11•20 years ago
|
||
Comment on attachment 180796 [details] [diff] [review] Fixed messageWindow.xul looks good Mike, although I haven't had a chance to test the new version yet. Thanks for the good stuff.
Attachment #180796 -
Flags: review?(mscott) → review+
Comment 12•20 years ago
|
||
Comment on attachment 180796 [details] [diff] [review] Fixed messageWindow.xul a=caillon
Attachment #180796 -
Flags: approval-aviary1.1a+
| Assignee | ||
Comment 13•20 years ago
|
||
FIXED on trunk, thanks for reviews!
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Flags: blocking-aviary1.1?
You need to log in
before you can comment on or make changes to this bug.
Description
•