Closed Bug 8163 Opened 26 years ago Closed 25 years ago

EXPORT - interface methods on "services" - appcores

Categories

(SeaMonkey :: UI Design, defect, P1)

defect

Tracking

(Not tracked)

CLOSED FIXED

People

(Reporter: chofmann, Assigned: law)

References

Details

(Whiteboard: [HELP WANTED])

We need all of these to become interface methods on "services" (which are singleton components called via interfaces that startup at the beginning of the app's life and shut down at the end). Yes, we need to find owners -- most of these are easy. appcores might go to don for a start. appcores 21 14 000017AD NS_InitBaseAppCoreClass 22 15 0000104B NS_InitBrowserAppCoreClass 23 16 00002063 NS_InitCookieCoreClass 24 17 0000182A NS_InitDOMPropsCoreClass 25 18 000012AD NS_InitEditorAppCoreClass 26 19 000304F0 NS_InitEventClass 27 1A 0000141F NS_InitPrefsCoreClass 28 1B 00002171 NS_InitProfileCoreClass 29 1C 00001460 NS_InitRDFCoreClass 30 1D 00001555 NS_InitSignonCoreClass 31 1E 000010B9 NS_InitToolkitCoreClass 32 1F 00001AFF NS_InitWalletCoreClass 33 20 0000193D NS_NewScriptAppCoresManager 34 21 000021A3 NS_NewScriptBaseAppCore 35 22 00001C30 NS_NewScriptBrowserAppCore 36 23 00001AA5 NS_NewScriptCookieCore 37 24 00001172 NS_NewScriptDOMPropsCore 38 25 00001D66 NS_NewScriptEditorAppCore 39 26 000306C0 NS_NewScriptEvent 40 27 0002FCC0 NS_NewScriptEventListener 41 28 00001384 NS_NewScriptPrefsCore 42 29 00001857 NS_NewScriptProfileCore 43 2A 00001D89 NS_NewScriptRDFCore 44 2B 000018D9 NS_NewScriptSignonCore 45 2C 00001C4E NS_NewScriptToolbarCore 46 2D 00001C6C NS_NewScriptToolkitCore 47 2E 000018B1 NS_NewScriptWalletCore
OS: Windows 95 → All
Priority: P3 → P1
Hardware: PC → All
Target Milestone: M8
Let me talk to Bill and find out what he thinks is the right thing to do here and to whom we should assign the other tasks. Stay tuned ...
Assignee: don → law
Target Milestone: M8 → M9
Bill, what should we do here? How hard is this?
Status: NEW → ASSIGNED
I am not sure where we stand on enabling these things to be changed as suggested. Some issues will go away as we wean ourselves from old idlc interfaces to xpidl ones. I'm accepting this but I'm not promising a solution till the issue is finally resolved.
Target Milestone: M9 → M10
I'm still unclear on this issue. Will put off till M10 (eventually, the bug will evaporate or I'll get clued in on what we're supposed to do, exactly).
Target Milestone: M11 → M5
Moving this stupid bug out of my hair.
Target Milestone: M5 → M15
Whiteboard: [HELP WANTED]
QA Contact: beppe → tever
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Since nobody has explained exactly what the bug *is*, it's as likely as not that it is already fixed.
This bug to eliminate static linking with appcores -- consequently these should become interface methods, or factory constructors. Brendan: How important is this still?
app cores are almost all gone (see bug #14999) so I guess that means this bug doesn't call for any additional work?
Blocks: 16950
old development issues - closing
Status: RESOLVED → CLOSED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.