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.
Just as with .odb files (issue 245429), when I have an .mwb file (MySQL WorkBench) in a project, there is no "Open in System" item in neither the "Projects" nor the "Files" view, to be able to open the file outside NetBeans with MySQL WorkBench. Right now, NetBeans forces me to open up MySQL WorkBench / Windows Explorer, browse all the way to the folder containing the file, and open it. Instead, it should always provide an "Open in System" option, which would simply call java.awt.Desktop.open(...) on the file. I really don't understand why NetBeans tries to claim files (such as anything that looks like a .zip file) when it doesn't allow you to do anything useful with them. PS: issue 245429 was closed without any motivation, so if you're going to close this one as WONTFIX either, at least take the time to explain why
Reassigned to DB for further evaluation. Matthias, is this something you would like to implement for ODB files? Meanwhile, why don't you Anthony use this plugin? http://plugins.netbeans.org/plugin/43217
(In reply to Jiri Kovalsky from comment #1) > Reassigned to DB for further evaluation. Matthias, is this something you > would like to implement for ODB files? I don't understand why you're reassigning to a specific component? This is an IDE-wide issue, and I just gave .odb/.mwb as 2 examples. I don't know how NetBeans implements "Open in System", but like I said: in theory it's as simple as calling java.awt.Desktop.open(...) on the file. Ideally, in addition to the "Open in System" context menu item, NetBeans should do the same when double-clicking the file while holding a modifier key (e.g. Shift + double-click would do "Open in System").
I reassigned it, because I thought it would help you in particular with opening your ODB files. The reason why your issue #245429 was closed is that we don't have anyone to implement this. If you are willing to do it, please sign OCA [1], attach the patch [2] to this issue and from next week it can be theoretically available in the development builds. Thanks! [1] http://wiki.netbeans.org/FaqHowDoIFileACA [2] https://netbeans.org/community/contribute/patches.html
(In reply to Jiri Kovalsky from comment #3) > I reassigned it, because I thought it would help you in particular with > opening your ODB files. The reason why your issue #245429 was closed is that > we don't have anyone to implement this. If you are willing to do it, please > sign OCA [1], attach the patch [2] to this issue and from next week it can > be theoretically available in the development builds. Thanks! > > [1] http://wiki.netbeans.org/FaqHowDoIFileACA > [2] https://netbeans.org/community/contribute/patches.html Thanks for your explanations (I think you mean MWB though, since ODB is not related to MySQL). And when I get around to learning the NetBeans Platform, I'll make sure to revisit this issue & try to create a patch for it ;-)
(In reply to terje7601 from comment #4) > I think you mean MWB though, since ODB is not related to MySQL) Oh, yes. My bad, sorry. > And when I get around to learning the NetBeans Platform, I'll make > sure to revisit this issue & try to create a patch for it ;-) That would be awesome! Thanks.
Created attachment 157031 [details] proposed patch I looked into this a bit and came to the conclusion, that this issue has its root in the java.j2seplatform module (Java SE Platforms and Libraries). The mentioned module offers a JAR DataLoader that offers a package view of the jar content. This is the cause for the missing menu entries. "Open in System" and "Open as" are provided for unknown file, but not for this now semi-known filetype. The JAR DataLoader is responsible, because it not only claims ownership over jar, war, ear, ?ar, but also everything with the signature of a ZIP file. All openoffice filetypes, openxml filetypes and also the mysql workbenach file match this signature and can only be determined by either doing deep-analysis of the content or guessing from the extension. While looking at this I also noticed, that the package view is not always appropriate for zip file, which primary represents a directory hierarchy, not java packages. So the attached patch does this: - Split Java-Archive Handling (?ar, apk, jad) and ZIP File handling (signature base detection + zip) - For "normal" ZIP show a folder hierarchy - Add "Open in System" and "Open as" to both filetypes
Following my reasoning in comment 6 (these two comments are split because the first comment done while attaching the patch), I change assignment to product "java" and product "platform". Please review the proposed patch. I subscribed to this bug - so comments will reach me.