This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Move extbrowser module to the platform cluster | ||
---|---|---|---|
Product: | ide | Reporter: | Tomasz Slota <tslota> |
Component: | Extbrowser | Assignee: | issues@ide <issues> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | jglick, jtulach, pjiricka, rkubacki, saubrecht |
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Tomasz Slota
2007-02-05 14:55:47 UTC
Perhabs we should only move the Desktop.browse()-based browser implementation to the Core project? The original reason for creating this issue is no longer valid. Default web browser is still available for the NB platform applications. Moving entire extbrowser to the platform cluster is not a good idea due to its size, amount of hacks and native calls. etc. IMO the Desktop.browse JDK 6 implementation ought to be in platform, as this is just basic functionality for an app. The rest (DLL hacks, configurable executable paths on Unix, etc.) can stay in the ide cluster. I guess P2 is an overestimate. The Swing browser may remain available but it is nearly useless in practice. I've heard opinion that some platform apps rely on the fact that calling a URLDisplayer will bring up a tabbed browser and that they could use Desktop.browse() directly if needed There are real platform apps which rely on the Swing browser? :-) What is the conclusion? In which cluster the extbrowser module should reside? Or do you suggest to split it? I would still suggest a split as in desc4 but I do not feel strongly about it. OK, let's assume the split of the Desktop.browse to separate module (which would be included into platform cluster) as a goal. Probably won'tfix since we have the embedded browser and that one shall be part of the platform. embedded browser won't be part of 6.8 platform it *may* appear in 6.8.next though This does not sound like a DEFECT to me - the clear solution is to just include the extbrowser module in the platform app. Tomasz is right that there is native code, so it does not feel right to put it into platform cluster. Also now we REALLY have the embedded browser - resolving as WONTFIX. If people feel strongly about putting it into platform, please reopen as ENHANCEMENT with justification - thanks. |