Closed
Bug 559481
(consoleui)
Opened 15 years ago
Closed 13 years ago
[meta] DevTools Console front end implementation
Categories
(DevTools :: Console, defect)
DevTools
Console
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 704110
People
(Reporter: ddahl, Unassigned)
References
Details
Attachments
(1 file, 1 obsolete file)
(deleted),
image/png
|
Details |
We are shooting for a beta-quality release on Trunk in Q2. Need some face time with UX, also filing a UI "mockups" bug.
I have begun working on the UI, but only enough to make things work. I think it is sparse enough for now that any functionality is not going to be too hampered by a radical design:)
try builds will be posted each week.
Reporter | ||
Comment 1•15 years ago
|
||
(In reply to comment #0)
> We are shooting for a beta-quality release on Trunk in Q2. Need some face time
> with UX, also filing a UI "mockups" bug.
After meeting with UX and discussing all of this with Johnath, Robcee, et al. It looks like we are still going for alpha-quality push to trunk in Q2
Reporter | ||
Comment 2•15 years ago
|
||
A meeting with limi has set the direction for this implementation:
1. a developer menu item in the UI exposes a button that shows an "Arrow Panel" with the console log running.
2. a user can select "open console in new window", "open console in tab" and "dismiss".
also:
We need a "filter toolbar". with toggle buttons for each tab to toggle event listeners, network logging, css parser logging, etc... We should use text-based buttons. Not icons.
Comment 3•15 years ago
|
||
(In reply to comment #1)
> (In reply to comment #0)
> > We are shooting for a beta-quality release on Trunk in Q2. Need some face time
> > with UX, also filing a UI "mockups" bug.
> After meeting with UX and discussing all of this with Johnath, Robcee, et al.
> It looks like we are still going for alpha-quality push to trunk in Q2
To be clear, here - I think we should push alpha quality asap, but still work to a goal of beta quality in Q2. Land early, land often.
Reporter | ||
Comment 4•15 years ago
|
||
(In reply to comment #3)
> to be clear, here - I think we should push alpha quality asap, but still work
> to a goal of beta quality in Q2. Land early, land often.
indeed. just being conservative here - i know the review process will be long.
Reporter | ||
Updated•15 years ago
|
OS: Linux → All
Comment 5•14 years ago
|
||
do we really need arrow panels for this? Why not a regular panel with a titlebar as the Inspector is going to have? See bug 552982.
Reporter | ||
Comment 6•14 years ago
|
||
(In reply to comment #5)
> do we really need arrow panels for this? Why not a regular panel with a
> titlebar as the Inspector is going to have? See bug 552982.
No, we don't need arrow panels. This was some preliminary ideas, that's all. It would be better if the Inspector and Console matched look and feel.
Comment 7•14 years ago
|
||
Taking this. Proposed mockup to be submitted for UX review to be attached.
Assignee: ddahl → pwalton
Status: NEW → ASSIGNED
Comment 8•14 years ago
|
||
Updated•14 years ago
|
blocking2.0: --- → ?
Comment 9•14 years ago
|
||
Rationale for blocking request: The console UI that is currently shipping as part of the beta has not been reviewed by the UX team and was never intended to be anything more than a placeholder. As these tools are new parts of Firefox 4 and on the roadmap, they should have a proper UI designed and implemented.
Comment 10•14 years ago
|
||
Attaching a third mockup (the second was not posted to this bug, sorry). Certain parts of it are highly subject to change:
(1) All icons will quite possibly be replaced by text, subject to graphic design bandwidth and platform constraints.
(2) The style of the filter bar has not yet been fully hashed out. limi raised some concerns with the design in the mockup; it is likely that it will first be a series of checkboxes.
Attachment #457907 -
Attachment is obsolete: true
Reporter | ||
Comment 11•14 years ago
|
||
(In reply to comment #10)
> Created attachment 459274 [details]
> Mockup 3.
>
> Attaching a third mockup (the second was not posted to this bug, sorry).
> Certain parts of it are highly subject to change:
>
> (1) All icons will quite possibly be replaced by text, subject to graphic
> design bandwidth and platform constraints.
> (2) The style of the filter bar has not yet been fully hashed out. limi raised
> some concerns with the design in the mockup; it is likely that it will first be
> a series of checkboxes.
regardless, this mockup is great. The direction is looking up.
Reporter | ||
Comment 12•14 years ago
|
||
I removed the arrow panels bug as a blocker here until all of the real mockups and concepts come in for the console UI. I don't think it is worth it to block on it.
Updated•14 years ago
|
Comment 13•14 years ago
|
||
Are we going to add UI for controlling the DOM mutation event logging? see bug 575791
Comment 14•14 years ago
|
||
(In reply to comment #13)
> Are we going to add UI for controlling the DOM mutation event logging? see bug
> 575791
As far as I know the DOM Mutation events are gone.
Updated•14 years ago
|
Comment 15•14 years ago
|
||
This is basically a meta-bug. Please request blocking on the individual bugs where change will actually occur.
Also, should get a UX review on these proposed changes as soon as possible.
blocking2.0: ? → ---
Hardware: x86 → All
Summary: DevTools Console front end implementation → [meta] DevTools Console front end implementation
Updated•14 years ago
|
Whiteboard: [kd4b5]
Updated•14 years ago
|
Whiteboard: [kd4b5]
Updated•14 years ago
|
Alias: consoleui
Updated•14 years ago
|
Assignee: pwalton → nobody
Updated•13 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Updated•13 years ago
|
Assignee: shorlander → nobody
Component: Developer Tools → Developer Tools: Console
QA Contact: developer.tools → developer.tools.console
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•