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.

Bug 94388 - Move extbrowser module to the platform cluster
Summary: Move extbrowser module to the platform cluster
Status: RESOLVED WONTFIX
Alias: None
Product: ide
Classification: Unclassified
Component: Extbrowser (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-05 14:55 UTC by Tomasz Slota
Modified: 2013-06-25 16:38 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomasz Slota 2007-02-05 14:55:47 UTC 
Platform applications should be able to invoke a default web browser. As the Swing HTML browser was 
removed (issue 87648) the default (Desktop.browse() or OS-specific implementation on JVM 5) is provided 
by the extbrowser module.
Comment 1 Tomasz Slota 2007-02-05 15:00:07 UTC 
Perhabs we should only move the Desktop.browse()-based browser implementation to the Core project?
Comment 2 Tomasz Slota 2007-03-20 15:35:07 UTC 
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.
Comment 3 Jesse Glick 2007-03-21 01:41:13 UTC 
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.
Comment 4 Tomasz Slota 2007-03-21 16:04:27 UTC 
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
Comment 5 Jesse Glick 2007-03-21 18:06:11 UTC 
There are real platform apps which rely on the Swing browser? :-)
Comment 6 Peter Zavadsky 2008-09-02 19:03:51 UTC 
What is the conclusion? In which cluster the extbrowser module should reside? Or do you suggest to split it?
Comment 7 Jesse Glick 2008-09-10 04:30:09 UTC 
I would still suggest a split as in desc4 but I do not feel strongly about it.
Comment 8 Peter Zavadsky 2008-11-17 21:39:48 UTC 
OK, let's assume the split of the Desktop.browse to separate module (which would be included into platform cluster) as a
goal.
Comment 9 Jaroslav Tulach 2009-08-27 08:32:00 UTC 
Probably won'tfix since we have the embedded browser and that one shall be part of the platform.
Comment 10 Stanislav Aubrecht 2009-08-27 09:08:49 UTC 
embedded browser won't be part of 6.8 platform
it *may* appear in 6.8.next though
Comment 11 Petr Jiricka 2013-06-25 16:38:17 UTC 
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.