Closed
Bug 253448
Opened 22 years ago
Closed 21 years ago
Need a toolkit product
Categories
(bugzilla.mozilla.org :: Administration, task)
bugzilla.mozilla.org
Administration
Tracking
()
VERIFIED
FIXED
People
(Reporter: mvl, Assigned: asa)
References
()
Details
I have been filing bugs on toolkit lately, but there is no good component. a
toolkit component would really help.
| Reporter | ||
Comment 1•22 years ago
|
||
It should even be a product, i think.
Summary: Need a toolkit component → Need a toolkit product
| Assignee | ||
Comment 2•22 years ago
|
||
We have a several toolkit components in Browser. You'll have to be more specific.
| Reporter | ||
Comment 3•22 years ago
|
||
example bugs:
bug 250793, bug 250867, bug 250868, bug 251195, bug 253387, bug 253446
They mostly are about files that all toolkit apps want to use, but live in
/browser (and /mail, and ...)
Comment 4•22 years ago
|
||
Asa, he means the stuff in mozilla/toolkit, which really shouldn't go under
Browser/XP Apps etc.
Bugs that affect all "new-toolkit" apps don't have a real home, neither do bugs
that cover moving duplicated code from said apps to a shared location. This is
what we're trying to separate out and manage. Post-1.0 I want to focus on
continuing a lot of the work pch was doing and it doesn't really belong in the
Thunderbird or Firefox components.
bug 233461 is another example of something that will affect ALL new toolkit apps.
| Assignee | ||
Comment 5•22 years ago
|
||
We'll have components for toolkit bits (roughly equivalent to XPToolkit
compontents currently under the Browser product) in the new Bugzilla re-org. The
"new toolkit" is an extension of XPToolkit (which by the way, wasn't browser
specific and included all of our toolkit widgets for browser, mail, composer,
etc.) I don't see why we should replicate Toolkit components when they already
exist.
Comment 6•22 years ago
|
||
Asa, as far as I can see the "new toolkit" is not just an extension of the old
one but covers pretty much everything of the old toolkit with additional
features like customizable toolbars, extension manager, download manager, ...
Since this covers more than just Firefox or the browser (in the case of
XPToolkit) it was a bad decision to put this under Browser from the start. We
shouldn't make that mistake again. The toolkit is cross-platform and
cross-application and Bugzilla should reflect that.
YMMV of course.
| Assignee | ||
Comment 7•22 years ago
|
||
Simon, in the new world, toolkit will be part of the "Core" product that's
shared between all of our "app" products. In my opinion, it belongs with Layout,
Networking, XPCOM, etc, in this new Core component with all of the other shared
backend modules.
| Reporter | ||
Comment 8•22 years ago
|
||
In the plan at http://www.damowmow.com/playground/bugzilla-plan.txt I don't see
a toolkit product or component. Is that the latest plan?
For example, for password manager bugs, the only place is firefox:password
manager. The code lives in toolkit. But if you use that password manager outside
of firefox, that product doesn't make much sense.
Maybe we can have a Toolkit: Password manager component in the Core product?
(And components for other toolkit stuff, and a Toolkit: General for the rest)
| Assignee | ||
Comment 9•22 years ago
|
||
They're individual components under Core. See things like XUL Trees,
Autocomplete, and Filepicker. The old components under Browser were XPToolkit:
Trees, Filepicker, etc.
Comment 10•21 years ago
|
||
*** Bug 258509 has been marked as a duplicate of this bug. ***
Comment 11•21 years ago
|
||
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Updated•15 years ago
|
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in
before you can comment on or make changes to this bug.
Description
•