[patch] RFC: Netx plugins

[Francis Kung]

>> I'm not opposed; I think the easiest way to do this would be to treat 
>> netx (without NetxPanel and PluginBridge) as a binary plug, compile it 
>> all during the build-plugs stage, and patch the OpenJDK make files to 
>> import them during the OpenJDK build.  If we do this, it could be a 
>> good opportunity to clean up the netx package names too, so they 
>> follow "proper" conventions =)
> I think this is a good idea -- I'll probably try to get this working 
> soon. What do you exactly mean by "proper" conventions? :)

Ahh, simply that packages should be a reverse domain name to avoid 
collisions (ie the original Netx should have been net.sourceforge.jnlp.*, 
rather than simply netx.*).

Sun hasn't quite followed these, with their sun.* package (and Classpath 
following with a top-level gnu.classpath.* package), and there's plenty 
of lively discussion around that, but personally I'm all for following 
convention =)  gnu.classpath.icedtea.netx might be an appropriate place?

>> Another possibility (which I don't have time to experiment with soon, 
>> unfortunately) would be to have NetxPanel extend AppletPanel, instead 
>> of AppletViewerPanel.  From a quick glance, that might eliminate 
>> (some? all?) API changes at the cost of some code duplication...
> I'll try to look into this eventually.

Thanks.  I'm not completely sure this will work: it may reduce but not 
eliminate API changes, in which case it doesn't help us much... I 
wouldn't spend too much time on it if it starts looking like a dead end.

Cheers,
Francis